PanelDue firmware 1.22 released


  • administrators

    I have just released new PanelDue firmware at https://github.com/dc42/PanelDueFirmware/releases/tag/1.22. This is mostly a bug fix release but it has a few new features:

    • If the printer sends a non-trivial response to the PanelDue and the Control or Print screen is being displayed, the response appears in a popup window. The popup times out after 5 seconds or can be closed manually.
    • The initial splash screen loads faster
    • Removed 40mm/sec feed rate from Extrude menu, added 2mm/sec
    • Alert messages can now occupy up to 3 lines of characters
    • Support longer command responses on the Console page
    • Support longer file lists on SAM4S-based PanelDues

    Bug fixes:

    • Macros displayed on the Control page didn't work if their names were more than 20 characters long
    • Fixed buffer overflow when more than 6 tools were configured using a 5" or 7" screen or more than 4 tools using a 4.3" screen
    • Fixed splash screen corruption when a splash screen file is appended to a binary for use on a version 1 or 2 PanelDue with ATSAM3S4 processor
    • When the printer has 5V power only, macro names are now displayed and commands can be sent
    • If "Always dim" is configured, the display no longer un-dims when there is a printer status change
    • When the Extrude menu is used, the extruder position is no longer reset to zero, to avoid problems when the Extrude menu is used while the print is paused and it was printing a file sliced in absolute extrusion mode.

    Please report any issues you find with this release in this thread.



  • Please, I would like to know how to install the PanelDue firmware from a Linux based machine.

    I could not find last time I updated and ended bringing the display home for the update.

    Thank you



  • @brunofporto said in PanelDue firmware 1.22 released:

    Please, I would like to know how to install the PanelDue firmware from a Linux based machine.

    I could not find last time I updated and ended bringing the display home for the update.

    Thank you

    You just need to install bossa on you linux distrubtion, not sure what are you running exactly and then run:

    sudo bossac -p /dev/ttyACM0 -e -w -v -b ~/Pobrane/PanelDueFirmware-v3-5.0.bin 
    

    Where last part points to the downloaded firmware



  • Thank you! Running Ubuntu 16.04. and 18.04. Just installed Bossa and I will try asap.



  • This is by far the best set of instructions for the procedure:
    https://betrue3d.dk/paneldue-update-firmware/



  • @dc42 said in PanelDue firmware 1.22 released:

    If the printer sends a non-trivial response to the PanelDue and the Control or Print screen is being displayed, the response appears in a popup window. The popup times out after 5 seconds or can be closed manually.

    This isn't good. It's popping up WAY too often and there's no way to disable it. It also exposes a problem if there's another popup already on the screen.

    For example, it's no longer possible to "baby step" twice in a row quickly via the paneldue. From the PanelDue "print" page, I tap "baby step" and I see the +0.02 and -0.02 buttons. As soon as I press one, I get a "Response" titled popup telling me that "Baby stepping offset is -0.02mm". I can't baby step again because that popup is "in the way." However, I can't tap the red X on the popup either (probably because the baby step popup is also up, behind the "response" popup.) The only escape is to wait a few seconds, or tap something like "Control" at the bottom - which will close BOTH the response popup and the baby step popup.

    Actually, the scenario where I discovered this was starting a print where I knew that Z 0 was about .04mm too high. So, I started the print and as soon as the nozzle came down to start printing, I went to tap baby step and -0.02 twice. I accidentally hit +0.02 (and realized it immediately) but couldn't correct the error soon enough because of the "response" mess. It was a failed first layer.

    Please either cut this "feature" or at the very least make it configurable. There are other cases when the "response" is annoying, such as when starting a print. I know I started a print. I did it on purpose. I don't want some big pop up covering my entire screen and preventing me from doing anything else until I acknowledge it telling me the obvious.

    Imagine if your compiler did that. You type "make" and hit enter. The entire screen is then immediately covered with a big black (or white) box with the text "You Started a Compile!" with a tiny "X" in the upper right that you'd have to peck at before being able to see the list of warnings and errors that just scrolled off the screen.


  • administrators

    @garyd9 said in PanelDue firmware 1.22 released:

    This isn't good. It's popping up WAY too often and there's no way to disable it. It also exposes a problem if there's another popup already on the screen.
    For example, it's no longer possible to "baby step" twice in a row quickly via the paneldue. From the PanelDue "print" page, I tap "baby step" and I see the +0.02 and -0.02 buttons. As soon as I press one, I get a "Response" titled popup telling me that "Baby stepping offset is -0.02mm".

    I think I should change the Duet firmware not to generate those messages.

    I can't baby step again because that popup is "in the way." However, I can't tap the red X on the popup either (probably because the baby step popup is also up, behind the "response" popup.)

    That sounds like a bug. It should be possible to clear the popup by touching the X. I will investigate that.



  • @dragonn said in PanelDue firmware 1.22 released:

    /dev/ttyACM0

    Please, @dragonn do you know the command to show this address? I am using Ubuntu πŸ˜„

    Thank you very much.



  • @brunofporto said in PanelDue firmware 1.22 released:

    @dragonn said in PanelDue firmware 1.22 released:

    /dev/ttyACM0

    Please, @dragonn do you know the command to show this address? I am using Ubuntu πŸ˜„

    Thank you very much.

    Connect you PanelDue via USB and run:

    dmesg
    

    At end of the log you should see that you PanelDue connected and at with port.



  • @dragonn Do I need some special driver or anything?? I just can not find it...



  • @dragonn It is the same issue I had before... I just do not show up anywhere πŸ˜„
    Tested using different USB ports and cables to be sure.



  • @dragonn ok....

    Well.... Now it appeared. After pressing the ERASE button... I show up as ttyACM0 But whenI use bossac it claims "No device found on /dev/ttyACM0"



  • @dc42, I was browsing the github commit for 1.22 and noticed that in UserInterface.cpp, the "extrudeSpeedValues" array was changed to have new display values for extrusion rates. However, the "extrudeSpeedParams" array was not changed and still reflects the old extrusion rates:

    static const char * array extrudeSpeedValues[] = { "50", "20", "10", "5", "2" };
    static const char * array extrudeSpeedParams[] = { "3000", "2400", "1200", "600", "300" };

  • administrators

    @garyd9 said in PanelDue firmware 1.22 released:

    @dc42, I was browsing the github commit for 1.22 and noticed that in UserInterface.cpp, the "extrudeSpeedValues" array was changed to have new display values for extrusion rates. However, the "extrudeSpeedParams" array was not changed and still reflects the old extrusion rates:

    static const char * array extrudeSpeedValues[] = { "50", "20", "10", "5", "2" };
    static const char * array extrudeSpeedParams[] = { "3000", "2400", "1200", "600", "300" };

    Thanks for pointing that out. I'll fix that in a 1.22.1 release. I'll wait a few days first to see what other issues with the new firmware arise.



  • @dc42 I didn't send a pull request for that extrudespeedparams as I wasn't really sure about it. I did send a pull request for an issue that popped up many versions ago and I was too lazy to fix. (Dim on Idle should treat "off" as being idle.)

    Please, Please, PLEASE forgive the parenthesis mess. πŸ˜‰



  • @brunofporto said in PanelDue firmware 1.22 released:

    @dragonn ok....

    Well.... Now it appeared. After pressing the ERASE button... I show up as ttyACM0 But whenI use bossac it claims "No device found on /dev/ttyACM0"

    You know that you need press the erase button?
    You should really read the instruction https://miscsolutions.wordpress.com/paneldue/
    You are just doing something wrong, it works perfectly fine. Even easier the on Windows.



  • @dc42 said in PanelDue firmware 1.22 released:

    @garyd9 said in PanelDue firmware 1.22 released:

    This isn't good. It's popping up WAY too often and there's no way to disable it. It also exposes a problem if there's another popup already on the screen.
    For example, it's no longer possible to "baby step" twice in a row quickly via the paneldue. From the PanelDue "print" page, I tap "baby step" and I see the +0.02 and -0.02 buttons. As soon as I press one, I get a "Response" titled popup telling me that "Baby stepping offset is -0.02mm".

    I think I should change the Duet firmware not to generate those messages.

    Some more: I'm using the paneldue to PAUSE a print. I have a big popup telling me I just paused the print. (Really? No! Is THAT what the "pause" button does??) Then I use the paneldue to CANCEL that print. Guess what happens? It pops up a message telling me I just canceled the print.

    This makes the paneldue miserable to use.



  • @dragonn I quit....

    Even with the device detected and correctly identified within the bossac command it simply did not work...

    I bring it home to update it using Windows again..... But thank you very much for your help. Maybe next time I'll discover what I did wrong.... πŸ˜„



  • It also tells me with an annoying pop up when the duet joins the network.

    I was excited for this pop up status feature mostly to see the results of the delta bed probing.

    It’d be really nice if paneldue parsed that response and displayed it next to the bed level button.



  • I am having some issues.

    1- If I call M591 D0 it still not enough text room for the entire response.
    2- The stop button at the top left did not work like the equivalent at DWC and after pressing it PanelDue was not able to connect again until I hit the emergency stop at DWC
    3- I run a macro for my Z-Probe tunning, that have some issues of not selecting the tool, but if called from PanelDue I do not get any warnings - it just locks as busy and do nothing (that is why I hit the Stop....)


Log in to reply