Reset needed when probe touches?!

JPoepsel

Hello everyone,
I have a stupid problem and maybe someone ran into the same and can help me...
When I start a probe, the spindel goes down, until the probe contact is closed (so far, so good), but then it does not rise  (at least most of the time) but starts beeping and requires a RESET.
The interesting thing: If I "simulate" the touch by puting some metal between the tool and the probe contact and remove it imediately after the touch, the contact is recognized correctly and the spindle rises as expected - no RESET needed at all.
I think, the problem is, that the probe contact is still closed at the end of a small time out after probing and DDCSV checks this status and goes into error stage, if true.
May be, the behavour is as described due to the fact, that I use an "inverted" probe signal: I set parameter #70  "Probe signal electric level" to heigh, connected the probe input by a 2.2kOhm pullup resistor to +12V-I and connected GND-I to GND (wich is connected to the metal parts of the machine).
Ytliu: would be fine if you have any idea!

Josef

edelec

I agree re the "talking to yourself" however some of us are listening<G>
I did wonder if your problem was limits but you cracked it before I could respond.

JPoepsel

Hi!

This Forum seems to degenerate to a self talk forum more and more....
Concerning this "Reset needed when probing" problem: It seems to be a bug in the software! All works perfect, if #70 is set to "low",  using a switch, which closes probe to +12V-I, when touching. If you set #70 to "heigh", pull up probe and short cut it to GND-I when touching results in the described "Reset problem".
This is not a problem of probe.nc et. al.! It seems, that the fundamental M101-M102 pair rises the Reset!

Ytilu: PLEASE: can you provide an update where at least the main known bugs are fixed? From my Point of view these are:
- White screen when toggeling through the different settings (FRO/SRO;SJR,F,S,...) reaching M5 (described elswere in the forum)
- Device hangs or behaves unpredictedly when too long comments appear in the G-Code to be scanned (reported by me)
- The "Reset on inverted probing" described here

Josef

JPoepsel

Hi!

The "Reset on inverted probing" was my fault! The reason was a short circuit in the connector between the y end limit and the probe input. Hard to find but it explains this stupid behavour...
So sorry for this wrong alarm. But Ytilu: you can add the the "execution continued with loaded program after extkey2.nc" to the bug list ...

Josef

Avis

What version do you use?
I have the 1.1 and it hangs with long programs, do those with version 2.1 work well or does it hang up?