Timing Signal Being Ignored

[christopera]

Hi Dave,

I hate to be a pain again, but I'm experience some issues. I switched from the ESS to UC300eth controller. I wanted to gain access to UCCNC but also keep my handy dandy Mach Std Mill setup because I know how to use it and have had excellent results machining with it.

Long story short, after changing to the UC300eth and adding a MX3660 and keeping my G540 I am now having issues measuring tools via the touch plate in the timing input. I have both the probe (master tool) and touch plate on the same port but separate pins. I can individually get the timing and probe to register correctly in the signals page. However when I go to set my TP MCz or measure any tool for that matter when the timing signal is activated the Z does not stop moving. Additionally, if I watch the signals during this, when the timing signal activates so does the probe. This despite the probe sitting on the tool shelf and being totally inactive. If I move the touch probe tip when not measuring tool length I see just the probe input. If i touch the touch plate to the spindle I only get the timing signal.

I tried creating a new profile and entering in all my settings. I was thinking it was a plugin issue with the UC300eth plugin versus the old ESS plugin. But creating a new profile and starting from scratch produced the same results. Perhaps I should reinstall Mach?

I'm on .66 with the most recent version of MSM.

All other inputs (limit switches) work correctly.

Thanks so much!
Chris

[DaveCVI]

Hi Chris,

I suspect you are correct when you wrote:

I was thinking it was a plugin issue with the UC300eth plugin versus the old ESS plugin.ris

The use of the Timing input for probing depends on the use of a call to mach which is known to work for a parallel port interface and on the ESS. I do not know if that call operates correctly with a UC300eth device. From what you are seeing, it appears that it may not be working correctly with the UC300ETH.

At this point, I should point out that the UC300 device is not an MSM supported device. That is not because CVI knows of any issues with them, it's just that we do not have the the bandwidth needed to test all the various motion devices on the market. The mach call involved is "SetInputData".

To get more information, I will send you a document (via direct email) which explains how to get an MSM probing debug log. If you will run the test where this fails for you and send me the log, I may/should be able to see what is happening when MSM makes the SetInputData call to mach when the UC300 is being used.

Dave

[christopera]

Log sent.

I'm on 2.3.6. When I tried to update to 2.3.12 it tells me my license isn't valid.

[christopera]

I'll probably re-up my license this evening. I'm not sure if I .12 will help, but since you provide reliable support I should provide reliable funding.