Error Parsing Response

pete1961

This post is deleted!

pete1961

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

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

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