search

Duet3D / RepRapFirmware

OO C++ RepRap Firmware
GNU General Public License v3.0
940 stars 534 forks source link

PanelDue communication fails after Duet restart #461

Closed gigix74 closed 3 years ago

gigix74 commented 3 years ago

Writing the PanelDue firmware with M997 S4 requires always to press erase first - even if I have the latest version. Firmware programming works then with no error. The display remains turned off after finish. A reset (or subsequent resets) of the PanelDue makes everything functional with a connection at 57600 baud. Power cycling or restarting the whole printer makes PanelDue not able to communicate anymore with the duet board (and resetting the display is not helping). Writing the PanelDue firmware with Bossa don't change the behavior.

Now the curious part: Issuing a M997 S4 again, (even it returns the "Error: Failed to communicate with PanelDue bootloader (no START signal received). Please press the Erase and Reset switches on PanelDue.") has the effect of PanelDue communication resume. As a workaround for the moment I will add this command to config.g.

Board: Duet 2 WiFi (2WiFi) Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2-beta4.1 (2020-12-02) Duet WiFi Server Version: 1.25beta0 Duet Web Control 3.2.0-beta4 PanelDue V3-5.0, FW: 3.2.6+1

gigix74 commented 3 years ago

Problem was caused by missing M575 P1 S1 B57600 from configuration. Programming and communication with PanelDue works correctly now.

Release note 3.1.0: https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md

All PanelDue users: the PanelDue connector (or IO_0 on Duet 3) is no longer dedicated to PanelDue, therefore if you connect a PanelDue to this port you must use the following command in config.g to enable it: M575 P1 S1 B57600. You can use baud rates other than 57600, however the IAP files all assume 57600 baud; therefore if you use another baud rate then PanelDue will not display firmware update progress.