@jay_s_uk Wow I seriously have read over that 10 times I think. sorry for the unnessecary question
Thanks all!

@Notepad works really well, thanks!

Got good results too, and plotted them in graphs! which shows a fun correlation of the temperature drift of our probe!

Thanks for the script! Appreciate it

@SanderLPFRG Got it working, version mismatch.

@OwenD I did exactly that yesterday late afternoon. It is working now.

; Custom buttons
M950 J1 C"^io2.in"      ; define logical input for E1 filamentsensor
M581 P1 T2 S0 R2        ; define trigger for filament auto load (trigger2.g)
M581 P1 T4 S1 R1        ; define trigger for filament runout (trigger4.g)

Thank you very much both!

@chrishamm It works!!

It both updated correctly, and now the M291 functions correctly.
Massive thanks Chris and Tony.

I'll now work on trying to understand how I can use the input to trigger Gcode commands

@jay_s_uk It is working, thanks!

@gloomyandy said in Trying to fix my dual markforged (HAQ-XY) kinematics:

at it is probably not a good thing

Ill redesign the belt tensioning mechanism and the belt mounting, when measuring it indeed looks to be too loose
WIll see what this does

@OwenD Damn, this did the trick. Thank you so much owen! also thanks @chrishamm

@Notepad @droftarts ,

My goal is to test a shitload of probes, and see how much it starts to deviate after thousands. Your script might actually work, let me test

@jay_s_uk yeahh I tried that already, but selective probing with scanning-type probe still tries to, youknow, scan.

Guess the only possibility is to enable the possibility to define a type1 probe on a CANboard

@jay_s_uk Hi, thanks for the reply
You mean setting the Probe type to P0? can I then still do a G30 probe with the load cell?

Hi,

I can now only configure our analogue-in loadcell probe as a SZP, which reads the signal correctly, and G30 functions well, but when doing a G29, it tries to scan the bed, resulting in a nozzle that scrapes the bed.

Until I figure out the firmware, I want to enable a simple mesh probe manually, which I want to do with;

M561                    ; clear any bed transform

; If the printer hasn't been homed, home it
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
  G28

; Probe the bed and do auto calibration
G1 X{move.axes[0].min} Y{move.axes[1].min}  U{move.axes[3].max} Z10 F12000   ; go to neutral position

;Start probing
G30 P0 X25 Y25 Z-99999
G30 P1 X299.5 Y25 Z-99999
G30 P2 X574 Y25 Z-99999
G30 P3 X25 Y250 Z-99999
G30 P4 X299.5 Y250 Z-99999
G30 P5 X574 Y250 Z-99999
G30 P6 X25 Y475 Z-99999
G30 P7 X299.5 Y475 Z-99999
G30 P8 X574 Y475 Z-99999
G29 S3 P"usual.csv" ; save probed points to "usual.csv"

I wonder if such thing is even possible, any tips?

@dc42 is it okay if I try to enable this functionality in a branch via github? If I manage I will make a pull request for you to integrate it into the main branches.

Lot to learn for myself, but I like a challenge.

@SanderLPFRG Got it working, version mismatch.

@dc42 I just tried to build with the latest master branch of the libtinyusb from here; https://github.com/Duet3D/LibTinyusb

I also tried the 3.6.0 beta2 release, which is the same as the rrf sourcecode I am trying to build

still did not work, same error

@dc42 please note that the tusb.h file is actually present

@dc42 said in Other analog Scanning Z Probes?:

Yeahh the biggest issue is that I do not want the loadcell configured as a scanning-type probe, but as a normal analog probe, which is prohibited for CANboards. so I am leaning to version 2.

I am trying to build new firmware for the 6HC (to remove the error it raises when remote Z probe type is not 8, 9 or 11) but I am getting building errors regarding the CoreN2G...

"../src/TinyUsbInterface.cpp:28:10: fatal error: tusb.h: No such file or directory"

@droftarts I see.

I get why it would be a possible issue with latency but for our use we need to be able to define it as such.
We found in the source code where it defines the probe and throws an error, but we would like some advice on if just removing the error gives us a solution

@droftarts Old topic, but I have another general analogue output probe (loadcell with op-amp structure and amplification with custom canBUS board)

I can configure and measure using the scanning Z probe (11) definition, but a load cell is unsuitable for a "scanning" measurement. It is however not possible to define it as a P1 probe on a canbus toolboard.

May I ask why this decision was made, and where in the firmware I could look to make it possible?