Hello Guest it is November 12, 2019, 04:00:22 AM

Author Topic: probe error : no contact with probe  (Read 530 times)

0 Members and 1 Guest are viewing this topic.

probe error : no contact with probe
« on: April 07, 2019, 04:32:44 PM »
I'm setting up a machine using a parallel  port for the time being and I can't get the probe to function correctly. I've flipped hi/low  settings , the z never moves and either it reads that its tripped or no contact with probe   . Debounce is set to 100. so I'm out of Ideas.
Re: probe error : no contact with probe
« Reply #1 on: April 07, 2019, 04:43:25 PM »
Hi,
does the Probe LED operate on the Machine Diagnostics tab operate when manually flicking the probe?

Craig
My wife left with my best friend...
     and I miss him!
Re: probe error : no contact with probe
« Reply #2 on: April 07, 2019, 05:42:42 PM »
yes the probe led works and g31 . I think it might be limits of the machine , not sure if that is set correctly . mach is very new to me . I was using flachcut
Edit : soft limits and home in place not enabled   
« Last Edit: April 07, 2019, 05:45:17 PM by tony978 »
Re: probe error : no contact with probe
« Reply #3 on: April 07, 2019, 05:51:20 PM »
Hi,
why do you think that the limits may have something to do with it?

I thin you might be trying to run before you can walk. Get the rest of the machine running and then look at probing.

Can you jog around the table?
Can you issue MDI commands and have the machine move accurately?
Do you have home switches? If you don't then you will have to 'home in place'.

Craig
My wife left with my best friend...
     and I miss him!
Re: probe error : no contact with probe
« Reply #4 on: April 07, 2019, 06:02:09 PM »
hi Craig ,
no home switches , mdi moves / calibrated all axis's and spindle relay tested . last thing was setting up the probe .
Re: probe error : no contact with probe
« Reply #5 on: April 07, 2019, 06:05:17 PM »
Hi,
OK, without home switches how are you referencing your machine? My understanding is that if you have
no home switches assigned then effectively if you hit <Ref All Home> then all axes must 'home in place'.
Is this what actually happens?

Craig
My wife left with my best friend...
     and I miss him!
Re: probe error : no contact with probe
« Reply #6 on: April 07, 2019, 06:10:57 PM »
yes that is what happens and just retested it . so its not  a case of mach not being homed or in disable mode .

so if it was debounce being set to low ,the led would flicker in the diag screen ?
Re: probe error : no contact with probe
« Reply #7 on: April 07, 2019, 08:51:20 PM »
Hi,

Quote
so if it was debounce being set to low ,the led would flicker in the diag screen ?

No, I don't think so. The LED on the diagnostic screen is not that fast, that is to say if the input signal
did flicker is a manner to cause Mach to record a probe strike it may be that the LED does not respond at all.
The LED is a useful diagnostic tool to see whether the probe circuit is working but not good enough to diagnose
noise problems.

Can you post the g31 code you are using to test the probe?

Craig
My wife left with my best friend...
     and I miss him!
Re: probe error : no contact with probe
« Reply #8 on: April 07, 2019, 09:01:43 PM »
Hi
I was using g31 z-3. F5.
Along with surface zero set .
No z movement with both .
Re: probe error : no contact with probe
« Reply #9 on: April 07, 2019, 09:10:46 PM »
Hi,
have a look in API.chm in your mach4 Docs folder in the section headed 'Plugin Development'.

I copied this out of it all associated with probing.

Quote
Probing
Motion plugin probing procedure.
The probe moves are really just G01 moves in exeact stop mode with the addition of being marked as EX_PROBE in the execution_t struct from mcMotionCyclePlannerEx().

When executing a G31, the core considers the move as an exact stop move and therefore will request a motor stop report. It waits on one of two conditions:

A probe strike condition where the motion plugin calls mcMotionSetProbeComplete().
An end of move condition where the motion plugin reports the motors as being still.
Until either of these conditions are satisfied, the core will generate no more moves after the EX_PROBE marked moves. In other words, all you will get out of mcMotionCyclePlannerEx() will be EX_NONE type data. In the event of a probe strike, this makes it safe to clear the planner and be sure that future moves are not removed by accident.

A motion plugin should implement probing in the following way:

Upon seeing the first move marked as EX_PROBE, the plugin should arm position latches on the hardware.
Then consume the EX_PROBE marked moves as normal.
If the probe stikes, the plugin should:
Cancel any MSG_REPORT_MOTOR_STOP requests. (see g. VERY important!)
Report the latched positions via mcMotionSetProbePos() for each motor.
Clear the hardware of any additional moves.
Call mcMotionClearPlanner() to clear the Mach planner of any unretrieved EX_PROBE moves.
Update Mach with the hardware's current position via mcMotionSetPos().
Call mcMotionSetProbeComplete().
If a MSG_REPORT_MOTOR_STOP has been received, do not acknowledge it. mcMotionSetProbeComplete() does this for you and a position sync as well.
If no probe strike, then the move continues to it's end point as if it is a regular move.
The plugin should ack the MSG_REPORT_MOTOR_STOP messages with mcMotionSetStill().
The positions latches should be disarmed (if needed) when a MSG_PROBE_DONE is seen.
In the event that the probe move is aborted, the plugin should:
Call mcMotionClearPlanner() to clear the Mach planner of any unretrieved EX_PROBE moves.
Call mcMotorSetPos() for each controlled motor.
Call mcMotionSync.
Call mcMotionSetStill() for each controlled motor.
Probe Operation Overview.
Upon executing G31, the core will mark those moves as EX_PROBE in the data stream.
If the probe strikes before the end of the G31 move, the plugin aborts the rest of the probe moves as described above. If a probe data file has been opened via mcCntlProbeFileOpen(), then the positions recorded by the motion plugin are inserted into the probe data file in the specified format.
If the probe doesn't strike and the G31 move reaches its end point and a probe data file has been opened via mcCntlProbeFileOpen(), then the end point positions are inserted into the probe data file in the specified format.
Using the probe data file routines.
int mcCntlProbeFileOpen(MINSTANCE inst, const char *filename, const char *format);
The format argument is a printf style format with expanding macros for the axis values. AXIS_X, AXIS_Y, AXIS_Z, AXIS_A, AXIS_B, AXIS_C. It is used in the following manner:


mcCntlProbeFileOpen(inst, "myProbeFile.csv", "%.4AXIS_X, %.4AXIS_Y, %.4AXIS_Z");
This will produce a probe file in CSV format like so:



1.0000, 2.0000, -1.4356
1.0100, 2.0000, -1.4343
1.0200, 2.0000, -1.4324
...

A format of "X%.4AXIS_X, Y%.4AXIS_Y, Z%.4AXIS_Z" would yield:



X1.0000, Y2.0000, Z-1.4356
X1.0100, Y2.0000, Z-1.4343
X1.0200, Y2.0000, Z-1.4324
...

A format of "X%.4AXIS_X\tY%.4AXIS_Y\tZ%.4AXIS_Z" would yield a tab delimited file:



X1.0000 Y2.0000 Z-1.4356
X1.0100 Y2.0000 Z-1.4343
X1.0200 Y2.0000 Z-1.4324
...

int mcCntlProbeFileClose(MINSTANCE inst); Closes the probe data file.

Craig
My wife left with my best friend...
     and I miss him!