unexpected Behavior on Duet 1LC Toolboard with Microprobe

[Superbrain8]

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

[droftarts]

@Superbrain8 They often change colours, and put the wiring loom in the reverse order. Something is going wrong, and to short the fan and thermistor to ground, it's for sure a wiring issue.

Ian

[Superbrain8]

the Silkscreen Print on the Probe itself matches what the Usermanual and the page from treamgloomy shows

[dc42]

@Superbrain8 said in unexpected Behavior on Duet 1LC Toolboard with Microprobe:

Powering on the printer works
Self Test of the probe Works
after a second or two the Hotend Cooling fan of the Tool where the probe is connected to turns on
the Thermistor reports 2000°C
Pin of the Probe doesnt get Deployed when sending a macro containing

If the hot end fan turns on a second or two after doing the probe self-test, then I suspect that the probe is overloading the 5V rail of the tool board and causing it to reset. Use M122 B210 to check the last reset time and reason.

The BLTouch draws quite a high current (a few hundred milliamps) for a very short time when it deploys or retracts the pin. The tool board has a capacitor to handle this short surge. It may be that the Microprobe draws more current, or draws current for a longer time, or draws a high current continuously when the pin is deployed.

[Superbrain8]

@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

[dc42]

@Superbrain8 said in unexpected Behavior on Duet 1LC Toolboard with Microprobe:

Last reset 00:00:26 ago, cause: power up

So was it 26 seconds ago that you powered up the whole system, or 26 seconds ago that you commanded the probe self-test?

[Superbrain8]

@dc42 powering up the system, cant command a self test manually, wont get executed after the initial selftest

[dc42]

@Superbrain8 if you power up the system, then send the configuration commands for the probe again, what happens when you command the pin to deploy?

[Superbrain8]

@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.

[jay_s_uk]

@Superbrain8 i ran my V1 microprobe on a 1LC with no issues. I can't remember whether I joined grounds or ran them separately