truncated M591 response in console

Adrian52

With 3.5.0-rc1, the output in the console from M591 D0 is truncated. I get the usual output up to the 'min' value, but only the 'a' of average, and nothing more. I tried rolling back dwc to 3.5 beta4, with the same result. Running stand alone on duet2 wifi, laser filament monitor.

dc42

@Adrian52 thanks for your report. We will try to reproduce it.

Adrian52

@dc42 Thank you. As there were no other immediate replies, I checked in 3.4.6, and the problem went away. Installing a fresh download 3.5rc1 and the problem came back. Perhaps should add I am running a fairly old duet2wifi - 1.01 I think.

dc42

@Adrian52 thanks. The M591 response is longer in 3.5.0-rc.1 than it was previously, so it is entirely possible that it no longer fits in the buffer available for it.

T3P3Tony

@dc42 confirmed this is being truncated early:

M591 D1
Duet3D rotating magnet filament monitor v3 on pin 10.io1.in, enabled when printing from SD card, sensitivity 24.80mm/rev, allow 40% to 120%, check printing moves every 2.0mm, version 3, mag 134 agc 0, measured sensitivity 24.66mm/rev, min 95% max 105% over

T3P3Tony

@Adrian52 this is logged as issue:

https://github.com/Duet3D/RepRapFirmware/issues/908

T3P3 created this issue in Duet3D/RepRapFirmware

closed M591 output truncated #908

Adrian52

The latest rc1+(from 31/10/2023) is still a little bit truncated:

Duet3D laser filament monitor v2 on pin (connlcd.encb,connlcd.3), enabled when SD printing, allow 1% to 300%, check all extruding moves every 10.0mm, calibration factor 0.398, quality 222, brightness 41, shutter 140, measured min 80% avg 101% max 120% over

dc42

@Adrian52 thanks, I'll abbreviate it some more.

dc42

@Adrian52 which Duet are you using?

Adrian52

@dc42 I have an early (1.01) duet 2wifi

dc42

@Adrian52 thanks. Please try the new firmware binary for Duet 2 at https://www.dropbox.com/scl/fo/tjznycpk7bv7sj71p0ssl/h?rlkey=096p4nvgmigyrb20jj8olg3wu&dl=0. I have moved the brightness and shutter value reports to the M122 report; so please check the Filament Monitors section of the M122 report as well as the M591 response. I don't have a version 3 laser filament monitor in a machine at present so I can't complete these tests myself.

Adrian52

@dc42 Thank you. The M591 response looks fine now:

Duet3D laser filament monitor v2 on pin (connlcd.encb,connlcd.3), enabled when SD printing, allow 1% to 300%, check all extruding moves every 10.0mm, cal. factor 0.398, quality 223, measured min 100% avg 101% max 103% over 1400.3mm

This is the M122 after the test print

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.1+ (2023-11-01 10:30:19) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W
Used output buffers: 3 of 26 (26 max)
=== RTOS ===
Static ram: 23084
Dynamic ram: 74860 of which 0 recycled
Never used RAM 14264, free system stack 112 words
Tasks: NETWORK(2,nWait,15.5%,214) HEAT(3,nWait,0.1%,310) Move(4,nWait,1.1%,261) MAIN(1,running,83.3%,851) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:31:22 ago, cause: software
Last software reset at 2023-10-22 17:39, reason: User, Gcodes spinning, available RAM 9544, slot 2
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 29.6, current 32.7, max 34.3
Supply voltage: min 24.1, current 24.4, max 24.7, 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: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min 0
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2023-11-01 21:40:28
Cache data hit count 4294967295
Slowest loop: 217.89ms; fastest: 0.17ms
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.8ms, write time 4.5ms, max retries 0
=== Move ===
DMs created 83, segments created 39, maxWait 271969ms, bed compensation in use: none, height map offset 0.000, ebfmin -0.99, ebfmax 1.00
no step interrupt scheduled
Moves shaped first try 1911, on retry 173, too short 353, wrong shape 466, maybepossible 58
=== DDARing 0 ===
Scheduled moves 3691, completed 3691, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 7], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null
HTTP is idle 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
Q0 segments left 0
Code queue 0 is empty
=== Filament sensors ===
check 3500690 clear 3025120
Extruder 0: pos 5.47, brightness 36, shutter 128, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0=== Network ===
Slowest loop: 207.47ms; fastest: 0.07ms
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta4
MAC address 5c:cf:7f:2c:24:6b
Module reset reason: Turned on by main processor, Vcc 3.38, flash size 2097152, free heap 42952
WiFi IP address 192.168.1.16
Signal strength -55dBm, channel 13, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 3 0 0 0 0 0

I think the filament sensor output needs a cr/lf at the end?

I just printed a plain cube, but it came out dimensionally correct and no y slope!

Thank you again.

dc42

@Adrian52 thanks, I've added that newline.