RRF 3.01-RC11 PanelDue Inop after update

DaveA

After updating to RC11 the PanelDue no longer connects. Status stays at Connecting.
PanelDue is at 1.2.4. DWC is at 2.1.6.
This is on a Duet 2 hardware
I see in the release notes a reference to the PanelDue but seems to be for Duet 3 only.
Reverting to RC10 brings the PanelDue back to life.

A Former User

Could be a glitch in the matrix, maybe add the ~~needed~~ relevant config and see if it helps?

M575 P1 S1 B57600

dc42

Odd, it works for me on Duet WiFi even with the M575 line in config.g commented out. Do you have a M575 line in config.g, and if so, what parameters does it have? Is the baud rate of the PanelDue set to 57600 on the Settings page?

DaveA

@bearer
My config has a M575 P1 S1 B115200 and the PanelDue setup has the baud rate set to 115200.
Can I not run at 115200 any longer?
When I get back downstairs I'll try at 57600.

A Former User

didn't expect it to make a difference, just a long shot waiting for the big guns to roll in

dc42

It looks like there may be a problem with changing the baud rate setting. For now I suggest you use 57600.

dc42

I found the cause of the problem (I think) and a workaround. Use command M575 P1 B115200 twice in config.g.

DaveA

I can confirm that 57600 works. I'll try the double M575 in a bit as it's printing right now.

DaveA

Just tried the M575 twice in config.g but no joy. The only baud rate that seems to work is 57600.
I'm using: M575 P1 S1 B1115200

gtj0

@DaveA said in RRF 3.01-RC11 PanelDue Inop after update:

Just tried the M575 twice in config.g but no joy. The only baud rate that seems to work is 57600.
I'm using: M575 P1 S1 B1115200

The 3 ones in B1115200 is just a transcription typo right?

DaveA

@gtj0 Yep.

dc42

Odd, last night had my Kossel working with the baud rate set to 115200 on the PanelDue in my Kossel, and these lines

M575 P1 B115200 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue)
M575 P1 B115200 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue)

in config.g. This morning I rebooted and it is still working. So I don't know why it's not working for you.

I'll prepare an unofficial release later today or tomorrow with this bug fixed. I'm thinking of making the M575 line mandatory for PanelDue users on Duet 2 as it is on Duet 3, that way the PanelDue port could be used as GPIO if there is no PanelDue.

arhi

@dc42 said in RRF 3.01-RC11 PanelDue Inop after update:

that way the PanelDue port could be used as GPIO if there is no PanelDue

That would be nice!

DaveA

@dc42 Same here now. I just powered up the printer and the PanelDue is working fine @115200 with the two M575 entries. Not sure what happened last night. Maybe I didn't really reboot after editing the config file. Anyway, all is well for now.