Coder Social home page Coder Social logo

Comments (8)

nicolas-lang avatar nicolas-lang commented on August 26, 2024

In summary my expectation is:

  • for a given physical location i would expect static machine coordinates, with the probing only affecting the current work coordinates.

This is not the case with my machine, so there must be some kind of issue.

Possible candidates for the issue:

  • The touchplace has some kind of delayed electrical triggering (capacity, contact resistance, ground loop with toolhead etc.)
    I will investigate this by trining to use a tool length sensor instead of a touchplate

  • Software Issue
    not sure how to debug this further, and right now i mainly would like to have confirmed if my expectation regading the designed behaviour of probing is correct (see first sentence)

from fluidnc.

MitchBradley avatar MitchBradley commented on August 26, 2024

Try with v3.7.15 . There was a change in the probing code since then that could possibly have affected the accuracy.

from fluidnc.

MitchBradley avatar MitchBradley commented on August 26, 2024

I did some tests on my laser gantry with various versions. I don't see any probe consistency problems with any version, including the latest 3.7.17.

I changed my config file so that the x limit switch is the probe pin, and probed in the -x direction, using $j between probes to pull away. In all cases, the probe position was repeatable within 1 step. My x steps_per_mm is 80 so 1 step is 0.0125 mm.

ok
g38.6 x-20 f100 p2
[PRB:0.188,0.000,0.000:1]
[MSG:INFO: Probe offset applied:]
ok
<Idle|MPos:0.013,0.000,0.000|FS:0,0|Pn:P|WCO:445.475,197.825,0.000>
$j=g91 g21 x3 f1000
ok
<Idle|MPos:3.013,0.000,0.000|FS:0,0|Pn:P>
g38.6 x-20 f100 p2 
[PRB:0.188,0.000,0.000:1]
[MSG:INFO: Probe offset applied:]
ok
$j=g91 g21 x10 f1000
ok
g38.6 x-20 f100 p2  
[PRB:0.200,0.000,0.000:1]
[MSG:INFO: Probe offset applied:]
ok
<Idle|MPos:0.025,0.000,0.000|FS:0,0|Pn:P|WCO:445.488,197.825,0.000>
$j=g91 g21 x10 f1000
ok
g38.6 x-20 f100 p2  
[PRB:0.200,0.000,0.000:1]
[MSG:INFO: Probe offset applied:]
ok
<Idle|MPos:0.013,0.000,0.000|FS:0,0|Pn:P|WCO:445.488,197.825,0.000>
$j=g91 g21 x17 f1000
ok
g38.6 x-20 f100 p2  
[PRB:0.200,0.000,0.000:1]
[MSG:INFO: Probe offset applied:]
ok

from fluidnc.

MitchBradley avatar MitchBradley commented on August 26, 2024

Perhaps you could check for mechanical problems. One way to do that would be to move back and forth, ending at the same position, and use a dial indicator or some other precise measuring tool to check the repeatability.

from fluidnc.

nicolas-lang avatar nicolas-lang commented on August 26, 2024

Hi, thanks for your comments it's much apreciated.
Especially your confirmation that the software side seems to work correctly removes a lot of variables from the testing...

I am quite sure to have no mechnical issue, as the same hardware has been working reliably with the previous controller (grbl with some arduino based shield) for 3+ years

Right now the main thing I'll be testing will probably be the electrical setup. Previously I was using a 24V touch plate circuit with optocoupler and a external pull-up. My new setup uses only one of the 5V Inputs of the optocoupler shield of the 6 pack, maybe this suffers from noise or capacity issues....

I'll do some more testing tomorrow and will update or close this issue afterwards.

Thanks a Lot, Nicolas

from fluidnc.

MitchBradley avatar MitchBradley commented on August 26, 2024

Okay, but yesterday I had a mechanical problem with a machine that has been working correctly for 25 years. Turns out that a dovetail saddle that holds the spindle on the Z axis had slipped by 9 mm. "Used to work" is evidence but not a proof.

from fluidnc.

MitchBradley avatar MitchBradley commented on August 26, 2024

You could also try I2SO_STATIC mode. It is supposed to switch to that for probing but maybe something is wrong.

from fluidnc.

nicolas-lang avatar nicolas-lang commented on August 26, 2024

I am mostly sure it was a strange effect that was caused by the 5V IO shield in combination with a badly designed touch plate (a double sided unetched circuit board blank) that acted like a plate-capacitior delaying the probe activation causing the drift.

I haven't had much time to confirm/test but it seems like adding pullup + transistor and switching to 24V for the touch plate resolved the issue...

from fluidnc.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.