Dynomotion

Group: DynoMotion Message: 9916 From: moray_cuthill Date: 8/6/2014
Subject: v4.33cc, Mach3 and probing

Hi,


I've just built a little dedicated probing machine using a KFlop and KStep, and have hit an issue.with the probe.


Initially I was using mach 3 43.66 with kmotion 4.31s as that was what I had installed on my laptop, but was experiencing a couple intermittent errors using the Crafty CNC Probe It wizard. The errors weren't major, but required the probing routine to be restarted.


This morning I tried updating to the latest kmotion version, and now any attempt at probing results in everything hanging after the first probe event. By hanging I mean motion stops as though mach is waiting for something, and can be recovered by issuing a new command or exiting the wizard. I tried going back to 4.31s by reflashing and swapping the mach plugin, but mach keeps saying the 4.31 plugin is defective. I tried fully uninstalling 4.33 with no difference.

 I tried reinstalling 4.31s, however the installer stops due to an error with no details.


Is there anything that has changed between the two versions that could affect probing?


Thanks

Moray
Group: DynoMotion Message: 9918 From: Moray Cuthill Date: 8/6/2014
Subject: Re: v4.33cc, Mach3 and probing

Ignore the bit about the earlier version not installing, turns out the anti-virus was causing that problem, and I now have mach3 loading 4.31s plugin ok. I'll test the probe once I get home from work, and let you know if probing is working again or not.

Thanks
Moray

On 6 Aug 2014 15:24, "moray.cuthill@... [DynoMotion]" <DynoMotion@yahoogroups.com> wrote:
 

Hi,


I've just built a little dedicated probing machine using a KFlop and KStep, and have hit an issue.with the probe.


Initially I was using mach 3 43.66 with kmotion 4.31s as that was what I had installed on my laptop, but was experiencing a couple intermittent errors using the Crafty CNC Probe It wizard. The errors weren't major, but required the probing routine to be restarted.


This morning I tried updating to the latest kmotion version, and now any attempt at probing results in everything hanging after the first probe event. By hanging I mean motion stops as though mach is waiting for something, and can be recovered by issuing a new command or exiting the wizard. I tried going back to 4.31s by reflashing and swapping the mach plugin, but mach keeps saying the 4.31 plugin is defective. I tried fully uninstalling 4.33 with no difference.

 I tried reinstalling 4.31s, however the installer stops due to an error with no details.


Is there anything that has changed between the two versions that could affect probing?


Thanks

Moray
Group: DynoMotion Message: 9923 From: Moray Cuthill Date: 8/6/2014
Subject: Re: v4.33cc, Mach3 and probing
More testing done.
 
After rolling back to 4.31s, probing started working as planned. Updated to 4.32a, and again it worked fine, but when updated to 4.33cc, the problem appears. I never tried the other 4.33 versions, and I probably won't be able to do so for at least another week as I'm away on holiday next week.
 
Moray


On Wed, Aug 6, 2014 at 7:36 PM, Moray Cuthill <moray.cuthill@...> wrote:

Ignore the bit about the earlier version not installing, turns out the anti-virus was causing that problem, and I now have mach3 loading 4.31s plugin ok. I'll test the probe once I get home from work, and let you know if probing is working again or not.

Thanks
Moray

On 6 Aug 2014 15:24, "moray.cuthill@... [DynoMotion]" <DynoMotion@yahoogroups.com> wrote:
 

Hi,


I've just built a little dedicated probing machine using a KFlop and KStep, and have hit an issue.with the probe.


Initially I was using mach 3 43.66 with kmotion 4.31s as that was what I had installed on my laptop, but was experiencing a couple intermittent errors using the Crafty CNC Probe It wizard. The errors weren't major, but required the probing routine to be restarted.


This morning I tried updating to the latest kmotion version, and now any attempt at probing results in everything hanging after the first probe event. By hanging I mean motion stops as though mach is waiting for something, and can be recovered by issuing a new command or exiting the wizard. I tried going back to 4.31s by reflashing and swapping the mach plugin, but mach keeps saying the 4.31 plugin is defective. I tried fully uninstalling 4.33 with no difference.

 I tried reinstalling 4.31s, however the installer stops due to an error with no details.


Is there anything that has changed between the two versions that could affect probing?


Thanks

Moray
Group: DynoMotion Message: 9925 From: Tom Kerekes Date: 8/7/2014
Subject: Re: v4.33cc, Mach3 and probing
Hi Moray,

I don't recall anything changing.  You might compare your Notify program with C:\KMotion433cc\C Programs\NotifyProbeMach3.c

Please use the latest Test Version 4.33c and post the Notify code you are using and a sequence that fails and we will test it.

Regards
TK

From: "Moray Cuthill moray.cuthill@... [DynoMotion]" <DynoMotion@yahoogroups.com>
To: DynoMotion@yahoogroups.com
Sent: Wednesday, August 6, 2014 4:27 PM
Subject: Re: [DynoMotion] v4.33cc, Mach3 and probing

 
More testing done.
 
After rolling back to 4.31s, probing started working as planned. Updated to 4.32a, and again it worked fine, but when updated to 4.33cc, the problem appears. I never tried the other 4.33 versions, and I probably won't be able to do so for at least another week as I'm away on holiday next week.
 
Moray


On Wed, Aug 6, 2014 at 7:36 PM, Moray Cuthill <moray.cuthill@...> wrote:
Ignore the bit about the earlier version not installing, turns out the anti-virus was causing that problem, and I now have mach3 loading 4.31s plugin ok. I'll test the probe once I get home from work, and let you know if probing is working again or not.
Thanks
Moray
On 6 Aug 2014 15:24, "moray.cuthill@... [DynoMotion]" <DynoMotion@yahoogroups.com> wrote:
 
Hi,

I've just built a little dedicated probing machine using a KFlop and KStep, and have hit an issue.with the probe.

Initially I was using mach 3 43.66 with kmotion 4.31s as that was what I had installed on my laptop, but was experiencing a couple intermittent errors using the Crafty CNC Probe It wizard. The errors weren't major, but required the probing routine to be restarted.

This morning I tried updating to the latest kmotion version, and now any attempt at probing results in everything hanging after the first probe event. By hanging I mean motion stops as though mach is waiting for something, and can be recovered by issuing a new command or exiting the wizard. I tried going back to 4.31s by reflashing and swapping the mach plugin, but mach keeps saying the 4.31 plugin is defective. I tried fully uninstalling 4.33 with no difference.
 I tried reinstalling 4.31s, however the installer stops due to an error with no details.

Is there anything that has changed between the two versions that could affect probing?

Thanks
Moray
Group: DynoMotion Message: 9932 From: Moray Cuthill Date: 8/7/2014
Subject: Re: v4.33cc, Mach3 and probing
Hi Tom,
 
I've just compared the notify code, and it's identical to the latest example file, with the exception of the input bit and active state. I'm using input 170, with active state 0/low (i.e. when the circuit breaks, the probe has hit)
 
Unfortunetly I don't have an exact sample of code (the Probe It wizard is all pre-compiled files/macros), however I've been in contact with the writer, and he says the error message I'm getting after I have to manually quit (press Esc) the routine, would indicate the macro is hanging while waiting for notification the motion has stopped. He says the macro code it fails at is simply -
G31 x# y#
while ismoving()
wend
obviously with the relevant XY values the macro has calculated.
 
I know when I first had issues after installing 4.33cc, I also tried Art's Digitize wizard using the default values which generates a g-code file, and it also hung after the first probe event. However I've not retried that wizard since getting things working again.
 
Just to clarify, is 4.33c or 4.33cc the latest version?
 
I won't get anytime to do any more testing for another week, as I'm away on holiday for a week starting saturday.
 
Thanks,
Moray


On Thu, Aug 7, 2014 at 1:38 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:
 

Hi Moray,

I don't recall anything changing.  You might compare your Notify program with C:\KMotion433cc\C Programs\NotifyProbeMach3.c

Please use the latest Test Version 4.33c and post the Notify code you are using and a sequence that fails and we will test it.

Regards
TK