Temperature chart scale up to 2000c after updating to RRF3.2?

Dougal1957

As far as I can tell your M140 (line 75) should come after the corresponding M950 (line 85)

"Order dependency

In RRF3 a M140 command with H parameter (other than H-1) must come after the M950 command that creates that heater, and before any M143 command that sets a temperature limit for that heater."

HTH Doug

Phaedrux

Most commands in RRF don't depend on order, but some do. You've found a couple. In addition to The M140/M143 problem, there's also M584.

@fractalengineer said in Temperature chart scale up to 2000c after updating to RRF3.2?:

; Axis configuration M669 K1 ; Corexy mode M584 X0 Y1 Z2:3:4 E5 ; Map X to drive 0 Y to drive 1, Z to drives 2, 3, 4, and E to drive 5 M208 X290 Y303 Z325 ; Set axis maxima and high homing switch positions (adjust to suit your machine) M208 X-27 Y0 Z0 S1

Your M584 line also needs to come earlier than any commands that refer to axis parameters.

@fractalengineer said in Temperature chart scale up to 2000c after updating to RRF3.2?:

; Mesh Bed Compensation G29 S1 ; Load height map from SD card M376 H3 ; Set taper height 3mm

Also, don't load the mesh in config.g because you've not defined z0 at startup at. Can lead to unexpected z offsets or weirdness.

Sending M98 P"config.g" to check for any other syntax errors might be a good idea.

dc42

The general rule on command order in config.g is: don't try to change the parameters of anything that you haven't already created and doesn't exist by default. For example:

Don't refer to any axis letter or extruder number that you haven't created using M584 (except that XYZ already exist by default)
Don't refer to any temperature sensor in M950 or M106 before you create it using M308
Don't refer to a heater in M307, M140, M141, M143 or m563 before you create it using M950
Don't refer to a fan in M106 before you create it using M950
Don't refer to a tool in G10 before you create it using M563

fractalengineer

Alright thanks guys; following your advice I moved the M140 block below M950, and while at it moved the M584 up top

DWC scale is back to 350deg, problem fixed!

Cheers

Phaedrux

I added those rule of thumb to the gcode wiki.

ÖrjanE

@dc42 Will the firmware generate an error message in these situations, or silently continue? If the latter; would it be possible to add such sanity checks?

Phaedrux

@ÖrjanE Sending M98 P"config.g" is a good sanity check before you start testing things. That will usually catch bad syntax.

ÖrjanE

@Phaedrux said in Temperature chart scale up to 2000c after updating to RRF3.2?:

@ÖrjanE Sending M98 P"config.g" is a good sanity check before you start testing things. That will usually catch bad syntax.

Yes, but I guess it will not catch these "order errors" since config.g will already have been processed once at startup. Things that need to be defined before use will be defined the second time config.g is processed.

The problem is how the firmware should communicate error messages at startup, when the web interface is not up yet. Perhaps logging them to a file on the sd-card would be an alternative?

dc42

@ÖrjanE said in Temperature chart scale up to 2000c after updating to RRF3.2?:

The problem is how the firmware should communicate error messages at startup, when the web interface is not up yet. Perhaps logging them to a file on the sd-card would be an alternative?

If you enable logging at the start of config.g using M929, they should already be logged.

ÖrjanE

@dc42 said in Temperature chart scale up to 2000c after updating to RRF3.2?:

If you enable logging at the start of config.g using M929, they should already be logged.

Ah, I had missed this possibility (probably did not get that far when studying the gcode-list...). Sounds like this would be a good recommendation for people trying to debug their configuration setup.