New PanelDue firmware 1.21RC4 available
-
David
Have you built the 7.0C Version for the V2 boards?
I have downloaded it and flashed the board but it is still showing as 1.20B1.
Tried it 3 times just in case!
Doug
I thought I had, but I've just rebuilt it and re-uploaded it. So please try again.
-
I had difficulties at first - turned out to be simply a bad USB cable - new firmware seems to be working well. May have more feedback after I've used it a bit.
-
I'd submit a pull request for this, but I'm currently at my paying job so can't fork, edit, etc:
A couple of suggestions.
First, move the code that dims the brightness to a simple function. A decent compiler will inline this, so there shouldn't be any overhead for a function call, but it's cleaner and more consistent with existing code such as RestoreBrightness() being a function.
In PanelDue.hpp, add a declaration for:
[c]extern void DimBrightness(void);[/c]In PanelDue.cpp (and hpp), add a new function:
[c]extern void DimBrightness(void)
{
Buzzer::SetBacklight(nvData.brightness >> 3); // or just /8.
isDimmed = true;
}
[/c]
Also in PanelDue,cpp, around line 1321 in main(), call DimBrightness() instead of calling setbacklight() and setting isdimmedNext, because the loop in main() is basing the dimmer timeout on the lastActionTime variable (and I don't see it being used for any other purpose), it might be a good idea to call "lastActionTime = SystemTick::GetTickCount()" within RestoreBrightness() (so the timers work when RestoreBrightness() is called from UserInterface.cpp, for example,)
Finally, in PanelDue.cpp, in the function SetStatus(), it might be nice to turn the backlight back on if/when the printer status changes. In that function, within the conditional for (newStatus != status), call RestoreBrightness()
(None of this is tested at all. I was just browsing your github during my lunch…)
-
@NYT - whats the content of your clear heater faults macro (I am just being lazy)
-
-
Thanks.
-
David
Have you built the 7.0C Version for the V2 boards?
I have downloaded it and flashed the board but it is still showing as 1.20B1.
Tried it 3 times just in case!
Doug
I thought I had, but I've just rebuilt it and re-uploaded it. So please try again.
Tried this again and it still shows as 1.20Beta 1 it's as if the Github hasn't refreshed time stamp shows same as the original files as well on the Git.
Doug
Ignore that My bad I was getting them from https://github.com/dc42/PanelDueFirmware/tree/master/Release/Edge-old which tho are labeled as 1.20rc4 they are all different file lengths from the ones in the release folder. Pays to follow links rather than go to the source GitHub
-
Please confirm that you are getting it from here https://github.com/dc42/PanelDueFirmware/releases/tag/v1.21RC4.
-
Please confirm that you are getting it from here https://github.com/dc42/PanelDueFirmware/releases/tag/v1.21RC4.
See my edited post above all now sorted thanks.
Doug
-
I see what happened. I renamed the Edge folder to Edge-old because I didn't want people using it; but the renaming means that github thinks the files init are new, so it has labeled then as being from the beta4 commit.
-
Is it necessary to update to a version 3 board if I want to add a splash screen to my 7" paneldue? I have a V2 currently.
-
I see what happened. I renamed the Edge folder to Edge-old because I didn't want people using it; but the renaming means that github thinks the files init are new, so it has labeled then as being from the beta4 commit.
Well I am getting old and senile David so get easily confused. but all sorted now
-
That depends:
- The binary + splash screen compressed image must together fit into the flash memory of the processor
- V2 boards may have ATSAM3S2B processors (128Kb flash), or ATSAM3S4B processors (256kb) flash
If your V2 board is the 256Kb flash version, you can add a splash screen. If it is the 128Kb version, you can only add a splash screen if you are using the 4.3" display and the splash screen compresses well.
-
Thanks David, I will check the memeory on my Paneldue tonight. I may just upgrade anyway due to the other features of V3.
-
I'd submit a pull request for this, but I'm currently at my paying job so can't fork, edit, etc:
Posted a pull request for two of the changes (that don't change any functionality.)
-
I've installed the update today and I like the macro reachability, but the issue with dialogs is not solved and I really, really don't like the dimming "feature". Please insert something in the settings tab to switch it off!
-
I've installed the update today and I like the macro reachability, but the issue with dialogs is not solved and I really, really don't like the dimming "feature". Please insert something in the settings tab to switch it off!
I just submitted a github pull request that includes this (as well as an option to only dim if the printer status is idle.)
-
Hi,
I am having trouble flashing my PanelDue7i
I am using same Bossac tools that work with my older 7" PanelDuet V1.0 which work with that.
On a W10 64 bit PC:
Connect 7i to PC with uUSB cables, get the usual enuneration beeps, device manager reports Bossa Program Port on com3
I do the erase reset on the 7i, screen goes blank,
Go to terminal mode and runC:\3D_Printer_Stuff\Bossac>LISTCOMPORTS
COM3 - Arduino LLC (www.arduino.cc) - USB\VID_03EB&PID_6124\6&2A0F59D2&0&4C:\3D_Printer_Stuff\Bossac>bossac.exe –port=COM3 -e -w -v -b PanelDue7i.bin
No device found on COM3Repeating the above with 7" PanelDuet V1.0 and relevant bin file works.
Any ideas ?
Thanks.
-
I've found in my own experiences with a normal 5 inch (paneldue v3) that sometimes you just have to wait a minute or two after the COM port shows up before bossac works. Until then, even though device manager shows the port properly, bossac won't work with it.
-
You might also consider jumping to RC5 which was just made available about an hour ago.
