forum.cncdrive.com

Hello,

After spending 185€ to buy the cncdrive pendant UCR201, i finally narrow the problem : After one G31 ok, no more G31 possible !
I must say that earlier that day, i made a succefull probing session. Weird.
But now...I get always the message that the probe sensor is already etc..

Hardware condition : The PC is new and dedicated, uccnc is the only software installed and running,Intel core2 6300, 4GoRam
os : win 7 up to date, NO PLUGIN but the UCR201 driver.
Soft : 1.2049
Firmware : 1.0230
Hard: 1.0
API: 2.1320
I use a UC300ETH_5LPT, serial CD112E
I set up a big led on the "run" page, duplicating the "probe" led in the diagnostic page.

The sensor is ok, and when i touch it, the big probe led turn green, and get back to grey as soon as i release the sensor.

NO FILE LOADED.

The sequence to reproduce : *** I Use the "run" screen to do all the job ***

1) Start uccnc with only the ucr201 driver enabled
2) Home all axis
3) move the head just above the sensor
4) Check, re-check, re-re-check the sensor is released.
5) G31 Z-200 F100 : works
6) set X to zero
7) G0 Z2
5) Check, re-check, re-re-check the sensor is released.
6) Again, just in case....
7) G31 Z-200 F30 : Popup the sensor was already active
5) Check, re-check, re-re-check the sensor is released.
6) Loop to 5)
6) I Want to die

I will send that message thrue CNBCDRIVE Support, but maybe somebody here will help ?

Sebastien

Hello Sebastien, Could you, please, upload your profile? I'd try the whole method as you described.

you may have to add a small wait after the move up- as the code runs very fast .
on my probes which are normally closed - open when probed. very occasionally the contacts wont close after a probe.
giving the probe a quick flick usually sorts this

Battwell may be right that you are not allowing enough time for contacts to break and regester the change.

UCCNC has some debounce settings which can be applied



and may help you, as well as adding
exec.Wait(200);

after your sequences.

As well as

while(exec.IsMoving()){}

to give motion a chance to finish before moving on to the next element.

if you provide your code we can have a look at it.

It is unlikley to be uccnc / uc motion controllers and it is likley to be hardware or coding related.

few answers to the remarks :
1) Wait 200ms, this is done for monthes. I am not anymore at that point.
2) Debounce is not an option : all the instruction are given with the command line, with my fingers and patience... Many seconds between actions !

This is a pure manual, slow set of instruction, made thru the native interface of UCCNC,

I thanks all of you guys, offering help. I will upload the profile in a few minutes...

Hey Balasz, i still wait for an approximate delay until that reproducible problem will be treated...
Seb

Guys, this is my configuration file, if you want to do some test and/or reproduce the problem.
Seb

Hi,

You already started this forum thread and my collegue Dezsoe already asked you for information and you also sent me an email about the same time.
It is waste of energy to reply on both the forum and in emails, so let's keep this on the forum only for now.
Dezsoe will check this issue out, just please give him informations if he asks something....

OK sir !

I could not guess who is who, and the relationship with cncdrive !
But i agree to continue on the forum.
Sebastien

Hello Sebastien,

Do you use all the two probe sensors? How are they connected and what kind of sensors do you use?

One sensor is a stepcraft 3D touch, the other a single contact,

see https://www.aliexpress.com/item/CNC-MACH3-Tools-Setting-Milling-Engraving-Machine-Auto-Check-Z-axis-Instrument-Probe-Sensor-Free-Shipping/32898210405.html

BTW : i just managed to do a process without any pendant : NO PROBLEM ! and 50 probe points...

I mean, the way the sensor are connected to the system is not an issue !

Sebastien