Error Parsing Response

wilriker · 17 Feb 2021, 19:34

@taylo708 This message generated whenever the status-updates from RRF cannot be parsed correctly. Can you confirm that this is new with RRF 3.3beta1 and you did not have this issue before?

If so, please post your config.g so I can investigate the issue.

taylo708 · 18 Feb 2021, 00:11

I was running 3.3 beta1. I also have a 3.3 beta I’m not sure if they are different or not. I went back to 3.3 beta and am still getting the same parsing error.

wilriker · 18 Feb 2021, 09:44

@taylo708 Please provide the following information:
Output of
M115 and M122 as well as your config.g.

taylo708 · 18 Feb 2021, 14:51

This post is deleted!

taylo708 · 22 Feb 2021, 23:59

m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.3beta ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-01-20 16:37:22

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3beta running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6JTD0-3S06T-1V86T
Used output buffers: 1 of 40 (23 max)
=== RTOS ===
Static ram: 149784
Dynamic ram: 90596 of which 24 recycled
Never used RAM 110268, free system stack 178 words
Tasks: NETWORK(ready,222) ETHERNET(blocked,117) HEAT(blocked,280) CanReceiv(blocked,887) CanSender(blocked,365) CanClock(blocked,326) TMC(blocked,49) MAIN(running,1120) IDLE(ready,20)
Owned mutexes:
=== Platform ===
Last reset 01:49:39 ago, cause: software
Last software reset at 2021-02-22 17:03, reason: User, GCodes spinning, available RAM 110268, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 45.4, current 45.6, max 46.0
Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 63181, writes 0 timeouts 0, SG min/max not available
Driver 1: position 0, standstill, reads 63181, writes 0 timeouts 0, SG min/max not available
Driver 2: position 0, standstill, reads 63182, writes 0 timeouts 0, SG min/max not available
Driver 3: position 0, standstill, reads 63182, writes 0 timeouts 0, SG min/max not available
Driver 4: position 0, standstill, reads 63182, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, standstill, reads 63181, writes 0 timeouts 0, SG min/max not available
Date/time: 2021-02-22 18:52:55
Slowest loop: 25.59ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.3ms, write time 3.3ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 2 -1 -1 -1
=== GCodes ===
Segments left: 0
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
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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 2044, send timeouts 0, received 2092, lost 0, longest wait 4ms for reply type 6024, peak Tx sync delay 147, free buffers 48 (min 47)
=== Network ===
Slowest loop: 26.25ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0```

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Wed Jan 13 2021 13:45:55 GMT-0500 (Eastern Standard Time)

; General preferences
G90                                           ; send absolute coordinates...
M83                                           ; ...but relative extruder moves
M550 P"DATA DRIVEN PERFORMANCE"               ; set printer name

; Network
M552 S1 192.168.254.57                                  ; Enable network
G4 S5
; Drives
M569 P40.0 R0 S0 T6:6:6:0                   ; physical drive 40 goes forwards
M569 P41.0 R0 S1 T6:6:6:0                   ; physical drive 41 goes forwards
M569 P42.0 R0 S0 T6:6:6:0                   ; physical drive 42 goes forwards
M569 P0.0 S1                                   ; physical drive 20 goes forwards
M584 X40.0 Y41.0 Z42.0 E0.0                 ; set drive mapping
M350 E16 I0                                 ; configure microstepping with interpolation
M92  X266.666 Y266.666 Z640.00 E130.00      ; set steps per mm
M350 E32
M566 X300.00 Y300.00 Z20.00 E30.00        ; set maximum Jerk (mm/min)
M203 X7000.00 Y7000.00 Z1000.00 E3000.00   ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z200 E2500             ; set accelerations (mm/s^2)                              
M906 E750 I30                               ; set motor currents (mA)
M84 S30                                     ; Disable motor idle current reduction

; Axis Limits
M208 X0 Y0 Z0 S1                              ; set axis minima
M208 X600 Y600 Z600 S0                        ; set axis maxima

; Endstops
M574 X1 S1 P"!20.io2.in"                      ; configure active-high endstop for low end on X via pin 124.io2.in
M574 Y1 S1 P"!io3.in"                         ; configure active-high endstop for low end on Y via pin io3.in
M574 Z1 S2                                    ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"20.io0.out"                        ; create servo pin 0 for BLTouch
M558 P9 C"^20.io0.in" H2 F120 T600          ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X30 Y90 Z2                          ; set Z probe trigger value, offset and trigger height
M557 X30:570 Y90:510 S28.5                     ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3500 ; configure sensor 0 as thermistor on pin temp1
M950 H0 C"out0" T0                           ; create bed heater output on out0 and map it to sensor 0
M307 H0 R0.086 C1484.1 D36.00 B0 S1.00       ; disable bang-bang mode for the bed heater and set PWM limit
M570 H0 T40
M140 H0                                      ; map heated bed to heater 0
M143 H0 S120                                 ; set temperature limit for heater 0 to 120C
M308 S1 P"spi.cs0" Y"thermocouple-max31856" "K"   ; configure sensor 1 as thermocouple via CS pin spi.cs0
M950 H1 C"out1" T1                           ; create nozzle heater output on 124.out0 and map it to sensor 1
M307 H1 R2.808 C254.0 D9.08 B0 S1.00                             ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S350                                 ; set temperature limit for heater 1 to 350C
M308 S2 P"temp1" Y"thermistor" T100000 B3500; configure sensor 2 as thermistor on pin temp0
M950 H2 C"io1.out" T2                        ; create chamber heater output on out1 and map it to sensor 2
M307 H2 A11 C99000 D2000 B1 S1.00                ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H2                                      ; map chamber to heater 2
M143 H2 S70                                  ; set temperature limit for heater 2 to 70C


; Fans
M950 F0 C"20.out1" Q500                      ; create fan 0 on pin 20.out1 and set its frequency
M106 P0 S0 H-1                                  ; set fan 0 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0                             ; define tool 0
G10 P0 X-30 Y0 Z0                               ; set tool 0 axis offsets
G10 P0 R0 S0                                  ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600                             ; enable support for PanelDue

dvmourik · 27 May 2021, 07:31

Is there any solution for this? We have the same problem with 3.3RC2 and 3.2.11 (PanelDue). We do multiple machines a week but this is our first machine where we get this problem.

What we tried allready:

New LCD screen
New cables between board and LCD
Firmware 3.2 to 3.3RC2
LCD Firmware 3.2.1 and 3.2.11

dc42 · 6 Jun 2021, 00:46

@dvmourik I can think of the following possible explanations:

Faulty hardware: this could be the Duet, the cable, or the PanelDue. You've replaced the cable and the PanelDue, but have you replaced the Duet?
Something different in the environment, e.g. something that is normally grounded isn't on this particular machine, and that is causing interference
An obscure firmware bug that is causing RRF to return invalid JSON because of the way the machine is configured. Is the config.g file on this machine the same as on the working machines?

Does the machine respond to commands sent from the PanelDue, e.g. the Home All button?

pete1961 · 6 Jun 2021, 00:47

@dc42
I just received a brand new panel due to upgrade an old one.
The new 7i causes these errors.
The old panel with extra board that plugged into it probably is 5 years old works fine.
I'm running the latest stable release of the duet firmware and also the current latest firmware for the panel 7i.

Any idea why this is causing me grief?
Considering returning the PanelDue as I believe something is wrong with it if the old PanelDue works fine.

Anything you recommend???

dc42 · 6 Jun 2021, 09:06

@pete1961 which firmware is the older PanelDue running?

pete1961 · 6 Jun 2021, 13:39

This post is deleted!

pete1961 · 6 Jun 2021, 15:02

I'm going to say at present after making a shorter cable from scratch the errors have stopped.
I went from about a 24" cable down to a 10" Cable.
I will come back here if I see more errors.

Phaedrux · 6 Jun 2021, 18:24

@pete1961 Using a braid or twist on the cable can help. so can using a higher gauge or shielding.

pete1961 · 7 Jun 2021, 15:08

Yes a better cable is in order with the 10" cable I fabricated the errors are more spurious than previously but still around.
The cabling is obviously the cause of this problem.

dc42 · 7 Jun 2021, 15:48

@pete1961 said in Error Parsing Response:

Yes a better cable is in order with the 10" cable I fabricated the errors are more spurious than previously but still around.
The cabling is obviously the cause of this problem.

24" (600mm) is not too long (I have a 1.5m cable on one of my machines), however there is a limit on the resistance per conductor. See the wiki for details.

dvmourik · 11 Jun 2021, 12:00

@dc42
-Replaced the hardware, we tried to go step by step and find out if it's faulty hardware or wiring. We've seen a lot of strange things happen. Sadly this is new for us and giving a bit of a headache.
What we see in our errorlog is sometimes:

Error: Bad command: N1557 M409 K"move" F"v"

or

Error: Bad command: N2559 M409 K"move" F"v"

or

Error: Bad command: M409 K"move" F"N2753 M409 F"d99f"*12N2755 M409 K"move" F"v"*113

So this directs me a bit in the software / bug side.

We downgraded both duet and panel to 3.22 and tried 3.3RC2 but always the same Parsing Response Error.

We use thick professional shielded cables in the machines which works in all our builded machines for 5 years now. So i can't believe it's the length of the wire suddenly.

dc42 · 11 Jun 2021, 12:23

@dvmourik please run M122 on the machine(s) affected after this issue has occurred.

Phaedrux · 11 Jun 2021, 16:55

@dvmourik said in Error Parsing Response:

So i can't believe it's the length of the wire

What is the resistance on each conductor?

the resistance per conductor should not exceed 0.1 ohm.

dc42 · 15 Jun 2021, 18:13

@dvmourik please see https://forum.duet3d.com/topic/23724/bad-command-errors-on-paneldue.

dvmourik · 19 Jul 2021, 15:12

@dc42 Thanks. The error parsing response is now gone. With the newest firmware we now have .....

Warning: failed to parse response move:currentMove: in state 12
Warning: failed to parse response inputs^:lineNumber: in state 12
Warning: failed to parse response inputs^:feedRates: in state 12

And some more.

LCD 7i is on FW 3.3.0-b
When we go back to 3.2.10 or 3.2.9 we still get Error parsing response
We tried from 115200 down to 38400 buadrate

Duet is on 3.3.0

It happens when we power on the machine. We build this machines as OEM vendor and never had any issues with our machines until last updates. For us the old firmware works fine but our customers want to upgrade and this results in fails.

Hopefully the error above gives a bit more details to help us out.

Phaedrux · 19 Jul 2021, 16:28

@phaedrux said in Error Parsing Response:

@dvmourik said in Error Parsing Response:

So i can't believe it's the length of the wire

What is the resistance on each conductor?

the resistance per conductor should not exceed 0.1 ohm.