Temp Variance

[IMBoring25]

Some of the other firmwares have provisions to boost the PID output as setpoint goes up. That seems to be what you really need, but you can try raising P some until 255 reaches setpoint. If the value that takes makes too much of a mess of things at 220, you might have to change the value as you change setpoints.

The interesting chart on the bed will be when you have one of the temperature excursions. It's not working too hard to maintain 60 and I wonder if the minimum PID drive might have something to do with it, like if something is happening that ~30% is still too much and it has to get out of the PID region before it will shut off completely.

[morgandc]

Well, I changed the Heat Manager for both the bed and nozzle to 0. Also described as Bang Bang method in the following link.
https://github.com/repetier/Repetier-Fi ... re-control

The nozzle actually reaches temp now, just cycles above and below with the average being a bit below. I guess it is time to look at PID settings...

The first graph is 255c/60c, the 2nd 260c/60c.

[morgandc]

For reference:

[morgandc]

What stumps me, is why am I having this issue? I have never printed ABS, but it looks like ABS and PLA have lower extrusion temps, but I have to believe that other people are printing PETG on the Rostock Max v3? What could be different about my setup, newer firmware setting than earlier v3's? I can't think of anything else based on the symptoms I can't imagine it being a hardware issue.

[morgandc]

So, the last thing left to do is adjust the PID settings. I discovered autotune, ran that and updated my configuration.h to reflect the changes. (I say this with confidence....meanwhile I was standing over the power button to shut everything off if the temp when too high during autotune or during the maiden run of the new values). The bed issue didn't rear it's head up for the last couple of hours, I haven't decided whether to tune it or not.

Now that the temp is holding within 1.5 degrees now, in the morning I get to do some more test prints with PETG....the same way I thought I was going to do today

M303 S260 ; Autotune default Extruder with a target of 260c

20:03:02.831 : Kp: 38.71
20:03:02.831 : Ki: 10.32
20:03:02.831 : Kd: 36.30

configuration.h previous/changes

//#define EXT0_PID_PGAIN_OR_DEAD_TIME 14.50
#define EXT0_PID_PGAIN_OR_DEAD_TIME 38.71
//#define EXT0_PID_I 0.73
#define EXT0_PID_I 10.32
//#define EXT0_PID_D 53.41
#define EXT0_PID_D 36.3

Set temp 260c/60c

[morgandc]

Did a quick test this morning to make sure that 220c was still stable with the new PID parameters. Seems OK to me, not as good as the original @ 220.

First bit @ 260c, final 10 min @ 220c

New PID Graph

Original PID Graph at 220c

Original PID graph at 260c

edit: compared the original @220 vs now. It was definitely better with the other PID parameters @ 220c. I have asked SeeMeCNC if there are any options to change the PID parameters on the fly like in some other firmware.

[Xenocrates]

Morgan, if you're aiming for that, You should be able to use the G/M codes to store to the EEPROM for the temperature you want, and embed that into either tool-change G-code blocks, or edit the files individually. To find out what you need, open the G-code terminal and then edit the EEPROM settings through the host program (Rep host or Mattercontrol, Octopi), then insert those into the correct code block. I believe some slicers support having a post-processor/conditionals built in such that you can have them automatically select the PID, but as I mostly run filaments around 230~240C, I can mostly get away with a single PID, especially with a socked E3D in a heated chamber, I've never gotten to fiddling with that.

[morgandc]

I tried using M301 to set the PID parameters, but it didn't like the command. I could change them using an eeprom tool, but would prefer to have a g/m code that I can put use as a material specific g/m code when slicing, or put a script that I can run vs a manual process where a typo won't cause issues.

-Dwight

[IMBoring25]

I've always used M206. You'll use T[ype] and P[osition] parameters that you can get by looking at what's printed to the console when you command M503 and an X value (because these are float-type parameters) for the value to use.

You can put the M206 commands into your start g-code for each material's profile and it will re-configure the PID appropriately at the start of each print job.

[morgandc]

Interesting, I was looking for more of a temporary setting, but that sounds like it would work!

[morgandc]

Well.... stabile temps while not printing or just on the first layer is very different than upper layers, especially with fans on. All of the initial issues are back to a significant degree, bouncing around under temp, bed going over temp, etc while printing at 270c/60c but better than before the autotune PID changes.

Currently doing a print at 270c/85c with the fans turned off to see what happens. It appears right now that the temp is still not a consistent line, but much closer to target than when the fans are running and I can likely get a print out that at least finishes. At looking at the print, I will need to turn the fans on some and/or lower the extruder temp a bit.

[morgandc]

Moving into ABS, need the bed hotter than it will go by default. PID autotune time for that as well.

M303 P1 C8 S110; run autotune on the bed for 110c

[nebbian]

What heat manager are you using for your nozzle?

I had similar issues with my printer, when it was using heat manager 3. Mine was consistently 3-5 degrees hotter than the setpoint, so I had to blow on the hotend to get it down to a temperature where it would start to print. Annoying, and not very professional

I changed this to heat manager 1, and after a bit of manual tuning of PID settings, it's great now. It bumps around the setpoint +- 2 degrees at most.


For the bed, if you're using a relay like me, then heat manager 2 is the one to use. It does sound like you might have a thermistor issue on your bed though. I'd check to ensure that the thermistor is making good contact with your bed.

[morgandc]

The bed temps for PLA and PETG seemed to be ok, so I am guessing my thermistor is ok? Possibly the I gain needs to be increased is what I was thinking? The temp just plateau's early. Besides taking too long (12v), I think it is a PID tune.

Does anyone have the M503 / M206 commands to set the bed PID parameters? Trying to decipher those. I really don't want to haul a laptop in to tune the eeprom configuration.h a lot of times manually.

[morgandc]

This link seems to hold the largest clue to understand M503/M206 so far.
http://forum.seemecnc.com/viewtopic.php ... 503#p30031

[morgandc]

Looking at the firmware Repetier page, no M503 is implemented. Looking at the Commands.cpp, no M503 is checked for. This command appears to be a dead end.
M205 might be what I am looking for, I need to find the data structure for the eeprom next.

case 205: // M205 Show EEPROM settings
EEPROM::writeSettings();
break;
case 206: // M206 T[type] P[pos] [Sint(long] [Xfloat] Set eeprom value
EEPROM::update(com);
break;

[morgandc]

M205 results, now to figure out how to use m206.

Code: Select all

Send: N9 M205*45
Recv: ok 9
Recv: EPR:2 75 250000 Baudrate
Recv: EPR:1 43 1 Advanced User
Recv: EPR:3 129 234.200 Filament printed [m]
Recv: EPR:2 125 115954 Printer active [s]
Recv: EPR:2 79 900000 Max. inactive time [ms,0=off]
Recv: EPR:2 83 600000 Stop stepper after inactivity [ms,0=off]
Recv: EPR:3 11 80.0000 Steps per mm
Recv: EPR:3 23 250.000 Max. feedrate [mm/s]
Recv: EPR:3 35 80.000 Homing feedrate [mm/s]
Recv: EPR:3 39 32.000 Max. jerk [mm/s]
Recv: EPR:3 133 0.000 X home pos [mm]
Recv: EPR:3 137 0.000 Y home pos [mm]
Recv: EPR:3 141 0.000 Z home pos [mm]
Recv: EPR:3 145 250.000 X max length [mm]
Recv: EPR:3 149 250.000 Y max length [mm]
Recv: EPR:3 153 400.025 Z max length [mm]
Recv: EPR:3 59 1850.000 Acceleration [mm/s^2]
Recv: EPR:3 71 3000.000 Travel acceleration [mm/s^2]
Recv: EPR:3 881 290.800 Diagonal rod length [mm]
Recv: EPR:3 885 143.381 Horizontal rod radius at 0,0 [mm]
Recv: EPR:3 925 200.000 Max printable radius [mm]
Recv: EPR:1 891 80 Segments/s for travel
Recv: EPR:1 889 200 Segments/s for printing
Recv: EPR:1 893 27 Tower X endstop offset [steps]
Recv: EPR:1 895 0 Tower Y endstop offset [steps]
Recv: EPR:1 897 15 Tower Z endstop offset [steps]
Recv: EPR:3 901 210.000 Alpha A(210):
Recv: EPR:3 905 330.000 Alpha B(330):
Recv: EPR:3 909 90.000 Alpha C(90):
Recv: EPR:3 913 0.000 Delta Radius A(0):
Recv: EPR:3 917 0.000 Delta Radius B(0):
Recv: EPR:3 921 0.000 Delta Radius C(0):
Recv: EPR:3 933 0.000 Corr. diagonal A [mm]
Recv: EPR:3 937 0.000 Corr. diagonal B [mm]
Recv: EPR:3 941 0.000 Corr. diagonal C [mm]
Recv: EPR:3 808 -0.200 Z-probe height [mm]
Recv: EPR:3 929 20.000 Max. z-probe - bed dist. [mm]
Recv: EPR:3 812 90.000 Z-probe speed [mm/s]
Recv: EPR:3 840 50.000 Z-probe x-y-speed [mm/s]
Recv: EPR:3 800 0.000 Z-probe offset x [mm]
Recv: EPR:3 804 0.000 Z-probe offset y [mm]
Recv: EPR:3 816 -123.565 Z-probe X1
Recv: EPR:3 820 -71.340 Z-probe Y1
Recv: EPR:3 824 123.565 Z-probe X2
Recv: EPR:3 828 -71.340 Z-probe Y2
Recv: EPR:3 832 0.000 Z-probe X3
Recv: EPR:3 836 142.680 Z-probe Y3
Recv: EPR:0 880 0 Autolevel active (1/0)
Recv: EPR:0 106 1 Bed Heat Manager [0-3]
Recv: EPR:0 107 255 Bed PID drive max
Recv: EPR:0 124 80 Bed PID drive min
Recv: EPR:3 108 87.860 Bed PID P-gain
Recv: EPR:3 112 3.010 Bed PID I-gain
Recv: EPR:3 116 641.820 Bed PID D-gain
Recv: EPR:0 120 255 Bed PID max value [0-255]
Recv: EPR:3 200 92.400 Extr.1 steps per mm
Recv: EPR:3 204 100.000 Extr.1 max. feedrate [mm/s]
Recv: EPR:3 208 45.000 Extr.1 start feedrate [mm/s]
Recv: EPR:3 212 6500.000 Extr.1 acceleration [mm/s^2]
Recv: EPR:0 216 1 Extr.1 heat manager [0-3]
Recv: EPR:0 217 180 Extr.1 PID drive max
Recv: EPR:0 245 80 Extr.1 PID drive min
Recv: EPR:3 218 27.7800 Extr.1 PID P-gain/dead-time
Recv: EPR:3 222 7.4100 Extr.1 PID I-gain
Recv: EPR:3 226 26.0500 Extr.1 PID D-gain
Recv: EPR:0 230 255 Extr.1 PID max value [0-255]
Recv: EPR:2 231 0 Extr.1 X-offset [steps]
Recv: EPR:2 235 0 Extr.1 Y-offset [steps]
Recv: EPR:1 239 3 Extr.1 temp. stabilize time [s]
Recv: EPR:1 250 150 Extr.1 temp. for retraction when heating [C]
Recv: EPR:1 252 0 Extr.1 distance to retract when heating [mm]
Recv: EPR:0 254 200 Extr.1 extruder cooler speed [0-255]
Recv: EPR:3 246 0.000 Extr.1 advance L [0=off]
Recv: wait
Send: N10 M105*22
Recv: ok 10
Recv: T:23.01 /0 B:22.61 /0 B@:0 @:0

[morgandc]

Back to the drawing board, changing SpeedMultiply was not the objective. Not even sure if I changed something.
m206 T3 P112 S4.0
m205

Resulted in:

Send: N120 M206 T3 P112 S4.0*120
Recv: ok 120
Recv: Transformation matrix: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
Recv: SpeedMultiply:100

[Eric]

Back to the drawing board, changing SpeedMultiply was not the objective. Not even sure if I changed something.
m206 T3 P112 S4.0
m205

Resulted in:

Send: N120 M206 T3 P112 S4.0*120
Recv: ok 120
Recv: Transformation matrix: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
Recv: SpeedMultiply:100

Try "m206 T3 P112 X4.0". S is for integers (T0-2), X is for floats (T3).

And you might find this link useful. It's about Repetier Host, but it explains exactly what commands are being used to talk to Repetier Firmware.
https://github.com/repetier/Repetier-Ho ... M-settings

[bananapanic]

I would love to jump on this bandwagon. I upgraded to the HE280 hotend right when it came out. I've run into about every problem I can figure in trying to get it to perform consistently. I thought I was through with the last of problems-- (having to autotune the PID functions because I couldn't get the hotend above 240). I got a couple prints in on Urethane 235/70, but came in this morning to last night's print barely starting. The temps were at def. I'm doing the same print this morning. The hotend and bed got up to temp, but at some point I noticed the hotend at 115-120 and the bed is around 52. I was thinking it was the power supply, so I turned the bed off with no difference in hotend temp. I'm leaning more towards the hotend resister failing? It seems like a power supply would show at least some difference when depending on what it's powering.