Error Parsing Response

pete1961

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

@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

@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

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

Phaedrux

@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

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

dvmourik

@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

@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.

mfs12

Hey @dvmourik , looking through the thread i couldn't find out which exact firmware versions were you using when things were still working fine?

Can you please post the versions of

PanelDue
RepRap

when things were still ok.

mfs12

Hey @dvmourik,

i build a patched firmware image to understand your problem better. Can you test it on your device and provide the results.

Here's the patched firmware:

PanelDueFirmware-3.3.0-rc3-dvmourik-5.0i-7.0i.bin

The major change i did is an increased timeout for requests.

dvmourik

@mfs12

Thank you very much, we are going to test it.
It happens from 3.2.x up and before we used (3.1.1 which was clean/no problems)

We even have it now on our small machines (desktop)

We are going to install the firmware now and will report within 2 hours with a result.

@Phaedrux resistance is in range and even much lower. We took a original cable (longest which was supplied before and meassured 3x as much restance. So this is not the issue as we think. Thanks for thinking with us.

dvmourik

@mfs12

We installed the firmware, but unfortunately it didn't solve our problems. Now we get a lot of error messages as shown in attached picture! We are currently running RRF 3.3 RC2 and WebControl 3.3.0 RC2 IMG_20210721_140124.jpg

jay_s_uk

@dvmourik can you upgrade to the stable 3.3 release?
There was a bug fix regarding "error parsing..." that was fixed between RC3 and the stable release. See here https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta-&-RC#reprapfirmware-33-post-rc3

dvmourik

@jay_s_uk

Upgraded to the stable release, but still the same problem

jay_s_uk

@dvmourik thanks for confirming

dc42

@dvmourik can you confirm that it is still only during startup that you see these messages?

dvmourik

@dc42 Nope, those messages, from the picture in my previous post, keep coming up every minute or so

mfs12

Hey @dvmourik, I need more information to get a better understanding.

Can you provide the following information:

which Paneldue Firmware were you running with your RRF-3.1.1 setup?
please share your config.g
please describe the process how to reproduce the errors

dvmourik

@mfs12 We have just uploaded 3.1.1. and 1.24 and this still seems to work without any errors. to reproduce we just turn the machine on, please see our config below:

;T3D v2.5.1.1
M111 S0
M550 PTractus3D T3000 ;DO NOT CHANGE - NEEDED FOR PROCESSES
M540 P0x02:0x80:0xC2:0x02:0x00:0xFF
M575 P1 B57600 S1
M98 P"_UserSettings.g"
M552 S1
M555 P1
G21
G90
M83

M569 P0 S0 ;E0
M569 P1 S0 ;E1
M569 P4 S0 ;Y
M569 P2 S0 ;X
M569 P3 S0 ;Z

M584 X2 Y4 Z3 E0

M92 X80 Y80 Z80
M92 E290
M906 X1700 Y1700 Z1700 E1100 I40
M201 X1000 Y1000 Z1000 E6000
M204 P500 T1000
M203 X18000 Y18000 Z18000 E18000
M566 X300 Y300 Z300 E600
M665 R494.50 L1063 B500 H1660 X0 Y0 Z0

M666 X0 Y0 Z0 A0 B0

M574 X2 S1 P"xstop"
M574 Y2 S1 P"ystop"
M574 Z2 S1 P"zstop"

M308 S0 A"Bed" Y"thermistor" P"bedtemp" T100000 B4400 R4700
M308 S1 A"Hotend 1" P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8

M950 H0 C"bedheat" T0

M308 S6 A"MCU" Y"mcu-temp"

M950 P0 C"exp.heater3"
M950 H1 C"e0_heat" T1

M950 F0 C"fan0"
M950 F1 C"fan1"
M950 F2 C"fan2" Q1000
M950 J1 C"e1stop"
M950 J2 C"exp.e2stop"

M201 X1000 Y1000 Z1000 E4000
M204 P1000 T1000
M566 X500 Y500 Z500 E1200

M106 P0 S0 H-1 C"Part cooling"
M106 P1 T50 H1 S255
M106 P2 T40:60 H2 L0.50 X1.0

M570 H0 P20 T20
M570 H1 P15 T20

M563 P0 D0 H1 F0 S"Hotend 1"
G10 P0 S0 R0

M140 H0

M307 H0 A119.9 C608.9 D1.4 S1.00 B1
M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0

M558 P5 C"e0stop" X0 Y0 Z0 F100 T10000
G31 X0 Y0 Z16.25 P500

M557 R400 S40

M208 S1 Z-0.5
M911 S20.5 R22.0 P"G91 M83 G1 Z3 E-3 F3000 M929 S0"

M579 X0.9926 Y0.9980
M912 P0 S2

M143 H0 P0 S110 A2
M143 H0 P1 S130 A0
M143 H1 P0 S300 A2
M143 H1 P1 S320 A0

M42 P0 S255
M42 P1 S255
M581 P1 T1 S1 R1

G28

mfs12

Hey @dvmourik, i put your config on my machine, but couldn't reproduce the problem. unfortunately.

Would RRF-3.2.x or RRF-3.3 and PD-1.24 work as a workaround for you?

Slowly i start to believe it might be related to the wiring.

Can you test the following:

disconnect duet3 from network (just to be sure it's nothing on the network keeping duet3 very busy)
enter M115 in the paneldue console and post reply
start the duet3 and paneldue your cable (check if error continues to occur)
start the duet3 and paneldue with short cable (check if error continues to occur)