Need help to set up filament runout sensor
-
@Phaedrux said in Need help to set up filament runout sensor:
M122
29.1.2021, 19:20:39 M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SN-6J9D2-3SJ6R-9BUBK Used output buffers: 2 of 24 (11 max) === RTOS === Static ram: 23460 Dynamic ram: 72804 of which 24 recycled Never used RAM 15792, free system stack 189 words Tasks: NETWORK(ready,183) HEAT(blocked,295) MAIN(running,452) IDLE(ready,19) Owned mutexes: WiFi(NETWORK) HTTP(MAIN) === Platform === Last reset 00:01:36 ago, cause: power up Last software reset at 2021-01-29 16:11, reason: User, GCodes spinning, available RAM 15792, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 23.7, current 28.5, max 28.7 Supply voltage: min 24.0, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 125740, standstill, SG min/max not available Driver 1: position 125740, standstill, SG min/max not available Driver 2: position 125740, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-01-29 19:20:38 Cache data hit count 116224094 Slowest loop: 3.48ms; fastest: 0.21ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP is ready with "M122 " in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 15.88ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.25 WiFi MAC address 40:f5:20:1d:bf:a8 WiFi Vcc 3.37, reset reason Turned on by main processor WiFi flash size 4194304, free heap 27056 WiFi IP address 192.168.1.43 WiFi signal strength -74dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: no filament29.1.2021, 19:21:17 M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 272C Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 547C Error: Bad command: trigger4.g Error: Bad command: trigger4.g Error: Bad command: trigger4.g Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 272C Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 547C -
Put a ; in front of trigger4.g
lemme double check the usage of M591 and M581
-
@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
