Machsupport Forum
Mach Discussion => Mach SDK plugin questions and answers. => Topic started by: rich05 on June 30, 2009, 01:04:11 AM
-
probing right now gives two sets of points per probe this makes it impossible to create surfaces with CAD applications. Is there an hope that some good soul could check out what is going on? The plugin is fubar because of this. Thanks !
-
which probing plugin are you speaking of.......... there are a few........ can you give a link?
scott
-
From main page
http://www.machsupport.com/plugins.php
I have read allot of posts about people getting two sets of dots, often cited as a problem with the plug in. Curious though if it is just cheap probes getting false reads when the mill head stops retracting. There have been allot of posts regarding this as a bug. My probe is also giving sterio dots. Is somethign wrong with the plug in?
thanks
-
Rich,
I would need a link or copy of the source code, to look into it and see if I could find the problem.
do you have a link or copy of the source code?
scott
-
I dont know who made it. Does anyone?
-
SCOTT I believe they are referring to ARTS probing plugin. THat is the only one known to give the double points
(;-) TP
-
Is this double point thing truely a bug? Or is it caused by bounce?
How can this plugin be available if its broken?
-
I sent Art and message asking if he would send a copy to me of the source code for the probing plugin. If he does I will see if there is an "Undocumented Feature" vs. you may be getting bouncing from your probe.....
you could set your debounce up to like 400ms (or higher), just for kicks to see if it loads a double point.
scott
-
I sent Art and message asking if he would send a copy to me of the source code for the probing plugin. If he does I will see if there is an "Undocumented Feature" vs. you may be getting bouncing from your probe.....
you could set your debounce up to like 400ms (or higher), just for kicks to see if it loads a double point.
scott
Thanks Scott,
How do i change debounce to 400ms? My probe itself is not adjustable. I did not see an option in the plugin. Getting this plugin to work right would really change my work flow.
Thanks!
-
under general config
I looked it over, I dont see a place where it is doucle writing, so I suspect your getting a bounce on the switch.
scott
-
hi Scott thanks how do i change the 400ms on the probe you mentioned? So all those posts I read about 5 threads about double points are just people with bad probes? Thanks Rich
-
under general config, change the debouce
-
Is this Input singal debouncing? Right now it is set for 1000. Will this effect my servos though?? I have the mill decently working dont want to screw that up.
Thanks, R
-
This is the reply I got back from someone that makes nice probes.
"I did some testing on your probe, I stretched the spring a bit to prevent any noise from false trips. I also tried a heavier spring but I didn't like it, it is just a little too heavy.
The problem is not the probe but the software, I got the same double points. What it looks like to me is the software records the touch point and the reset point. This software plugin needs work."
Seems others are having the same problem....
-
I tried changing debounce to 400, also putting that 1k resistor between 5v and pin 15, and also using a heavier spring in the probe. Still getting two points per probe. Need help with this please. Thank you very much. Rich
small probe of 1"x 1" .05 grid, .05 retract, 5 inch per minute probe. note the double set of points.
(http://img40.imageshack.us/img40/2839/twosets.jpg)
-
GUYS it is NOT you PROBES (;-) Once mach sees the first trip of the G31 thats it you could tripp it a 100 times the first trip stops the G31 and it records that point. ANY extra trips are ignored UNTIL the g31 is called again for the next cycle.
the problem has to be in the plugin. Probably a piece of safety code to protect the probe causes a double trip to be recorded in error.
ONLY Art has the source code and only HE can fix it.
(;-) TP
-
Well, I looked over the probing source code and discussed it with Art last night......
Here is what Art says for you probers that are getting the double points to try first!!!!:
Art Fenerty:
"tell those that get double points to use a larger pullback...
reversals shoudl be 1.. but has a max of five, then it fails.. so larger pullback.. if no double points then thats whats causing it..
as I recall anyway.."
So, set your pull back to a larger value, (or even much larger), and then see if it clears up, if it does clear up, then thats the issue, and you can then reduce the pull back, until you see the double points again, then increase slightly.
NOTE: If that fails to resolve the problem, I did find a section of code that could potentially be the "culprit", Art IS aware of the section, so he thinks that the pull back is the issue.
scott
-
That is great news you and Art are looking into the problem with the probe plug in. A big thank you!
I am using the max pullback of .05 (that is the maximum pullback the plug in will allow), so that the points could be seperated out. Shown here you can see it forces a pullback of .05
(http://img41.imageshack.us/img41/6034/probesetting.jpg)
-
Pull back COULD be the issue at hand, Looking at the plugin code.
You have to account for the amount of movement in th eprobe to untrip it on reversals. I have seen some probes that had .010-.020" travel to untrip. ADD that to .010-.020"overtravel due to slow deaccellaration and add in the .010 min travel required by MACH it all adds up.
Certainly worth a try to those having the problem. I know I have logged in a zillion g31 probe cycles over the years and NEVER saw a double points write from the G31 in ANY file.
BUT I never use the 3D plugin either.
(;-) TP
-
min travel is .05 it tells me