PanelDue 5i - Stuck on initializing after updating to 3.2-RC3+1



  • Hello,

    Upgrading my BigBox Dual, got all Duet 3 MB6HC / RPi and PanelDue 5i up and running with no inputs, started installing temperature sensor (PT100 daughter board). Updated the config.g and all temperature sensor appeared as expected, all good, until a message flashed up saying outdated firmware. So I foolishly started to update to the latest version at which points the wheels fell off.

    The panel due is sat with "initializing" in the top right corner since I've upgraded to 3.2-RC3+1 and also updated the Duet3 6MB to Release 3.2 Beta1.

    Confirmed I hadn't got any poor connections and the wires were swapped over as per the instructions, confirmed in the config.g that

    M575 P1 S1 B57600

    Downloaded and installed a clean version of Duet Lite (22/08/2020) just in case. No change.

    Reverted back to 1.24 and 3.11 and problem remains so I'm guessing something isn't correct. Any pointers as where to look at for fault finding to find out where my issue is?

    The panel works fine (touch screen and menus), just doesn't communicate with the motherboard. - On 3.2-RC3 the console shows it's connected.


  • Moderator

    I would suggest that you stick to firmware/dwc 3.1.1 and paneldue 1.24 for the time being, especially for initial setup. Sounds like you're back to that, so that's good.

    M575 P1 B57600 S1 you've got already, so that's good.

    Are you sure the paneldue baud rate is also set to 57600 in the setup page?

    How are you connecting the paneldue? Ribbon cable or 4 wire?


  • administrators

    PanelDue 1.24 still works with RRF 3.2beta1.



  • Reverted back to my initial build, 3.1.1 and PanelDue 1.24 and a clean version of Duet-Lite (May 2020).

    When powered up paneldue still sitting at connecting.

    Could it be the motherboard not communicating as not all the components are connected (currently only the PT100 daughter board with the 2 extruder PT100 sensors) and the heated bed thermistor (Temp0). Now I think of it, it was working till it got powered down to update the motherboard.

    I know the daughter board was working as during the initial setup the paneldue displayed the 2 extruders and bed temperatures were displayed. Bit confused as to where I've gone wrong and also how to move forward.


  • Moderator

    @Phaedrux said in PanelDue 5i - Stuck on initializing after updating to 3.2-RC3+1:

    Are you sure the paneldue baud rate is also set to 57600 in the setup page?
    How are you connecting the paneldue? Ribbon cable or 4 wire?



  • I've made up a new PanelDue to Duet 3 MB6HC IO_0 cable and have had the same results....

    But, this time I decided to carry on and ingnore the PanelDue which was still showing "Connecting" in the top right hand side and use the web interface, all looked good, temperatures showing on the bed and extruders. So being brave plugged in the heated bed power and energised it. Temperature went up (no surprise there), it did however time out due to not rising quick enough (probably the slab of aluminium on top - I'll deal with the PID setup later). This alarm that came up also was displayed on the PanelDue.

    Not sure what it means / helps but something on the motherboard is probably not happy due to missing most of it's connections so time to start labelling and re-crimping where required.



  • Hi!

    I have a similar issue with a PanelDue v3 + 7" LCD screen.

    I upgraded RRF from 3.0beta_something to 3.1.1, and reflashed PanelDue with 1.24 firmware, and now, it does not connect anymore. DWC runs fine.

    I re-sent the M575 P1 B57600 S1 command, as my PanelDue is set to 57600 bauds: no change.

    What could be the problem? How to investigate?

    Thanks for your help.


  • Moderator

    It's a little unusual that it is getting messages to display but also still showing connecting.

    When you have your hardware connected please share some more details like the results of sending M122, M98 P"config.g", your entire config.g, and how you have the panel connected, and ensure the baud rate in config.g and the panel match.



  • @Phaedrux said in PanelDue 5i - Stuck on initializing after updating to 3.2-RC3+1:

    ensure the baud rate in config.g and the panel match

    My bad! I didn't put the command in config.g file, I was only sending it through the console. So, it didn't survive the reset cycle...

    It works fine, now, thanks!



  • How can I test my paneldue 5i. I can update the firmware via Bossa and the USB port no issues, but when I plug it using option 2 (4 Way Cable) on IO_0 to the Duet 3. I've made up 2 cables configured as shown in the diagrams / pictures.
    Using 1.24 firmware and 3.1.1 on the main board, it still sticks at initialising. Any pointers greatly received.


  • Moderator

    @Phaedrux said in PanelDue 5i - Stuck on initializing after updating to 3.2-RC3+1:

    It's a little unusual that it is getting messages to display but also still showing connecting.
    When you have your hardware connected please share some more details like the results of sending M122, M98 P"config.g", your entire config.g, and how you have the panel connected, and ensure the baud rate in config.g and the panel match.

    @Bluemalu I've asked for this information a few times now.


Log in to reply