Posts made by Yurk_12

Thanks @fcwilt.

the idea of having mechanical motion on power up doesn't seem like a good idea

I see your point, but I'd argue that systems that start upon powering up are ubiquitous (a simple room fan starts blowing whenever you turn it on).

Thanks @phaedrux.

Can you try adding a delay in your config.g of a few seconds with G4 S4 right before your job is called and move the job call to the end of the file and see if it makes a difference.

Ah yes, good point. A main difference between running from config and from DWC is the time the board is ON since startup, I should have thought of that. It is now working as expected, I will keep this 4 seconds delay then. The board must go through some initializations at startup I assume.

Could you share your config.g?

Sure, nothing fancy here though I believe.

Thanks a lot for your prompt help

; Configuration file for Duet 3 Mini 5+ (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.0 on Tue Aug 03 2021 20:00:32 GMT-0400 (Eastern Daylight Time)

; General preferences
G91                                              ; send absolute coordinates...
M550 P"Tests_v0"                                 ; set printer name

; Network
M552 P169.254.163.66 S1                          ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                       ; enable HTTP
M586 P1 S0                                       ; disable FTP
M586 P2 S0                                       ; disable Telnet

; Drives
M569 P0.0 S0                                     ; physical drive 0.0 goes forwards
M569 P0.1 S0                                     ; physical drive 0.1 goes forwards
M569 P0.2 S0                                     ; physical drive 0.2 goes forwards
M569 P0.3 S0                                     ; physical drive 0.3 goes forwards
M569 P0.4 S1                                     ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2 U0.3 V0.4                    ; set drive mapping
M350 X16 Y16 Z16 U16 V16 I1                      ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 U80.00 V80.00           ; set steps per mm
M566 X90000.00 Y90000.00 Z90000.00 U90000.00 V90000.00      ; set maximum instantaneous speed changes (mm/min)
M203 X60000.00 Y60000.00 Z60000.00 U60000.00 V60000.00 ; set maximum speeds (mm/min)
M201 X5000.00 Y5000.00 Z5000.00 U5000.00 V5000.00      ; set accelerations (mm/s^2)
M906 X600 Y600 Z600 U600 V600 I30                 ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                          ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 U0 V0 S1                                 ; set axis minima
M208 X999999 Y999999 Z999999 U999999 V999999 S0                  ; set axis maxima

; Endstops
; WARNING: No endstops configured

; Heaters
M140 H-1                                         ; disable heated bed (overrides default heater mapping)

; Fans

; Tools

; Custom settings are not defined

M564 S0 H0
M220 S0

;M669 K0 X1:0:0:0:0 Y0:1:0:0:0 Z0:0:1:0:0 U0:0:0:1:0 V0:0:0:0:1
G4 S4
M32 duet_test.gcode

Thanks @fcwilt and @phaedrux.

Doing anything like that from config.g seems like a very bad idea to me.

but I get the sense this maybe isn't a typical usage of a Duet.

It is not a 3D printer. I am actuating motors to achieve a certain function in a mechanical assembly.

Why are you trying to do that?

For a very easy user experience. The user starts the power of the assembly and the desired motion is executed.

What was the mechanical issue?

2 motors were mechanically stuck into one position. No rotation possible during the 30 min of blocking.

Are you sure it's not still a mechanical issue? Like a loose grub screw maybe?

I am sure the mechanical issue has been fixed. The job now works normally when called from DWC. I'm switching back and forth between calling the job from DWC and from config.g and it alternately works and fails.

Those are small motors, did they get burnt being locked in position while trying to move?

Maybe, but everything works as expected when calling the job from DWC.

Job called from DWC: success
Job called from config.g and ethernet cable connected to computer: fail
Job called from config.g and no cable plugged: fail

Hi,

My gcode job describes a certain motion to drive 5 Nema 8 motors. The job is in the Jobs folder and it is run on startup thanks to a M32 filename.gcode added to config.g.

The following happened: during the job, 2 motors were mechanically stopped for about 30 min. The job was still executing. I turned off the board, fixed the mechanical part, and started again the board: the job is run but commands with low speed are not executed while commands with high speed are executed.

When I run the job by uploading it in DWC and starting it from DWC it still works as expected. It seems that calling the job from config.g or calling the job from DWC is different.

The job looks like below.
Lines #1,#2 are properly executed.
In line #3, only the X-200 is executed. The Y,Z,U,V-5.4 are not executed, and this only when the job is called from the config.g at startup. Diagnostics pasted below.

Any idea what is happening? In general also, how bad is it if a job is mechanically blocked for a long time with mechanically stopped motors?
Thanks a lot

G21 G91 
G1 X-200.0 Y-145.94594594594594 Z-91.89189189189189 U-37.83783783783784 F18500
G1 X-200.0 Y-5.405405 Z-5.405405 U-5.405405 F9250.0 
G1 X-200.0 Y-5.405405 Z-5.405405 U-5.405405 F9250.0 
G1 X-200.0 Y-5.405405 Z-5.405405 U-5.405405 F9250.0 
G1 X-5.405405 Y-5.405405 Z-5.405405 U-5.405405 F500.0 
G1 X-5.405405 Y-5.405405 Z-5.405405 U-5.405405 F500.0 
G1 X-5.405405 Y-5.405405 Z-5.405405 U-5.405405 F500.0 

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: 5DNBA-B296U-D65J0-40KM6-2503Z-HSDTT
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 99352 of which 296 recycled
Never used RAM 41332, free system stack 152 words
Tasks: NETWORK(ready,27.7%,240) ETHERNET(notifyWait,0.1%,574) HEAT(delaying,0.0%,415) Move(notifyWait,0.1%,300) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.7%,115) MAIN(running,70.2%,408) IDLE(ready,0.4%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:19 ago, cause: power up
Last software reset at 2021-08-04 21:08, reason: User, GCodes spinning, available RAM 41332, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 139750, completed 139748, timed out 0, errs 0
Step timer max interval 797
MCU temperature: min 24.6, current 31.0, max 31.0
Supply voltage: min 10.5, current 11.0, max 12.2, 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
Driver 0: position -203676, standstill, SG min/max 0/24, read errors 0, write errors 0, ifcnt 16, reads 7313, writes 16, timeouts 0, DMA errors 0
Driver 1: position -97297, standstill, SG min/max 0/102, read errors 0, write errors 0, ifcnt 16, reads 7313, writes 16, timeouts 0, DMA errors 0
Driver 2: position -84324, standstill, SG min/max 0/34, read errors 0, write errors 0, ifcnt 16, reads 7312, writes 16, timeouts 0, DMA errors 0
Driver 3: position -24649, standstill, SG min/max 0/88, read errors 0, write errors 0, ifcnt 16, reads 7312, writes 16, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 7320, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-08-04 21:16:47
Cache data hit count 230021930
Slowest loop: 210.47ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.7ms, write time 2.1ms, max retries 0
=== Move ===
DMs created 83, maxWait 19454ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 7, completed moves 7, 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 = -1 -1, chamberHeaters = -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
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 699, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 699/0/0
Tx timeouts 0,0,698,0,0,0 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 1054.23ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0

@phaedrux

And what IP address does your computer have? Is it in the same subnet as 120.20.20.x?

Oh, it was not in the same subnet indeed.

Autoconfiguration IPv4 Address. . : 169.254.163.65

I changed the IP of the board as follows:

M552 S0
Network stopped
ok
M552 S1 P169.254.163.66
ok
Ethernet running, IP address = 169.254.163.66
M552
Ethernet is enabled, configured IP address: 169.254.163.66, actual IP address: 169.254.163.66
ok

and now it works:

Updating the firmware on the mini5 is a bit different over USB.
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Duet_3_Mini_5_WiFi_Ethernet

Oh great, thanks, I had missed it.

Thanks a lot for your help

Hi,

I'm failing at Step 11 of the Getting Connected doc.

Config

Duet 3 Mini 5+ Ethernet freshly received, first time trying.
Windows 10
Board connected and powered by USB computer port
Ethernet cable connected to computer directly: tried both normal and crossover cables
Firmware 3.2.2 (I could not update the firmware in step #7 because it needs access to DWC)
The green and yellow network LEDs on the board are ON. The green one sometimes blinks.

Problem

In YAT I have:

M552 S0
Network stopped
ok
M552 S1 P120.20.20.20
ok
Ethernet running, IP address = 120.20.20.20
M552
Ethernet is enabled, configured IP address: 120.20.20.20, actual IP address: 120.20.20.20
ok

Putting the IP in Chrome does not work. Going to duettest.local does not work either.

Below is the diagnostics M122. Am I doing something wrong?
Thanks for any help

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: 5DNBA-B296U-D65J0-40KM6-2503Z-HSDTT
Used output buffers: 1 of 40 (15 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 101112 of which 404 recycled
Never used RAM 44968, free system stack 124 words
Tasks: NETWORK(ready,454) ETHERNET(blocked,652) HEAT(blocked,362) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,362) TMC(blocked,123) MAIN(running,400) IDLE(ready,20) AIN(blocked,260)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:33:15 ago, cause: power up
Last software reset time unknown, reason: HardFault bfarValid precise, GCodes spinning, available RAM 44968, slot 0
Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000040 SP 0x2000a7e0 Task MAIN Freestk 779 ok
Stack: 00000000 00000571 0000056d 00000000 ffffffff 000664e9 000781ca 61010000 00000000 ffffffff 2001c8dc 20009b54 2001c6d8 2000a850 000914f0 200095b4 2000a8ec 0007dca3 00000001 2000a850 20000008 0007b369 0008bd6c 0006d049 20028928 20000008 20000008
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.9, current 0.9, max 0.9, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 2: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 3907942329
Slowest loop: 4.47ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.2ms, 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 = -1 -1, chamberHeaters = -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 ready with "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.45ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 2 2 2 2 2 0 0 0
=== CAN ===
Messages queued 8774, send timeouts 8774, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
ok

@yurk_12

It is actually now working after using a different USB cable (the one provided by Duet3D actually...). Sorry for the noise. Still putting my screenshots here for the record now that it's working:

Hi,

I'm failing at the first steps of connecting to my Duet 3 Mini 5+ Ethernet.

Before plugging in, Device manager looks like:

No change in device manager after plugging in and after "Scan for hardware changes". 2 LEDs are ON and the third red one is blinking:

The doc says

• "If a USB device does show the yellow triangle" : no yellow triangle for me
• "or as a Generic USB device" : I have many Generic USB devices. How to know which one to choose?

Should I use the "Add legacy hardware" in Device manager and point to the driver files I downloaded? I choose manual installation, COM port, point to the folder, it shows

Which one should I choose? I've tried the following two and I get yellow triangles, and no COM port appears available in YAT:

Any idea what I might be doing wrong?
Thanks for any help

Thanks @phaedrux.

Duet 2 wifi/ethernet or Duet 3 mini5+ would be good options.

OK, thanks.

I would say that some passive ventilation would be required at minimum regardless of what you drive. Sealing up electronics entirely is never ideal.

Absolutely, I agree.

Is this going to be in a harsh/dirty environment?

Quite clean environment. I can have passive ventilation holes on several sides.

Mounting the board vertical can help as well since both sides of the board are able to convect upwards.

I see. Unfortunately, I'll have to mount it horizontally.

Hi,

I would like to drive motors smaller than the usual ones for which the board is designed:

• Nema 8 (PHB20Y28-406)
• 2 phases, 0.6A/phase -> 1.2A total rating
• 0.9 mH/phase inductance
• 3.2 Ohm/phase

Looking at a comparison of the drivers of the Duet 2 and 3 (TMC2660, TMC2209), I am not sure whether one would be more suited than the other. Desired features:

• driving 5x Nema 8 motors at 1A each (~85% of the 1.2A rating)
• minimizing the heat generated by the board. The board will be in a metal enclosure along with some small electronics. Is ventilation of the enclosure recommended to drive such small motors (the rest of the electronics in the box does not generate heat)? I believe having simple ventilation holes without a fan would be enough?

This post seems to suggest that the Duet2-TMC2660 might be cooler due to the lower resistance?

Also, these boards do not require heatsinks on the motor drivers because they already dissipate efficiently into the PCB, correct?

Thanks for any hint

@t3p3tony Excellent, thanks a lot for your answer. I'll send an email then.
I agree with you on being careful with the startup code.

Hi,

I'm new to this board, could someone please help me confirm whether Duet boards fulfill the following requirements? If yes, which board versions in particular would be suitable? I believe "Duet 2 Ethernet", "Duet 2 Maestro" and "Duet 3 6HC" would work, but maybe I've missed something.

Thanks a lot

1. RoHS compliant: I've seen threads about that (like here), but I have not found official certificates. Is there one somewhere or should we contact resellers privately?

2. I believe that there is no need for costly Electromagnetic Compatibility/Interference (EMC/EMi) testing in the boards "Duet 2 Ethernet", "Duet 2 Maestro" and "Duet 3 6HC" because they simply do not have a wifi module, correct? These boards are then not considered as intentional emitters.

3. independent simultaneous control of 5 stepper motors with g-code

4. automatic execution of g-code upon startup (no button press needed). Can the g-code be preloaded in the board or in the SD card? It seems to be possible, by writing commands at the end of config.g as mentioned here?

5. Is there any information about the REACH compliance of these boards, that is, is there a certificate stating that they do not contain any SVHC (substance of very high concern)?