Firmware 1.20 released
-
so it is working… I recorded this so I could show it if it didn't work and see if I was doing something wrong or it was omething that you guys could see I was missing, or what ever... anyway.. I'll post it for kicks.
https://youtu.be/ICiRkWutB2U -
I had problems installing newer versions than 1.19 on my Duet 0.6 - it would not run.
Can I use the 1.20 on this old board or is the board limited to 1.19?
-
Yes there is a build of 1.20 for the Duet 0.6 and 0.8.5.
-
Great! Thanks.
-
I'm still having problems I'm afraid. Cannot connect to my Duet 0.6 after upgrade to 1.20.1 (RepRapFirmware.bin). I can see that it boots up and runs for about 25 secs, then both ethernet connecor LEDs go out for 3-4 seconds and pattern repeats over an over.
I've installed manually the DuetWebControl associated with this firmware release.
Any ideas?
Regards /Thom
-
I tested 1.20 on a Duet 0.8.5 but not on a 0.6. You could try putting a minimal config.g file on the SD card, with the network parameters and not much else in it.
Version 1.19.2 was tested on a Duet 0.6.
-
This is my current config.g
[c]
; Configuration file for Duet 0.6 (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Fri Nov 17 2017 18:51:38 GMT+0100 (Västeuropa, normaltid); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P1 ; Set firmware compatibility to look like RepRapFirmare;Delta parameters
M665 L190.000 R90 H236.8 B72.0 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; Endstops
M208 Z-0.5 S1 ; Set minimum Z; Endstops
M574 X2 Y2 Z2 S1 ; Set active high endstops
M558 P4 X0 Y0 Z0 H4 F120 T8000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
G31 P600 X0 Y0 Z-0.10 ; Set Z probe trigger value, offset and trigger height
M557 R78 S20 ; Bed mesh; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M92 X100 Y100 Z100 E141.8 ; Set steps per mm
M566 X1200 Y1200 Z1200 E1500 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E12000 ; Set maximum speeds (mm/min)
M201 X2200 Y2200 Z2200 E2000 ; Set accelerations (mm/s^2)
M906 X960 Y960 Z960 E1600 I60 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B3950 C0 R1000 H10 ; Set thermistor + ADC parameters for heater 0
M143 H0 S130 ; Set temperature limit for heater 0 (bed) to 130C
M305 P1 T100000 B4267 C0 R1000 H10 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C; 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; Network
M550 PMy Mini Kossel ; Set machine name
M540 PBE:EF:DE:AD:FE:ED ; Set MAC address
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency.
; thermostatic control is turned off; Read in calibration override settings
M501
G29 S1 ; Read in bed height correction map; Miscellaneous
T0 ; Select first tool
[/c]I'm going to try the network parameters only and then if I manage to connect to it, I'll uncomment paragraphs
step by step./Thom
-
I'm still having problems I'm afraid. Cannot connect to my Duet 0.6 after upgrade to 1.20.1 (RepRapFirmware.bin). I can see that it boots up and runs for about 25 secs, then both ethernet connecor LEDs go out for 3-4 seconds and pattern repeats over an over.
I've installed manually the DuetWebControl associated with this firmware release.
Any ideas?
Regards /Thom
This sounds exactly like my problem with 0.85 too.
I did not think about simplifying the config.g, since this is not an option to my opinion, but I am curious to see the results. I am still on 1.18.1 because of that. The 1.19 does run, but it is very unstable, and the 1.20 will not start up at all with my config. -
I'm able to make connection via the USB port using Repetier-Host V2.05. A short clip from the serial log:
[c]22:27:09.813 : RepRapFirmware for Duet is up and running.
22:27:09.816 : N10 M111 S686
22:27:09.816 : FIRMWARE_NAME: RepRapFirmware for Duet FIRMWARE_VERSION: 1.20.1RC2 ELECTRONICS: Duet 0.6 FIRMWARE_DATE: 2018-01-01
22:27:09.816 : N11 T010
22:27:09.847 : X:0.000 Y:0.000 Z:0.000 E0:0.0 E1:0.0 E2:0.0 E3:0.0 E4:0.0 E5:0.0 Count 0 0 0 User 0.0 0.0 0.0
22:27:09.847 : serial: T0
22:27:09.847 : serial: M20
22:27:09.847 : Begin file list
22:27:09.849 : Enclosures
22:27:09.849 : Kossel
22:27:09.849 : Art
22:27:09.849 : Supports and mounts
22:27:09.849 : X5S
22:27:09.849 : Couplings
22:27:09.849 : MK PLA L015 N035 (Noraft) PrtAlignmentModel.gcode
22:27:09.849 : Diverse
22:27:09.849 : Gee(i3)
22:27:09.849 : Alu profile 20x20
22:27:09.852 : End file list
22:27:09.852 : serial: M80
22:27:09.852 : serial: M105
22:27:09.853 : serial: M111 S6
22:27:09.853 : serial: T0
22:27:12.803 : N12 M10520
22:27:12.805 : serial: M105
22:27:15.863 : N13 M10521
22:27:15.864 : serial: M105
22:27:18.929 : N14 M10518
22:27:18.930 : serial: M105
22:27:21.989 : N15 M10519
22:27:21.990 : serial: M105
22:27:25.048 : N16 M10516
22:27:25.049 : serial: M105
22:27:28.114 : N17 M10517
22:27:28.114 : serial: M105
22:27:31.174 : N18 M10530
22:27:31.175 : serial: M105
22:27:34.240 : N19 M10531
22:27:34.241 : serial: M105
22:27:37.300 : N20 M10521
22:27:37.301 : serial: M105
22:27:40.367 : N21 M10520
22:27:40.368 : serial: M105
22:27:43.426 : N22 M10523
22:27:43.428 : serial: M105
22:27:46.492 : N23 M10522
22:27:46.493 : serial: M105
22:27:49.552 : N24 M105*17
22:27:49.553 : serial: M105
[/c]However, if I connect the Ethernet cable, Repetier-Host gets disconnected and the Reboot pattern starts to run again. The current config.g:
[c]
; Configuration file for Duet 0.6 (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Fri Nov 17 2017 18:51:38 GMT+0100 (Västeuropa, normaltid); General preferences
;M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
;M83 ; ...but relative extruder moves
;M555 P1 ; Set firmware compatibility to look like RepRapFirmare;Delta parameters
;M665 L190.000 R90 H236.8 B72.0 ; Set delta radius, diagonal rod length, printable radius and homed height
;M666 X0 Y0 Z0 ; Endstops
;M208 Z-0.5 S1 ; Set minimum Z; Endstops
;M574 X2 Y2 Z2 S1 ; Set active high endstops
;M558 P4 X0 Y0 Z0 H4 F120 T8000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
;G31 P600 X0 Y0 Z-0.10 ; Set Z probe trigger value, offset and trigger height
;M557 R78 S20 ; Bed mesh; Drives
;569 P0 S1 ; Drive 0 goes forwards
;569 P1 S1 ; Drive 1 goes forwards
;M569 P2 S1 ; Drive 2 goes forwards
;M569 P3 S1 ; Drive 3 goes forwards
;M92 X100 Y100 Z100 E141.8 ; Set steps per mm
;M566 X1200 Y1200 Z1200 E1500 ; Set maximum instantaneous speed changes (mm/min)
;M203 X18000 Y18000 Z18000 E12000 ; Set maximum speeds (mm/min)
;M201 X2200 Y2200 Z2200 E2000 ; Set accelerations (mm/s^2)
;M906 X960 Y960 Z960 E1600 I60 ; Set motor currents (mA) and motor idle factor in per cent
;M84 S30 ; Set idle timeout; Heaters
;M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
;M305 P0 T100000 B3950 C0 R1000 H10 ; Set thermistor + ADC parameters for heater 0
;M143 H0 S130 ; Set temperature limit for heater 0 (bed) to 130C
;M305 P1 T100000 B4267 C0 R1000 H10 ; Set thermistor + ADC parameters for heater 1
;M143 H1 S280 ; Set temperature limit for heater 1 to 280C; 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; Network
M550 PMy Mini Kossel ; Set machine name
M540 PBE:EF:DE:AD:FE:ED ; Set MAC address
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Fans
;M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency.
; thermostatic control is turned off; Read in calibration override settings
;M501
;G29 S1 ; Read in bed height correction map; Miscellaneous
;T0 ; Select first tool
[/c] -
As I work with embedded systems myself I see the typical symptoms of a stack crash. While watching the output from the serial line I could observe some kind of "hartbeat" messages from classes running inside the Duet. All seems normal until I plug the ethernet cable in. Then everything just stops.
-
If you run M122 from USB, how much free memory does it report?
-
I'm not sure wich number you're after so I copied the entire response:
[c]17:34:17.138 : serial: M122
17:34:17.143 : LINK
17:34:17.145 : xmit: 0
17:34:17.145 : recv: 0
17:34:17.145 : fw: 0
17:34:17.145 : drop: 0
17:34:17.145 : chkerr: 0
17:34:17.145 : lenerr: 0
17:34:17.145 : memerr: 0
17:34:17.145 : rterr: 0
17:34:17.145 : proterr: 0
17:34:17.145 : opterr: 0
17:34:17.145 : err: 0
17:34:17.145 : cachehit: 0
17:34:17.145 : ETHARP
17:34:17.145 : xmit: 0
17:34:17.145 : recv: 0
17:34:17.145 : fw: 0
17:34:17.145 : drop: 0
17:34:17.145 : chkerr: 0
17:34:17.145 : lenerr: 0
17:34:17.145 : memerr: 0
17:34:17.145 : rterr: 0
17:34:17.146 : proterr: 0
17:34:17.146 : opterr: 0
17:34:17.146 : err: 0
17:34:17.146 : cachehit: 0
17:34:17.146 : IP_FRAG
17:34:17.146 : xmit: 0
17:34:17.146 : recv: 0
17:34:17.146 : fw: 0
17:34:17.146 : drop: 0
17:34:17.146 : chkerr: 0
17:34:17.146 : lenerr: 0
17:34:17.146 : memerr: 0
17:34:17.146 : rterr: 0
17:34:17.146 : proterr: 0
17:34:17.146 : opterr: 0
17:34:17.146 : err: 0
17:34:17.146 : cachehit: 0
17:34:17.146 : IP
17:34:17.146 : xmit: 0
17:34:17.146 : recv: 0
17:34:17.146 : fw: 0
17:34:17.146 : drop: 0
17:34:17.146 : chkerr: 0
17:34:17.146 : lenerr: 0
17:34:17.147 : memerr: 0
17:34:17.147 : rterr: 0
17:34:17.147 : proterr: 0
17:34:17.147 : opterr: 0
17:34:17.147 : err: 0
17:34:17.147 : cachehit: 0
17:34:17.147 : IGMP
17:34:17.147 : xmit: 0
17:34:17.147 : recv: 0
17:34:17.147 : drop: 0
17:34:17.147 : chkerr: 0
17:34:17.147 : lenerr: 0
17:34:17.147 : memerr: 0
17:34:17.147 : proterr: 0
17:34:17.147 : rx_v1: 0
17:34:17.147 : rx_group: 0
17:34:17.147 : rx_general: 0
17:34:17.147 : rx_report: 0
17:34:17.147 : tx_join: 0
17:34:17.148 : tx_leave: 0
17:34:17.148 : tx_report: 0
17:34:17.148 :
17:34:17.148 : ICMP
17:34:17.148 : xmit: 0
17:34:17.148 : recv: 0
17:34:17.148 : fw: 0
17:34:17.148 : drop: 0
17:34:17.148 : chkerr: 0
17:34:17.148 : lenerr: 0
17:34:17.148 : memerr: 0
17:34:17.148 : rterr: 0
17:34:17.148 : proterr: 0
17:34:17.148 : opterr: 0
17:34:17.148 : err: 0
17:34:17.148 : cachehit: 0
17:34:17.148 : UDP
17:34:17.148 : xmit: 0
17:34:17.148 : recv: 0
17:34:17.148 : fw: 0
17:34:17.148 : drop: 0
17:34:17.148 : chkerr: 0
17:34:17.148 : lenerr: 0
17:34:17.148 : memerr: 0
17:34:17.149 : rterr: 0
17:34:17.149 : proterr: 0
17:34:17.149 : opterr: 0
17:34:17.149 : err: 0
17:34:17.149 : cachehit: 0
17:34:17.149 : TCP
17:34:17.149 : xmit: 0
17:34:17.149 : recv: 0
17:34:17.149 : fw: 0
17:34:17.149 : drop: 0
17:34:17.149 : chkerr: 0
17:34:17.149 : lenerr: 0
17:34:17.149 : memerr: 0
17:34:17.149 : rterr: 0
17:34:17.149 : proterr: 0
17:34:17.149 : opterr: 0
17:34:17.149 : err: 0
17:34:17.149 : cachehit: 0
17:34:17.149 : MEM HEAP
17:34:17.149 : avail: 1024
17:34:17.150 : used: 0
17:34:17.150 : max: 0
17:34:17.150 : err: 0
17:34:17.150 : MEM UDP_PCB
17:34:17.150 : avail: 5
17:34:17.150 : used: 2
17:34:17.150 : max: 2
17:34:17.150 : err: 0
17:34:17.150 : MEM TCP_PCB
17:34:17.150 : avail: 16
17:34:17.150 : used: 0
17:34:17.150 : max: 0
17:34:17.150 : err: 0
17:34:17.150 : MEM TCP_PCB_LISTEN
17:34:17.151 : avail: 4
17:34:17.151 : used: 0
17:34:17.151 : max: 0
17:34:17.151 : err: 0
17:34:17.151 : MEM TCP_SEG
17:34:17.151 : avail: 16
17:34:17.151 : used: 0
17:34:17.151 : max: 0
17:34:17.151 : err: 0
17:34:17.151 : MEM REASSDATA
17:34:17.151 : avail: 2
17:34:17.151 : used: 0
17:34:17.151 : max: 0
17:34:17.151 : err: 0
17:34:17.151 : MEM FRAG_PBUF
17:34:17.151 : avail: 8
17:34:17.151 : used: 0
17:34:17.151 : max: 0
17:34:17.151 : err: 0
17:34:17.151 : MEM IGMP_GROUP
17:34:17.152 : avail: 8
17:34:17.152 : used: 0
17:34:17.152 : max: 0
17:34:17.152 : err: 0
17:34:17.152 : MEM SYS_TIMEOUT
17:34:17.152 : avail: 8
17:34:17.152 : used: 6
17:34:17.152 : max: 6
17:34:17.152 : err: 0
17:34:17.152 : MEM PBUF_REF/ROM
17:34:17.152 : avail: 4
17:34:17.152 : used: 0
17:34:17.152 : max: 0
17:34:17.152 : err: 0
17:34:17.152 : MEM PBUF_POOL
17:34:17.152 : avail: 5
17:34:17.152 : used: 0
17:34:17.152 : max: 0
17:34:17.152 : err: 0
17:34:17.152 : === Diagnostics ===
17:34:17.153 : Used output buffers: 1 of 32 (15 max)
17:34:17.153 : === Platform ===
17:34:17.153 : RepRapFirmware for Duet version 1.20.1RC2 running on Duet 0.6
17:34:17.153 : Static ram used: 44836
17:34:17.153 : Dynamic ram used: 40508
17:34:17.153 : Recycled dynamic ram: 672
17:34:17.153 : Stack ram used: 3520 current, 5528 maximum
17:34:17.153 : Never used ram: 6760
17:34:17.154 : Last reset 00:07:46 ago, cause: power up
17:34:17.154 : Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 8620 bytes (slot 2)
17:34:17.154 : Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087e6c
17:34:17.155 : Stack: 000bfb1f 01c8a8c0 fffffff9 00ffffff 20087ebc 20070fe8 01c8a8c0 20087ebc 000a6221 000a6220 21000000 20087ea0 2007a938 00000000 2007376c 200737a8 20087ebc 0000012c 2007aea8 75207369 01c8a8c0 2007376c 000a5b1d 2001376c
17:34:17.155 : Error status: 0
17:34:17.155 : Free file entries: 10
17:34:17.155 : SD card 0 detected, interface speed: 21.0MBytes/sec
17:34:17.155 : SD card longest block write time: 0.0ms
17:34:17.155 : MCU temperature: min 26.2, current 27.3, max 27.8
17:34:17.156 : Date/time: 1970-01-01 00:00:00
17:34:17.156 : Slowest main loop (seconds): 0.009165; fastest: 0.000104
17:34:17.156 : === Move ===
17:34:17.156 : MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0
17:34:17.156 : Scheduled moves: 0, completed moves: 0
17:34:17.156 : Bed compensation in use: none
17:34:17.157 : Bed probe heights: 0.000 0.000 0.000 0.000 0.000
17:34:17.157 : === Heat ===
17:34:17.157 : Bed heaters = 0, chamberHeaters = -1 -1
17:34:17.157 : === GCodes ===
17:34:17.157 : Segments left: 0
17:34:17.157 : Stack records: 1 allocated, 0 in use
17:34:17.157 : Movement lock held by null
17:34:17.157 : http is idle in state(s) 0
17:34:17.157 : telnet is idle in state(s) 0
17:34:17.157 : file is idle in state(s) 0
17:34:17.157 : serial is ready with "M122" in state(s) 0
17:34:17.158 : aux is idle in state(s) 0
17:34:17.158 : daemon is idle in state(s) 0
17:34:17.158 : queue is idle in state(s) 0
17:34:17.158 : autopause is idle in state(s) 0
17:34:17.158 : Code queue is empty.
17:34:17.158 : === Network ===
17:34:17.158 : Free connections: 16 of 16
17:34:17.158 : Free transactions: 24 of 24
17:34:17.158 : Locked: 0, state: 2, listening: 0x0, 0x0, 0x0
[/c] -
The "heartbeat" message
[c]17:36:25.475 : N151 M10534
17:36:25.476 : serial: M105
17:36:28.535 : N152 M10533
17:36:28.537 : serial: M105
17:36:31.062 : Class GCodes spinning
17:36:31.062 : Class Move spinning
17:36:31.062 : Class Platform spinning
17:36:31.062 : Class Network spinning
17:36:31.062 : Class Network spinning
17:36:31.064 : Class Heat spinning
17:36:31.064 : Class PrintMonitor spinning
17:36:31.601 : N153 M10532
17:36:31.602 : serial: M105
17:36:34.660 : N154 M10539
17:36:34.661 : serial: M105
17:36:37.720 : N155 M10538
17:36:37.721 : serial: M105
17:36:40.786 : N156 M10537
17:36:40.787 : serial: M105
[/c] -
I upgraded my Duet WiFi firmware from 1.19 to 1.20 yesterday. All seems to be working but I'm getting strange error messages when I start a print. They start at layer 0 but I was slow to capture them - each layer gives an error like this:
[c]17:34:59Error: Bad command: // starting layer 19 at 2.47368mm
17:34:47Error: Bad command: // starting layer 18 at 2.4mm
17:34:35Error: Bad command: // starting layer 17 at 2.2mm
17:34:24Error: Bad command: // starting layer 16 at 2.18947mm
17:34:12Error: Bad command: // starting layer 15 at 2mm
17:34:01Error: Bad command: // starting layer 14 at 1.90526mm
17:33:49Error: Bad command: // starting layer 13 at 1.8mm
17:33:37Error: Bad command: // starting layer 12 at 1.62105mm
[/c]The print worked OK but layer height was 0.2mm so I'm a little surprised by some of the layer heights.
What does this mean, please?
Thanks.
Richard
(edited to correct the starting layer from 1 to 0)
-
OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"
The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.
I'll report back once I confirm that this is the issue and is sorted.
-
This is confirmed - it was a slicer setting, nothing at all to do with the Duet firmware but a bit strange that the prior version didn't report errors with that format. Anyway, all sorted, thanks.
OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"
The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.
I'll report back once I confirm that this is the issue and is sorted.
-
This is confirmed - it was a slicer setting, nothing at all to do with the Duet firmware but a bit strange that the prior version didn't report errors with that format. Anyway, all sorted, thanks.
OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"
The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.
I'll report back once I confirm that this is the issue and is sorted.
It's because RRF now recognises lower case command letters, and also parses lines of gcode more thoroughly.
-
I'm not sure wich number you're after so I copied the entire response:
…
17:34:17.154 : Last reset 00:07:46 ago, cause: power up
17:34:17.154 : Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 8620 bytes (slot 2)
17:34:17.154 : Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087e6c
17:34:17.155 : Stack: 000bfb1f 01c8a8c0 fffffff9 00ffffff 20087ebc 20070fe8 01c8a8c0 20087ebc 000a6221 000a6220 21000000 20087ea0 2007a938 00000000 2007376c 200737a8 20087ebc 0000012c 2007aea8 75207369 01c8a8c0 2007376c 000a5b1d 2001376c
...Thanks, that should help me to track the problem down.
-
@dc42
I've gone back to 1.19 while your busy finding the rodent messing around in the Network task in the 0.6 hardware. I kept the newest DWC and found that this also works with 1.19 FW. Nice with some new functionality. I'm not sure wether all the new controls works for real with 1.19 but the extended system edit possibilities are welcome. -
I have it on my list to investigate your report before the 1.20.1 release, however I need to get the prototype laser filament sensors completed and shipped first to avoid additional delay to production of filament sensors.
