This is another Neopixel project: https://github.com/mule1972/NeoPixelBLVmgn
I wrote the readme for the project a while ago, and I think it outlines the hardware part of the serial communication with the Duet well.
You do need to enable the serial port on the Duet. See the "Changes to your Duet Configuration" section of the readme. (Edit: I see you've already figured that out! It is a great read though.)
@dc42 said in 12864 Display Unresponsive on Preheat Page 3.3b2:
I have fixed the RRF code in the soon-to-be-released 3.3beta3
Wow! Your excellent support continues to amaze me! 
@dc42 Thanks a lot for your time! I really do appreciate it, and will update the repository soon with the fix for that bug in the display file.
@leckietech Unfortunately, I haven't figured anything out yet.
If you have the time to troubleshoot it, I'd greatly appreciate it! I'm simply too busy to work with it right now.
@dc42 Have you and your team had a chance to look into this? It's no rush, but my curiosity is getting the best of me! Thanks!
@caviara said in Duet 3 Mini 5+ : Initial announcement:
In order not to make bad commercial for the reseller i will reply on private to you.
As an average guy running a small business, I really appreciate that attitude. Keep it up!
@Phaedrux said in Can I run a Duet2 Wifi without the module?:
inquire about a refurbished unit
Are these available to the general public to buy without an exchange?
@Phaedrux said in 12864 Display Unresponsive on Preheat Page:
Would you be able to test with 3.3beta2?
Absolutely! I can confirm that it behaves in exactly the same way. Here's another M122 dump:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.3beta2 running on Duet Maestro 1.0
Board ID: 08DAM-9F9GA-J24TD-6J9DL-3SW6K-T71YV
Used output buffers: 1 of 24 (16 max)
=== RTOS ===
Static ram: 21348
Dynamic ram: 74636 of which 0 recycled
Never used RAM 19512, free system stack 210 words
Tasks: NETWORK(ready,253) HEAT(delaying,335) TMC(notifyWait,116) MAIN(running,469) IDLE(ready,21)
Owned mutexes:
=== Platform ===
Last reset 00:06:26 ago, cause: power up
Last software reset at 2021-03-06 11:14, reason: User, GCodes spinning, available RAM 18776, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 1,1,1
MCU temperature: min 15.9, current 17.2, max 23.9
Supply voltage: min 0.0, current 24.7, 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 0, standstill, read errors 0, write errors 0, ifcnt 8, reads 64281, writes 8, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, read errors 0, write errors 0, ifcnt 8, reads 64281, writes 8, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, read errors 0, write errors 0, ifcnt 8, reads 64281, writes 8, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, read errors 0, write errors 0, ifcnt 9, reads 64280, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, read errors 0, write errors 0, ifcnt 8, reads 64281, writes 8, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-03-12 15:14:42
Slowest loop: 79.93ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest read time 3.6ms, write time 1.4ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 1 -1, chamberHeaters = 2 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.0
Heater 2 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Filament sensors ===
Extruder 0 sensor: ok
=== Network ===
Slowest loop: 30.73ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
Interface state active, link 100Mbps full duplex
Great!
If the Arduino's RX light blinks, then it should be getting a signal. That likely means it's not running the code. How do you know the Arduino isn't receiving data? Because the NeoPixels don't light?
Definitely check the serial monitor. 
Good afternoon!
I routinely use my set of display files (Github) for the 12864 display on my Duet Maestro, but recently the preheat page stopped working. When you open it the text is sometimes jumbled and it always freezes up the display. The easiest way to fix it is to simply reset the board. I did not edit the display code when the issue happened.
I have two different machines with the issue (both Maestros, one with 3.2-RC2 and another with 3.2.2). Another user just reported on Github that he's having the issue as well.
Below I've attached the code and also an M122 dump after it freezes. All other pages appear to work well.
Thanks for your help!
Jadon
; Duet 12864 Menu Files
;
; This is a set of menu files for running a 12864 display with a duet3D control board.
;
; Written by Jadon Miller - 2/27/2019
; Partially adapted from the work of tinkerlifeprojects on Github.
;
; File "preheat"
;
; The goal of this menu is to make it easy to preheat the printer. It
; has a group of buttons to set the temperature and the current temperatures
; at the bottom with a shortcut to print/resume.
;
; Note: To modify the preset temperatures, there are two places to change for
; each temperature. The "T" parameter determines what is shown on the button
; and the number after the "S" is the temperature sent to the firmware. For example,
; if I wanted to change the second bed heater button to 45C, I would change this line:
;
; button C46 W19 T"40" A"M140 S40"
;
; To this line:
;
; button C46 W19 T"45" A"M140 S45"
;
; The hotend buttons work the same way.
;
; Note: you may need to change the gcode commands for each button if you don't use the
; default heater configuration.
; --------------- Header ---------------
text R0 C0 W63 F0 H1 T"Preheat"
image L"imgs/vline.img"
button W64 F0 T"Back" A"return"
image R11 C0 L"imgs/hline.img"
; --------------- Preheat Bed ---------------
image R14 C6 L"imgs/bed.img"
button C23 W22 T"Off" A"M140 S0"
button C46 W19 T"40" A"M140 S40"
button C66 W19 T"50" A"M140 S50"
button C86 W19 T"60" A"M140 S60"
button C106 W19 T"70" V3 A"M140 S70"
; --------------- Preheat Hotend ---------------
image R27 C6 L"imgs/temp.img"
button C23 W22 T"Off" A"G10 P0 S0"
button C46 W19 T"130" A"G10 P0 S130"
button C66 W19 T"200" A"G10 P0 S200"
button C86 W19 T"210" A"G10 P0 S210"
button C106 W19 T"230" A"G10 P0 S230"
; --------------- Print Button---------------
; The "print" button is shown when not printing and "resume" when paused.
button R40 C0 W128 V5 T"Print" A"menu selectSD"
button R40 C0 W128 V6 T"Resume" A"M24|menu main"
; --------------- Temperatures ---------------
image R53 C0 L"imgs/hline.img"
; Bed Temperature
image R54 C5 L"imgs/bed.img"
value H2 N180
text T"/"
value N80
; Hotend Temperature
image L"imgs/temp.img"
value H2 N100
text T"/"
value N0
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.2-RC2 running on Duet Maestro 1.0
Board ID: 08DJM-956DU-LLMS4-7JKD2-3S07J-1VPQJ
Used output buffers: 1 of 24 (11 max)
=== RTOS ===
Static ram: 22292
Dynamic ram: 73632 of which 24 recycled
Never used RAM 18884, free system stack 216 words
Tasks: NETWORK(ready,206) HEAT(blocked,340) TMC(blocked,117) MAIN(running,467) IDLE(ready,20)
Owned mutexes:
=== Platform ===
Last reset 00:06:22 ago, cause: power up
Last software reset at 2021-03-11 07:40, reason: User, GCodes spinning, available RAM 18376, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 13.3, current 22.7, max 23.3
Supply voltage: min 0.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, read errors 0, write errors 0, ifcnt 8, reads 63622, writes 8, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, read errors 0, write errors 0, ifcnt 8, reads 63622, writes 8, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, read errors 0, write errors 0, ifcnt 9, reads 63621, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, read errors 0, write errors 0, ifcnt 8, reads 63622, writes 8, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, read errors 0, write errors 0, ifcnt 6, reads 63624, writes 6, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-03-12 13:49:00
Slowest loop: 81.19ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest read time 3.6ms, write time 0.6ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== 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 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 129.51ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(1) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
=== Filament sensors ===
Extruder 0 sensor: ok
``@gaweyo The system is designed to simply listen to the PanelDue communications. Details on the Github.
I'm really not sure what the issue could be, unless his Arduino isn't picking up the 3.3V signal.
@danny_v1 If you keep the Arduino connected to the Computer, open a Serial Port window, and set it to 57,600baud, does it display a string of text starting with "M" every few seconds? This would confirm that the Arduino is actually running the sketch.
Also, do you have an oscilloscope or someway to check if the arduino is getting a 3.3V serial signal?
Just to confirm, you need to have both the PanelDue and the Arduino hooked up at the same time for this sketch to work.
Did you try putting this gcode somewhere in your config.g file?
M575 P1 S0
I don't know if that will fix it or not. I have Neopixels connected, but not a PanelDue. (I actually wrote the instructions on the Github page.)
That command disables checksums, which are enabled by default. A checksum is a basic way of verifying that the receiver of a serial command heard correctly. The receiver runs a calculation on what he thinks he heard and replies with a number. The sender also calculates what that number should be and if they match, then all is well!
The PanelDue calculates these checksums, but the Arduino does not. That's why you have to disable them for an Arduino/Neopixel setup. Like I said, I don't know if you have to do that if you have a PanelDue connected though.
Good luck!
Jadon
Are the URXDO pins for the Panel Due 5V tolerant on the Maestro?
Thanks!
@dc42 Thanks for letting us know! This is very helpful, as I use the external SD card occasionally, and I have had some strange issues with it that I never looked into.
It seemed to just stop and become unresponsive at random times during the print. 
Thanks again!
@Veti said in Finally a viable filament diameter sensor!:
we have accelerometer measuring of ringing in the hotend to tune it.
This sounds interesting! Do you have a link with more details?
@fma said in Finally a viable filament diameter sensor!:
Does it really makes sens to compensate for such small differences in diameter?
Realistically, probably not, but diameter consistency is one of the worst problems with dirt-cheap filament. I think it would be one step closer to making printers as reliable as toasters, for example.
@dc42 said in How to add a graphical display to your printer!:
Duet 3 firmware does not currently support 12864 displays, but does support PanelDue.
Just to confirm, the Mini 5+ now includes both hardware and software support. Correct?
Thanks!
@Veti said in Finally a viable filament diameter sensor!:
it opens up the possibility to adjust the flow based on the reading.
Yeah. It just outputs the diameter over I2C. Unfortunately, he hasn't released the code yet, but he said he plans on making it open-source, and I'm sure he will soon!
I was surprised at how simple it is! There aren't any optics or expensive sensors as in some previous versions!
Has anyone seen Thomas Sanladerer's video about filament diameter? He designed an ingenious magnet-based filament diameter sensor.
Basically, it uses a lever with a magnet on the end running against the filament and varying in distance from a hall effect sensor. He says it's quite repeatable and exceeded his expectations.
I wonder if it would make any print quality difference if you'd rig it up to adjust the extrusion settings as the filament is fed into the printer.
Anyway, it's a really cool video with a lot of engineering behind it. Check it out!
Does anyone know of a bed leveling sensor that can withstand 80-90C heated chamber temperatures? I'd prefer a touch-based sensor like the BLTouch, but might have to go some other direction.
Thanks!
@garyd9 said in What firmware version are you using?:
@Phaedrux
I have 2 printers. One is running 3.2 (as I voted) and the other is running 2.05
My setup exactly.