@dc42 nothing, would guess that the probe draws to much for the 5v rail to actuate the pin.
I take the L on this one and look for a different solution for replacing the BL touch.
@dc42 nothing, would guess that the probe draws to much for the 5v rail to actuate the pin.
I take the L on this one and look for a different solution for replacing the BL touch.
@dc42 powering up the system, cant command a self test manually, wont get executed after the initial selftest
@dc42 Here is the Readout of the Affected Toolboard
M122 B20
Diagnostics for board 20:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.6 (2023-07-21 14:17:33)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2984, free system stack 88 words
Tasks: Move(notifyWait,0.0%,155) HEAT(notifyWait,0.1%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,92.0%,441) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:00:26 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 13293, writes 9, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/8, peak Rx sync delay 202, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.5, current 24.5, max 24.6
MCU temperature: min 17.2C, current 20.8C, max 20.8C
Last sensors broadcast 0x00000000 found 0 135 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 234, send timeouts 0, received 353, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0
the Silkscreen Print on the Probe itself matches what the Usermanual and the page from treamgloomy shows
ive used the teamgloomy page for reference, and to verify the correct order of colors.
https://teamgloomy.github.io/fly_e3_v2_bltouch.html
did compared the Original Harness for the BL Touch with the one for the Microprobe and both have the colors in the same order
will provide the other stuff shortly.
but i dont think its wiring related. Connecting a BL Touch with the same wires doesnt cause this issue.
the pinout of both probes is the same, ran the BL Touch for over a year on the Toolboard with no issues.
Here is a picture of the Crimps on the Connector facing the Toolboard, other side is facory Crimped.
Good Day,
I want to replace a BL Touch on one of my Printer with a Biqu Microprobe due to the smaller formfactor giving me a more favorable probe placement.
With the BL Touch connected everything is fine, connecting the Microprobe causes the Connected Thermistor to get lost, causing the hotend to go into a Error state.
The Printer where running with the BL Touch now for a few months in this Configuration
The printer is running as a Idex equiped with:
Duet 3 Mini5+
2 1LC Toolboards
2 Mosquito Magnum each running a PT1000
2 BMG-M Extruder
2 Roatating Magnet Filament Monitors
Running on 3.4.6
Changed the config from the Working BL Touch settings to:
; Z-Probe
M558 P9 C"^!20.io0.in" H7 F250:30 T8000 A20 R0.75 S0.01 ; BL Touch
M950 P0 C"20.io0.out" ; BL Touch Servo Pin
G31 P25 X-38 Y-3.8 Z2.12 ; set the trigger height and Offset BL Touch 2.55
M557 X5:220 Y-17:220 S50 ; define mesh grid
M376 H10 ; Taper height of 10mm (fade)
Deployprobe.g and Retractprobe.g got configured to support the new probe
M42 P0 S1
G4 P500
The Behavior i get with a BLTouch connected:
The behavior with the Microprobe connected:
M42 P0 S1 ; Turn on pin so it deploys
G4 P500
ive tried to see if the cable is the issue, but swapping in the BL Touch on the same cable doesnt cause the issue.
The pinout of both probes is also the same
had some connection issues with the 1LC in the past.
adding a Strain relief to the Cables and securing the connector with a dab of hotglue fixed it for me.
the zh connector used for the CAN connection is quite unreliable
Is there a chance to get the board RMAd?
bought it 23.12.2023, arrived the 28th from Dold-Mechatronik
After some more digging around its only the Mosfet that gets Hot the Zenner Diode for the header too.
in the Attached video you can see the Mosfet pulsing from the PSU resetting from the Overcurrent protection and tripping again
measured reistance on the header is about 1 Ohm the header below about 1 MOhm
Good Morning Folks,
Got my hands on a Duet 3 6HC and a Duet 3 3HC earlier this week and had time to wire it up yesterday.
Vin is a 24V 200W Meanwell PSU
5V is externaly powered over a Meanwell 5V PSU
VIN Out0 is not connected.
Running on 3.5.0-RC2
Powered it up this morning to verify everything where right.
Overall no issues, no Sparks.
After attempting a PID tune on the Hotend the PSU tripped.
powering down the printer and having it sit unpowered for a bit caused it to power on again.
After some digging the PSU tripped again but since then Printer refuses to power on again.
Removing any load from the PSU gets it to start.
Just having the 3HC connected works also fine.
Removing any plugged in Device from the 6HC and powering it over 24V trips the PSU
just powering it on 24V without 5V showed a slight glow on the Out3 Status LED
Im somewhat in a lucky Position in owning a Thermal Camera and ive took a Video of the Mosfet for Out3
Xinf_231231_094202_924.mp4
Good Day,
Noticed that my Printer running a Duet 3 Mini5+ and a Duet Toolboard had a failing CAN connection during a print,
noticed this error after about 5 minutes.
My question is why didnt the printer stopped with an Error?
i know that the heater control loop should be not interrupted if the heater and thermistor are on the same CAN Board, but having it running for over 5 minutes with no reaction of the Mainboard should not be a thing.
the failing Can connection where solved by wiggling the JST connector for the CAN connection on the Toolboard (should add a dab of hotglue)
M122 Readout (after having resolved the issue)
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.2 (2022-09-13 15:14:33) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: YQ6KF-K096U-D65J0-40KMG-4G03Z-H28XK
Used output buffers: 3 of 40 (24 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 111292 of which 0 recycled
Never used RAM 23088, free system stack 112 words
Tasks: NETWORK(notifyWait,13.6%,185) HEAT(notifyWait,0.0%,340) Move(notifyWait,3.7%,261) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.2%,325) CanClock(delaying,0.0%,339) TMC(notifyWait,0.7%,106) MAIN(running,80.7%,409) IDLE(ready,0.2%,30) AIN(delaying,0.9%,263), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:29:32 ago, cause: software
Last software reset at 2023-02-17 13:28, reason: User, GCodes spinning, available RAM 23568, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 5372758, completed 5372757, timed out 0, errs 0
Step timer max interval 1489
MCU temperature: min 19.2, current 25.2, max 25.4
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/316/282, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 20002, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 20002, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 20002, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 20011, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 20002, writes 19, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-02-17 14:58:27
Cache data hit count 4294967295
Slowest loop: 1077.90ms; fastest: 0.11ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 6.5ms, write time 181.4ms, max retries 0
=== Move ===
DMs created 83, segments created 33, maxWait 231032ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 459661, completed 459621, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 7855, 0], CDDA state 3
=== 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
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 85
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) 3
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
Code queue is empty
=== Filament sensors ===
Extruder 0: no data received
=== CAN ===
Messages queued 492187, received 108998, lost 0, boc 248
Longest wait 3ms for reply type 6053, peak Tx sync delay 48919, free buffers 18 (min 3), ts 26863/22456/0
Tx timeouts 38321,0,4280,0,0,3342 last cancelled message type 51 dest 20
=== Network ===
Slowest loop: 1077.92ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address f0:08:d1:02:e5:fa
WiFi Vcc 3.42, reset reason Power up
WiFi flash size 2097152, free heap 26144
WiFi IP address 192.168.188.70
WiFi signal strength -75dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
@dc42 will be a non issue for me in the future, im working on replacing the entire ribbon cable due to its limitations.
will run individual wires, just have to seperate them properly so they wont be close to stepper motor or other higher current wires.
@jay_s_uk this solves another issue, thanks for the reply.
yea the ribbon sucks, replaced it with individual wires, but i have to tweak this a bit, rn there is to much crosstalk. will have to change some stuff, but im looking forward towards this.
@fcwilt ok thanks,
will look into rerouting some of the wire and see if it will improve the situation.
@fcwilt probably is the issue, replaced the ribbon cable itself with individual wires, but i guess i have to optimize this more
(issue was present with the stock ribbon cable connecting the axis to the base, from there to the mainboard)
the thing is this issue was not present while running Marlin and klipper
@fcwilt Inductive endstops that come with the Artillery Sidewinder.
@fcwilt didnt worked out, behavior persists.