Hi All,
I have an issue with a probefile and needs to get some 'tools' to solve it.
I use a software utility to probe a PCB blank on a set of mesh points, the board I'm working on at the moment has 210 probe
mesh points which are recorded in a file. The G-code probe job runs fine, the file is created and the data triplets recorded.
The problem it that the file contains more data triplets than probe cycles, sometimes as many as 220 after only 210 probe cycles.
Thought in first instance that I had a noisy probe circuit. I've used this setup with M3/PP for sometime without this behaviour.
Tried increasing debounce settings on ESS probe pin, no change. Fitted capacitor to the BOB pin with a time constant of 1ms, no change.
Have probed the output of the BOB with my scope and have yet to find any switch bounce. I can't categorically state that its not a hardware
issue but increasingly forced to believe the hardware is good..ergo the ESS/M4 combination is randomly recording two events instead of one.
When an extra unintended data triplet is recorded its a duplicate of the preceeding entry.
I have watched the ESS plugin diagnostics page like a hawk when a probe job is running but have yet to see a fault. There doesn't appear to
be any facility to log the diagnostic so I can only watch it in realtime, hardly conducive to finding a fault if there is one. Does anyone know if the
diagnostic can be logged either by a built in facility or maybe some code that would have to crafted to do so?.
Have had a look at the M4 log but have only a few guesses at what all the entries mean. Is there any documentation official or otherwise that might
allow me to make more sense of what I'm seeing?
What I'm hoping is that I can record a probe job run log and then either manually count the events in the log or 'strip' the logfile of irrelevant entries
to focus on the probe event/issue of data triplet record to the outgoing file stream.
Craig