Found it:
Field "filamentPresent" is removed from those types of filament monitor that previously supported it. Use "status" instead.
Best posts made by jdebuhr
-
RE: Filament sensor Meta Command issue
Latest posts made by jdebuhr
-
RE: Filament sensor Meta Command issue
Found it:
Field "filamentPresent" is removed from those types of filament monitor that previously supported it. Use "status" instead. -
Filament sensor Meta Command issue
HI, I have a Duet 2 WiFi and it is on old Prusa MK2.5s hardware. so I am working out so details and I am using Kolbi's setup ( mostly) and some of his macros.
Now in a couple of his Macros found here:
https://forum.duet3d.com/topic/18002/zaribo-prusa-i3-mk3s-duet-2-wifi-rrf-3-11/15
(Specifically Set Filament Type and Filament Handling there is this line that is giving me errors:
if sensors.filamentMonitors[0].filamentPresent = truehere is the response for: m591 d0
Simple filament sensor on pin e0stop, enabled, output high when no filament, filament present: noWhen I run the Set Filament Macro I get this error:
M98 P"0:/macros/Set Filament Type"
Error: in file macro line 5 column 4: meta command: unknown value 'filamentPresent'When I run M409 K"sensors.filamentMonitors" F"filamentPresent"
I get this response:{
"key": "sensors.filamentMonitors",
"flags": "filamentPresent",
"result": [
{
"status": "noFilament"
}
],
"next": 0
}I know I am missing something, but what am I missing?
below is my
m122 "config.g"
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SD-6J9F6-3SN6Q-KVQHK
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 74880 of which 204 recycled
Never used RAM 13128, free system stack 184 words
Tasks: NETWORK(ready,14.6%,242) HEAT(notifyWait,0.0%,332) Move(notifyWait,0.0%,364) MAIN(running,85.4%,440) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: WiFi(NETWORK) HTTP(MAIN)
=== Platform ===
Last reset 00:30:23 ago, cause: software
Last software reset at 2022-05-08 21:12, reason: User, GCodes spinning, available RAM 9440, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 28.4, current 28.8, max 29.2
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-05-08 21:42:53
Cache data hit count 4294967295
Slowest loop: 7.06ms; fastest: 0.19ms
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 0.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "m122 "config.g"" 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
=== Filament sensors ===
Extruder 0 sensor: no filament
=== Network ===
Slowest loop: 201.65ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 3
WiFi firmware version 1.26
WiFi MAC address f4:cf:a2:ea:8c:e5
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25112
WiFi IP address 192.168.1.104
WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
- WiFi -