@rkutun if you want to make all objects have configurable height then you will need to add the height variable to the base class DisplayField instead of adding it to the SingleButton class. Then you would need to add a suitable parameter to the constructors of DisplayField and all classes derived from DisplayField (including SingleButton) and pass the value down to the base class, just as the width parameter (called pw in most of them) is.

As @elmoret says, providing detailed development assistance is beyond the free support that we provide.

@Phaedrux

Hc05: https://a.aliexpress.com/_EGOKr6V

5V UPS: I just found this on AliExpress:
1,47€ | Mini 5V 1A UPS Uninterrupted Output Module 2 in 1 Charge Discharge 3.7V 3.8V 4.2V Li-Ion Li-Polymer 18650 Battery Charger Board
https://a.aliexpress.com/_EIco57n

1x 18650 li-ion battery or other flat li-ion battery.

1 switch from the shelve.

My design for the case.

@droftarts Thank you.

@sinned6915
Hello, I have the same issue on PanelDue7.0/V3 controller.
I can't recompile the firmware with the modified PanelDue.cpp file because I don't have the skills. Would it be possible to share the one you use? Thanks in advance

@droftarts
Thank you Ian

@jay_s_uk You did a great job identifying the right place to customize the software (at least for me, it would have been a lot of work).

Anyways, considering that in this case I would need to host the whole programming environment for this minor change, which would not be persistent at the next release, I decided to rather try to create a macro and use the BtnCmd plugin to make it available in DWC.

Thanks for your help.

Happy to report that I was able to flash all six PanelDues (four V2s & two V3s), and I'll accept user error. Let me explain what I did as I know others will likely fall into the same trap I did. I installed BOSSA like normal which includes the baked-in CDC driver. The port doesn't show up in Device Manager just yet. Plug in the PanelDue and the BOSSA Driver still doesn't show up yet. The instructions say to press the erase button. Well, I hadn't held the button long enough apparently. Windows will eventually detect and then you will see the BOSSA driver appear in the device manager. I may have figured this out sooner had I left the PanelDue plugged into the screen, but since I'm using a 7" screen, I was concerned about power - there was nothing wrong with having it plugged in, and it went black as it states in the instructions. 🤦 Now to plug back into the printers and see the fruits of my labor suffering.

@omtek Okay, thanks, this might be one for @chrishamm to have a look at, in that case.

Ian

@droftarts thank you very much, I'll be sending the email shortly.

@adhanabal PanelDueFirmware supports image buttons. The homing buttons are examples. You could modify PanelDueFirmware to support additional buttons. There is no facility to use images uploaded from the Duet on buttons.

@mfs12 said in PanelDue Firmware 3.5.0-rc9 released:

Hey, i can't reproduce it. Everythng shows up as expected. Is there a problem with your folder structure on the sd card? do you have some unusual folder nesting?

Just wanted to come back around to this, i had updated to the 3.5.0 release and saw the same thing. I noticed something when using DWC to move a gcode to a folder, i got a permissions error. I ssh into my pi and checked the owner of everything in the gcodes, macros, and sys. Turns out that when I followed the instructions to update the os on the pi (involved backing up those items, imaging the sd card, and sftp the backed up files back) that those items took on the owner of the user i was connected through sftp with, which was pi. I went through gcodes, macros, and sys and did 'sudo chown dsf:dsf folderorfilename' and now everything is showing up normally for me in Panel Due

I decided to test a little further back to see if it was firmware issues or hardware. I'm definitely leaning towards hardware issue.

I went and flashed the PanelDue V3.0a board with firmware 1.17 which was the oldest firmware I could find for V3 and connected it to the SSD1963QL9AU608F LCD screen. No good. The backlight comes on, but it just flashes a white line across the edge of the LCD screen. This PanelDue V3.0a refuses to drive this specific 7" LCD. It works with the PanelDue V1.1 and PanelDue V2.0 boards but does not work with the PanelDue V3.0a board. Go figure, but there must be something different on this specific LCD panel that's not compatible with this newer board.

Either way, I have a fix and will just swap the LCD panels on the machines until I get combinations that work.

@PDBeal See: https://forum.duet3d.com/topic/35545/3-5-1-error-pop-stack-underflow-on-aux?_=1715676158188

@bpatt it's on GitHub https://github.com/Duet3D/PanelDueFirmware

will be released with 3.5.0-rc9.

@astra Sounds like this display has no firmware running on this. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue and especially the "update via USB" section to flash the firmware.