SOLVED DWC JSON Error
At work we started getting this error: Duet Web Service , unterminated string at line 1 column 1461 of the JSON data
We logged into the RPI and looked at the log file for DWC too:
And sent an M122 command and this is what we received:
'=== Diagnostics ===\nRepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)\nBoard ID: 08DJM-956BA-NA3TJ-6JKDD-3S46N-KA86S\nUsed output buffers: 1 of 40 (11 max)\n=== RTOS ===\nStatic ram: 149788\nDynamic ram: 61712 of which 0 recycled\nNever used RAM 147332, free system stack 200 words\nTasks: Linux(blocked,117) HEAT(blocked,356) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1300) IDLE(ready,19)\nOwned mutexes: HTTP(MAIN)\n=== Platform ===\nLast reset 00:23:26 ago, cause: power up\nLast software reset at 2021-06-25 20:19, reason: User, none spinning, available RAM 147084, slot 0\nSoftware reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a\nError status: 0x00\nAux0 errors 0,0,0\nAux1 errors 0,0,0\nMCU temperature: min 44.7, current 50.4, max 50.7\nSupply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes\n12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0\nDriver 0: position 0, standstill, reads 32807, writes 14 timeouts 0, SG min/max 0/0\nDriver 1: position 0, standstill, reads 32808, writes 14 timeouts 0, SG min/max 0/0\nDriver 2: position 0, standstill, reads 32808, writes 14 timeouts 0, SG min/max 0/0\nDriver 3: position 0, standstill, reads 32808, writes 14 timeouts 0, SG min/max 0/0\nDriver 4: position 0, standstill, reads 32808, writes 14 timeouts 0, SG min/max 0/0\nDriver 5: position 0, standstill, reads 32808, writes 14 timeouts 0, SG min/max 0/0\nDate/time: 2021-06-25 21:07:34\nSlowest loop: 0.45ms; fastest: 0.06ms\n=== Storage ===\nFree file entries: 10\nSD card 0 not detected, interface speed: 37.5MBytes/sec\nSD card longest read time 0.0ms, write time 0.0ms, max retries 0\n=== Move ===\nDMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000\n=== MainDDARing ===\nScheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1\n=== AuxDDARing ===\nScheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1\n=== Heat ===\nBed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1\n=== GCodes ===\nSegments left: 0\nMovement lock held by null\nHTTP* is doing "M122" in state(s) 0\nTelnet is idle in state(s) 0\nFile is idle in state(s) 0\nUSB is idle in state(s) 0\nAux is idle in state(s) 0\nTrigger* is idle in state(s) 0\nQueue is idle in state(s) 0\nLCD is idle in state(s) 0\nSBC is idle in state(s) 0\nDaemon is idle in state(s) 0\nAux2 is idle in state(s) 0\nAutopause is idle in state(s) 0\nCode queue is empty.\n=== CAN ===\nMessages queued 0, send timeouts 7034, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48\n=== SBC interface ===\nState: 4, failed transfers: 0\nLast transfer: 1ms ago\nRX/TX seq numbers: 49828/49828\nSPI underruns 0, overruns 0\nNumber of disconnects: 0, IAP RAM available 0x2c8a8\nBuffer RX/TX: 0/0-0\n=== Duet Control Server ===\nDuet Control Server v3.2.2\nCode buffer space: 4096\nConfigured SPI speed: 8000000 Hz\nFull transfers per second: 21.88\nMaximum length of RX/TX data transfers: 2892/732\n'
If anyone has information regarding this issue it would be appreciated.
Are you able to update to 3.3?
@phaedrux since we are in a production environment it would be great if we figured out root cause of the issue and weren't forced to upgrade, although we can try that if necessary. Is there a bug fix in 3.3 for this issue?
You can see the change logs here:
Doing a test update to 3.3 would be worthwhile. There are many fixes in place.
You can also enable monitoring on the Pi to get some additional info: https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional
Hi @phaedrux thanks for the help so far, we updated to 3.3 and we are still getting the same error with DWC.
@garth_42 Please try to delete dwc-settings.json and check if that improves things.
@chrishamm thanks for the reply. We looked at it and compared it to the JSON file of another of our printers whom DWC was operational. The JSON was truncated, hence the issue. We copied over the JSON file from the other printer and now everything is working again. Thanks for the help!