No step signal on duet Meastro E2 and E3
-
Hi,
I have a CR20-pro with a duet maestro to which I want add an LDM extruder using a mechaduino closed loop stepper motor. For this I want to use the step/dir signal of E2. However I do not see any step signals on my scope when I rotate the extruder. The dir signal is working and when I switch my config to use drive 4 I am also able to turn a stepper motor. But for some reason I'm just not seeing any step signal if I set it to use drive 5. I added my config file below, am I doing something wrong in there? Should I maybe do something with E2_EN or E2_UART?
Best regards,
Martijn
; Configuration file for Duet Maestro (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.1 on Sun Jun 07 2020 16:33:27 GMT+0200 (Central European Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"CR-20 Pro" ; set printer name ; Network M552 P192.168.178.82 S1 ; enable network and set IP address M553 P255.255.255.0 ; set netmask M554 P192.168.178.1 ; set gateway M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S0 ; physical drive 0 goes backwards M569 P1 S0 ; physical drive 1 goes backwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S0 ; physical drive 3 goes backwards M569 P4 S0 ; physical drive 4 goes backwards M569 P6 S0 M584 X0 Y1 Z2 E3:6 ; set drive mapping M350 X256 Y256 Z256 E256:16 ; configure microstepping without interpolation M92 X1280.00 Y1280.00 Z6400.00 E1488.00:464 ; set steps per mm M566 X1500.00 Y1500.00 Z24.00 E300.00:300.00 ; set maximum instantaneous speed changes (mm/min) M203 X15000.00 Y15000.00 Z180.00 E6000.00:6000.00 ; set maximum speeds (mm/min) M201 X700.00 Y700.00 Z100.00 E5000.00:5000.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E1000:1000 I50 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X235 Y235 Z260 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S2 ; set endstops controlled by probe ; Z-Probe M950 S0 C"^zprobe.mod" ; create servo pin 0 for BLTouch M558 P9 C"zprobe.in" H10 F180 T9000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-56 Y-5 Z2.15 ; set Z probe trigger value, offset and trigger height M557 X15:175 Y15:215 S40 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 A140 C500 D10 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S150 ; set temperature limit for heater 0 to 150C M308 S1 P"e1temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 A318 C120 D3.3 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"fan0" Q100 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 S"FDM" D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"LDM" D1 F0 ; define tool 1 G10 P1 X-55 Y-30 Z-0.7 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous T0 ; select first tool -
-
Hi Veti,
Thank you for the link, I checked the comments there. I updated to RepRap firmware 3.2.2, but that didn't change anything. I also checked the enable pin, but it was fixed at 0V, instead of the 3.3V that was mentioned under your link. However I also ran M122 (see below) and that told me "Driver 5: position 0, assumed not present". So I guess drive 5 and 6 are not enabled unless a chip is detected through the uart? Do you maybe know if there any way to disable this and just have it output steps whether it detected a motor driver chip or not?
Martijn
M122 === Diagnostics === RepRapFirmware for Duet 2 Maestro version 3.2.2 running on Duet Maestro 1.0 Board ID: 08DJM-9X66L-LG3SJ-6JTDL-3SN6R-KSXQR Used output buffers: 3 of 24 (12 max) === RTOS === Static ram: 22284 Dynamic ram: 66720 of which 36 recycled Never used RAM 25792, free system stack 218 words Tasks: NETWORK(ready,206) HEAT(blocked,341) TMC(blocked,117) MAIN(running,498) IDLE(ready,21) Owned mutexes: === Platform === Last reset 00:00:05 ago, cause: software Last software reset at 2021-02-19 21:19, reason: User, GCodes spinning, available RAM 25756, 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 34.1, current 34.6, max 34.8 Supply voltage: min 0.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, standstill, read errors 0, write errors 1, ifcnt 44, reads 848, writes 6, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, read errors 0, write errors 1, ifcnt 44, reads 848, writes 6, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, read errors 0, write errors 1, ifcnt 47, reads 848, writes 6, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, read errors 0, write errors 1, ifcnt 41, reads 848, writes 6, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, read errors 0, write errors 1, ifcnt 44, reads 848, writes 6, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-02-19 21:19:45 Slowest loop: 3.72ms; fastest: 0.16ms 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: 15.0MBytes/sec SD card longest read time 0.5ms, write time 0.0ms, 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: 61.44ms; 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 -
i only know of people who tried to get external motors to work on the mini but i dont know anyone who as actually done it.
