PanelDueFirmware 3.2.4 released
-
@wilriker did another 5 flashes at each baud rate; 7i seems to only occasionally not erase; but consistently does not reset when on 57600. 115200 is all good. I can try to dig out logic analyzer to log the serial traffic later if of interest.
But as long as its not the intended behaviour I'm less confused:)
-
My (genuine) 7i also does not seem to reset after a flash (it always seems to erase and program ok). I'm running the 7i at 57600 and have not (yet) tried changing that to 115200 (will do so later if it helps). FYI I'm running this on the LPC version of RRF and had assumed the lack of reset was down to some problem with my port of the code, but perhaps that is not the case?
-
My v3 non-integrated PanelDue configured for 57600 baud does erase and then flash successfully, but never resets after flashing.
-
I think I found the reason why it did not Erase-and-Reset in the beginning and/or reset at the end for some users. Currently testing.
-
@wilriker poke me if you want me to test on my troublesome hardware, genuine and not so genuine (don't think that makes a difference in this case?)
edit: wilriker seems to have fixed in latest rrf 3.02-dev on git
-
@Karabox said in PanelDueFirmware 3.2.4 released:
@wilriker said in PanelDueFirmware 3.2.4 released:
You could try to use the
PanelDue-v3-5.0.bininstead. It might work since it uses a slightly different display driver.But note that for clones there is no support.
You were right, the firmware came up, the red color is in place. Thank you very much!
I cannot get my fysetc unit to connect now thative upgraded the duet rrf3 fw...
tried the v3-5.0 bin but to no avail ... jsut sits there "connecting" no use ... not communicating with the duet. cant see the files or move the axis ...
was working pretty well before....
-
Did u actually get your fysetc paneldue workign with the other variant of fw - and comunicating the the duet - or just the color changes work? I got hte different colors and the lcd functions on the usb - but it cant seem to connect to the duet on rrf 3.2-beta4
-
@SputnikOC3d said in PanelDueFirmware 3.2.4 released:
but it cant seem to connect to the duet on rrf 3.2-beta4
if you upgraded from before 3.1 check out the release notes https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-310
-
@bearer
TY - I was on 3.1.1 RRF for the duet but had not updated the paneldue fw for quite a while
-
@bearer said in PanelDueFirmware 3.2.4 released:
@SputnikOC3d said in PanelDueFirmware 3.2.4 released:
but it cant seem to connect to the duet on rrf 3.2-beta4
if you upgraded from before 3.1 check out the release notes https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-310
Found another thread / post where you identified the issue :
Ive got no M575 P1 S1 B57600
Think thats the issue ?
TY ...
-
Solved it - missing vital COM line in config.g
M575 P1 S1 B57600
Release notes people ... READ them
-
Did anyone notice small dot's in corners, when screen saver is active? Are they suppose to be there?
-
@wilriker back to the PanelDue refreshing the way it now does.. with all due respect, I don't like it.. maybe I don't understand the problem it is trying to solve though. However, it just seems to now refresh all the time. Where it really bugs me is on the Move screen - it seems to blink after every button press.. sometimes multiple times.
-
@oozeBot said in PanelDueFirmware 3.2.4 released:
@wilriker back to the PanelDue refreshing the way it now does.. with all due respect, I don't like it.. maybe I don't understand the problem it is trying to solve though. However, it just seems to now refresh all the time. Where it really bugs me is on the Move screen - it seems to blink after every button press.. sometimes multiple times.
Yep. The lag on the refresh is not as pleasant.
-
@oozeBot Either there is a bug I have missed it I just not get what you mean. Could perhaps make a video?
Only fields changing there values should see a refresh. Are you saying you see full refreshes all the time?
-
@wilriker here you go: https://vimeo.com/490200847
-
@oozeBot Thanks. This is definitely not intended behavior. I have a theory what is causing this and will investigate.
-
@wilriker Glad to know this isn't intentional! Thanks for the hard work on this..
-
@oozeBot I found it and have fixed it in the source code already. I will probably release a new version early next week.
-
(If you push the changes to git it might get tested, in a totally hypothetical scenario)
((in a less hypotetical scenario; kudos!))