@dc42 yeah, definitely is more sensitivity. Either way, my suggestion is so long as the units are consistent between messaging and configuration, I think it'll be more intuitive.

In addition to this. This IDEX also uses independent z leveling on a kinematic coupling. Instead of just moving the bed up and down, wouldn't it be more ideal if the bed also tilted to match the height of both nozzles instead of just one?

So there is no power recovery with DuetPi at this time correct?

@bot said in Could Duet2 cause this? CoreXY skew.:

@GeorgeM that’s funny! Glad you figured it out.

If you would still like to adjust scaling, you can use the M579 command.

Thanks bot, that is my next move.

I thought I'd follow-up on this post as I hate when people leave the thread hanging. I received my new (genuine) ethernet module from the US - I have plugged it in and everything is working as it should be. This is a timely lesson to me as I was getting lazy in turning off my duet when switching out hardware (fans in this case). I think I got off extremely lightly!
Thanks again for the help.

@empi00 said in Duet 2 Wifi to Duet 3 --> config and some general questions:

moving from a Duet Wifi FW3 to a Duet 3

gotcha, then just the pin names, the Duet3 are all generic like out0 etc. so e0heat becomes out1 etc.

ref https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names has a list for all the boards to compare.

The stepper drivers are still named 0...5 so if you wire them according to their old numbers then no change to the config - except you can add stealth chop settings.

@Phaedrux said in Software bundle 3.1.1 now available:

Plus if you used the USB method, you'd still need to make sure the IAP programing files are on the SD card so that future firmware updates work, and you'd still have to update DWC either manually or by upload.

i could be wrong, but uploading 1 zip file, answer "no" to doing the upgrade in dwc and then running bossa could be the shortest possible path, but limited testing admittedly.

M122:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7J1FJ-3SJ6S-189BQ
Used output buffers: 3 of 24 (21 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93732 of which 44 recycled
Exception stack ram used: 472
Never used ram: 8844
Tasks: NETWORK(ready,364) HEAT(blocked,768) MAIN(running,1880) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:49:56 ago, cause: power up
Last software reset at 2020-07-05 21:24, reason: User, spinning module GCodes, available RAM 9912 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 26.6, current 28.8, max 29.6
Supply voltage: min 23.8, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/87
Driver 1: standstill, SG min/max 61/185
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: 2020-07-05 22:42:51
Cache data hit count 4294967295
Slowest loop: 16.89ms; fastest: 0.13ms
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 4.5ms, write time 5.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 1465810ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 15, completed moves: 15, 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, 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 79.80ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
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.23
WiFi MAC address bc:dd:c2:2d:67:97
WiFi Vcc 3.39, reset reason Unknown
WiFi flash size 4194304, free heap 21720
WiFi IP address 10.1.2.149
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

@FelixH there is precision piezo orion that do the same thing as smart effector...i use it on my hypercube printer...and i also have 3 kossels with smart effectors on it...and the result is the same...very good stuff...(for my delta printers the smart effector along with magnetic arms and duet2 wifi was the best decision i made, on my hypercube the duet2 wifi and precision piezo orion v2 was the best decision i made)on my cartesian printer(prusa clone) i use bltouch...because is what was the best at that time, though if i had to make it again i 100% go with precision piezo...

@7ambrion most of them will have some sort of preview in the slicer before the file is exported or sendt to the printer.

@Phaedrux
The motor wires were connected incorrectly and I just disable the fan function in the RepRap firmware because I did not order the corresponding wires yet. Anyways, the homing of the x and y-axis works well now.
Thank you.

@Phaedrux Holy crap I didn't know. Thanks for passing this on

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Sat Jul 04 2020 14:57:29 GMT+0200 (heure d’été d’Europe centrale)
M561 ; clear any bed transform
G28 ; home all towers
; Probe the bed at 10 peripheral and 6 halfway points, and perform 9-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y88.34 H0 Z-99999
G30 P1 X62.31 Y85.77 H0 Z-99999
G30 P2 X114.13 Y37.08 H0 Z-99999
G30 P3 X114.13 Y-37.08 H0 Z-99999
G30 P4 X70.53 Y-97.08 H0 Z-99999
G30 P5 X0 Y-120 H0 Z-99999
G30 P6 X-64.49 Y-88.76 H0 Z-99999
G30 P7 X-85.63 Y-27.82 H0 Z-99999
G30 P8 X-77.81 Y25.28 H0 Z-99999
G30 P9 X-47.8 Y65.79 H0 Z-99999
G30 P10 X0 Y33.72 H0 Z-99999
G30 P11 X46.71 Y26.97 H0 Z-99999
G30 P12 X51.96 Y-30 H0 Z-99999
G30 P13 X0 Y-60 H0 Z-99999
G30 P14 X-31.82 Y-18.37 H0 Z-99999
G30 P15 X-26.38 Y15.23 H0 Z-99999
G30 P16 X0 Y0 H0 Z-99999 S9
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

I've made a note to fix the truncation of M207 output when there are >= 4 tools in firmware 3.2.

@Phaedrux https://www.youtube.com/watch?v=BZSb0JCWcXk

@dc42 said in Duet 3 WiFi:

@nriviera said in Duet 3 WiFi:

Is there a plan for a cheaper option with a CAN bus? I think the biggest draw card for the Duet3 is then can bus with more people making tool changers of late but don't need to run large steppers.

We are already planning a Duet 3 main board with outputs for external stepper drivers (probably between 6 and 😎 instead of having six drivers on board. It is aimed at those building large machines using step-servo drives.

Looks like an alternative to the Mach 3/4 environment, right?

AFAIR we didn't remove any fields from the JSON response, although we may have added some.

I do appreciate all your attention to this. You were able to get me corrected about the U parameters. That's a win.

I do need to start a new thread about why my laser wont operate from gcode commands.

@Émile said in Maestro U3 burned:

Is there a warranty?

https://www.duet3d.com/warranty

short version leave a note for the admins when and where you purchased it and they'll be along to evaluate / ask questions to determine the cause and action to take if still under warranty.

Is the G-Code something like G1 A32.5?

You can post-process the script and change this command to M280 P0 S32.5...