PanelDue warnings and errors after homing

droftarts

@Inno-3D I'd guess a corrupt SD card, or your PanelDue is not communicating properly with the board, so check PanelDue wiring. Are you using the SD card slot on the PanelDue?

Please send M122 and post the report. To test the SD card, see https://duet3d.dozuki.com/Wiki/SD_Card#Section_Troubleshooting_SD_Card_issues

Please also post your homeall.g file.

Ian

A Former User

Are you not seeing the same errors in DuetWebControl?

Inno 3D

@droftarts I've checked the wiring and it seems that there is everything ok.

No I don't using the SD card slot on the PanelDue.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N8PS0-7JTDG-3SJ6N-TBB7R
Used output buffers: 3 of 24 (10 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93880 of which 20 recycled
Exception stack ram used: 264
Never used ram: 8928
Tasks: NETWORK(ready,384) HEAT(blocked,1248) DUEX(suspended,160) MAIN(running,1848) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:52 ago, cause: power up
Last software reset at 2020-08-04 14:15, reason: User, spinning module GCodes, available RAM 8456 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 25.7, current 30.8, max 31.3
Supply voltage: min 18.7, current 23.3, max 23.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2020-08-05 11:32:40
Cache data hit count 302554629
Slowest loop: 5.17ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.72ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address ec:fa:bc:5b:45:8f
WiFi Vcc 3.37, reset reason Unknown
WiFi flash size 4194304, free heap 24288
WiFi IP address 192.168.88.69
WiFi signal strength -62dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 1, 0.35 reads/min

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Mon Aug 03 2020 15:55:28 GMT+0200 (Mitteleuropäische Sommerzeit)
G91                      ; relative positioning
G1 H2 Z5 F6000           ; lift Z relative to current position
G1 H1 X-1505 Y2505 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y-5 F6000       ; go back a few mm
G1 H1 X-1505 Y2505 F360  ; move slowly to X and Y axis endstops once more (second pass)
G90                      ; absolute positioning
G1 X15 Y2485 F6000         ; go to first bed probe point and home Z
G30                      ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91                     ; relative positioning
;G1 Z5 F100              ; lift Z relative to current position
;G90                     ; absolute positioning

@bearer no in the DuetWebControl there isn't any error or warning

Many Thanks

Phaedrux

Are you using the 4-wire cable or ribbon cable? How long is it? Is it running next to other wires?

nhof

This is certainly a comms issue of some sort. The paneldue is normally send M408 commands regularly and reads back the status. Because you are constantly getting M508, M4080, etc it's probably the serial signal that's getting messed up.

The stepper motors are enabled when you command motion for homing, and these tend to be electrically noisy. You can check to see if any motor cables run near the paneldue cables, this could cause interference. You should also check the paneldue cables to make sure all the crimps are making good contact, there is no damage, it's plugged in securely etc. Also make sure the cable is not too long. My money points towards being related to the motor cabling as you say there isn't any issue until you move the system, and generally the motors will not be enabled on startup until you command a move.

You might also be able to reduce the baud rate of the paneldue and the duet, slower baud rates might reduce the bit errors. You can reduce the baud rate by using the M575 P1 command in your config.g, and selecting the same baud rate on the paneldue setup menu. This would be a workaround rather than a fix though.

Inno 3D

@Phaedrux I'm using the 4-wire cable. I think it's 2.5 m long. Yes it's running next to other cables.

I think, I will test it whitout any cables next to the PanelDue Cable.

@nhof no there isn't any motor cable which is near the PanelDue cable. I will check the cable and give fedback.

How I said, the cable is 2.5m long. Is it too long?

Ok I will check the cable and give feedback.

Many thanks for help!!

dc42

@Inno-3D said in PanelDue warnings and errors after homing:

How I said, the cable is 2.5m long. Is it too long?

That depends on how thick the wires are. The resistance per conductor should not exceed 0.1 ohms over that 2.5m length.

Inno 3D

I had two other wires next to te PanelDue wire.

I've removed the wire and now It's working perfectly!

Many thanks for your help!!

dc42

@Inno-3D said in PanelDue warnings and errors after homing:

I had two other wires next to te PanelDue wire.
I've removed the wire and now It's working perfectly!

Were they stepper motor wires? Those are the worst for creating interference in adjacent wiring.

mitch

I am getting strange errors on the PanelDue as well. It started after my upgrade to 3.1.1. I just found this post and I am curious if it is now just corruption going to the PanelDue. Can that corruption between the paneldue potentially cause strange print behavior as well?

After the upgrade to the latest FW I had to set the panel baud in config.g
M575 P1 S1 B57600

Panel seems to work fine other than these random messages while printing.

Phaedrux

@mitch Please start a new thread.