*Unofficial* 1.22.0-gtj1 Release *Unofficial*



  • nologo.bin - the same problem. Interesting that after boot it works for a 1-2 seconds, even the touchpad is responsive, then it crashes.



  • When you first started the panel after the firmware install, were you asked to recalibrate your screen?



  • @gtj0 Yes, it asked my ever time when I re-flash the firmware.



  • @dragonn OK, I'm looking through what I changed to see where the issue might be. It's odd though since you have the same panel resolution (800x480) as the 7i I have. When you first start the panel, see if you can quickly get to the Setup screen, then tap "Macro Columns" and set it to 1. Then go back the Control screen and see if it still crashes.



  • @gtj0 I set macro columns to 0 and then it works. Hmmm I think I see what is the problem, when I entered settings after flashing from old to new version marco columns was set to 255 :D. And it doesn't work when I set macro columns to auto, then it shows 255 too :P.



  • I found another bug - I clicked STOP on panel Due to kill my printer and disable heaters, the firmware did restart and DWC showed heaters active temp 0C but on PanelDue the didn't update, still was set 280C witch was not true.



  • @dragonn AhHa! OK, I made something unsigned when I should have made it signed. An easy fix and I'll do it tonight.



  • @dragonn said in *Unofficial* 1.22.0-gtj1 Release *Unofficial*:

    I found another bug - I clicked STOP on panel Due to kill my printer and disable heaters, the firmware did restart and DWC showed heaters active temp 0C but on PanelDue the didn't update, still was set 280C witch was not true.

    That's not a bug it's a feature 🙂
    I really dislike when the DWC forgets the temperature you've set when you turn the heater off. The PanelDue now remembers it but maybe I need to clear it if the printer has been reset and the PanelDue reconnects.



  • @gtj0 I think we need to be consistent across DWC and PanelDue if you want to have you work merged. It will be confusing if DWC works another way then PanelDue witch such critical things like heaters.



  • @dragonn You maybe right but I also don't want to go down the route of not being able to fix things in PanelDue that are "broken" in DWC. I'll revert that for now and maybe add an option in setup for it later.



  • Update to fix the Macro Column initialization and revert the "sticky temps" feature...

    https://github.com/gtjoseph/PanelDueFirmware/releases/tag/v1.22.0-gtj2


  • administrators

    @dragonn said in *Unofficial* 1.22.0-gtj1 Release *Unofficial*:

    @gtj0 PanelDueFirmware-v3-5.0.bin now I will try PanelDueFirmware-v3-5.0-nologo.bin

    If your panelDue controller is version 2.0 (check the back of the board) then you will need a v2 build, not a V3 build.



  • @dc42 Checked, I have v3.0 :P, didn't know 2.0 isn't the latest version.
    @gtj0 I can confirm that now everything works fine. About the sticky temps, I think we need a better solutions, maybe something like 'restore' button when you open the change temp menu.
    BTW. do you have plans to fix/add option to select with fan is controlled with PanelDue? My part cooling fan is connected to number 3 and not one :P. Would be nice to allow user selecting witch fan is controlled by PanelDue.



  • @dragonn said in *Unofficial* 1.22.0-gtj1 Release *Unofficial*:

    @dc42 Checked, I have v3.0 :P, didn't know 2.0 isn't the latest version.
    @gtj0 I can confirm that now everything works fine. About the sticky temps, I think we need a better solutions, maybe something like 'restore' button when you open the change temp menu.

    I am just about to upload a new version that has a new setup option for turning Sticky Temps on or off. There are a few other fixes as well.

    BTW. do you have plans to fix/add option to select with fan is controlled with PanelDue? My part cooling fan is connected to number 3 and not one :P. Would be nice to allow user selecting witch fan is controlled by PanelDue.

    I didn't but I could. There's only 1 more slot left for storing config data though so @dc42 would need to weigh in. At some point we may need to start reading extended config info from a file on the printer but I don't know how @dc42 would feel about that. 🙂



  • @gtj0 reading config from Duet could be a really good idea, but it wouldn't limit the usage of PanelDue with other firmware's.



  • I just created 1.22.0-gtj3

    https://github.com/gtjoseph/PanelDueFirmware/releases/tag/v1.22.0-gtj3

    Changes since last release:

    The ability to remember the active and standby temps when
    heaters are turned off is back and controlled by a new
    setup option. The default is "off" to be compatible with
    the DWC.

    Fixed an issue where the tool selection button wasn't
    cycling through the states correctly.

    Fixed an issue where the number of macro columns
    wasn't taking effect until a panel reset



  • @gtj0 Look like everything works fine for me :D.



  • @gtj0 the firmware number also changes on the display to 1.22 or not because I used it but remains at 1.21.3 release. stand



  • @dragonn said in *Unofficial* 1.22.0-gtj1 Release *Unofficial*:

    BTW. do you have plans to fix/add option to select with fan is controlled with PanelDue? My part cooling fan is connected to number 3 and not one :P. Would be nice to allow user selecting witch fan is controlled by PanelDue.

    @dragonn Is your part cooling fan assigned to a tool? If so, I could make the fan control automatically use the fan assigned to the active tool.

    @dc42 The output from M408 S3 just prints the integer equivalent of the fan bitmap instead of outputting a json array like the axis map. It's no big deal to work with the bitmap but would there be heartburn with backwards compatibility if I gave you a pull request to print the array instead of the bitmap?


  • administrators

    M408 S3 produces the same output as HTML request rr_status with type=1 so it can't be changed without breaking DWC. Besides, the status response is already rather long and I don't want to lengthen it unnecessarily.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.