topic_solved PanelDue 3.3 Button colors and print status bar not updating.
Nurgelrot last edited by
I have 2 PanelDues v3 (fysetc version) running the new 3.3 release of the paneldue firmware. When using the Dark Theme1 The Home buttons don't always update their color to indict that the axis are homed. Also the Progress bar on the Status page for a print doesn't update - never fills in as the print progresses. Did something change in a config I can update or anything else I'm doing wrong? Or is this something that got missed?
Where do you connect them to? Can you share screenshots and a step by step process how to reproduce? Does you printer support Object Model?
Nurgelrot last edited by
@mfs12 Both of them are connected to Mini5's one via the ribbon cable the other via io.0. I just did what I should have done before posting here and re-flashed them. Same print as last night on the one with the ribbon cable is now showing the green progress bar correctly. The home buttons not updating has been random I'll try and snag a picture and config/status dump if/when it happens again. Hopefully it was just me and I've fixed whatever I did by re-flashing. So nice to be able to do it right from DWC.
These where both new displays So the first flash was from 1.24 (I think) to 3.3 via Bossa. The re-flash was via DWC. Who knows if that had anything to do with it.
Thanks I'll post here if I can make it show up again.
Hey @nurgelrot, thanks for reporting back.
I mark this topic solved for now. If it re-occurs feel free to reopen it again.
Nurgelrot last edited by Nurgelrot
@mfs12 I was able to get a photo of it this time. about halfway in nothing is showing on the progress bar. If navigate to another tab it it will update -second shot. Seems to be random when its going to choose to not update And like I said sometimes it the homing buttons not updating but I haven't got a shot of that yet. PanelDue Firmware Version 3.3.0 This printer is using the ribbon cable but it happens on serial too.
And a m122 if its useful...
m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus Ethernet (SBC mode) Board ID: JMA1H-6296U-D65J0-40KM2-NP03Z-78M5J Used output buffers: 1 of 40 (27 max) === RTOS === Static ram: 102724 Dynamic ram: 93056 of which 0 recycled Never used RAM 47924, free system stack 120 words Tasks: SBC(ready,38.7%,324) HEAT(notifyWait,0.3%,344) Move(notifyWait,2.1%,274) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,357) CanClock(delaying,0.1%,338) TMC(notifyWait,6.6%,80) MAIN(running,44.4%,527) IDLE(ready,0.0%,29) AIN(delaying,7.8%,264), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 08:53:52 ago, cause: power up Last software reset at 2021-08-06 10:24, reason: User, none spinning, available RAM 47924, slot 2 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 32032107, completed 32032105, timed out 0, errs 0 Step timer max interval 1458 MCU temperature: min 23.9, current 43.9, max 45.2 Supply voltage: min 0.1, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 7782, standstill, SG min/max 0/406, read errors 0, write errors 0, ifcnt 23, reads 44781, writes 23, timeouts 0, DMA errors 0 Driver 1: position 8562, ok, SG min/max 0/416, read errors 0, write errors 0, ifcnt 23, reads 44781, writes 23, timeouts 0, DMA errors 0 Driver 2: position 8240, standstill, SG min/max 0/164, read errors 0, write errors 0, ifcnt 21, reads 44782, writes 21, timeouts 0, DMA errors 0 Driver 3: position 0, ok, SG min/max 0/510, read errors 0, write errors 0, ifcnt 17, reads 44786, writes 17, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 44795, writes 9, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-09-06 01:06:16 Cache data hit count 4294967295 Slowest loop: 90.16ms; fastest: 0.07ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 4224869ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 57738, completed moves 57711, hiccups 0, stepErrors 0, LaErrors 0, Underruns [2, 0, 0], CDDA state 3 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.5 Heater 1 is on, I-accum = 0.5 === GCodes === Segments left: 1 Movement lock held by null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G1 X90.310997 Y104.796997 E0.024420" in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue* is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 288203, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 160161/0/0 Tx timeouts 0,8,160160,0,0,128032 last cancelled message type 30 dest 127 === SBC interface === State: 4, failed transfers: 1, checksum errors: 1 Last transfer: 4ms ago RX/TX seq numbers: 35024/35024 SPI underruns 0, overruns 0 Disconnects: 0, timeouts: 0, IAP RAM available 0x10b2c Buffer RX/TX: 1520/2776-0 === Duet Control Server === Duet Control Server v3.3.0 File: Buffered code: G1 X90.311 Y104.797 E0.02442 Buffered code: G1 X91.025 Y105.511 E0.03421 Buffered code: G1 X91.926 Y105.970 E0.03420 Buffered code: G1 X92.924 Y106.128 E0.03422 Buffered code: G1 X93.922 Y105.970 E0.03421 Buffered code: G1 X94.823 Y105.511 E0.03420 Buffered code: G1 X95.537 Y104.797 E0.03420 Buffered code: G1 X95.997 Y103.896 E0.03423 Buffered code: G1 X96.101 Y103.239 E0.02251 Buffered code: G1 X96.251 Y103.239 E0.00509 Buffered code: G1 X96.251 Y103.275 E0.00122 Buffered code: G1 X97.665 Y103.275 E0.04786 Buffered code: G1 X97.665 Y106.621 E0.11326 Buffered code: G1 X97.682 Y106.621 E0.00057 Buffered code: G1 X97.675 Y116.865 E0.34675 Buffered code: G1 X95.125 Y116.810 E0.08633 Buffered code: G1 X95.125 Y108.171 E0.29243 Buffered code: G1 X95.092 Y108.171 E0.00112 Buffered code: G1 X95.092 Y106.849 E0.04475 Buffered code: G1 X95.089 Y106.389 F9000.000 Buffered code: G1 X94.945 Y106.158 Buffered code: G1 F1388 Buffered code: G1 X95.005 Y106.143 E0.00036 Buffered code: G1 X95.069 Y106.097 E0.00046 Buffered code: G1 X93.719 Y106.398 F9000.000 Buffered code: G1 F1388 Buffered code: G1 X93.332 Y106.428 E0.01125 Buffered code: G1 ==> 1280 bytes Code buffer space: 1392 Configured SPI speed: 8000000Hz Full transfers per second: 4.77, max wait times: 42.0ms/0.0ms Codes per second: 1.34 Maximum length of RX/TX data transfers: 3448/1664 File /opt/dsf/sd/gcodes/NEW BMG Direct Drive wBLTouch_2h42m_0.2mm_245C_PETG_ENDER3.gcode is selected, processing
Hey @Nurgelrot, I wrapped up your problem and trying to investigate it.
In general quite a lot changed in recent versions. Especially from 1.24 but also from 3.2.11. And there will be another iteration with 3.4.0.
Feel free to check the releases on github for major changes:
I tried to wrap up your process... is this accurate?
- hardware PanelDue v3 (fysetc),
- firmware PanelDue 3.3.0,
- select dark theme 1
- start a print
- wait status page or home buttons are not updated
- everything is properly updated all the time
- does this happen also with other themes?
- how long is you ribbon cable?
- do you get any errors in console tab?
- are standing in setup tab? (in this tab no communication to RRF is done!!!)
Nurgelrot last edited by Nurgelrot
@mfs12 Okay I figured this out and its okay to mark it resolved (it was never an issue hahahaha I'm an idiot) The screen isn't updating cuz it's in it's idle and dimmed mode. The lighting in my shop is such that it near impossible to tell the difference between the dim mode and the not dim mode most of the time. So I'd start a job from the web console and walk over to the display later that has been dim the whole time and the bar wouldn't be updated. Soon as I touch the screen it updates. Same with the home buttons. looks like it not homed but as soon as the screen wakes up the buttons assume their proper colors.
Sorry for the noise.
@nurgelrot it should still update in dimmed mode, just not quite as quickly.