Conditional GCode and object model variables

appjaws

Just a few question for @dc42

Has the object model been updated recently?
Is it possible to have the fan[].fanPercent included?
What test can I used to check if a filament is loaded?
When will we be able to define a variable?

Thanks for any help

dc42

@appjaws said in Conditional GCode and object model variables:

Has the object model been updated recently?

Yes, in 3.01-RC2.

Is it possible to have the fan[].fanPercent included?

I will look into it.

What test can I used to check if a filament is loaded?

Currently you would need to define a GP input pin for the filament present switch and then test it.

When will we be able to define a variable?

In the 3.02 release.

dc42

@appjaws said in Conditional GCode and object model variables:

Is it possible to have the fan[].fanPercent included?

fan[].requestedValue and fan[].actualvalue are already provided.

dc42

@appjaws said in Conditional GCode and object model variables:

What test can I used to check if a filament is loaded?

Filament monitors of type 1 and 2 (simple switch) already provided a filamentPresent field in the object model. I have just added the same field for type 4 (rotating magnet + switch) and type 6 (laser + switch).

appjaws

Thanks dc42,
The fan entries are failing with "Error: unknown value"
I'm I using it correctly?
while true
if fan[3].actualvalue <0.2
M106 P3 Sfan[3].requestedValue+0.1
M400
echo "LED Red value = " ^ fan[3].actualvalue

Where can I print out the latest object models?

dc42

I'm sorry, it's actualValue with uppercase V.

appjaws

@dc42 said in Conditional GCode and object model variables:

actualValue

Sorry but none of these work
"Cooling"
echo "LED Red value = " ^ fan[0].actualValue
"Extruder"
echo "LED Red value = " ^ fan[1].actualValue
"System"
echo "LED Red value = " ^ fan[2].actualValue
"LED Red"
echo "LED Red value = " ^ fan[3].actualValue
"LED Green"
echo "LED Red value = " ^ fan[4].actualValue
"LED Blue"
echo "LED Red value = " ^ fan[5].actualValue

dc42

I'm sorry again, it's "fans" not "fan".

Send M409 K"fans" to see all the fan OM values.

NexxCat

Apologies is this is a stupid question, or I'm overthinking this problem, but currently I run a delta calibration prior to every print. Whilst it's not a big issue normally, if I'm doing one print after another, allowing the nozzle to cool to my probing temperature (130C), probe, and then heat back up, is time wasted. With the release of 3.02 and variable support, would the following be possible for example?

On startup (in config.g?) assign a variable (say deltaCalibrated) to 0
After G32 is run, set deltaCalibrated to 1
If G28 is called, check to see if the calibration has been run, if so override the homing and move to Z-Max instead. If not, act as normal
If M84 is called, reset deltaCalibrated to 0

This would mean I would only have to run the delta calibration once per power-on under normal circumstances. It wouldn't re-home and mess up the existing Z height, and would only re-calibrate when needed.

Again, apologies if I'm overthinking this, or something like this is already possible, but this has been in the back of my mind since conditional gcode was first talked about

dc42

You can already test whether calibration is run. The results for the most recent calibration are available in the object model, and if the final deviation is reported as zero then calibration has not been run.

NexxCat

@dc42 said in Conditional GCode and object model variables:

You can already test whether calibration is run. The results for the most recent calibration are available in the object model, and if the final deviation is reported as zero then calibration has not been run.

Sounds like I need to get my config moved over to RRF3 and have a play then! Thanks for all your hard worth with the Duet and firmware @dc42

dc42

Also, if you turn the motors off using M84 then the axes will all be flagged as not homed, and you can test this too.

Argo

I think this thread might be the right location for this I guess because it's something I would need

Since I upgraded my Prusa MK3s to a Duet 2 WiFi board I try to enable all the features the Prusa original FW had.
This means:

automatic loading of filament when there is no filament in the extruder
PINDA temperature compensation table because the probe Z offset differs depending on the temperature. In my experience this is not linear and the higher the temperature the lower Z = 0 becomes meaning if you calibrate your printer with PLA, ABS will need recalibration as the nozzle will be too low.

My target is to create a config package for others so they can 1:1 swap their board and don't need to tweak much as my config uses all the convenient features, like the filament sensor, with explanation of what needs to change in the config depending of the used extruder or stepper motors (e.g. 0.9/1.8 degree).

1.
Feature to load the filament automatically.
Status: no filament in the extruder, extruder has PLA temperature (210°C)
Behaviour: Putting filament in the extruder triggers the filament sensor which then automatically loads filament.
Problem I had: The firmware only allows me to operate the filament sensor in one direction because the pin is blocked/reserved. Meaning I could only enable auto load or run out detection at once. So I had to split it in two over macros and start gcode.

So here is my (over complicated?) solution right now:

config.g

; Filament Sensor Port and Loading Feature ON
M950 J1 C"e0stop" ; Input 1 e0 Filament Sensor 
M581 P1 T2 S0 R0 ; Filament Sensor P1 triggers Trigger2.g always (R0)

Runout is not working right now. So when the printer is starting up and there is no filament and filament is put into the extruder trigger2.g is called:

trigger2.g:

; Loading Filament Script

M300 S800 P200
M581 P1 T2 S-1 R0 ; Filament Sensor does not listen anymore (S-1). Autoload is disabled. 
M291 P"Please wait while the nozzle is being heated up" R"Loading PLA" T5 ; Display message
T0 ; Activate Hotend
M291 P"Feeding filament Trigger2" R"Loading PLA" T5 ; Display new message
G1 E70 F800 ; Feed 70mm of filament at 800mm/min
G1 E55 F300 ; Feed 50mm of filament at 300mm/min
G4 P1000 ; Wait one second
G1 E-5 F800 ; Retract 3mm of filament at 800mm/min
M400 ; Wait for moves to complete
M292 ; Hide the message
G10 S150 ; Set current tool temperature to 150C
;G10 S0 ; Turn off the heater again

; Filament Sensor Port and Runout Feature ON
M581 P1 T2 S-1 R0 ; Filaent Sensor does not listen anymore (S-1). Autoload is disabled. 
M950 J1 C"nil" ; Input 1 e0 Filament Sensor 
M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor

After the loading script the sensor is put into mode "runout detection ON"

But what if you turn your printer on and filament is already loaded and you directly start your print? This would mean that there is no runout detection enabled.
My solution right now is putting this into the Start GCODE in the slicer software:

; Prime Filament Sensor for Runout
M581 P1 T2 S-1 R0 ; Filament Sensor P1 triggers Trigger2.g always (R0)  TRIGGER OFF
M950 J1 C"nil" ; Input 1 e0 Filament Sensor 
M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor

And there is a third scenario. What if you want to manually change your your color (filament) mid print?
After unloading the filament the sensor needs to be in mode "autoload" and after the autoloading is complete it has to go back to the mode "runout detection".

So i added this to my filament-change.g macro:

M25
G91 ; Relative Positioning
G1 Z20 F360; Raise Z
G90 ; Absolute Values
G1 X200 Y0 F6000 ; Parking Position
M300 S800 P8000 ; play beep sound
M98 Pejectfilament.g
M400

Called Pejectfilament.g:

M591 D0 P0 C"e0stop" S1 ; Filament Runout Sensor
M950 J1 C"nil"

M291 P"Please wait while the nozzle is being heated up" R"Unloading PLA" T5 ; Display message
T0 ; Activate Hotend
M109 S210
M291 P"Retracting filament..." R"Unloading PLA" T5 ; Display another message
G1 E+8 F300 ; Extrude 8mm of filament at 300mm/min
G1 E-45 F800 ; Retract 480mm of filament at 800mm/min
G1 E-15 F900 ; Retract 480mm of filament at 900mm/min
G1 E-25 F900 ; Retract 480mm of filament at 900mm/min
M400 ; Wait for the moves to finish
M292 ; Hide the message again
M300 S800 P200

; Filament Sensor gets ready for next load
M950 J1 C"e0stop" ; Input 1 e0 Filament Sensor 
M581 P1 T3 S0 R0 ; Filament Sensor P1 triggers Trigger3.g

At the end trigger3.g:

M300 S800 P200
M581 P1 T2 S-1 R0 ; Filaent Sensor does not listen anymore (S-1). Autoload is disabled. 
M291 P"Please wait while the nozzle is being heated up" R"Loading PLA" T5 ; Display message
T0 ; Activate Hotend
M291 P"Feeding filament Trigger3" R"Loading PLA" T5 ; Display new message
G1 E70 F800 ; Feed 70mm of filament at 800mm/min
G1 E55 F300 ; Feed 50mm of filament at 300mm/min
G4 P1000 ; Wait one second
G1 E-1 F800 ; Retract 1mm of filament at 800mm/min
M400 ; Wait for moves to complete
M292 ; Hide the message

; Filament Sensor Port and Runout Feature ON
M581 P1 T2 S-1 R0 ; Filaent Sensor does not listen anymore (S-1). Autoload is disabled. 
M950 J1 C"nil" ; Input 1 e0 Filament Sensor 
M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor

I know it first seems quite complex but when runout is enabled the port is blocked and can't be used for autoload.
Now I've read about the implementation of if / else statement which could make things quite simpler and also lowers the change of error as there would be no need to put code into the start gcode.

Like so (be aware, I'm no coder! )
Filament Sensor Status = 1 means no filament

func autoload {
M581 P1 T2 S-1 R0 ; Filament Sensor does not listen anymore (S-1). Autoload is disabled.
M950 J1 C"nil" ; Input 1 e0 Filament Sensor
M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor
}

func runout_detection {
M581 P1 T2 S-1 R0 ; Filament Sensor P1 triggers Trigger2.g always (R0) TRIGGER OFF
M950 J1 C"nil" ; Input 1 e0 Filament Sensor
M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor
}

if Filament_Sensor state changed to "1" {
autoload
} else {
runout_detection
}

Something like that

2. PINDA Temperature calibration

The PINDA (v2) has an built in thermistor to use the Prusa FWs temperature compensation table.
RRP FW has has similar feature built in into the G31 command:

G31 P1000 X23 Y5 Z0.995 C0.0010 S20 H2

I've measured the Z trigger height with several temperatures from 20°C, 25°C up to 50°C and saw that the variance was not linear. At first the offset got bigger meaning the nozzle would be too close to the bed and after 40°C the difference were much smaller up to 50°C.
I'm not quite sure how the Prusa FW stores and uses the recorded values when the FW does it's auto temperature PINDA calibration but what would work is if you could use different G31 code lines depending of the temperature of the PINDA thermistor.

My "I'm no coder" mind thinks of the following:

if PINDA_Thermistor <25°C {
G31 P1000 X23 Y5 Z0.995
}
else if PINDA_Thermistor >=25° AND PINDA_Thermistor <30° {
G31 P1000 X23 Y5 Z1.005
}
else if PINDA_Thermistor >=30°C AND PINDA_Thermistor <35° {
G31 P1000 X23 Y5 Z1.020
}
.
. and so on...
else {
G31 P1000 X23 Y5 Z2.0 ; safety height
}

Hope it is clear what I mean

o_lampe

I'm just gathering bits and pieces for the TicTacToe-macro.
So I'd like to know if and how I can create an two-dimensional array? (rows and collums)
I would also like to use vectors for the AI calculations? How could I express length and direction in a single variable?

dc42

There are no array variables yet, and no vector variables. Here are some ideas:

You could pack several integer variables into a single integer variable, but take care not to exceed 2^31-1.
You could create 9 axes in total, then use the offsets of each axis in one or more of the workplace coordinate systems as 9-element arrays