I had this behaviour, but I tracked it down to a faulty network connection on my Deut2. I was looking at my config.g, and lost connectivity temporarily. However the config.g file was now 0K in size. I noticed that whenever my network dropped, it zeroed the file I had open in the editor. I used the config.bak file to get me close to where I was earlier. Now that the network issue has been fixed, all has been good. Thanks for the great support guys.
Posts made by trobison
-
RE: File contents disappearing on RRF 3.4.4posted in General Discussion
-
RE: Spurious heater faults againposted in Using Duet Controllers
Thank you very much for taking the time to explain that. This is very useful. I have set my initial temperatures in the config.g file. Once again, thank you for your time.
-
RE: Spurious heater faults againposted in Using Duet Controllers
@deckingman How do you handle different materials (temperatures)? Thank you for explaining how cura is handling temperature commands.
-
RE: Spurious heater faults againposted in Using Duet Controllers
@deckingman Here are my tool changing configs.
Cura likes to level the bed with a tool attached, and the toolchanger probes the bed without a tool. Anyway, the heater fault only happens with Cura, and not SuperSlicer.
Regards
-
RE: Spurious heater faults againposted in Using Duet Controllers
@deckingman No problem. This is the cura version. https://www.dropbox.com/s/gc7tmprbw0pgb2q/CFFFP_xyzCalibration_cube.gcode?dl=0
and the superslicer version. https://www.dropbox.com/s/c3r9vwbow25h1om/xyzCalibration_cube.gcode?dl=0
This is a test print using Tool 2 with 0.6 nozzle.
-
RE: Spurious heater faults againposted in Using Duet Controllers
@dc42 I get them. I have a E3D toolchanger / duet 2 / RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet Ethernet 1.02 or later + DueX5v0.11.
I seem to get this issue more often when I slice with Cura, less with SuperSlicer. This is strange, but if I heat the extruder up via console to the temp I am going to use (and bed), then submit the job, the issue doesn't happen as often.
I am printing now, but yesterday the same sliced file would not print, mid way into the print I got the heater issue. I "preheated" the extruder and let it set for several min, then committed the job and it's working. This job was sliced with Cura. It's strange, I can't explain it, but it is repeatable.
Regards,
-
RE: How to test duex.pwm5posted in Firmware installation
Cheers guys. I installed a replacement Duex5 board. All working nicely now. I have a question. Is there firmware I have to worry about on the extension board, or is it just that, an extension to the DUET 2 board and firmware is installed there.
-
RE: How to test duex.pwm5posted in Firmware installation
@phaedrux Yes. The same issue. I was asked to send my details to the warranty team. Thank you for following up.
Regards, -
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@t3p3tony I completed this task earlier on 4 April. There was no difference with the servos, but the network does not disconnect and reconnect with a M122. I still can't get Ports PWM5 and PWM5 to function.
-
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@dc42 G'day dc42. Can you provide a way to test the ports on the DueX? I can move the servo to the next port, reconfigure the config.g and send a command to move the servo, but nothing happens. When I configure them from the console, no errors are present. It looks like hardware, but you are correct. It could be a bug.
-
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@airscapes Since I removed the screen, the network has been stable.
I can send an M122 and that will cause the network to disconnect and reconnect at any time. I can work with that. It was convenient to have a screen without a PC near to control the printer if required.My most pressing issue are the ports used to control the servos. I can't get them to function and have no idea how to test this on the expansion board, DueX5.
-
RE: How to test duex.pwm5posted in Firmware installation
@dc42 Sorry, I though I had the output of M122. Here is the output from the console when I powered up the printer, then sent a M122 from the console. Midway down you can see the network drop out after M122 has been sent, then the results from M122. I believe it is running version 3.4.0.
07/04/2022, 22:31:37 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet Ethernet 1.02 or later + DueX5 Board ID: 0JD0M-9P6M2-NWNS0-7J9DJ-3SJ6S-K90RJ Used output buffers: 2 of 24 (19 max) === RTOS === Static ram: 23868 Dynamic ram: 73160 of which 0 recycled Never used RAM 14788, free system stack 118 words Tasks: NETWORK(ready,23.8%,226) HEAT(notifyWait,0.1%,332) Move(notifyWait,0.0%,285) DUEX(notifyWait,0.0%,24) MAIN(running,75.1%,440) IDLE(ready,1.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:01:13 ago, cause: power up Last software reset at 2022-04-07 16:44, reason: User, GCodes spinning, available RAM 15260, slot 1 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 17.5, current 22.2, max 22.4 Supply voltage: min 24.0, current 24.1, max 24.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 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min 0 Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-04-07 22:31:33 Cache data hit count 2629899681 Slowest loop: 6.55ms; fastest: 0.16ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 4.4ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 11, maxWait 44815ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 20, completed 20, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 1, 0.82 reads/min === Network === Slowest loop: 23.75ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 of 8 Interface state active, link 100Mbps full duplex 07/04/2022, 22:31:36 Connection established 07/04/2022, 22:31:36 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 07/04/2022, 22:31:34 M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet Ethernet 1.02 or later + DueX5 Board ID: 0JD0M-9P6M2-NWNS0-7J9DJ-3SJ6S-K90RJ Used output buffers: 2 of 24 (19 max) === RTOS === Static ram: 23868 Dynamic ram: 73160 of which 0 recycled Never used RAM 14788, free system stack 118 words Tasks: NETWORK(ready,23.8%,226) HEAT(notifyWait,0.1%,332) Move(notifyWait,0.0%,285) DUEX(notifyWait,0.0%,24) MAIN(running,75.1%,440) IDLE(ready,1.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:01:13 ago, cause: power up Last software reset at 2022-04-07 16:44, reason: User, GCodes spinning, available RAM 15260, slot 1 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 17.5, current 22.2, max 22.4 Supply voltage: min 24.0, current 24.1, max 24.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 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min 0 Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-04-07 22:31:33 Cache data hit count 2629899681 Slowest loop: 6.55ms; fastest: 0.16ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 4.4ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 11, maxWait 44815ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 20, completed 20, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 1, 0.82 reads/min === Network === Slowest loop: 23.75ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 of 8 Interface state active, link 100Mbps full duplex 07/04/2022, 22:30:54 Connected to 192.168.10.60 -
How to test duex.pwm5posted in Firmware installation
I have decided to start a new thread on my issues. My original query was in Feb. I was experiencing network dropouts. I upgraded to version 3.4 in hopes of removing the dropouts. However, they persisted. I removed anything that could be picking up interference that was non-essential to printing. This included the screen. I found that with the screen removed, the network issues are almost non-existent.
The more pressing issue, I seem to have two servo ports that are not working. For many months before the update, I was using "duex.pwm5" to clean nozzles and the toolchange selected a new extruder. When I reconnected the servo, it no longer worked. I tried “duex.pwm4” and that did not drive a stepper either. But “duex.pwm3” worked. At this point I swapped to a hobby 9G servo for testing to simply as much as possible. I get the same results.
This servo can be driven on “duex.pwm3” but not “duex.pwm4” or “duex.pwm5”. How can I test these ports?
To exercise the servo connected to duex.pwm3 I use:
;Exercise Servo M280 P0 S180 ; Set Servo Position for Wipe to 160 degrees G4 P600 ; Pause 600 ms M280 P0 S1-0 ; Set Servo Position for Wipe to 0 degrees G4 P600 ; Pause 600 ms M280 P0 S180 ; Return to Servo Position for WipeOther interesting behaviour since upgrading to Version 3.4. Sending a M122 causes the network to drop out and then return. I didn’t get this Version 3.3. Is this new and normal?
Current working config.
; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.5 on Sat Nov 13 2021 18:20:50 GMT+1100 (Australian Eastern Daylight Time) ; General preferences M111 S0 ; Debugging off G21 ; Work in millimetres M575 P1 S1 B57600 ; enable support for PanelDue ;M575 P1 S1 B115200 G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"ToolChanger" ; set printer name M669 K1 ; select CoreXY mode ; Network M552 S1 P192.168.10.60 ; enable network and set IP address M553 P255.255.255.0 ; set netmask M554 P192.168.10.1 ; set gateway M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S1 T0 ; Enable Telner ; Drives M569 P0 S0 ; X physical drive 0 goes forwards M569 P1 S0 ; Y physical drive 1 goes forwards M569 P2 S1 ; Z physical drive 2 goes backwards M569 P3 S1 ; E0 physical drive 3 goes backwards M569 P4 S1 ; E1 physical drive 4 goes backwards M569 P5 S1 ; E2 physical drive 5 goes backwards M569 P6 S1 ; E3 physical drive 6 goes backwards M569 P7 S0 ; Coupler physical drive 7 goes forwards M569 P8 S0 ; Unused - physical drive 8 goes forwards M569 P9 S0 ; Unused - physical drive 9 goes forwards M584 X0 Y1 Z2 C7 E3:4:5:6 ; set drive mapping M350 X16 Y16 Z16 E16:16:16:16 I1 ; configure microstepping with interpolation M350 C16 I10 ; Configure microstepping without interpolation M92 X100 Y100 Z800 C91.022 E395:395:395:395 ; set steps per mm M566 X900 Y900 Z8 C2 E800:800:800:800 ; set maximum instantaneous speed changes (mm/min) - Jerk Settings M203 X35000 Y35000 Z1200 C5000 E5000:5000:5000:5000 ; set maximum speeds (mm/min) M201 X6000 Y6000 Z400 C500 E3000:3000:3000:3000 ; set accelerations (mm/s^2) M906 X1800 Y1800 Z1330 I30 ; Idle motion motors to 30% M906 E1000:1000:1000:1000 C500 I10 ; Idle extruder motors to 10% M84 S30 ; Set idle timeout ; Axis Limits M208 X-10 Y-7 Z0 S1 ; set axis minima M208 X350 Y275 Z300 S0 ; set axis maxima M208 C-45:360 ; Endstops M574 X1 Y1 S3 ; Set X / Y endstop stall detection M574 C0 Z0 ; No C Z endstop ; Z probe M558 P8 C"zstop" H3 F360 I0 T20000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds G31 P200 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height M557 X30:333 Y50:249 S40 ; Set probing points ; Heaters M308 S0 P"bedtemp" Y"thermistor" A"Bed" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 q10 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S200 ; set temperature limit for heater 0 to 200C M308 S1 P"e0temp" Y"thermistor" A"T0" T100000 B4725 C7.06e-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 S300 ; set temperature limit for heater 1 to 300C M308 S2 P"e1temp" Y"thermistor" A"T1" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin e1temp M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H2 S300 ; set temperature limit for heater 2 to 300C M308 S3 P"duex.e2temp" Y"thermistor" A"T2" T100000 B4725 C7.06e-8 ; configure sensor 3 as thermistor on pin duex.e2temp M950 H3 C"duex.e2heat" T3 ; create nozzle heater output on duex.e2heat and map it to sensor 3 M307 H3 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H3 S300 ; set temperature limit for heater 3 to 300C M308 S4 P"duex.e3temp" Y"thermistor" A"T3" T100000 B4725 C7.06e-8 ; configure sensor 4 as thermistor on pin duex.e3temp M950 H4 C"duex.e3heat" T4 ; create nozzle heater output on duex.e3heat and map it to sensor 4 M307 H4 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H4 S300 ; set temperature limit for heater 4 to 300C ; Fans M950 F0 C"fan0" Q0 ; create fan 0 on pin fan0 and set its frequency - Fan Not used M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off - Fan not used M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T70 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q0 ; create fan 2 on pin fan2 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off M950 F3 C"duex.fan3" Q500 ; create fan 3 on pin duex.fan3 and set its frequency M106 P3 S1 H2 T70 ; set fan 3 value. Thermostatic control is turned on M950 F4 C"duex.fan4" Q0 ; create fan 4 on pin duex.fan4 and set its frequency M106 P4 S0 H-1 ; set fan 4 value. Thermostatic control is turned off M950 F5 C"duex.fan5" Q500 ; create fan 5 on pin duex.fan5 and set its frequency M106 P5 S1 H3 T70 ; set fan 5 value. Thermostatic control is turned on M950 F6 C"duex.fan6" Q0 ; create fan 6 on pin duex.fan6 and set its frequency M106 P6 S0 H-1 ; set fan 6 value. Thermostatic control is turned off M950 F7 C"duex.fan7" Q500 ; create fan 7 on pin duex.fan7 and set its frequency M106 P7 S1 H4 T70 ; set fan 7 value. Thermostatic control is turned on M950 F8 C"duex.fan8" Q0 ; create fan 8 on pin duex.fan8 and set its frequency M106 P8 S0 H-1 ; set fan 8 value. Thermostatic control is turned off ; Tools M563 P0 S"T0" D0 H1 F2 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"T1" D1 H2 F4 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 S"T2" D2 H3 F6 ; define tool 2 G10 P2 X0 Y0 Z0 ; set tool 2 axis offsets G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C M563 P3 S"T3" D3 H4 F8 ; define tool 3 G10 P3 X0 Y0 Z0 ; set tool 3 axis offsets G10 P3 R0 S0 ; set initial tool 3 active and standby temperatures to 0C ;tool offsets ; !ESTIMATED! offsets for: ; Hemera-tool: X20 Y43.5 Z-6 ; G10 P0 X-0.10 Y-1.0 Z-7 - Use this as initial starting point for leveling nozzle heights to avoid crashing nozzles into bed ; Tool Offsets G10 P0 X-0.00 Y0.00 Z-5.31 ; Tool 0 G10 P1 X-0.32 Y-0.76 Z-5.40 ; Tool 1 G10 P2 X-0.20 Y-0.98 Z-5.42 ; Tool 2 G10 P3 X-0.32 Y-0.96 Z-5.53 ; Tool 3 ; Pressure advance was turned off by default. M572 D0 S0.020 ; pressure advance T0 Hemera M572 D1 S0.020 ; pressure advance T1 M572 D2 S0.020 ; pressure advance T2 M572 D3 S0.020 ; pressure advance T3 ; Custom settings ;Safty Switches M950 J0 C"!^e0stop" ; NC Microswitch - In use on Tool Grabber ;M950 J1 C"!^e1stop" ; NO Microswitch Attached yet (Free) ;Duet 2 WiFi and Ethernet: Use this command to tell RRF about the accelerometer: ;M955 P0 C"spi.cs4+spi.cs3" M593 P"zvd" F42.5 ; use ZVD input shaping to cancel ringing at ;M593 P"none" ; disable input shaping ; Pebble Wiper Config M950 S2 C"duex.pwm5" ; Port 2 M950 S1 C"duex.pwm4" ; Port 1 M950 S0 C"duex.pwm3" ; Port 0 ; Miscellaneous M501 ; load saved parameters from non-volatile memoryM98 P"config.g"
HTTP is enabled on port 80 FTP is disabled TELNET is enabled on port 23 Warning: Heater 0 predicted maximum temperature at full power is 551°C Warning: Heater 1 predicted maximum temperature at full power is 495°C Warning: Heater 2 predicted maximum temperature at full power is 470°C Warning: Heater 4 predicted maximum temperature at full power is 542°C -
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@phaedrux This was my working config.g with Version 3.3
; Servo Config M950 S0 C"duex.pwm5"and to exercise the servo:
M280 P0 S180 ; Set Servo Position for Wipe to 160 degrees G4 P600 ; Pause 600 ms M280 P0 S1-0 ; Set Servo Position for Wipe to 0 degrees G4 P600 ; Pause 600 ms M280 P0 S180 ; Return to Servo Position for WipeAfter the update to version 3.4, I couldn't get the servo working. I have moved to duex.pwm3. duex.pwm4 did not work, this port never had anything connected to it previously.
Current config.g has this definition.
M950 S0 C"duex.pwm3" ; Port 0and to exercise the servo:
M280 P0 S180 ; Set Servo Position for Wipe to 160 degrees G4 P600 ; Pause 600 ms M280 P0 S1-0 ; Set Servo Position for Wipe to 0 degrees G4 P600 ; Pause 600 ms M280 P0 S180 ; Return to Servo Position for WipeI have been testing with a small hobby 9G servo. It works in duex.pwm3 but not in duex.pwm4 or duex.pwm5.
-
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@phaedrux I'm not sure if I can even print without the Duex. Functionality is spread across the two boards. What is concerning is the PWM4 and PWM4 ports can't drive a servo. PWM5 worked before, but PWM4 was never tested until I was looking for a functioning port. Can these be tested. I tried downgrading and that did not work. I am back at Version 3.4 and switched my servo to PWM3. PWM1 and PWM2 are in use .
-
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@trobison I downgraded to version 3.3. I then reinstalled the SD Card with my version 3.3 config files. This version had a working servo on PWM5 on the DuetX5 board. After the downgrade, I could not get this working nor PWM5. I performed a M122 all looked good. It was running 3.3 not errors.
I performed another upgrade to 3.4. I performed another M122. This verified that I was now running version 3.4. An interesting observation is that M122 causes a network disconnect and reconnect. I did not get this with version 3.3. Perhaps M122 now cycles the network now.
I have two ports that are not driving my servos (PWM4 and PWM5). Is there a way to test these ports? I have not connected a servo to PWM4 until PWM5 stopped working. I have a functioning servo on PWM3 used to clean nozzles on tool changes.
-
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@phaedrux Ok, but I'm not keen on rolling it back. It is printing nicely. Do I just update to version 3.3, and that downgrades it?
-
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@trobison
I conducted a few more tests. The first was the tap tests as suggested. No effect that I could detect. The next test was a vibration test. I made an apparatus to send vibrations into the printer frame. This had no effect that I could detect.Then I had the idea of removing the only interface that allowed me to cancel or control the printer when the network stopped, the screen. The network stayed up. Then I thought this must be where the interference was coming from over the unshielded four-wire connection. I cut up a shielded USB cable and created another cable (shielded) to run from the Duet2 to the screen. It faulted but had significantly fewer errors dropping from every 30 seconds to around 2 per hour.
The next test was to remove the four-wire cable and try the 10 wire ribbon cable. I still get network errors. I didn’t try shielding this cable at this point.
I have no issues with the printer after submitting the print job. But when the network dropouts start, this effectively removes any ability to interact with the printer until I cycle the power via the webpage. I can stop and start the network with a PI and telnet session, that has no effect on correcting the problem. The issue remains until I cycle the Duet.
I still have to determine where the issue is. Is it the screen? Is it a noisy chip on the board? Is it a stepper motor?
I put a clamp on the 24v rail to record the current draw. 1.8 amps while printing. I didn't see any significant deviation in the current draw while printing (0.1 amp).
I can leave the printer powered on for hours and I have no issues with the network. It’s only after some time into a print the network becomes a real issue. Can a faulty screen knock the printer’s network out? I have experienced the same results with shielded and unshielded four wire connection, and with the 10 wire ribbon connection.
I have not been able to get my servo running for cleaning nozzles since I removed everything to simplify testing. The configuration has not changed. The servo definition was the same as I had before upgrading to version 3.4 from 3.3. It worked for months under 3.3, but stopped under 3.4.
After I reconnected the wires, the servo did not work. I tried with a hobby servo in its place as a test and this did not work either.
I tried another port by changing my configuration:
M950 S0 C"duex.pwm5" to M950 S0 C"duex.pwm3"After the change, the servo works using duex.pwm3. I tried to restore the original configuration back to "duex.pwm5" the original port with the original setting that worked for months. I can't get it to work now. I also tried C"duex.pwm4" and that does not drive the servo either. Is there a way to test "duex.pwm5" and "duex.pwm4".
Without the Panel/Screen connected, the network chip is still warm. Is this within spec? What is considered too hot? I have included a photo.
This is the network chip in the image.Sorry for the long post.
M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is enabled on port 23 Warning: Heater 0 predicted maximum temperature at full power is 551°C Warning: Heater 1 predicted maximum temperature at full power is 495°C Warning: Heater 2 predicted maximum temperature at full power is 470°C Warning: Heater 4 predicted maximum temperature at full power is 542°C ``` -
RE: Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnectposted in Duet Web Control
@airscapes I can give it a go. There is a print on there now, with...
Connection interrupted, attempting to reconnect...
Operation failed (Reason: Service Unavailable) every 30 seconds.
Once this has started, the only way to recover is to cycle the Duet 2.