How to upgrade from 2.05.1 to 3.1.1?

A Former User

@zapta said in How to upgrade from 2.05.1 to 3.1.1?:

Error: Bad command: 205

From the looks of it RRF thinks it receives a command 205 which isn't valid g-code.

I'd look over configs and triggers for syntax errors or linebreaks on the loose.

(just to verify, you're getting the same message on USB/WEB right?)

edit: cloned git and no results when grepping for 205 so thats odd. could you have gotten a bonus config-override.g that is misformatted? would be interesting to know if it comes before or after the e-stop (i.e. in config.g or not). I'd add some echo to the top and bottom of config.g and look at the USB console.

zapta

@bearer said in How to upgrade from 2.05.1 to 3.1.1?:

(just to verify, you're getting the same message on USB/WEB right?)

Not getting it on the WEB, just on PanelDue when issuing the command from PanelDue. Didn't try the USB connection, will give it a try, including with planted messages.

BTW, I got also other codes, not just 255. E.g. 204, 44, 247 so I think it's at lower level than just bad gcode in a file.

Phaedrux

Can you send M98 P"config.g" in the console and report any errors? I'm guessing that's where the bad command is coming from. It's showing up on the paneldue after an emergency stop because the board is up and running when you issue it and the paneldue is able to catch the error which otherwise might get missed on a cold boot.

zapta

@Phaedrux said in How to upgrade from 2.05.1 to 3.1.1?:

M98 P"config.g"

When I issue this command from the DWC I don't see the error message, just this which looks normal:

7/28/2020, 4:38:43 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is disabled
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 262C
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 528C

I also hooked a logic analyze to the duet's tx/rx lines to the paneldue and it seems that it's the paneldue sends the bad command which results in the error message. Will try to describe it here, hopefully it's clear.

This is the dump from the logic analyzer. TX=duet->paneldue, RX=paneldue->duet.
capture.csv

At one point, after issuing the restart, the paneldue sends this and gets back the error 198 message. The actual number changes, not always 198.

Any idea what the problem is? Am I the only one that experience it?

1.179844000000000,RX,N (0x4E)
1.180016000000000,RX,1 (0x31)
1.180189000000000,RX,2 (0x32)
1.180361000000000,RX,0 (0x30)
1.180534000000000,RX,' ' (0x20)
1.180706000000000,RX,M (0x4D)
1.180879000000000,RX,1 (0x31)
1.181051000000000,RX,1 (0x31)
1.181224000000000,RX,2 (0x32)
1.181396000000000,RX,' ' (0x20)
1.181569000000000,RX,; (0x3B)
1.181741000000000,RX,'240' (0xF0)
1.181914000000000,RX,'15' (0x0F)
1.182086000000000,RX,* (0x2A)
1.182259000000000,RX,1 (0x31)     <---
1.182431000000000,RX,9 (0x39)     <---
1.182482000000000,TX,{
1.182604000000000,RX,8 (0x38)     <---
1.182656000000000,TX,"
1.182776000000000,RX,\n (0x0A)

A Former User

@zapta said in How to upgrade from 2.05.1 to 3.1.1?:

I also hooked a logic analyze to the duet's tx/rx lines to the paneldue and it seems that it's the paneldue sends the bad command which results in the error message. Will try to describe it here, hopefully it's clear.

was worried about when the bad commands varied and wasn't present in any file. does it do the same if you only connect power and no rx/tx to the paneldue?

zapta

@bearer said in How to upgrade from 2.05.1 to 3.1.1?:

does it do the same if you only connect power and no rx/tx to the paneldue?

I will give it a try, assuming it will let me issue a Stop without being able to connect to the duet.

I think this is the relevant code, and it seems that the data the paneldue sends after the 0xf0 0x0f is corrupted.

https://github.com/Duet3D/PanelDueFirmware/blob/master/src/UserInterface.cpp#L1671

A Former User

Just don't see how updating RRF would affect the PanelDue firmware; interesting issue if nothing else:/

zapta

@bearer said in How to upgrade from 2.05.1 to 3.1.1?:

Just don't see how updating RRF would affect the PanelDue firmware; interesting issue if nothing else:/

One explanation is that the PanelDue behaved the same but RRF2 didn't detect and response to the bad command, for example if it took longer time to reboot. (this is a speculation). I may try to restore RRF2 and look again with the logic analyzer.

Phaedrux

4 wire or ribbon cable for the Panel?

zapta

@Phaedrux , 4 wires.

Phaedrux

I might try a different 4 wire cable. I had some bad command and the panel being stuck on "connecting" occasionally and it turned out to be a bad 4 wire cable. I also braided the replacement since it runs along with some stepper wires. Haven't had an issue since.

zapta

@Phaedrux said in How to upgrade from 2.05.1 to 3.1.1?:

I might try a different 4 wire cable.

The problem was very consistent. I just reverted my printer to RRF 2 and the problem disappeared. I will check tomorrow with logic analyzer if the transmission from the PanelDue is corrupted the same and possibly RRF2 is just more tolerant somehow.

zapta

@Phaedrux, I use a logic analyzer to capture the duet/paneldue serial traffic under RRF2 and RRF3. In both cases the results are very consistent, with same hardware, same cables, etc, always works cleanly with RRF2 and always giving an error message with RRF3.]

Looking at the capture signal, RRF3 behaves differently from RRF2. With RRF2, the duet lets the paneldue sending the entire M112 message with no response, with RRF3, the duet response immediately with an error message.

https://github.com/Duet3D/PanelDueFirmware/blob/master/src/UserInterface.cpp#L1674

This is how it looks under RRF2:

And this is under RRF3

This is from the rrf3.csv, it shows how the the duet response (TX) before the paneldue completes its transmision (RX):

3.274821000000000,TX,1
3.274994000000000,TX,}
3.275168000000000,TX,\n
3.476848000000000,RX,N (0x4E)
3.477020000000000,RX,4 (0x34)
3.477193000000000,RX,9 (0x39)
3.477365000000000,RX,3 (0x33)
3.477538000000000,RX,4 (0x34)
3.477710000000000,RX,' ' (0x20)
3.477883000000000,RX,M (0x4D)
3.478055000000000,RX,1 (0x31)
3.478228000000000,RX,1 (0x31)
3.478400000000000,RX,2 (0x32)
3.478573000000000,RX,' ' (0x20)
3.478745000000000,RX,; (0x3B)
3.478918000000000,RX,'240' (0xF0)
3.479090000000000,RX,'15' (0x0F)
3.479263000000000,RX,* (0x2A)
3.479435000000000,RX,2 (0x32)
3.479608000000000,RX,5 (0x35)
3.479685000000000,TX,{   <<-- RRF3 doesn't like the M112 message
3.479780000000000,RX,5 (0x35)
3.479858000000000,TX,"
3.479953000000000,RX,\n (0x0A)
3.480032000000000,TX,s
3.480205000000000,TX,e
3.480378000000000,TX,q

This is the corresponding section from RRF2:

4.297585000000000,TX,1
4.297759000000000,TX,}
4.297932000000000,TX,\n
5.048296000000000,RX,N (0x4E)
5.048468000000000,RX,1 (0x31)
5.048641000000000,RX,8 (0x38)
5.048813000000000,RX,8 (0x38)
5.048986000000000,RX,' ' (0x20)
5.049158000000000,RX,M (0x4D)
5.049331000000000,RX,1 (0x31)
5.049503000000000,RX,1 (0x31)
5.049676000000000,RX,2 (0x32)
5.049848000000000,RX,' ' (0x20)
5.050021000000000,RX,; (0x3B)
5.050194000000000,RX,'240' (0xF0)
5.050366000000000,RX,'15' (0x0F)
5.050539000000000,RX,* (0x2A)
5.050711000000000,RX,1 (0x31)
5.050884000000000,RX,9 (0x39)
5.051056000000000,RX,6 (0x36)
5.051229000000000,RX,\n (0x0A)
// 1 sec later, per the 1000ms in the source code
6.050462000000000,RX,N (0x4E) 
6.050635000000000,RX,1 (0x31)
6.050807000000000,RX,8 (0x38)
6.050980000000000,RX,9 (0x39)
6.051152000000000,RX,' ' (0x20)
6.051325000000000,RX,M (0x4D)
6.051497000000000,RX,9 (0x39)
6.051670000000000,RX,9 (0x39)
6.051842000000000,RX,9 (0x39)
6.052015000000000,RX,* (0x2A)
6.052187000000000,RX,4 (0x34)
6.052360000000000,RX,2 (0x32)

Any idea why the RRF3 doesn't like the M112 message and responds immediately instead of waiting for the M999 ?

rrf2_capture.csv

rrf3_capture.csv

A Former User

@zapta said in How to upgrade from 2.05.1 to 3.1.1?:

Any idea why the RRF3 doesn't like the M112 message and responds immediately instead of waiting for the M999 ?

i think the 0xf0 0x0f is a special case to reset immediately without getting stuck in the queue; so the difference must be in how RRF3 reacts to this? time to put up the ~~bat~~ dc42 signal?

Phaedrux

@dc42 is away on vacation until next week, but I'm sure he'll find this interesting.

zapta

@bearer, I think you are right. The code actually says that RRF2 and RRF3 are different in their handling of the stop command:

// We send M112 for the benefit of old firmware, and F0 0F (an invalid UTF8 sequence) for new firmware
SerialIo::SendString("M112 ;" "\xF0" "\x0F" "\n")

https://github.com/Duet3D/PanelDueFirmware/blob/master/src/UserInterface.cpp#L1674

A Former User

i did get the sense when dc42 commented the 0xf0 0x0f thing that new firmware also included newer rrf2 but couldn't find any refrence to it

but its odd that duet3 people have been using paneldue since the first rrf3 with no similar reports, so there might be more to it (or they never pressed the stop button).

on the other hand there isn't any reason the paneldue should transmit anything between 0xf0 0x0f and 0x0a (0x0a being the newline)?

(edit I have a 4.3 regular paneldue and a 7i here - I was hoping to log the same data from, but looks like a case for tomorrow. but should at least be able to confirm if those behave the same)

zapta

@bearer said in How to upgrade from 2.05.1 to 3.1.1?:

I was hoping to log the same data from, but looks like a case for tomorrow.

Thanks @bearer. Looking forward for your findings.

A Former User

@bearer said in How to upgrade from 2.05.1 to 3.1.1?:

on the other hand there isn't any reason the paneldue should transmit anything between 0xf0 0x0f and 0x0a (0x0a being the newline)?

Its the checksum thats before the newline

N13 M112 ;ð␏*247

N2 M112 ;ð␏*199

So the bad command would change with the line number and checksum presumably.

I.e. the issue is with RRF3

A Former User

Yeah, its definitively the Duet reacting to the rx buffer after 0x70 0x07 and ending up parsing it as a bad command.

If you increase the baud rate you get one less digit, and if you decrease the baud raute you get the asterisk plus the digits as well, i was hoping the asterisk would get the parser to see it as checksum and discard it, but no.

Poked around a bit, but didn't find where the 0x70 0x07 is handled, it seems M112 is clearing out the rx buffer as part of the estop. Id test flushing SERIAL_AUX_DEVICE rx buffer as its initialized but messed up the build env somehow.

It'd be interesting to see one of the Duet3 users with PanelDue tap the stop button and see if they get the same error. Is searching for M575 P1 B57600 S1 and tagging everyone who didn't read the upgrade notes bad form?:P