Probing not working in 1.2022 with UC100

[cncdrive]

Hi Eric,

Yes, it will help a lot, thank you, because honestly I could only get the issue to happen once when tested with your profile, then I confirmed the issue on the forum and I could not reproduce it anymore.
So however my collegue said he found what the issue is, but it would be great if you could test it on your computer which can clearly reproduce this issue.
It is already very late night here, but tomorrow we will compile the release and I'll send a link to you first.

[cncdrive]

Hi Eric,

The bug fixed version of the UCCNC is ready for testing, the download link is in this forum thread: viewtopic.php?f=2&t=103

I appritiate if you could test the probing on the PC which you mentioned you could clearly reproduce this issue.

[eabrust]

Hi Eric,

The bug fixed version of the UCCNC is ready for testing, the download link is in this forum thread: viewtopic.php?f=2&t=103

I appritiate if you could test the probing on the PC which you mentioned you could clearly reproduce this issue.

Hi Balazs,

Unfortunately the patched version has not resolved the problem on my shop PC which controls the machine. It exhibits same behavior as version 1.2022, diagnostics shows the probe input trigger, but the probing doesn't respond/stop. In addition, when I run the tool touch-off macro (M31), there is a significant delay before it begins to run it (5 seconds maybe), and then it begins movement of z axis and also ignores probe input without stopping.

In addition, I know you said you were able to apply the profile and it would start working, that doesn't work for me either.

I've attached screen shots of the UCCNC 'about' information for the version that works (1.2020) and the version that still doesn't (1.2023), and also the stats of my two PCs. Both PCs are core duo machines, my office PC that worked with 1.2022 is a laptop, and my shop computer that doesn't work with 1.2022 and 1.2023 is a desktop, both run Win 7. I am still able to run ver 1.2020 in the shop without issues.


regards,
Eric

[eabrust]

In addition, I know you said you were able to apply the profile and it would start working, that doesn't work for me either.

I've attached screen shots of the UCCNC 'about' information for the version that works (1.2020) and the version that still doesn't (1.2023), and also the stats of my two PCs. Both PCs are core duo machines, my office PC that worked with 1.2022 is a laptop, and my shop computer that doesn't work with 1.2022 and 1.2023 is a desktop, both run Win 7. I am still able to run ver 1.2020 in the shop without issues.


regards,
Eric

One last screen grab of info for the PC that does work (a laptop in my office)

[cncdrive]

Hi Eric,

Thank you for testing it so fast and it's not too good that the issue is still there,
then it should be something else, not what my collegue thought about.
Unfortunately as I described you we currently can't reproduce the issue anymore on any of our computers, so it is a bit groping in the dark,
but we will continue looking for the possible reasons for this problem.

[cncdrive]

Hi Eric,

We worked on the probing issue all day today and it seems we found the real reason now for the problem.
Here is a new version for testing: http://forum.cncdrive.com/viewtopic.php?f=2&t=105

If you will have some time then please test it on the PC you can reproduce the issue with and let me know how this version works.

[eabrust]

Hi Eric,

We worked on the probing issue all day today and it seems we found the real reason now for the problem.
Here is a new version for testing: viewtopic.php?f=2&t=105

If you will have some time then please test it on the PC you can reproduce the issue with and let me know how this version works.

Balazs,
Great news! Probing works for me now. MDI commanded G31 and the probe trigger while jogging stops. I restarted UCCNC several times, went back to ver 1.2020 so the firmware reverted, then went back to 1.2024 and it hasn't failed yet! Thanks for digging in at fixing it so fast!

The only oddity I have found (based on the minimal test time I had tonight), is that my M31 toolsetting macro behaves strange. It works as it should, but there are very weird delays. As an example, after pressing button to initiate the macro, there is about 5 second delay, then it begins moving down. If I touch the tool plate, it stops instantly as G31 should, but then there is another 5-10 second delay before it retracts. After it retracts, there is another 5-10 second delay before it moves in for second probe, and so on. What used to run in about 5-10 seconds total from start of macro to finish, is now taking 30-45 seconds. I have attached a copy of the basic script which has always worked no problem in versions 1.2020 and prior. Seems like this would be an issue with the macro interpreter or delays in issuing the exec.code commands?

Code: Select all

//M31 probing macro (set for inches units)

//double probeX = 200;
//double probeY = 300;
double Zmin = -5;
double Feedrate = 10;
double Feedrateslow = 1;
double Slowretract=.05;
double SafeZ = 2;
double retractheight = 1.0;
double platethick = 1.0;

//if(!exec.GetLED(56)||!exec.GetLED(57)||!exec.GetLED(58)) // If machine was not homed then it is unsafe to move in machine coordinates, stop here...
//{
//  MessageBox.Show("The machine was not yet homed, home the machine before run to parking position!");
//  exec.Stop();
//  return;
//}

while(exec.IsMoving()){}
exec.Wait(200);

double Xoriginalpos = exec.GetXmachpos(); // Get the current machine coordinates
double Yoriginalpos = exec.GetYmachpos(); // Get the current machine coordinates

//exec.Code("G00 G53 Z" + SafeZ); // Move Z up first
//while(exec.IsMoving()){}

//exec.Code("G00 G53 X" + probeX +" Y" + probeY); // Move to the probe sensor position in XY
//while(exec.IsMoving()){}

exec.Code("G31 Z" + Zmin + "F" + Feedrate); // fast probe to touch plate
while(exec.IsMoving()){}
exec.Wait(200);

 double Zupslow = exec.GetZmachpos() + Slowretract;
 if(Zupslow > SafeZ)
 {
   Zupslow = SafeZ;
 }
 exec.Code("G00 G53 Z" + Zupslow); // Move to slow clearance plane
 while(exec.IsMoving()){}
 exec.Wait(1000);

exec.Code("G31 Z" + Zmin + "F" + Feedrateslow); // slow probe to touchplate
while(exec.IsMoving()){}
exec.Wait(200);

AS3.Setfield(platethick, 99); //Sets the value of the z current coordinate field to 'platethick'
AS3.Validatefield(99); //Validates the 'platethick' valuefor the z current coordinate field  with writting the offset coordinates as nessessary.


//if(!exec.Ismacrostopped()) // If tool change was not interrupted with a stop only then validate new tool number
//{
// exec.Code("G44 H1"); // Load tool offset one, note the tool lenght is defined in the tools menu
// while(exec.IsMoving()){}
// exec.Wait(1000);

 double Zup = exec.GetZmachpos() + retractheight;
 if(Zup > SafeZ)
 {
   Zup = SafeZ;
 }
 exec.Code("G00 G53 Z" + Zup); // Move 1inch above probe plate
 while(exec.IsMoving()){}
 exec.Wait(1000);

// exec.Code("G00 G53 X" + Xoriginalpos +" Y" + Yoriginalpos); // Move back to the original XY position
// while(exec.IsMoving()){}
//}





regards,
Eric

[cncdrive]

Hi Eric,

Thank you for the testing and confirming that the probing works OK now.

About the delays: I have checked and ran your macro a few times but I do not see the mentioned delays, I mean on my computers it all run as it should without the delays you mentioned.
Can you please check and tell me a few things:

1.) Are the delays there on both of your computers?
2.) Can you test if the delay is caused by the exec.Code or the while(exec.IsMoving()){} or the exec.Wait(); ?
I mean I'm not sure which one is causing the delay for you.
I'm thinking of making a very simple macro with just executing one exec.Code and before that a MessageBox.Show and also after that a MessageBox to see if there is any delays before or after that.
Another test I advice is to place a IDLE LED (copy from the Diagnostics page) and check when does the controller goes back to idle after the movement stops and then place the while(exec.IsMoving()){} to see if the issue is that the controlles changes late to idle.
And the third is to place an exec.Wait with for example 1000msec time between MessageBoxes and check if the wait time is the delay cause or not.

Unfortunately all of these works fine on my computer, so I need some help in narrowing down the problem so we could see what is causing the delay on your system,
if we could see at least which function is causing it then we will have a higher chance to find the reason.

[eabrust]

Hi Eric,

Thank you for the testing and confirming that the probing works OK now.

About the delays: I have checked and ran your macro a few times but I do not see the mentioned delays, I mean on my computers it all run as it should without the delays you mentioned.
Can you please check and tell me a few things:

1.) Are the delays there on both of your computers?
2.) Can you test if the delay is caused by the exec.Code or the while(exec.IsMoving()){} or the exec.Wait(); ?
I mean I'm not sure which one is causing the delay for you.
I'm thinking of making a very simple macro with just executing one exec.Code and before that a MessageBox.Show and also after that a MessageBox to see if there is any delays before or after that.
Another test I advice is to place a IDLE LED (copy from the Diagnostics page) and check when does the controller goes back to idle after the movement stops and then place the while(exec.IsMoving()){} to see if the issue is that the controlles changes late to idle.
And the third is to place an exec.Wait with for example 1000msec time between MessageBoxes and check if the wait time is the delay cause or not.

Unfortunately all of these works fine on my computer, so I need some help in narrowing down the problem so we could see what is causing the delay on your system,
if we could see at least which function is causing it then we will have a higher chance to find the reason.

Hi Balazs,

I finally got a little test time.

1) The delay is NOT on both computers, it is only on the 'shop' computer that originally would not trigger probe input. office computer works fine.

2) I did a bunch of tests using my G31 touchplate macro, and have it pinpointed to the exec.wait(xxxx) as the culprit. I verified that there is no delay for the control going to idle from run. I put a message box on either side of an exec.wait, and could then count out actual seconds as compared to milisec. I will attach my sample code below, which has comments with actual delays in seconds listed as notes.

The final thing I did was to comment out every single exec.wait from the macro, and it ran great, just like it always used to.

Hope this helps!

regards,
Eric

Code: Select all

//M31 probing macro

//double probeX = 200;
//double probeY = 300;
double Zmin = -5;
double Feedrate = 10;
double Feedrateslow = 1;
double Slowretract=.05;
double SafeZ = 2;
double retractheight = 1.0;
double platethick = 1.0;

//if(!exec.GetLED(56)||!exec.GetLED(57)||!exec.GetLED(58)) // If machine was not homed then it is unsafe to move in machine coordinates, stop here...
//{
//  MessageBox.Show("The machine was not yet homed, home the machine before run to parking position!");
//  exec.Stop();
//  return;
//}
//MessageBox.Show("start");  instantly appears-not problem

while(exec.IsMoving()){}
//MessageBox.Show("after ismoving");   no delay here-not problem

exec.Wait(200);
//MessageBox.Show("after wait 200"); a delay here, ~1-2 seconds

double Xoriginalpos = exec.GetXmachpos(); // Get the current machine coordinates
double Yoriginalpos = exec.GetYmachpos(); // Get the current machine coordinates

//exec.Code("G00 G53 Z" + SafeZ); // Move Z up first
//while(exec.IsMoving()){}

//exec.Code("G00 G53 X" + probeX +" Y" + probeY); // Move to the probe sensor position in XY
//while(exec.IsMoving()){}


//MessageBox.Show("probe");  no delay here - not problem
exec.Code("G31 Z" + Zmin + "F" + Feedrate); // Move to the probe sensor position in XY
while(exec.IsMoving()){}
//MessageBox.Show("pre-wait"); no delay here-not problem
exec.Wait(200);
//MessageBox.Show("post-wait");  delay here ~2-4 seconds!!

 double Zupslow = exec.GetZmachpos() + Slowretract;
 if(Zupslow > SafeZ)
 {
   Zupslow = SafeZ;
 }
 exec.Code("G00 G53 Z" + Zupslow); // Move to slow clearance plane
 while(exec.IsMoving()){}
//MessageBox.Show("pre-wait"); //no delay here-not problem
 exec.Wait(1000);
//MessageBox.Show("post-wait"); // delay here ~15 seconds!!

exec.Code("G31 Z" + Zmin + "F" + Feedrateslow); // Move to the probe sensor position in XY
while(exec.IsMoving()){}
exec.Wait(200);

AS3.Setfield(platethick, 99); //Sets the value of the z current coordinate field to 'platethick'
AS3.Validatefield(99); //Validates the 'platethick' valuefor the z current coordinate field  with writting the offset coordinates as nessessary.


//if(!exec.Ismacrostopped()) // If tool change was not interrupted with a stop only then validate new tool number
//{
// exec.Code("G44 H1"); // Load tool offset one, note the tool lenght is defined in the tools menu
// while(exec.IsMoving()){}
// exec.Wait(1000);

 double Zup = exec.GetZmachpos() + retractheight;
 if(Zup > SafeZ)
 {
   Zup = SafeZ;
 }
 exec.Code("G00 G53 Z" + Zup); // Move 1inch above probe plate
 while(exec.IsMoving()){}
 exec.Wait(1000);

// exec.Code("G00 G53 X" + Xoriginalpos +" Y" + Yoriginalpos); // Move back to the original XY position
// while(exec.IsMoving()){}
//}





[Robertspark]

Is your shop computer offline?

Could it be that there is some .net incompatibility issues because it is not running some Microsoft .net update that needs to be downloaded?