Duet 2 Wifi- EBoB Struggles

JRCL

Trying to control a 4A stepper with my duet 2 wifi broken out with the EBoB, but I can't get it to turn. Not sure if my timing is incorrect or if my issue is elsewhere, but I can hear it making some noises. Using a DM542T driver

;CONFIG.G

; General preferences
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"RL1 V3"                        ; set printer name

; Network
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S0                                     ; disable FTP
M586 P2 S0                                     ; disable Telnet

; Drives
M569 P5 T2.5:2.5:10:10 R0            ; physical drive goes forward
M584 X5                         ; set drive mapping
M350 X16 I1                     ; configure microstepping with interpolation
M92 X80.00           			;set steps per mm
M566 X900.00           			;set maximum instantaneous speed changes (mm/min)
M203 X6000.00      				;set maximum speeds (mm/min)
M201 X500.00       				;set accelerations (mm/s^2)
M906 X800                  		;set motor currents (mA) and motor idle factor in per cent
M84 S30                         ;Set idle timeout

; Axis Limits
M208 X0 S1                        ; set axis minima
M208 X600 S0                      ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"             ;configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop

M122 Results
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-9F8TA-GJ4TD-6J9F2-3S86M-KQPL6
Used output buffers: 1 of 26 (11 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 73640 of which 0 recycled
Never used RAM 14604, free system stack 184 words
Tasks: NETWORK(ready,10.0%,237) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,85.3%,607) IDLE(ready,4.7%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:19 ago, cause: software
Last software reset at 2023-08-10 18:45, reason: User, GCodes spinning, available RAM 14532, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 102.5, current 102.6, max 103.4
Supply voltage: min 23.9, current 24.1, max 24.3, 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
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-08-10 18:46:17
Cache data hit count 734607754
Slowest loop: 4.39ms; fastest: 0.17ms
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.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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: 15.39ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
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.26
WiFi MAC address e8:68:e7:7f:6d:8e
WiFi Vcc 3.43, reset reason Power up
WiFi flash size 2097152, free heap 23728
WiFi IP address 192.168.1.159
WiFi signal strength -39dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

T3P3Tony

please show how you have the EBOB wired to the driver.

JoergS5

@JRCL said in Duet 2 Wifi- EBoB Struggles:

a DM542T driver

microsteps and current are set at the DM542, maybe your switches are set wrong. You can check SW4 as well which could be set half current.

JRCL

Ended up switching to a Duet 3 for more connections anyway, never figured this one out