Posts made by Hornetrider

Hi there,

I am experiencing step losses on the X-Axis while printing. This came up a few days ago.
I am using Duet2 Wifi since more then 3 years on this printer and it has been working fine so far.
The motor has always been is a Nema 17, 1.8° with 1.2A rating.

What have I done so far without improvement:

• Installed a brand new Nema 17 with same rating
• Cleaned and checked the X-axis guide for easy movement (without belt)
• exchanged the GT2 9mm belt by a new one
• latest FW update to see if there is any improvement

What I haven't done so far:

• changes to the config file in matters of acceleration, speed and current limits

Here is the section of the config file for the motor settings:
; Speed & Acceleration

M566 X600.00 Y600.00 Z80.00 E1200.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X8000.00 Y8000.00 Z450.00 E6000.00 ; Set maximum speeds (mm/min)
M201 X800.00 Y800.00 Z45.00 E3000.00 ; Set accelerations (mm/s^2)
; Motor Current
M906 X1200.00 Y1200.00 Z1000.00 E950 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S5 ; Set idle timeout

---

Still experiencing erratic loss of steps, sometimes you can even hear them while printing. And then the prints are not good at all...not usable.

My guess right now is that the x-axis driver on the board or the wiring to the motor might have an issue.

Is there a way to run a diagnostic procedure to find any issues?

In case the driver should be the problem, is there a possibility to use the E1 driver instead for the X-Axis?

Looking forward for your inputs.

Hi @RyanP

I have had similar issues with my printer concerning the bed leveling.
Have you tried to mechanically align all axis to the bed?

What helped me was the following procedure:

1. Check with a digital Bevel box if the frame of printer is leveled (x, Y and Z Frame)
   -> If not, get it leveled
2. Check if the bed is leveled with digital Bevel Box
   -> use X & Y Frame as reference (zero bevel box to that reference)
   -> Level it out as good as possible
3. Check X and Y axis are leveled to the bed with a caliper and get this down to 0.1..0.2 mm
   -> It might be that axis are out of level to the frame

Funny thing though, even after mechanically aligning my printer I had a weird effect on the height map.
My finding is, that if the height map shows a clear deviation to one side (mostly X-axis) then the mechanical alignment to the bed might be poor.

@dc42
So no change in wifi connection handling?

@Phaedrux
Thx, I'll give it a try.

BTW. FW1.24 is on the Due

Does FW3.1.1 implement a new FW for WiFi too?

@Phaedrux

see here:
https://forum.duet3d.com/topic/18601/panel-due-hanging-up-after-loss-of-wifi

please also check this thread:
https://forum.duet3d.com/topic/17611/paneldue-crashing/18

More detailed info:

xxxxxxxxxxxxxxxxx
PanelDUE FW: 1.24
Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0 (2020-01-03b3)
Duet WiFi Server Version: 1.23
xxxxxxxxxxxxxxxx

Diag:
Send code...
10.9.2020, 20:26:29 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6J9DD-3SN6R-1SVB9
Used output buffers: 3 of 24 (21 max)
=== RTOS ===
Static ram: 30516
Dynamic ram: 91948 of which 36 recycled
Exception stack ram used: 560
Never used ram: 8012
Tasks: NETWORK(ready,640) HEAT(blocked,1240) MAIN(running,3740) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 84:43:09 ago, cause: software
Last software reset at 2020-09-07 07:42, reason: User, spinning module GCodes, available RAM 8028 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 10
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 390.4ms, max retries 0
MCU temperature: min 32.1, current 34.0, max 36.3
Supply voltage: min 23.9, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/173
Driver 1: standstill, SG min/max 0/155
Driver 2: standstill, SG min/max 0/781
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max 0/176
Date/time: 2020-09-10 20:26:15
Cache data hit count 4294967295
Slowest loop: 84.39ms; fastest: 0.09ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 102, MaxWait: 82940312ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 7, completed moves: 7, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 391.94ms; 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 running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address ec:fa:bc:2d:e8:d1
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25672
WiFi IP address 192.168.1.110
WiFi signal strength -39dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
10.9.2020, 20:26:11 Connected to 192.168.1.110
XXXXXXXXXXXXXXXXXX

Config:
M552 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 S0 ; Drive X goes backwards
M569 P1 S1 ; Drive Y1 goes forwards
M569 P2 S0 ; Drive Z goes forwards
M569 P3 S1 ; Drive E0 goes backwards
M569 P4 S0 ; Drive Y2

M584 X0 Y1:4 Z2 E3 ; Apply custom drive mapping

; Microstepping
M350 X32 Y32 Z16 E16 I1 ; Configure microstepping without interpolation

M92 X160 Y160 Z1600.00 E410 ; @32 X and Y Ratio 24:20 (2020.01.12)Set steps per mm for Bondtech BMG Extruder

; Speed & Acceleration

M566 X600.00 Y600.00 Z80.00 E1200.00 ; Set maximum instantaneous speed changes (mm/min)

M203 X8000.00 Y8000.00 Z400.00 E6000.00 ; Set maximum speeds (mm/min)
;M203 X8000.00 Y8000.00 Z400.00 E6000.00 ; Set maximum speeds (mm/min)

M201 X800.00 Y800.00 Z45.00 E3000.00 ; Set accelerations (mm/s^2)
;M201 X800.00 Y800.00 Z30.00 E3000.00 ; Set accelerations (mm/s^2)

; Motor Current
M906 X1000.00 Y1000.00 Z900.00 E950 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S5 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X295 Y330 Z298 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

; Z-Probe Inductive
;M558 P5 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
;G31 P500 X0 Y0 Z1.42 ; Set Z probe trigger value, offset and trigger height
;M557 X5:170 Y5:275 S40 ; Define mesh grid

; BLTouch
;M307 H4 A-1 C-1 D-1
;M558 P9 F100 H3 R0.3 T7000 A5 B1 ; Set Z probe type to switch and the dive height + speeds
;G31 P25 X-40 Y40 Z2.26 ; Set Z probe trigger value, offset and trigger height
;M557 X5:215 Y5:295 S55 ; Define mesh grid

; Precision Piezo
M558 P8 C"zprobe.in+zprobe.mod" I1 R0.4 H2 F420 T3000 A5 B0 ; Set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z-0.5 ; Set Z probe trigger value, offset and trigger height
M557 X5:285 Y5:330 S93 ; Define mesh grid

; Laser Filament Sensor
;M591 D0 P5 C3 R130:280 E3.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 120%, 3mm comparison length, disabled

; Rotating Magnet Filament Sensor
M591 D0 P3 C3 R70:130 E3.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 120%, 3mm comparison length, disabled

; Heaters RRF3.0x
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; 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
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Heaters RRF2.05
;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
M950 F0 C"fan0" Q500 ; 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

; Board Cooling
M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as thermistor on pin e1temp for left stepper
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 H2:3 L0.15 X1 B0.3 T36:45 ; set fan 2 value

; Fans RRF2.05
;M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
;M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P2 T36:46 H100:101:102 ; Set Fan speed to cool MCU

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

; Automatic saving after power loss is not enabled

; Custom settings are not configured
; MCU temp Adjustment
M912 P0 S-9

; Miscellaneous
T0 ; Select first tool

;load config-override
M501

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Homeall:
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Dec 31 2018 02:05:14 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-300 Y-340 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X10 Y10 F6000 ; go back a few mm
G1 H1 X-15 Y-15 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X147.5 Y167 F8000 ; go to first bed probe point and home Z
M140 S50 ; Set Bed to 50DEC
G10 S210 ; Set current tool temperature to 130C
M116 ; Wait for the temperatures to be reached

G30 ; home Z by probing the bed

;play sound
M400
G4 P200
M300 P200 S523.25
G4 P200
M300 P200 S659.25
G4 P200
M300 P200 S739.99
G4 P250
M300 P285 S880.00
G4 P450
M300 P285 S880.00
G4 P285
M300 P625 S1108.73
G4 P200

G90

XXXXXXXXXXXXX

Hi there

some time ago I have expirienced the behaviour of freezing communication between PanelDue and DuetWifi. And it allways happens when the Wifi Module reports a lost of connection.
After running all latests updates, both on PanelDue and DuetWifi and resetting the Wlan Hotspot (finding a better channel) this issue was gone for a while.
But now last week it started again.
I have rebootet my Hotspot, and set the Wifi channels to less used channels. The connection has become stable again, at least for now.

In my opinion the freeze of the comm is related to the procedure on how the DuetWifi handles the Wifi connection initialisation and time out.
I have also noticed, that right after restart of the DuetWifi and before the Wifi conn is established the communication between the PanelDue ant the DuetWifi is extremly delayed.
For example:

Switch on DuetWifi
run Home all (during this period the Wifi Conn is not established as the machine has something different to do...)
after Home all and without promt of Wifi Conn-> try to activate a Makro or reading out files via PanelDue...extreme delay in 10+ sec
right after the Wifi has established a stable Connection everything works fine and in usual speed
One more thing. The "Wifi lost conn" occurs shortly after the first connection build up (prompt by Duet) or even during a print.
Only the STOP button on the Paneldue keeps working!

More to come...

Just an additional info.

After rebooting my routers and setting up the Wifi to a less used channel, now the connection to the Duet Wifi has become stable again.
But this is a side effect and my impression is, that something in the handling of the Wifi connection reset on the Duet Wifi is odd.

@Phaedrux
ok, got it.
Better creating a lot of personal threads instead of keeping related information for the same event in one single thread.

No problem at all, thx for the advise.

@Veti
Sorry, don't get your point.

HI @Phaedrux

why a new thread if everything is explained here?
Please find requested data below.

xxxxxxxxxxxxxxxxx
PanelDUE FW: 1.24
Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0 (2020-01-03b3)
Duet WiFi Server Version: 1.23
xxxxxxxxxxxxxxxx

Diag:
Send code...
10.9.2020, 20:26:29 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6J9DD-3SN6R-1SVB9
Used output buffers: 3 of 24 (21 max)
=== RTOS ===
Static ram: 30516
Dynamic ram: 91948 of which 36 recycled
Exception stack ram used: 560
Never used ram: 8012
Tasks: NETWORK(ready,640) HEAT(blocked,1240) MAIN(running,3740) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 84:43:09 ago, cause: software
Last software reset at 2020-09-07 07:42, reason: User, spinning module GCodes, available RAM 8028 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 10
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 390.4ms, max retries 0
MCU temperature: min 32.1, current 34.0, max 36.3
Supply voltage: min 23.9, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/173
Driver 1: standstill, SG min/max 0/155
Driver 2: standstill, SG min/max 0/781
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max 0/176
Date/time: 2020-09-10 20:26:15
Cache data hit count 4294967295
Slowest loop: 84.39ms; fastest: 0.09ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 102, MaxWait: 82940312ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 7, completed moves: 7, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 391.94ms; 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 running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address ec:fa:bc:2d:e8:d1
  WiFi Vcc 3.39, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 25672
  WiFi IP address 192.168.1.110
  WiFi signal strength -39dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0
  10.9.2020, 20:26:11 Connected to 192.168.1.110

XXXXXXXXXXXXXXXXXX

Config:
M552 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 S0 ; Drive X goes backwards
M569 P1 S1 ; Drive Y1 goes forwards
M569 P2 S0 ; Drive Z goes forwards
M569 P3 S1 ; Drive E0 goes backwards
M569 P4 S0 ; Drive Y2

M584 X0 Y1:4 Z2 E3 ; Apply custom drive mapping

; Microstepping
M350 X32 Y32 Z16 E16 I1 ; Configure microstepping without interpolation

M92 X160 Y160 Z1600.00 E410 ; @32 X and Y Ratio 24:20 (2020.01.12)Set steps per mm for Bondtech BMG Extruder

; Speed & Acceleration

M566 X600.00 Y600.00 Z80.00 E1200.00 ; Set maximum instantaneous speed changes (mm/min)

M203 X8000.00 Y8000.00 Z400.00 E6000.00 ; Set maximum speeds (mm/min)
;M203 X8000.00 Y8000.00 Z400.00 E6000.00 ; Set maximum speeds (mm/min)

M201 X800.00 Y800.00 Z45.00 E3000.00 ; Set accelerations (mm/s^2)
;M201 X800.00 Y800.00 Z30.00 E3000.00 ; Set accelerations (mm/s^2)

; Motor Current
M906 X1000.00 Y1000.00 Z900.00 E950 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S5 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X295 Y330 Z298 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

; Z-Probe Inductive
;M558 P5 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
;G31 P500 X0 Y0 Z1.42 ; Set Z probe trigger value, offset and trigger height
;M557 X5:170 Y5:275 S40 ; Define mesh grid

; BLTouch
;M307 H4 A-1 C-1 D-1
;M558 P9 F100 H3 R0.3 T7000 A5 B1 ; Set Z probe type to switch and the dive height + speeds
;G31 P25 X-40 Y40 Z2.26 ; Set Z probe trigger value, offset and trigger height
;M557 X5:215 Y5:295 S55 ; Define mesh grid

; Precision Piezo
M558 P8 C"zprobe.in+zprobe.mod" I1 R0.4 H2 F420 T3000 A5 B0 ; Set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z-0.5 ; Set Z probe trigger value, offset and trigger height
M557 X5:285 Y5:330 S93 ; Define mesh grid

; Laser Filament Sensor
;M591 D0 P5 C3 R130:280 E3.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 120%, 3mm comparison length, disabled

; Rotating Magnet Filament Sensor
M591 D0 P3 C3 R70:130 E3.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 120%, 3mm comparison length, disabled

; Heaters RRF3.0x
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; 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
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Heaters RRF2.05
;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
M950 F0 C"fan0" Q500 ; 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

; Board Cooling
M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as thermistor on pin e1temp for left stepper
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 H2:3 L0.15 X1 B0.3 T36:45 ; set fan 2 value

; Fans RRF2.05
;M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
;M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P2 T36:46 H100:101:102 ; Set Fan speed to cool MCU

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

; Automatic saving after power loss is not enabled

; Custom settings are not configured
; MCU temp Adjustment
M912 P0 S-9

; Miscellaneous
T0 ; Select first tool

;load config-override
M501

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Homeall:
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Dec 31 2018 02:05:14 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-300 Y-340 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X10 Y10 F6000 ; go back a few mm
G1 H1 X-15 Y-15 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X147.5 Y167 F8000 ; go to first bed probe point and home Z
M140 S50 ; Set Bed to 50DEC
G10 S210 ; Set current tool temperature to 130C
M116 ; Wait for the temperatures to be reached

G30 ; home Z by probing the bed

;play sound
M400
G4 P200
M300 P200 S523.25
G4 P200
M300 P200 S659.25
G4 P200
M300 P200 S739.99
G4 P250
M300 P285 S880.00
G4 P450
M300 P285 S880.00
G4 P285
M300 P625 S1108.73
G4 P200

G90

XXXXXXXXXXXXX

Any comments at all?

Hi there

some time ago I have also expirienced the same behaviour of freezing communication between PanelDue and DuetWifi. And it allways happens when the Wifi Module reports a lost of connection.
After running all latests updates, both on PanelDue and DuetWifi and resetting the Wlan Hotspot (finding a better channel) this issue was gone for a while.
But now this week it started again.
Today I have rebootet my Hotspot, to hopefully find a new and better 2.4GHz channel and therefore creating a stable connection.

In my opinion the freeze of the comm is related to the procedure how the DuetWifi handles the Wifi connection initialisation and time out.
I have also noticed, that right after restart of the DuetWifi and before the Wifi conn is established the communication between the PanelDue ant the DuetWifi is extremly delayed.
For example:

• Switch on DuetWifi
• run Home all (during this period the Wifi Conn is not established as the machine has something different to do...)
• after Home all and without promt of Wifi Conn-> try to activate a Makro or reading out files via PanelDue...extreme delay in 10+ sec
• right after the Wifi has established a stable Connection everything works fine and in usual speed

One more thing. The "Wifi lost conn" occurs shortly after the first connection build up (prompt by Duet) or even during a print.
Only the STOP button on the Paneldue keeps working!

Any ideas?

@Phaedrux
thx. It works fine with the example.
Should have known that there is documentation arround

Hi

I am currently preparring the change from RRF2.05 to RRF3.0x on my Duet2 WIFI maschine.
I know that with Duet3 we need to create heaters to control fans, alsu for MCU Temp based cooling of the board.

Could sombody help me with Duet2 Wifi and RRF3.0x in this case?

On Duet2 Wifi with RRF2.05 I have used:
M106 P2 T33:45 H100:101:102 ; Set Fan speed to cool MCU

On the Duet3 with RRF3.0x:
M308 S3 Y"mcu-temp" A"MCUTemp" ; configure sensor 3 as MCU Temperature
M308 S4 Y"drivers" A"DriversTemp" ; configure sensor 4 as Dirver Temperature
M950 F2 C"!out4+out4.tach" Q25000 ; create fan 2 on pin out4 and set its frequency
M106 P2 H3:4 T33:45 C"MCU FAN" ; set fan 2 value. Thermostatic control is turned on

Thanks.

Cheers

so, an empty cancel.g should keep heaters on?
or should heaters be selected by T0 & T1 within cancel.g?

thanks for the feedback.

Twisted pairs will become more crucial the higher the speed and load on the CAN is. A high and fixed transmission rate according to the amount of nodes that are applicable is probably the easiest way to reduce application issues.

Well okay if you can use the RJ11 cables that come with the VDSL/ADSL modems, that have to be replaced every now and then, then you have it at home anyway, Problem solved

But any IT store around the corner has at least RJ45 Ethernet cables...these seem to come more durable for moving cables...personal opinion...
In the end it doesn't matter that much, but having to crimp a different connector to the cable and than a tiny JST ...well I don't know, it does just not feel good to me.

@dc42
what is the current transmission rate setup for the CAN FD?

Hi

I have a Duet3 board 6HC in use and I am thinking of implementing the Duet3 toolboard...
But I have come along some thoughts about the selected connectors for the CAN.

1. On the Main board there is a RJ11 for CAN-FD, ok but why not RJ45 ethernet? RJ45 this is widely used...and probably easier to get then old telefone RJ11. And you have better cable categories! Twisted pair!...

2. On the Toolboard a JST connector to connect CAN-FD??? Then you need to cut a Phone Cable/Ethernet Cable to crimp to an JST. Kind of strange.

I would love to use standard cables if possible. Why not using connectors that enable us to buy standard cables?
Btw. for CAN cables twisted pair is extremely recommended, but I find it hard to find RJ11 twisted pair cables..any sources known?

On the other hand, if you use the "tool distribution board" you need to connect the CAN FD via these tiny JST to the Toolboard, okay same connector on both sides, but the "tool distribution board" for a single extruder printer is kind of an overkill.
And how do you deal with the CAN network if from the "tool distribution board" the toolboards are connected like star and not daisy chained? Do you select the longest cable connection and then terminate that one?

What was the thought behind the selection of the connectors for CAN?

Please get me right, I love this equipment and its performance, great job of all involved people.
Just thinking of how to make life easier

Cheers and stay safe
Ric

thx for clarifying.

@dc42
now everything is like it should be... thx a lot!

Hey

it seems that nobody has interest in this topic or that some solutions are around.
I'll keep searching and trying

Cheers