I'm in the process of building a Railcoreii using a Duet3D WIFI with the Duex5 for the 3 Z axis motors and a BL Touch. I have been struggling with the Duex5 for the past week. I have only had the board show up with M115 a couple times. When it does, the Z axis works like expected, but cycle the power or restart the firmware and it is gone and the Z axis doesn't work. The correct VIN and GND wiring was followed. I've checked the IDE cable and reseated it many times, with power off of course. Looking for suggestions.
It may help to know the firmware version you're using as well as the results of an M122 diagnostic report.
Sorry forgot to include it.
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.02(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-12-24b1
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSJ-6JKDD-3SN6J-9SRV9
Used output buffers: 2 of 20 (7 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98620 of which 0 recycled
Exception stack ram used: 280
Never used ram: 6648
Tasks: NETWORK(ready,648) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
=== Platform ===
Last reset 00:02:02 ago, cause: power up
Last software reset at 2019-04-29 19:35, reason: User, spinning module GCodes, available RAM 6648 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 3.3ms, max retries 0
MCU temperature: min 35.1, current 36.8, max 37.0
Supply voltage: min 23.8, current 24.0, max 24.2, 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
Date/time: 2019-04-29 20:23:50
Cache data hit count 447133891
Slowest loop: 25.56ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 22.97ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.22
WiFi MAC address cc:50:e3:0d:2f:f5
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26464
WiFi IP address 192.168.3.2
WiFi signal strength -55dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
Have you wired the ground connections to the Due and DueX as described here https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring ?
Yes, I followed that wiring diagram. When the Duex5 is recognized the Z motors have some resistance to turn by hand like they should because the drives are enabled. When the board is not recognized, the motors turn freely like the power is off.
Veti last edited by
can you post the diagnostic output when all axis have moved a bit.
I don't know how to answer without sounding sarcastic, because I am truly looking for help, but I don't have all axis movement. I have only had all axis movement 3 times in the last week, but if I do get all axis movement I will for sure grab a diagnostic output.
Veti last edited by
can you post a picture of your wiring?
What might not be clear in the photo is the GND connection. There is individual 18awg GND from power supply to each board, but there is also a 18awg GND jumper between boards.
deckingman last edited by
@memyr6 Suggest you remove the individual GND wires from the PSU. In bold letter here https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features it says " Do not run separate ground wires from each terminal block back to the power supply unless the power supply is very close (less than 100mm) to the Duet 2 and Duex." Looking at the picture, I'd say your additional GND wires are longer than 100mm.
whosrdaddy last edited by
@deckingman Looking at the photo, I believe he has a GND connection between Duet and Duex, no?
bot last edited by bot
It sounds like he has both. I’m not an electronics expert, but I hear alarm bells ringing.
It also looks like you (op) have two ferrules jammed into the same screw terminal. That seems janky. Put two wires into one ferrule.
whosrdaddy last edited by whosrdaddy
Yes indeed, I did not see that he has a second ground connection on the Duex5.
@memyr6, there are 2 extra wide ferrules delivered in the wiring kit, you should use those to connect the Duex5
like depicted here: https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring
I have removed the extra ground I had and used the twin lead ferrule, no change. As a test, I also removed all wiring from the 2 boards except for the ribbon cable and powered the 5V through the USB, M115 still shows no DUEX5. I'm assuming it would show up like described in the commissioning section??
@memyr6, please ask you supplier to replace your DueX and the ribbon cable. It sounds to me that it is not always responding to interrogation from the Duet,