The impedance of MCU pins is between 100kΩ and 1MΩ
A pull-up > 10kΩ is considered weak in most cases (happily stand corrected here)
The STM MCU series have internal pull-ups in the rage of 30kΩ to 50kΩ (=weak)
Weak pull-ups can cause issues on timing critical pins as they form a RC circuit and the bigger the resistance is the bigger the impact on signal timing
Weak pull-ups are more susceptible to noise
On battery applications, weak pull-ups are preferred as they limit the current draw
This is my understanding of this matter, but I happily learn and stand corrected.
What is a STM MCU ?
STMicroelectronics? Fysect Spider is equipped with STM, so it is weak. I understand.
Then I have to use the Z-Max pin.
THX the Biqu is ordered.
[output_pin probe_enable]
pin: PB11 # Change this to the Servo/control pin number for your board.
value: 0
[probe]
pin: ^PE0 # Change this to the Probe/Z- pin number for your board
deactivate_on_each_sample: False
x_offset: 0.0 # Change the probe offsets to meet your machine requirements.
y_offset: 25.0 #z_offset: 2.350
speed: 7.0
samples: 1
sample_retract_dist: 4.0
samples_tolerance: 0.05
samples_tolerance_retries: 3
activate_gcode:
Probe_Deploy
G4 P50 # allow time for probe to deploy
deactivate_gcode:
Probe_Stow
[safe_z_home]
home_xy_position: 199.9, 201.4 # Change coordinates to the center of your print bed
speed: 100
z_hop: 5 # Move up 5mm
z_hop_speed: 5
tried to test the BIQU Microprobe, connected to the std. BLTouch pins
Klipper does not like the printer.cfg, according to the upper post and the BIQU discription the printer.cfg is changed, but he whants to have a control pin ? printer.cfg (14.9 KB)
The Biqu description gave a code for Klipper, the code that was already posted here is similar. GitHub - bigtreetech/MicroProbe
With this code I’m trying to test the Biqu to see if it works.
There are macros in the code so you can move the pin in and out.
As soon as I turn on the power on the printer, the pin comes out and otherwise no longer moves, the macros (buttons in the mainsail) have no effect, i.e. the G-code functions. not, the settings in the printer.cfg are not correct.
The pressure is not referenced without a working Z-probe, I don’t think that will have an impact on the macros.
########################
#BIQU Microprobe
########################
[output_pin probe_enable]
pin: PA2 # Change this to the Servo/control pin number for your board.
value: 0 # Probe default retracted
[gcode_macro Probe_Deploy]
gcode:
SET_PIN PIN=probe_enable VALUE=1
[gcode_macro Probe_Stow]
gcode:
SET_PIN PIN=probe_enable VALUE=0
[probe]
pin: ^PA0 # Change this to the Probe/Z- pin number for your board
deactivate_on_each_sample: False
x_offset: 0.0 # Change the probe offsets to meet your machine requirements.
y_offset: 25.0
z_offset: 2.350
speed: 5.0
#samples: 1
#sample_retract_dist: 4.0
#samples_tolerance: 0.05
#samples_tolerance_retries: 3
activate_gcode:
Probe_Deploy
G4 P500 # allow time for probe to deploy
deactivate_gcode:
Probe_Stow
[safe_z_home]
home_xy_position: 199.9, 201.4 # Change coordinates to the center of your print bed
speed: 100
z_hop: 5 # Move up 5mm
z_hop_speed: 5
mounted on the Fysect Spider 2.2 board on the same pins as the BLTouch, later on Z-Max.
found, the small plug with grd/signal has to be turned around, plugged in the wrong way, now the Probe does a check on power on, does go out and back on macros.
Startig referencing Z he tells me now, the z-endstop still is active
ok, that means I have to change something in the printer.cfg?
if I deploy the probe, both are active printer (4).cfg (14.8 KB)
tried a view things with endstop, but do not get the point what he wants?
the signal from the BIQU are fine, but both Endstop Z and Probe are active on sensor out.
