Reprap Forum - Duet

Servo motor control mode (1 reply)

thomas22 — Tue, 18 Jun 2024 03:12:27 -0400

Hi,
I am building machine other than 3d printer, type of the eletctrical press. Best for this application is torque control mode wich is provide by servo and controler that im using, it's here:
https://www.oyostepper.de/goods-1100-T6-Serie-1000W-AC-Servomotor-Kit-3000-Umin-319Nm-mit-Brems-17-Bit-Encoder-IP65--1000W-AC-Servomotortreiber.html
(I need the motor to push thing, and then go back to estop, in cycle, but with counting cycles etc, i just want to use duet because of DWC)
Setup:
DUET 3 MINI 5+, 2pcs 1XD, SBC mode with RPI4

With standard step/dir mode i run it smoothly like in 3D printer, and made some macros for alarms etc.
My first try was with analog input in servo and provide 0-10V with some type of converter from duet (controling torque like a fan with PWM, than convert it to 0-10V). But after i ordered the servo i found out that servo drive doesn't have physical analog input. Only the inside setup value or outer comunication via RS485.
And i found TTL converter (wich is suported by duet) to RS485.

And now i have two question:

Is it possible to comunicate duet and setup rs485 comunication with this servo drive in some easy ways, and then by comands listed in servo drive guide just use the servo by sending comands or use macros from DWC.

How can i use this simple torque mode with setup parameters from Motion Studio that is provided with T6 Servo, im trying to find anything but it seems that it is very little about it in the instruction, maybe i will program servo drive 1 cycle, and then send digital signal from duet to induce cycle or induce part of the movement.

What is the Logical Pin number for FAN0? (1 reply)

Radian — Thu, 28 Mar 2024 03:08:37 -0400

Hi. After many orbits or the Sun I dug out my laser cutter fitted with an early Duet and flashed the controller with the "ultimate" DC42 firmware for the board (1.26.1)
My previous technique was to use "M571 Set output on extrude" to enable the laser from the FAN0 output but that no longer works.
Looking at the Notes for M571 in [docs.duet3d.com] it says:

"RepRapFirmware 1.20 and later do not default to using the FAN0 output, so you must send M571 with a P parameter at least once to define the pin that you wish to use."

Ok, but what logical pin number activates FAN0? All the tables of logical pin numbers I can find only list signals on the expansion header.
I confirmed this works in principle by issuing M571 S1.0 P65 and that does indeed drive pin 35 on the expansion header high during extrusion but I need an inverted signal, and I liked using FAN0 mosfet switching to ground when active for this purpose.

Duet2 WiFi V1.04 (3 replies)

catmandu — Wed, 23 Nov 2022 12:48:56 -0500

Hello
I have been given a Duet2 WiFi V1.04 board amongst a few other things including about 5/6 sd cards, but of course there is a problem| The board came without a sd card in it and none of the cards that came with it hold reprap firmware of any sort I understand that the board is supplied pre flashed and if that is true then it seems that the firmware has been "erased". If this is the case is it possible to reinstall the firmware and if so what files will I need to do it, I intend using it on a linear delta. I already have 2 deltas running RRF WiFi , but on SKR1.4Turbo boards, and I have no experience with Duet boards at all. Thanks in advance for any assistance.

Extending cable for paneldue (5 replies)

daninet — Tue, 26 Jul 2022 16:02:37 -0400

Hello!
Duet2 wifi + 5" paneldue
I'm using the 4wire paneldue connector to communicate with an arduino so I'm stuck with the conn_sd 10pin connector. My issue is that I need 800mm cable between the board and the paneldue and the communication is just not working for the screen. The cable is perfect, I tested it. I did read in the manual the recommended length is 300mm max. My question is if I don't need the sd card function could I get away with a shielded cat6 ethernet cable? Provided that there is at least 1 pin I don't need to use for the sd card. I could shield the cable with the gnd so i would have 9 conductors total. Would this work? Also whick pin I could omit to try this?

DUET2 WIFI AND REVO VORON (3 replies)

MARCENEIRO JOVEM — Sun, 24 Jul 2022 14:01:18 -0400

I need a little help from my friends.

I'm riding a Voron 2 using RevoVoron hotend, Duet2 wifi and RepRap Firmware. The RevoVoron sensor is connected in E0 Thermistor 1 and the Heater is connected in E0 Heater. It happens that the temperature is at 600 degrees Celcius. Config.g is like this. Where am I going wrong?

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; 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 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 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4267 C7.060000e-8 ; 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 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to

Dual Z setup one of the motors turning half speed (2 replies)

daninet — Fri, 08 Jul 2022 13:18:49 -0400

Hello,
I'm in the process of building a core xy machine with dual Z bed. I'm using duet 2 wifi board. One of the motors turning half the steps as the other. If one is turning 2 the other is one. I have one of the motors connected to E1 the other to Z output.
I have swapped the connectors (Z to E1, E1 to Z) and that particular motor is still turning half. They have detachable cable, I have swapped their cable to make sure it is not a wining issue, still same motor turning half the steps.
Is the stepper toast?

Homing issues (3 replies)

tubaman — Tue, 08 Mar 2022 03:50:43 -0500

Hi, I'm trying to set up a Duet2 wifi board with RepRap on my cnc machine. I'm using the Workbee firmware version although I don't think this is causing the issue I have. I have the axis sizes set to X650 and Y600 ( M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X650 Y600 Z200 ; Set axis maxima ) and limit switches at the low end ( M574 X1 P"xstop" S1 ; Set active low X endstop
M574 Y1 P"ystop" S1 ; Set active low Y endstop
M574 Z0 P"zstop" S1 ; Set active low Z endstop )
What I don't understand is why, after homing, the machine always sets its position to the high end, X650, Y600 and not X0, Y0.
Can someone please explain what I am doing wrong? Thanks

Creality CR6-SE steppers are loud (1 reply)

bulldogbob — Sun, 30 Jan 2022 02:40:12 -0500

I have a problem with my Duet2 wifi board on my Creality CR6-SE. I have a duet2 wifi on my hypercube and it works fine and is nice and quiet. Because I like the board so much, I also wanted it on my CR6-SE. Now I have it connected but the steppers make a lot of noise, more than the hypercube. They also make a hissing sound at idle. I don't hear this with the hypercube either. When I send gcode M84 everything is silent. The steeppers are connected correctly and everything is going in the right direction.

; 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
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 E128 I0 ; configure microstepping without interpolation
M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E138.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

Dual Z homing issue - one motor only (1 reply)

happycaribou77fr — Sun, 21 Nov 2021 05:54:06 -0500

Hello,

I have passed quite a few hours on trying to troubleshoot my dual Z homing on my duet:

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3 (2021-06-15)
Duet WiFi Server Version: 1.26

upon startup, if I manual enter in the console:
G91
G1 H2 Z30 F6000
G1 H2 Z-30 F6000
All good, as both motors are moving in the right direction and the bed is moving +/-3cm.
M122:
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 192210, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available

if I run after
G1 H1 Z-30 F1800
only 1 motor moves... which is an issue for homing. I have no clue what is wrong.....

Could you please help?

I attached my config.g, homeall.g and homez.g.
I tried switch motor cables Z1<->Z2 and it just changed the problem to the other motor.

keep getting spurious http: disconnect messages (1 reply)

shadowphile — Thu, 30 Sep 2021 11:08:16 -0400

Just in the last day or two I keep getting this random message, even when the printer is not doing anything:
'Connection interrupted, attempting to reconnect... HTTP request timed out' then it automatically reconnects.
Is there a way to trace this down to either my local network or an issue with the duet?
thanks

Need help setting up final calibration using config.g (2 replies)

shadowphile — Sun, 19 Sep 2021 18:30:12 -0400

I have a delta with a piezo z probe running RRF3.4b3. I have worked out the z-probe offset and confirmed it with both G30 S-1 and also G30 alone.
I have also probed out the mesh bed correction. It looks 'ok', not great (max height - min height is about .25mm)
Now I want to invoke mesh bed correction without having to run G29 and G32 but I can't enable the heightmap correction until I've established a zero datum.
I tried putting this at the end of my config file:
G28 ;home
G1 X0 Y0 Z5 ;go to Z=5
M201 Z100 ;set accel real slow (I found this keeps my piezo from triggering during the start of a probe and use it for my G29 and G32 runs)
M566 Z20 ;set jerk really low
G30 ;probe bed once to trim zero height.
M201 Z5000 ;return accel to high
M566 Z300 ;set jerk to high
G1 Z300
It all runs fine, except the web interface does not know I homed and zero'd already, still have to click 'Home' manually. Is this normal?

question: If I configure the Z=0 datum by a single probe to the bed, does a subsequent homing erase that offset?
question: I want to programmatically set the accel and jerk very very low for any z-probe moves. I have that control in bed.g but how do I ensure the same thing for heightmap creation? I am thinking that I might creat a mesh.g file and put M557 there along with adjustments to the accel and jerk so I can return them to high values afterword but I'm burnt trying things out and just need some deeper info than the docs provide.
I realize that by doing this, my bed and nozzle aren't at printing temps. My meshbed is too large to run before every print but I'm used to manually ensuring the physical Z=0 anyway so I'm assuming that G32 and G29 at room temp will still be mostly valid and only have to adjust for the thermal expansion before a print.

JFYI, here is my z-probe setup:

M558 P5 C"z_probe.in" H5 F1000 T4000 R.75 ; create z probe input and type. H is dive height, F is probe speed, T is travel speed, R is settling time
M557 R150 S30 ; define mesh grid, radius and step size mm
G31 X0 Y0 Z-0.17 P500 ; probe height from actual surface (Volcano)
thanks

Duet Ethernet won't detect new accelerator board (2 replies)

shadowphile — Sat, 11 Sep 2021 12:47:47 -0400

Before you get lost in the text below, I want to squeeze in a thanks for reading this and hope you can find errors (otherwise my board is bad).

I've been following the instructions to set up an Adafruit LIS3DH accelerometer on my DuetEthernet. I've been running 3.3 up till now, then installed 3.4b3. I have a temp daughterboard so made my cable according to that (along with some grumbling because I could NOT find the daughterboard pinout anywhere so had to do it the hard way with a DMM. 8-))

When I manually attempt to run M955 P0 C"spi.cs4+spi.cs3" S1000 to set up an accelerometer, I get 'accelerometer not found on specified port'.
After double-checking my wire routing, I put an oscilloscope on all the pins of the temp daughterboard's Output connector. There is regular bus data going on, including activity on CS1 and CS2 when the PT100 sensors are read. But CS3 and CS4 don't change when I send the M995 command. I hope my Duet board isn't damaged! It might be the firmware, see below.

Getting the new firmware up (3.4b3) has been an uncertain process. I finally got the latest firmware to bootup without a wifi-error AFTER I discovered the .json editor, which is how I got the board to bootup.
Problems:
...3.4b3 web control is not showing either tool on the dashboard, just the bed. the temp graph however has three heaters in the legend (I have a dual extruder). so something is broken.

I am not familiar with the .json thing except to know it is text config file similar to the role of .xml, so I don't know what the role of the .json files are, maybe data for a bootloader?
The only way I could find to configure 3.4b3 for a Duet Ethernet was to use the editing tool but that also forces you to make an entire config file and I want to keep my original + neccessary edits. I did select to 'reuse' my original config.g file but the result had problems and I still crafted the config.g file by hand.

Config.g file is attached, along with config.json file. Below is the diagnostic report form the Duet board.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6JKDD-3SN6J-TVWHG
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 69888 of which 584 recycled
Never used RAM 20068, free system stack 150 words
Tasks: NETWORK(ready,26.0%,231) HEAT(delaying,0.1%,330) Move(notifyWait,0.1%,317) MAIN(running,73.9%,503) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:05:09 ago, cause: software
Last software reset at 2021-09-10 21:02, reason: User, GCodes spinning, available RAM 20308, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 32.7, current 33.2, max 36.0
Supply voltage: min 24.1, current 24.3, 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
Driver 0: position 150194, standstill, SG min/max not available
Driver 1: position 150194, standstill, SG min/max not available
Driver 2: position 150194, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-09-10 22:07:28
Cache data hit count 4294967295
Slowest loop: 22.02ms; 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 2.0ms, write time 8.7ms, max retries 0
=== Move ===
DMs created 83, maxWait 171ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1, completed moves 1, hiccups 130458, 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 -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
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: 66.95ms; fastest: 0.02ms
Responder states: HTTP(2) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

Duet WIFI Thermistor values (2 replies)

Viper97 — Mon, 16 Aug 2021 19:04:09 -0400

Does anyone have the thermistor values for a Mosquito Hotend 300 degree thermistor I can plug in? Thanks.

Duet 2: Config 1x X, 4x Y and 2x Z motor (1 reply)

Space96 — Fri, 25 Jun 2021 09:30:29 -0400

Hello together,

I am currently building a 3D printer (Corexz). However, I need help to adjust the config file to the number of axis motors so that the 4x Y-motors and the two Z-motors run in parallel. Can one of you help me? Many thanks smiling smiley

Hardware:

- Duet 2 Ethernet
- Duex5

Assignment:

Duet 2:
Z: Z1
Y: Y1
X: X1
E0: E0
E1: E1

Duex5:
E6: Z2
E7: Y2
E8: Y3
E9: Y4

Config:

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M569 P4 S1 ; physical drive 4 goes forwards
M569 P7 S1 ; physical drive 7 goes forwards
M569 P6 S1 ; physical drive 6 goes forwards
M569 P6 S1 ; physical drive 6 goes forwards
M569 P6 S1 ; physical drive 6 goes forwards
M584 X0 Y1 Z2 E3:4:7:6:6:6 ; set drive mapping
M350 X16 Y16 Z16 E16:16:16:16:16:16 I1 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z533.33 E873.08:873.08:533.33:160.00:160.00:160.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00:120.00:60.00:900.00:900.00:900.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00:180.00:6000.00:6000.00:6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00:20.00:500.00:500.00:500.00 ; set accelerations (mm/s^2)
M906 X1680 Y1680 Z1680 E1680:1680:1680:1680:1680:1680 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

variable encoder steps for varying extrusion print speeds (2 replies)

shadowphile — Tue, 15 Jun 2021 13:10:08 -0400

Running a filament at different extrusions rates obviously alters the backpressure so trying to put a 'correct' value in config.g is confusing. One of my 1.75mm PLA filaments would change as a much as 6% between extruding at 1mm/sec and 5 mm/sec (albeit 5 is a little over the thermal volumetric limit for a V6 heater block)
So temperature, extrusion rate, and nozzle-size can all impact the correct encoder steps for a particular print.
Is there a facility or plans for accounting for these? Pressure-advance can only adjust for some established amount of filament-compression (or bowden) so not sure that can be a cure-all, and does not track any of the mentioned variables that impact extrusion rate.
thanks

Bltouch along with Endstop (1 reply)

SaarNeu93 — Sun, 13 Jun 2021 02:27:11 -0400

Hi everybody,
I am using Duet wifi 2 and reprap comfiguration.
I want to right a macro that the printer will first make a Z home (G28 Z) with a simple endstop, which will be located in the center of the bed (with a jig). Next i will remove the jig and it will make a homing sequence again but with the Bltouch.
I connected the bltouch to "Z Probe" and the endstop to "Z stop".

Here is my config:

; Drives
M569 P4 S1                                         ; physical drive 4 goes forwards
M569 P1 S1                                         ; physical drive 1 goes forwards
M569 P2 S0                                         ; physical drive 2 goes backwards
M569 P3 S1                                         ; physical drive 3 goes forwards
M584 X4 Y1 Z2 E3                                ; set drive mapping
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.00                  ; set steps per mm
M566 X600.00 Y600.00 Z18.00 E300.00                ; set maximum instantaneous speed changes (mm/min)
M203 X10000.00 Y10000.00 Z300.00 E1200.00          ; set maximum speeds (mm/min)
M201 X5000.00 Y5000.00 Z300.00 E10000.00           ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z800 E800 I30                    ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Axis Limits
M208 X-10 Y-25 Z0 S1                               ; set axis minima
M208 X220 Y220 Z240 S0                             ; set axis maxima


; Endstops
M574 X1 Y1 S0                                      ; set active low and disabled endstops
M574 Z1 S2                                         ; set endstops controlled by probe


; Z-Probe
M307 H3 A-1 C-1 D-1                                ; disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000                              ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X30.44 Y-9.48 Z0.825                      ; set Z probe trigger value, offset and trigger height
M557 X30.44:220 Y0:200 S30                         ; define mesh grid

; Heaters
M307 H0 B0 S1.00                                   ; disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4725 C7.060000e-8 R4700           ; set thermistor + ADC parameters for heater 0
M143 H0 S130                                       ; set temperature limit for heater 0 to 130C
M305 P1 T100000 B4725 C7.060000e-8 R4700           ; set thermistor + ADC parameters for heater 1
M143 H1 S275                                       ; set temperature limit for heater 1 to 275C

; Fans
M106 P0 S0 I0 F500 H-1                             ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45                          ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 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

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600                                  ; enable support for PanelDue
M501                                               ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0                                                 ; select first tool

Help please!
Thanks you all

Duet and Graphics Controler? (2 replies)

aamcle — Sun, 06 Jun 2021 12:42:55 -0400

I'm considering the Duet3 Mini for a Cartesian printer and I have spare a RepRap Full Graphics controller unused.
Would it work with the Duet and would it in fact be needed or of anyuse?

Thanks All. Aamcle

stuttering hot-end? (4 replies)

shadowphile — Wed, 09 Jun 2021 20:48:41 -0400

Don't know why I'm having problems lately, although redesigning the entire effector might have something to do with it :)
In this case that doesn't matter.
I'm printing a 10" single filament circle for calibration purposes. I'm generally running it at 50mps (1st level).
The skirt runs fine all the way around but the path along the object itself stutters badly when rounding the curve where the X and Y axis are swapping %s. That sounds like code starving but I've never encountered it before with the driver board and that doesn't explain the skirt printing ok.

Weird scaling artifact (6 replies)

shadowphile — Thu, 10 Jun 2021 15:36:22 -0400

I have Duet 2 Ethernet and the latest firmware. My z-probe is a custom piezo sensor/electronics that uses the nozzle tip.
I've gotten comfortable troubleshooting printing issues but this one is a stumper: my Benchy seems to have changed scale in mid print, see pics. I searched for the G-code scaling commands and even something that may have changed my calibration numbers but they weren't found in the file.
(sliced by PrusaSlicer)
Can't include the gcode. I keep getting 'too large' errors, even when I try to use a reply and just add a 1.5M zip of the gcode. You can request a copy from my email shadowphile@gmail.com if you want.
(update: I haven't tried to reprint this object because it's a longish print (.09mm layers) and it would be worse if it was ok the second time since I couldn't replicate the problem.)

thanks for reading and I hope you can help.

Hotend fan and security (1 reply)

build3r — Mon, 10 May 2021 02:11:42 -0400

I worry a bit about the heat break fan or its cable failing. Ideally, printing would then stop.

How do you deal with this scenario? Just accept the risk? Or is there a standard way to detect and deal with such a failure?

(not sure whether this is the right forum, but I use a Duet 2)

Best Firmware / Web Control for Duet 0.6 (1 reply)

ntsewell — Wed, 05 May 2021 02:52:35 -0400

Hi everyone,

I've had my RepRap printer since the last quarter of 2015, and although I used it a lot for the first 3 years, children and life got in the way and I haven't used it much over the past couple of years.

I recently dug it out, gave it a clean up, unblocked the nozzle and printed a calibration cube I first printed on 12 Jan 2016! It worked great! But it I got a few AJAX errors (drop outs) during printing, and actually it's pretty inconvenient now having the plug the thing into the wired network at home. So, I have three questions that I'm hoping the hive mind might help me with!

1) What version of the firmware would people recommend for this old beast (Duet 0.6) - currently I'm running 1.09c-dc42 (2015-06-25) (RapRepFirmware)
2) What web interface would you recommend (currently HTML: 1.06, JS: 1.06
3) Is there a sensible way to run it either on the USB or, if not, what networking solution would you recommend please?

Thank you in advance everyone!

Dual Z Issues for Ender 3 w/ Duet 2 Wifi (2 replies)

Ripeds_O3P — Mon, 26 Apr 2021 13:40:50 -0400

Hello everyone. So I recently upgraded my Ender 3 to Duet. I managed to get everything working except Dual Z. Now, I had to reposition the pins of my X & Y motors to work with the Ender Pro settings in the config manager as I had the wires the opposite way of what they should have been. I thought I copied the original wiring configuration right, but it seems I hadn't at the time. Those two work fine homing to where they should now.

Then I tried that with each Z motor (separate wires running to each motor & the Z ports on the board). And it doesn't
seem to work right. I did try looking this up online to try to narrow down what it could be.

The Z axis seems to semi work. Getting a CM or two in one direction. Although it feels like one motor is doing more work as it sort of hops up. Also, homing seems to send it up? Then it seems to get stuck, as powering it off drops the x-gantry slightly.

The wiring is what it should be for one Z motor. The second motor has the middle two wires swapped on the motor connector to turn it in the opposite direction. As that was the only way to get it to work on the old board. [Note: If they're both wired the same on the creality board, then one side of the x-gantry goes up and the other side goes down. But that was merged into one cable.] On the Duet, if try the exact same wiring by using X & Y cables from Z ports to Z motors it seems to repeat the same results (homing moves the gantry up). Either way, I get the impression that one motor is doing more work then the other. But I've tested both motors finding that they do both power up and turn (at least individually, when they're both hooked up I am unsure if they're both getting the power needed).

Tested a few gcode commands:

- M906 to see if power is getting to the motors, it reads 100% on Z. Though it only shows it once, rather then twice.
-I tried G1 S2 Z10 F100 this to get Z to move without homing. The X gantry moves up like it does with Z homing.

**edited after more testing***

board	"duetwifi10"
firmware	3
nvram	false
auto_save	
enabled	true
save_threshold	10
resume_threshold	11
gcodes_to_run	"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"
display	
type	1
encoder_steps	4
spi_frequency	2000000
menus	
0	
name	"main"
value	"text C10 R20 \"Powered by Duet3D\""
images	[]
geometry	
type	"cartesian"
mins	
0	0
1	0
2	0
maxes	
0	235
1	235
2	250
delta_radius	105.6
homed_height	250
low_dive_height	false
max_carriage_travel	260
print_radius	85
rod_length	215
z_min	0
drives	
0	
direction	0
microstepping	16
microstepping_interpolation	true
steps_per_mm	80
instant_dv	20
max_speed	150
acceleration	500
current	800
driver	0
endstop_type	1
endstop_location	1
driver_v3	"0.0"
endstop_pin	"xstop"
1	
direction	0
microstepping	16
microstepping_interpolation	true
steps_per_mm	80
instant_dv	20
max_speed	150
acceleration	500
current	800
driver	1
endstop_type	1
endstop_location	1
driver_v3	"0.1"
endstop_pin	"ystop"
2	
direction	1
microstepping	16
microstepping_interpolation	true
steps_per_mm	400
instant_dv	0.4
max_speed	3
acceleration	100
current	800
driver	2
endstop_type	1
endstop_location	1
endstop	null
driver_v3	"0.2"
endstop_pin	"zstop"
3	
direction	1
microstepping	16
microstepping_interpolation	true
steps_per_mm	410
instant_dv	5
max_speed	100
acceleration	5000
current	1000
driver	3
driver_v3	"0.3"
idle	
used	true
factor	50
timeout	30
homing_speed_fast	50
homing_speed_slow	4
travel_speed	100
z_dive_height	5
slow_homing	false
probe	
type	"noprobe"
recovery_time	0.4
trigger_height	2.5
trigger_value	500
x_offset	0
y_offset	0
speed	2
deploy	false
points	[]
pwm_channel	64
pwm_inverted	false
pwm_pin	null
input_pin	"zprobe.in"
modulation_pin	null
bed_is_nozzle	false
bed	
present	true
heater	0
use_pid	false
chamber	
present	false
heater	2
use_pid	false
heaters	
0	
temp_limit	150
scale_factor	100
series	4700
thermistor	100000
beta	4092
c	0
channel	0
sensor	0
output_pin	"bedheat"
sensor_type	"thermistor"
sensor_pin	"bedtemp"
1	
temp_limit	290
scale_factor	100
series	4700
thermistor	100000
beta	4092
c	0
channel	1
sensor	1
output_pin	"e0heat"
sensor_type	"thermistor"
sensor_pin	"e0temp"
num_nozzles	1
toolchange_wait_for_temperatures	true
generate_t_code	false
tools	
0	
mix_ratio	[]
number	0
name	""
extruders	
0	0
heaters	
0	1
fans	
0	0
x_offset	0
y_offset	0
z_offset	0
compensation_x_offset	15
compensation_y_offset	15
peripheral_points	3
halfway_points	0
calibration_factors	3
probe_radius	85
mesh	
x_min	15
x_max	215
y_min	15
y_max	195
radius	85
spacing	20
home_first	false
orthogonal	
compensation	false
height	50
deviations	
0	0
1	0
2	0
network	
enabled	true
mac_address	""
name	""
password	""
ssid	""
ssid_password	""
dhcp	true
ip	""
netmask	""
gateway	""
protocols	
http	true
ftp	false
telnet	false
fans	
0	
name	""
value	0
inverted	false
frequency	500
thermostatic	false
heaters	[]
trigger_temperature	45
output_pin	"fan0"
1	
name	""
value	100
inverted	false
frequency	500
thermostatic	true
heaters	
0	1
trigger_temperature	45
output_pin	"fan1"
2	
name	""
value	100
inverted	false
frequency	500
thermostatic	true
heaters	
0	1
1	0
trigger_temperature	45
output_pin	"fan2"
custom_settings	""
expansion_boards	[]
standalone	true
panelDue	false

RepRapFirmware for Duet Ethernet Frequent Disconnects of DWC (3 replies)

wirlybird — Mon, 08 Mar 2021 15:33:39 -0500

Hi all,
Hoping to get some insight into an issue I am having. Here is the info first.

The printer is a Fusion3 F410.
Firmware Name: RepRapFirmware for Duet Ethernet
Firmware Electronics: Duet Ethernet 1.0
Firmware Version: Fusionware 1.18.1 RC2 (2017-05-15)
Web Interface Version: 1.19.3
Web Interface by Christian Hammacher
Licensed under the terms of the GPL v3

The issue I am having is I am getting frequent disconnects with the DWC, Windows 10 with Edge.
This is a replacement printer. The first machine did not have this disconnect issue. Board and firmware etc. should be the same as the first printer.
I am using wired Ethernet connection with a static IP assigned in the printer. Same configuration as the first printer. No changes to router or switch.

I get the typical AJAX disconnect message but the reason given is "unauthorized" rather than timed out or anything else.
This can happen while prints are running or if the printer is sitting idle.

Thank you for any advice and I can try to provide any additional info that may be needed.

Duet wifi Vssa fuse short? (1 reply)

i_c_miller — Thu, 04 Feb 2021 03:24:21 -0500

I am using a duet wifi 1.04 and have had an issue where all thermistors read 2000c. From what I have read this indicates a vssa short. Additionally I measured the resistance from vssa to ground with a multimeter at 200 ohms and got a reading of "0.7". I am honestly newer to hobby electronics so what would be my next course of action for this issue?
I heard for this board version the fuse is self resetting but the thermistor reading persists even after unplugging everything from the board and resetting it.
Any tips are appreciated.

DUET2 IR leveling problem (1 reply)

Jdsuniphase — Wed, 09 Sep 2020 16:20:12 -0400

After I use the IR sensor to automatically level, the nozzle always does not move on the surface of the hot bed when printing documents, and the nozzle is always about 1 mm away from the surface of the bed. Please help me see

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Fri Sep 04 2020 09:43:22 GMT+0800 (中国标准时间)

; General preferences
M80
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"VORON 2.4" ; set printer name
M669 K1 ; select CoreXY mode

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

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P5 S1 R1 ; physical drive 2 goes forwards
M569 P6 S0 R1 ; physical drive 2 goes forwards
M569 P7 S0 R1 ; physical drive 2 goes forwards
M569 P8 S1 R1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z5:6:7:8 E3 ; set drive mapping
M671 X-65:-65:515:515 Y-10:525:525:-10 S20 ; Z leadscrews positions S是最大调整
M350 X16 Y16 Z16 E16 I0 ; configure microstepping without interpolation
M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
M566 X600.00 Y600.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z300.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z30.00 E500.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z-10 S1 ; set axis minima
M208 X240 Y240 Z240 S0 ; set axis maxima

; Endstops
M574 X2 Y2 S0 ; set active low and disabled endstops
M574 Z1 S2 ; set active low and disabled endstops

; Z-Probe
M558 P1 Z0 H8 F120 T6000 ; Set Z probe type mini ir sensorspeed and travel speed
G31 P500 X20 Y30 Z0.567 ;
M557 X50:235 Y50:235 S40 ; define mesh grid

; Heaters
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T80 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 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
M376 H10
M42 P7 I1 S0.5 F500
M280 P7 S50
; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M207 S5 R0.0 F3600 T3600 Z0.00
M572 D0 S0.03
M912 P0 S-8
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

DUET2 uses IR to automatically level the problem (1 reply)

Jdsuniphase — Wed, 09 Sep 2020 16:19:37 -0400

Do not send a file starting with a number from Simply3D! (2 replies)

dlc60 — Mon, 07 Sep 2020 19:06:51 -0400

Others have probably already discovered this - So this is prolly just a message refresh to unbury it :)
I have a hollow icosahedron (20 sided) model that I wanted to test on a new build, called "20sided". My Duet 2 Maestro kept saying command M3220 not supported.
Hmm, not in the gcode, not in my startup script, then, lightbulb! This line in my post-processing commands:

curl "maestro/rr_gcode?gcode=M32[output_filename].gcode"

Oops.

Just a fun item on a Sunday morning.

DLC

CoreXY printer intermittant level shifts45 degrees (3 replies)

dlc60 — Wed, 12 Aug 2020 01:35:23 -0400

I have a scratch built CoreXY that I recently completed. For a couple of weeks it has worked flawlessly, but now I am getting intermittent diagonal layer shifts toward the "X" stepper (the right one looking from the front). I know this is the direction traveled when the X stepper is running and the Y stepper is not. It seems to happen "mostly" on larger models, more compact models 90% of the time will print fine.

When I see the print go wrong, I cancel it. Cancel.g tells the carriage to home X/Y. But, while it homes the X, it gets ALMOST to the Y home switch, but stops before it gets there. Is this related?

My frame is 300mmx400mm using 37oz.in(26Ncm) 12V 0.4Amp 1.8deg steppers.
Controller: Duet 2 Maestro, running the steppers at 800ma
Acceleration 1000mm/s^2
Jerk 15mm/s
Max travel speed 120mm/s (print speed typically under 40mm/s)
I do not think that it is mechanical, I am using a pretty typical (unstacked) CoreXY design, and this is a pretty small printer (200mm bed). Nothing seems to be binding, grinding, catching or skipping when I move it manually. But definitely have heard the "bonking" sound of a stepper balking or a belt skip on a pulley. I don't THINK that my belts are either too tight or too loose, they feel the same as another CoreXY machine that I have. My idlers are free moving and there is nothing, that I can see, that is binding.

CoreXY printers are new to me, I have only had them for the last two months or so. I am not sure where to go to troubleshoot this problem. I have read enough to know that a 45 degree shift to the "back right" means that the "X" stepper is moving when the "Y" stepper is not moving. So, if both steppers should be moving and the "Y" stepper jams, that would shift everything to the diagonal pointing to the "X" stepper. The steppers get a little warm, nothing to worry about. The "bonking" sound sounds like the motor is either balking, or trying to move too fast and the belt is skipping.

Does anyone have a process that they use to troubleshoot this kind of thing? Is my current too low, acceleration too high, steppers too weak, ???
I don't usually start replacing mechanical things when trouble starts, belts, pulleys and motors are really reliable. What are some good steps to take in settings or speeds that can point me to a cause?

Troubleshooting:
I increased the current. No effect.
I reduced accel down to 200mm/s No effect.
I reduced jerk down to 5mm/s No effect.
I have slowed my speeds down by 30% No effect.

When I abort the print, I hear the printer "gronk" like a belt skip as it tries, and fails to home X/Y - It almost never homes Y all the way, but does home the X.
So, now I AM thinking something is catching in the mechanical system - Time for a tear-down?

This is my machine
[attachment 115914 IMG_0644.JPG]
Here is a bad print
[attachment 115915 IMG_0649.JPG]
Here is a good print (from the same time period.)
[attachment 115916 IMG_0651.JPG]

Checking my timeline, I think my problems started when I dressed the cables and put the Maestro in this enclosure (with a fan).
[attachment 115917 IMG_4602.JPG]

Many thanks,
DLC

Duet web interface 3.1.1 print duration? (2 replies)

dlc60 — Mon, 08 Jun 2020 16:37:54 -0400

I have a Duet 2 Maestro running the most recent firmware (3.something) on my scratch-built small CoreXY machine. Duet kicks the Marlin/Octoprint combo up one side and down the other of the road, IMO. With a couple of minor nits.
The Duet tracks times it takes per layer, which is totally cool, but I benchmark my high-speed attempts by looking at the elapsed print time at the end of a print, which the Duet does NOT do, the job duration time is n/a at the end of a print. This seems really strange with all the other intuitive aspects of the RepRap firmware and the Duet web interface. Is there a setting to set or a request form to fill out to get the web interface or the display to tell how long the full print took? I am sure it should be there somewhere, but I cannot find that time.

This system is awesome, I now feel like I wish the board had WiFi so I could put it in the garage with the printer farm. Live and learn.

DLC

Duet 3 resetting during print (no replies)

Via — Wed, 03 Jun 2020 04:55:35 -0400

I have asked on duet forums and awaiting reply, cross posting here to see if anyone has any ideas...

Have a new Duet3 build wired up and working, done a test calibration cube which printed fine. However on longer prints the printer is failing after an hour or so (this is second occurence in a row now, hoped first was one off glitch).

02/06/2020, 19:42:57 	Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)

02/06/2020, 18:17:07 	M32 "0:/gcodes/[PLA ] CFFFP_Top - No Text.gcode"

File 0:/gcodes/[PLA ] CFFFP_Top - No Text.gcode selected for printing

Running 3.1.1, M122 info below. Search brings up a lot of info regarding 3.1.0 that was resolved with 3.1.1 so at a loss currently on what to do next.

M122

=== Diagnostics ===

RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)

Board ID: 08DJM-956L2-G43S4-6J9FA-3S86T-1B5LD

Used output buffers: 1 of 40 (10 max)

=== RTOS ===

Static ram: 154604

Dynamic ram: 162972 of which 56 recycled

Exception stack ram used: 224

Never used ram: 75360

Tasks: NETWORK(ready,1972) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,204) MAIN(running,4944) IDLE(ready,76)

Owned mutexes:

=== Platform ===

Last reset 00:47:22 ago, cause: watchdog

Last software reset at 2020-06-02 18:09, reason: User, spinning module LinuxInterface, available RAM 75056 bytes (slot 2)

Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN

Error status: 0

MCU temperature: min 35.5, current 35.7, max 40.4

Supply voltage: min 13.0, current 13.0, max 13.1, under voltage events: 0, over voltage events: 0, power good: yes

12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0

Driver 0: standstill, reads 62000, writes 14 timeouts 0, SG min/max 0/0

Driver 1: standstill, reads 62000, writes 14 timeouts 0, SG min/max 0/0

Driver 2: standstill, reads 62001, writes 14 timeouts 0, SG min/max 0/0

Driver 3: standstill, reads 62001, writes 14 timeouts 0, SG min/max 0/0

Driver 4: standstill, reads 62001, writes 14 timeouts 0, SG min/max 0/0

Driver 5: standstill, reads 62005, writes 11 timeouts 0, SG min/max 0/0

Date/time: 2020-06-02 20:30:19

Slowest loop: 4.05ms; fastest: 0.14ms

=== Storage ===

Free file entries: 10

SD card 0 not detected, interface speed: 37.5MBytes/sec

SD card longest read time 0.0ms, write time 0.0ms, max retries 0

=== Move ===

Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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 = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1

=== GCodes ===

Segments left: 0

Movement lock held by null

HTTP* is ready with "M122" 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 0, running macro

Aux2 is idle in state(s) 0

Autopause is idle in state(s) 0

Code queue is empty.

=== Network ===

Slowest loop: 0.68ms; fastest: 0.01ms

Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions

HTTP sessions: 0 of 8

- Ethernet -

State: disabled

Error counts: 0 0 0 0 0

Socket states: 0 0 0 0 0 0 0 0

=== CAN ===

Messages sent 11366, longest wait 0ms for type 0

=== Linux interface ===

State: 0, failed transfers: 0

Last transfer: 19ms ago

RX/TX seq numbers: 11820/26640

SPI underruns 0, overruns 0

Number of disconnects: 0

Buffer RX/TX: 0/0-0

=== Duet Control Server ===

Duet Control Server v3.1.1

Daemon:

Finishing macro daemon.g, started by system

> Next stack level

Code buffer space: 4096

Configured SPI speed: 8000000 Hz

Full transfers per second: 32.32