I'm still seeing an undocumented error status code
-
All I've done since I powered on the machine is print a temperature test tower for a new filament and a small cube to verify an adjustment. As I'm about to start what might be a three day print, I'd really like to know what these errors mean. I don't want to waste all that time and filament!
Here's the M122 I'm currently seeing:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7JTD0-3S86S-KYTND
Used output buffers: 4 of 24 (10 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93716 of which 344 recycled
Exception stack ram used: 540
Never used ram: 10792
Tasks: NETWORK(ready,652) HEAT(blocked,1236) MAIN(running,1668) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 04:42:17 ago, cause: power up
Last software reset at 2019-08-19 09:31, reason: User, spinning module GCodes, available RAM 10688 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 24
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 391.7ms, max retries 0
MCU temperature: min 25.8, current 34.2, max 40.3
Supply voltage: min 23.9, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/146
Driver 1: standstill, SG min/max 0/154
Driver 2: standstill, SG min/max 0/48
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max 0/55
Date/time: 2019-08-20 21:19:35
Cache data hit count 4294967295
Slowest loop: 139.09ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 2, FreeDm: 169, MinFreeDm: 110, MaxWait: 3300406ms
Bed compensation in use: mesh, comp offset 0.000
=== DDARing ===
Scheduled moves: 1, completed moves: 1, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 3 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 392.82ms; fastest: 0.00ms
Responder states: HTTP(3) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
-- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 84:f3:eb:42:a3:23
WiFi Vcc 3.44, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 20864
WiFi IP address 192.168.1.29
WiFi signal strength -48dBm, reconnections 0, sleep mode modem
Socket states: 2 4 0 0 0 0 0 0The secondary question is: If I simulate the file I'm about to print, will error status codes get conditioned by simulation?
-
what error exactly are you talking about? I can´t see anything special
-
-
@dc42 said in I'm still seeing an undocumented error status code:
https://duet3d.dozuki.com/Wiki/Error_codes_and_software_reset_codes
Where on that page is the definition of this code: Error status: 24???
0x04 is: Output buffer starvation
0x20 is: ??????????????????????? -
It is a bitmask: 24 (decimal) = 1 1000
So that's 2 error codes being set: 0x10 (16) and 0x08 (8). -
I'll change it to display the value in hex in the next release.
-
D'oh!
My mistake, I assumed that as the codes were listed in hex, the value displayed would also be hex.