Posts made by Mr.Crispin

undefined

its just begging to be modded to be a corexy

undefined

Evening All

I searched and couldn't find any other posts on this topic.

I stumbled across This Video

The guy seems to know what he is doing and has employed a duet board too

undefined

@droftarts said in [3.6.0-beta.1] installation issues (SOLVED) heads up only.:

@Mr-Crispin said in [3.6.0-beta.1] installation issues (SOLVED) heads up only.:

Bootloader ID: not available

That definitely means it's on an old version of the bootloader, so worth updating.

And i admit i have a little bit of hesitance to update the bootloader on an older toolboard, as i tried that a year or so ago on another v1.0 board which bricked it.

I wonder if this, and the updating malfunctioning, are indicative of something else? Possibly CAN wiring, or CAN termination problems?

Ian

The bricking occurred on my other machine. And it has been updated with no issues (although not to 3.6 yet)

I dislike RJ11 connectors, I removed them on both of my 6hc boards and added JST-XH connectors with twisted pair silicone wire.

My day job is as a network installation engineer, including fibre optics, so im happy enough with my connections.

undefined

Here is the output from my tool board.

But I dont think its going to be of any help as mine is listing : Bootloader ID: not available.

And i admit i have a little bit of hesitance to update the bootloader on an older toolboard, as i tried that a year or so ago on another v1.0 board which bricked it.

luckily duet3d granted a goodwill replacement on that board, but i dont want to push my luck

M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.0 or earlier firmware version 3.6.0-beta.1 (2024-09-24 08:53:50)
Bootloader ID: not available
All averaging filters OK
Never used RAM 9264, free system stack 104 words
Tasks: Move(3,nWait 7,0.0%,140) TMC(2,delaying,3.6%,52) HEAT(2,nWait 6,0.3%,104) CanAsync(5,nWait 4,0.0%,48) CanRecv(3,nWait 1,0.0%,70) CanClock(5,nWait 1,0.0%,58) MAIN(1,running,91.3%,318) IDLE(0,ready,0.0%,40) AIN(2,delaying,4.7%,112), total 100.0%
Owned mutexes:
Last reset 00:28:34 ago, cause: software
Last software reset data not available
Moves scheduled 0, hiccups 0 (0.00/0.00ms), segs 0, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00
Peak sync jitter 4/9, peak Rx sync delay 216, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 3008825729 ticks, disabled
VIN voltage: min 22.9, current 23.4, max 24.0
MCU temperature: min 49.7C, current 55.5C, max 67.6C
Driver 0: pos 0, 395.0 steps/mm, standstill, SG min 2, read errors 0, write errors 1, ifcnt 28, reads 5439, writes 12, timeouts 0, DMA errors 0, CC errors 0
Last sensors broadcast 0x00000002 found 1 112 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 34425, send timeouts 0, received 15494, lost 0, ignored 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: none
I2C bus errors 4639, naks 4639, contentions 4639, other errors 4639

undefined

As per the title

A few days ago, I decided to try out the new firmware.

I have a 6hc board with a LC1 Tool board, (standalone) I attempted to update to 3.6.0-beta from within DWC.

The system said it was updating and then at the normal reconnect after the update it wouldn't reconnect...

I tried cycling power a few times and Nada.

Upon connecting the board to my pc via USB the port listed itself as a "bossa" post instead of a USB device, I'm like W.T.F.

So i tried to re-flash via bossa flash tool x3 attempts all failed with no actual listed error. I redownloaded the .bin file from the repository in case it was a corrupted download. This didn't cure the issue.

I was able to successfully flash back to 3.5.3 no problem and that allowed me back into the printer via DWC, a second attempt to update via DWC resulted in the same issue.

After x3 attempts (and trying different USB cables which made no difference) via bossa I finally managed to get 3.6.0-beta.1 to upload and verify successfully. And I was able to upgrade the tool board from within DWC, no problem.

M122 attached

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.6.0-beta.1 (2024-09-24 10:07:51) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Used output buffers: 1 of 40 (29 max)
=== RTOS ===
Static ram: 136444
Dynamic ram: 126712 of which 444 recycled
Never used RAM 67952, free system stack 200 words
Tasks: NETWORK(1,ready,32.9%,180) ETHERNET(5,nWait 7,0.1%,324) HEAT(3,nWait 6,0.0%,356) Move(4,nWait 6,0.0%,333) TMC(4,nWait 6,3.1%,379) CanReceiv(6,nWait 1,0.0%,794) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,353) MAIN(1,running,63.5%,103) IDLE(0,ready,0.4%,29) USBD(3,blocked,0.0%,147), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:28 ago, cause: power up
Last software reset at 2024-10-09 20:46, reason: HardFault, none spinning, available RAM 67952, slot 1
Software reset code 0x0073 HFSR 0x80000000 CFSR 0x00000000 ICSR 0x00400803 BFAR 0x00000000 SP 0x2041b740 Task NETW Freestk 532 ok
Stack: 00000001 00000000 20415d9c 00000035 0000023c 0041dde9 00421794 61010000 2041aa80 004ba638 00000009 0000000a 0000000b 0000000c 0000000b 0003000c 00000000 2041aa80 20415e08 00000000 20415c44 e000e000 a5a5a5a5 a5a5a5a5 a5a5a5a5 0041e8fb 002dfff0
Error status: 0x00
MCU temperature: min 23.4, current 32.7, max 32.7
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Date/time: 2024-10-10 11:56:08
Slowest loop: 2.60ms; fastest: 0.07ms
USB interrupts 2
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 1.5ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00
no step interrupt scheduled
Driver 0: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Driver 1: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Driver 2: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Driver 3: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 56463, writes 11 timeouts 0
Driver 5: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Phase step loop runtime (us): min=0, max=73, frequency (Hz): min=1633, max=2568
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering erHeater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x80000003
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 272, received 581, lost 0, ignored 0, errs 581, boc 0
Longest wait 1ms for reply type 6042, peak Tx sync delay 27193, free buffers 50 (min 49), ts 143/142/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 4.99ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 1 0 0
Socket states: 2 6 2 2 2 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

undefined

@jay_s_uk said in Can no longer use the manual extrude Buttons (greyed out):

@Mr-Crispin add "T0" on its own line at the end of your config

ok (that worked) Thank You

But why is/was that now needed when it wasn't needed previously ? Not trying to be funny, im just trying to understand

undefined

As Per the Title

Turned on this printer for the first time in about a week, and after heating the hot end the extrude/retract buttons normally come alive after a certain temp now they don't, haven't changed firmware or config.g it was fine last week.....

Board Duet-2 wifi

Duet Web Control 3.5.2

Product Short Name Version
Duet 2 WiFi 2WiFi 3.5.2
Duet WiFi Server n/a 2.1.0
Duet Web Control DWC 3.5.2

Added config.g but 100% NOTHING Has been changed since it worked last week

; General preferences
;--------------------------------------------------------------------------------------------------------------
;
M552 S1
G90                                                     ; Use absolute coordinate moves
M83                                                     ; Relative extruder moves
M550 P"300mm Titan Aero"                                ; Printer name
M564 S0 H0                                              ; Allow movement before homing
;
;--------------------------------------------------------------------------------------------------------------
; Network
;--------------------------------------------------------------------------------------------------------------
;
M552 S1                                                 ; Enable network
M586 P0 S1                                              ; Enable HTTP
M586 P1 S0                                              ; Disable FTP
M586 P2 S0                                              ; Disable Telnet
;
;--------------------------------------------------------------------------------------------------------------
; Drives
;--------------------------------------------------------------------------------------------------------------
;
M669 K0                                                 ; Kinematics Type is set to "Cartesian"
M671 X-25:255 Y0:0 S10                                  ; Z axis pivot points
M569 P0 S0                                              ; Drive 0 (X) goes forwards
M569 P1 S1                                              ; Drive 1 (Y) goes backwards
M569 P2 S1                                              ; Drive 2 (Z1 Left) goes forwards
M569 P3 S0                                              ; Drive 3 (Extruder) goes forwards
M569 P4 S0                                              ; Drive 4 (Z2 Right) goes forwards
M584 X0 Y1 Z2:4 E3                                      ; Drive mapping
M350 X32 Y32 Z16 E16 I1                                 ; Micro-stepping with interpolation
M92 X160.00 Y200.00 Z400.00 E465                        ; Steps per mm
M566 X900.00 Y900.00 Z900.00 E300.00                    ; Mximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z1800.00 E6000.00                ; Maximum speeds (mm/min)
M201 X800.00 Y800.00 Z500.00 E5000.00                   ; Accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I50                         ; Motor currents (mA) & motor idle factor %
M84 S30                                                 ; Idle timeout
;
;--------------------------------------------------------------------------------------------------------------
; Axis Limits
;--------------------------------------------------------------------------------------------------------------
;
M208 X-8 Y-30 Z-2 S1                                    ; Axes min
M208 X300 Y300 Z350 S0                                  ; Axes max
;
;--------------------------------------------------------------------------------------------------------------
; Endstops
;--------------------------------------------------------------------------------------------------------------
;
M574 X1 S1 P"xstop"                                     ; The X axis endstop is at the low end, & mapped to the "xstop" pin
M574 Y1 S1 P"ystop"                                     ; The Y axis endstop is at the low end, & mapped to the "ystop" pin
M574 Z1 S2                                              ; z-probe endstop at the low end on Z
;
;--------------------------------------------------------------------------------------------------------------
; Z-Probe (BL-Touch)
;--------------------------------------------------------------------------------------------------------------
;
M950 S0 C"exp.heater3"                                  ; The servo pin is "heater-3" for the BLTouch
M558 P9 C"zprobe.in" H10 R0.3 T15000 F15000:240         ; The Z probe type signal pin is "zprobe in", the dive heigt is 10mm + speed settings
G31 P500 X-24 Y-38 Z2.378                               ; Toolhead Offsets, the Z probe trigger value, offset and trigger height, (make the numbers SMALLER to move the nozzle AWAY from the bed)
M557 X30:260 Y50:280 P12                                ; Define a mesh grid
;
;--------------------------------------------------------------------------------------------------------------
; Z Stop
;--------------------------------------------------------------------------------------------------------------
;
M558 K1 P8 C"!zstop" H10 R0.3 F6000 T10000 A3 S0.06       ; The Z End-Stop is type 8 (A Simple Switch) & is mappped/connected to the zstop port on the mainboard 
G31 K1 P500 X0 Y0 Z0                                      ; Z End-Stop X, Y & Z offsets
;
;--------------------------------------------------------------------------------------------------------------
; Bed Heater 
;--------------------------------------------------------------------------------------------------------------
;
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138          ; The Bed sensor "sensor 0" is a thermistor
M950 H0 C"bedheat" T0                                   ; The bed heater is configured to the "bedheat"and mapped to sensor 0         
M307 H0 R0.881 K0.405:0.000 D10.62 E1.35 S1.00 B0       ; Heater tuning results
M140 H0                                                 ; The bed heater is mapped to be "H0"
M143 H0 S120                                            ; The temperature limit for "H0" is  set to 120C  
;
;--------------------------------------------------------------------------------------------------------------
; Hot-End Heater
;--------------------------------------------------------------------------------------------------------------
;
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8  ; The hot-end sensor "sensor 1" is a thermistor
M950 H1 C"e0heat" T1                                    ; the hot-end is configured to "e0heat" mapped to sensor 1  
M307 H1 R2.563 K0.367:0.000 D3.24 E1.35 S1.00 B0 V24.1  ; Heater tuning results
M143 H1 S310                                            ; The temperature limit for "H1" is 310C    
;
;--------------------------------------------------------------------------------------------------------------
; Fans
;--------------------------------------------------------------------------------------------------------------
;
M950 F0 C"fan0"                                         ; The art-cooling" fan is "fan1" & it's frequency is set to 500
M106 P0 S0                                              ; The start value of fan0 is ZERO
;
;--------------------------------------------------------------------------------------------------------------
; Tools
;--------------------------------------------------------------------------------------------------------------
;
M563 P0 S"Titan Aero" D0 H1 F0                          ; Tool 0's definitions
G10 P0 X0 Y0 Z0                                         ; Tool 0's axis offsets
G10 P0 R0 S0                                            ; The tool "tool 0" is set to active and  it's standby temperatures is set to 0C

Output From M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.2 (2024-06-11 17:13:43) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4S8-6J9D8-3SJ6M-15BZW
Used output buffers: 6 of 26 (22 max)
=== RTOS ===
Static ram: 23384
Dynamic ram: 73056 of which 12 recycled
Never used RAM 13764, free system stack 136 words
Tasks: NETWORK(2,nWait 6,13.8%,218) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,310) MAIN(1,running,86.1%,742) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 01:33:27 ago, cause: software
Last software reset at 2024-06-22 16:59, reason: User, Gcodes spinning, available RAM 13912, 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
MCU temperature: min 46.0, current 48.9, max 50.4
Supply voltage: min 23.8, current 24.2, max 24.5, under voltage events: 1, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/16/16, 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 0
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2024-06-22 18:39:00
Cache data hit count 4294967295
Slowest loop: 22.62ms; fastest: 0.18ms
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 9.9ms, write time 5.6ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 481601ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 13, completed 13, 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
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.2
=== GCodes ===
Movement locks 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
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 34.77ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address 5c:cf:7f:2c:29:2d
Module reset reason: Turned on by main processor, Vcc 3.39, flash size 4194304, free heap 42884
WiFi IP address 192.168.0.103
Signal strength -49dBm, channel 6, mode 802.11n, reconnections 1
Clock register 00002002
Socket states: 0 5 0 0 0 0 0 0

undefined

I just have the following in my end g code in my slicer

G0 Z10 X0 Y400 F6000      ; Drop the bed & Park the head out of the way

undefined

Sounds very similar to my recent issue

undefined

@Phaedrux

That's the package I originally downloaded.

It's working fine on the older firmware, so I will leave well alone until i have to update

undefined

@Phaedrux said in 3.5.1 "forgetting" the assigned WiFi connection:

And the problem doesn't occur there anymore?

Correct, As soon as I roll back the firmware, the problem disappears

undefined

@Phaedrux said in 3.5.1 "forgetting" the assigned WiFi connection:

Can you share an M122 report?
What is the reported wifi server version?

The wifi module forgetting the networks after the initial upgrade isn't totally unheard of, but it shouldn't be forgetting it every reboot.

I have permanently rolled back to Release 3.5.0-rc.4

WiFi Sever is 2.1 Beta 8

Results of M122 (board ID & MAC Address removed)

(Edit) I did remove all saved networks using M588 S"*" before re-adding my SSID/Password

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1 (2024-04-19 14:40:46) running on Duet WiFi 1.0 or 1.01
Board ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Used output buffers: 14 of 26 (14 max)
=== RTOS ===
Static ram: 23256
Dynamic ram: 72848 of which 12 recycled
Never used RAM 17028, free system stack 170 words
Tasks: NETWORK(2,nWait 6,13.1%,220) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,359) MAIN(1,running,86.2%,745) IDLE(0,ready,0.7%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:31 ago, cause: power up
Last software reset at 2024-04-20 16:29, reason: User, Gcodes spinning, available RAM 12972, 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
MCU temperature: min 34.8, current 37.6, max 38.7
Supply voltage: min 24.1, current 24.2, max 24.5, 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 n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2024-04-21 11:53:07
Cache data hit count 4294967295
Slowest loop: 11.05ms; fastest: 0.18ms
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.8ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
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
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks 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
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 8.32ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta8
MAC address xxxxxxxxxxxxxxxx
Module reset reason: Turned on by main processor, Vcc 3.39, flash size 4194304, free heap 39236
WiFi IP address 192.168.88.222
Signal strength -55dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

undefined

I updated to 3,5,1 on one of my Duet-2 (1.04) boards yesterday, and I am encountered an issue where after the update in that I couldn't reconnect to DWC via Wi-Fi

I connected via a USB cable, and instantly I started receiving Wi-Fi connection errors stating no known networks were available

I disabled the Wi-Fi Adapter to suppress the error, then re-initialized it, putting it into an idle state.

Sending M587 shows no networks were saved,

I then Re-Added my Wi-Fi connection and got re-connected via DWC (the printer prints normally on the new firmware after I got connected) I initially just put it down to the update not doing its thing properly.

Went to connect to the printer this morning and couldn't, connecting via USB started the cycle i encountered during the upgrade, if I carried out the rectification procedure again I could connect until I shut down then the cycle begins again.

If I roll back to earlier firmware (on the same board with no changes to the config.g) the problem disappears.

undefined

I Twist & solder using a clamp i made myself

undefined

@adrian said in Tool board for Roto connectors ?:

@Mr-Crispin Do you be chance have a mount for the roto tool board for the voron that you'd be willing to share?

Hello

I do have a mount, I got it from a guy I know, he printed it for me along with other parts for the head system he designed, he doesn't use this forum, he frequents the Team FDM forum where he posted his designs a while back, you could look there and see if he will do a set for you.

undefined

Hello

my printer (a corexy) with a 6hc and 1lc tool board has recently started throwing up the following error at various intervals on boot , but not all the time.

JSON parse. unexpected character at line 1 column 1 of the json data

Im on Duet Web Control 3.5.0-b1
And Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.6-rc.1 (2023-06-28)

M98 P"config.g" Displays NO Result
Changing to another SD card had no effect.

The printer runs fine otherwise, can anyone shed any light on how to get rid of this error

undefined

Hello

I would like to deploy a roto tool board in a printer (a voron 2.4 im building) that doesn't have a roto extruder because the tool board is slightly smaller than the "normal" tool boards.

I can't find any info on whether the roto tool board comes with a connector pack or not, can anyone shed any light on this.

And I'm struggling to find any resellers actually advertising the roto tool board for sale outside the US/UK. (I'm in southern Spain)

Any assistance appreciated

undefined

@oliof said in Board arrived with a damaged component:

is that the 12V regulator? RatRig puts 1.3A+ 12V fans on their systems for cooling which is too much for the Duet3 mini 5+ (they note this on their shop).

If that is the case, then rat rig shouldn't really be supplying a product that is not fit for purpose and Duet3d shouldn't have to foot the bill for a replacement.

undefined

@jay_s_uk said in Orbiter V3.0, Can the "smart" hardware be used with Duet2/RRF?:

I spoke with the designer when the orbiter v3 was being developed and he had no interest in adding RRF support

Messer Lorenz is more than a little supercilious, right enough.

undefined

@DieterSw said in 6HC inductive 4 wire endstop wiring:

@Mr-Crispin Why do you think that? I connected BN to 5V_EXT, BU to GND. And BK to iO.in. I might switch black/white to use the NO closed contact but the rest seems correct I think?

ok then apply logic.

The wiring diagram from the data sheet shows a different way from what you have

You are wired differently/incorrectly according to the duet docs

(The most glaringly obvious one) IT'S NOT WORKING FOR YOU in its current configuration

Ask yourself why.