Need help to set up filament runout sensor
-
@Phaedrux the added the ; but no change. I only added this line because i thought this way the T4 parameter is assigned to this file...
-
I think the problem is that you are trying to use the same switch for filament sensing and as a trigger at the same time.
The filament sensor behavior is to send a pause command when the filament is not present.
If you want to use the switch to trigger a custom macro, you would just use M581.
It has been requested previously to allow for a custom macro on filament runout and it's on the work list.
https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M591_Configure_filament_sensing
https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M581_Configure_external_trigger
So in the meantime, configure as one or the other.
-
@Phaedrux thank you i will try. Also found that trigger T1 resets the board, T2 pauses and all numbers above executes triggerX.g files. Is this in RRF3 still the case? I can't find this info in the wiki. I found it by google...
Thank you for your help. Will report the result
-
Okay now it works. I just deleted the trigger code...
A few other questions i dont want to open a new thread:
I always calibrated my delta in cold state (heaters off) now if i want to always calibrate before a print starts should i do this in cold state? I ask because if i also want to use mesh compensation i have to do this with heated bed state. Should i also always do a mesh compensation after delta calibration before each print? Or just load a state after calibration? -
@PuddingBaer91 said in Need help to set up filament runout sensor:
Also found that trigger T1 resets the board, T2 pauses and all numbers above executes triggerX.g files. Is this in RRF3 still the case? I can't find this info in the wiki. I found it by google...
It's literally in the link I posted above.
Trigger number 0 causes an emergency stop as if M112 had been received. Trigger number 1 causes the print to be paused as if M25 had been received. Any trigger number # greater than 1 causes the macro file sys/trigger#.g to be executed. Polling for further trigger conditions is suspended until the trigger macro file has been completed. RepRapFirmware does not wait for all queued moves to be completed before executing the macro, so you may wish to use the M400 command at the start of your macro file. If several triggers are pending, the one with the lowest trigger number takes priority.
@PuddingBaer91 said in Need help to set up filament runout sensor:
I always calibrated my delta in cold state (heaters off) now if i want to always calibrate before a print starts should i do this in cold state? I ask because if i also want to use mesh compensation i have to do this with heated bed state. Should i also always do a mesh compensation after delta calibration before each print? Or just load a state after calibration?
I think it's usually best to perform any calibration in a hot state to better match the thermal expansion changes that happen during the actual print.
-
thank you
Another thing i noticed: If i probe the bed in DWC the z-probe shows most time 0 but sometimes it shows a red 1000. Is this normal? Probe triggers at all cases correct...
-
@PuddingBaer91 Yes that's normal. The web interface can't update fast enough for probes that only briefly show the triggered state.
-
thank you again
another thing
If i heat the hot end the probe led flickers. If i set the sensity to 70 it's gone. Is this way okay or do i have to check/change something?
-
@PuddingBaer91 said in Need help to set up filament runout sensor:
If i set the sensity to 70 it's gone
What does this mean?
If the probe is still functioning normally I wouldn't worry about the flicker.
-
i meant the sensity parameter for smart effector:
M672 S105:70:185
