Communication jamming between PanelDue and Duet 2 WiFi

Triet

I am using a BLV Cube delivered as a kit by FYSETC , which includes a Duet 2 WiFi board and a PanelDue 5 Display. It also features Neoring LEDs controlled by an Arduino mini pro module, which is connected to the Duet:
https://www.fysetc.com/en-de/products/fysetc-blv-led-light-control-panel-arduino-mini-pro-module-for-blv-mgn-cube-3d-printer
The PanelDue is connected to the Duet via flat ribbon cable. The other 4 pins connected is used for the Arduino. The Arduino LED Controller is hooked on the transmit wire of the Duet, and depending of the data it captures, the display of the LED is adapted.

The display was working OK at first but after upgrading the firmware of all components to the current version, the PanelDue can only send data but not receive. Only if I disconnect the Neoring controller then the PanelDue can send and receive data as it should.

If anyone has an idea how to overcome this issue I would very much appreciate. I think there should be a fixed firmware for the Arduino board somewhere.

I assume that the interference is due to different voltage levels. If that is the case, would an optocoupler be a solution?

Thanks in advance.

droftarts

@Triet Please note that your kit will have come with a clone Duet 2 WiFi board, so there is a limit to what support we can offer.

What firmware for the Duet and PanelDue where you on before, and what are you on now?
When you say "The other 4 pins connected is used for the Arduino" I assume you mean the PanelDue header on the Duet?

Please post your config.g file (or the section that deals with the configuration of the PanelDue and the Arduino), and the response to M115. Also please post an example of the commands you send to change the LEDs.

You might be seeing a similar problem to the one seen here: https://forum.duet3d.com/topic/33976/paneldue-cnc-pendant-pass-trough-not-working
A recent change in the PanelDue firmware has changed how the PanelDue and Duet communicate, and enforces CRC rather than checksum to validate data sent between the Duet and PanelDue. It may be messing with the Arduino. The current workaround is to use PanelDue firmware 3.4.0 https://github.com/Duet3D/PanelDueFirmware/releases/tag/3.4.0. This was from before the CRC feature was implemented. Let me know if that helps.

Ian

elmoret

@Triet have you asked Fysetc for help? What was their response?

Triet

@elmoret said in Communication jamming between PanelDue and Duet 2 WiFi:

@Triet have you asked Fysetc for help? What was their response?

I have tried to register on ther Support site, but something is going wrong and I can't get the privilege to write a message. Haven't given up yet though.

elmoret

@Triet Sounds frustrating!

darkwingbreydin

@Triet said in Communication jamming between PanelDue and Duet 2 WiFi:

I am using a BLV Cube delivered as a kit by FYSETC , which includes a Duet 2 WiFi board and a PanelDue 5 Display. It also features Neoring LEDs controlled by an Arduino mini pro module, which is connected to the Duet:
https://www.fysetc.com/en-de/products/fysetc-blv-led-light-control-panel-arduino-mini-pro-module-for-blv-mgn-cube-3d-printer
The PanelDue is connected to the Duet via flat ribbon cable. The other 4 pins connected is used for the Arduino. The Arduino LED Controller is hooked on the transmit wire of the Duet, and depending of the data it captures, the display of the LED is adapted.

The display was working OK at first but after upgrading the firmware of all components to the current version, the PanelDue can only send data but not receive. Only if I disconnect the Neoring controller then the PanelDue can send and receive data as it should.

If anyone has an idea how to overcome this issue I would very much appreciate. I think there should be a fixed firmware for the Arduino board somewhere.

I assume that the interference is due to different voltage levels. If that is the case, would an optocoupler be a solution?

Thanks in advance.

I have the same problem with my fysetc kit bought in december 23. My fix is to use one of the three switches to power on/off the neopixel board. When off, the paneldue works like it should, i can use makros and both sd slots. When on the neopixels show the status, but the paneldue works not correct.

oliof

If these are neopixel LEDs, you could cut out the Arduino middleman and drive them directly off of CONN_LCD

https://docs.duet3d.com/User_manual/Connecting_hardware/IO_Neopixel_DotStar#connections

That will require adjustment of the macros setting the LEDs but will likely be a better setup overall.