Thanks a lot, this fixed it.

@jay_s_uk didnt really showed up when searching for it, the pinned macros showed up but they are a bit bulky

@jay_s_uk didnt really showed up when searching for it, the pinned macros showed up but they are a bit bulky

I where looking for a easy method to test how much Accleration i could potentially run on my Printer.
Klipper has that nice macro written by Andrew Ellis that makes it easy to run tests Automated so ive looked into creating something similar to test how far i can push the Accleration at a set speed

Resulting in the Following Macro

;-------------------Accel Test Macro----------------------------------------------
;this Macro aims to create random movements at set speed and set Accel
;There is a chance that this macro causes a Rapid Movement towards the Min Axis point the macro takes X0 and Y0 as Origin
;aviable macro parameters:
; S = max speed in mm/min
; I = Max Iterations
; A = Accleration Increment

;move.axes[0] X Axis
;move.axes[1] Y Axis
;move.axes[2] Z Axis

;--------------------Variables---------------------------------------------------
var xmax  = floor(move.axes[0].max-5)                                          ; Grab Max Distance in X
var ymax = floor(move.axes[1].max-5)                                           ; Grab Max Distance in Y 
var xmaxspeed = move.axes[0].speed                                             ; Grab Max Speed in X
var ymaxspeed = move.axes[1].speed                                             ; Grab max Speed in Y
var maxspeed = 0                                                               ; Placeholder for Max speed
var maxiterations = 5                                                          ; how often does the Macro gets repeated
var maxmoves = 30                                                              ; how many moves are made by the macro
var xaccel = move.axes[0].acceleration                                         ; grab XAccel from config
var yaccel = move.axes[1].acceleration                                         ; grab YAccel from config
var accel_inc = 0                                                              ; increment accleration by this value each iteration

;------------------Functions----------------------------------------------------
set var.maxspeed = var.xmaxspeed > var.ymaxspeed ? var.xmaxspeed:var.ymaxspeed ; get max configured speed for the test
if exists(param.S)
    set var.maxspeed = param.S                                                 ; Overwrite Max Speed from Macro parameter if set
if exists(param.I)
    set var.maxiterations = param.I                                            ; Overwrite Iterations from macro parameter if set
if exists(param.A)
    set var.accel_inc = param.A                                                ; Overwrite accel_inc from a macro parameter if set
;------------------Prepare Printer----------------------------------------------
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
    G28                                                                        ; Home Axis if not Homes
G1 Z20                                                                         ; Clear Bed
M400                                                                           ; Wait for movements to finish
;-----------------Test Gcode----------------------------------------------------
echo "running Accel Test"
echo "Max Speed:",var.maxspeed
echo "Iterations:", var.maxiterations
while true   
    M400                                                                       ; Wait for all movements to finish
    M201 X{var.xaccel} Y{var.yaccel}                                           ; set Accel
    if iterations = var.maxiterations
        abort "finished Accel Test"                                            ; Loop until max repats are reached
    echo "running Iteration", iterations  
    echo "X Accleration", var.xaccel
    echo "Y Accleration", var.yaccel
    set var.xaccel = var.xaccel+var.accel_inc                                  ; increment the X axis accleration for the next loop
    set var.yaccel = var.yaccel+var.accel_inc                                  ; Increment the Y axis accleration for the next loop
    while true
        if iterations = var.maxmoves
            break
        var xrnd = random(var.xmax)
        var yrnd = random(var.ymax)
        G1 F{var.maxspeed} X{var.xrnd} Y{var.yrnd}                             ; Move X and Y in random directions at set speed
M400
echo "restart the Mainboard or Reload the Config file again to reset Accleration to its original value"
M2

This Macro takes the machine limits in X and Y (expecting Home to be at the Min point)
and then puts random movements within the Machine Limit at the set speed and Accleration
by default it doesnt increase the Accleration with each Iteration but can be configured to do so with a Parameter attached to the Macro Call

its not perfect but gave me useable results
might be helpful for others so i post it here.

Something to consider because of the Random Movements is that its not 100% repeatable but should give more realistic results due to being closer to actual print movements

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

• Powering on the printer works
• Self Test of the Probe works
• Printer goes to Idle
• Pin Deploys when configuration is adjusted for the probe

The behavior with the Microprobe connected:

• 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

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