I'm running a dual arm DEA Bravo with 2017 R2. There is a section of one of my programs where I am measuring with a long arm on the master side. For no reason at all, the program suddenly thinks it has the short probe at a A0B0 angle, which can be seen in the graphic display window. This caused it to crash into the part because it suddenly thinks its a lot further from the part than it really is. When I hit the cancel button, it reverts back to the proper probe and angle in the display window. My code is solid, it doesn't happen every time I run, maybe 1 out of every 10 times. It only happens on the master side, with the long arm, and only happens with about 6 different features randomly. Has anyone ever had anything like this happen to them?
Random probe change causing a crash....
Collapse
X
-
M_71X2
M_ denotes the master side
71 is approximate length in centimeters of the probe and the arm
X2 2mm ball
So, it will randomly jump from the M_71X2 to the M_40X2 in the program.
Comment
-
seems robust and not a contributor, i'd definitely agree with Sora5 that the problem is likely some ghost embedded in in the old routine. "Shell" it, and see if that fixes it. otherwise, you might have a corrupt probe file.
On second thought, i'm naiive to dual-arm setups... Do you share the same probe files with both arms? How do you differentiate the probes for each arm? Is this possibly a contributor? Do you have that same probe name defined for both arms, and the demon is getting confused with which one it should be using?
-
-
I've had similar things happen, though rarely, and it comes from over editing a program thru over usage of copy/paste/rename, etc.
The few times these issues pop up, I've managed to get by by copying the entire program, start up a new program and pasting. Be mindful of the first probe command. That's permanent and requires you to rearrange (copy/paste) any code in your program up to the first probe callout to be above the new probe command of the new program.
This basically breaks all the links in your old program and relinks them when you paste in the new program getting rid of any weird background happenings from all the prior editing.
Comment
Related Topics
Collapse
-
I have a romer arm infinity 2.0 with pc_dmis 2011 installed. I've been using it since 2011 without any significant problems.
I use the 3mm probe...-
Channel: PC-DMIS for CMMs
01-23-2020, 01:45 PM -
-
by BlueRayWe're running a Romer Absolute arm 7535, and are currently shopping some new tips. My question is whether or not there is a simple way to change the tips...
-
Channel: PC-DMIS Portable
04-03-2013, 11:51 AM -
-
by biohazardI did program and bent a probe. and i need to run a diffrent program that used that probe. If i load a diffrent probe in its place will it work for that...
-
Channel: PC-DMIS for CMMs
01-17-2013, 10:34 AM -
-
by FMX554Ok so i have a program that runs great with no problems but we just bought a shank probe and id like to use that probe instead so i can just add the dimensions...
-
Channel: PC-DMIS for CMMs
03-31-2011, 10:16 AM -
-
by XanthroVersion 4.2
Sheffield Discovery's
I have a couple programs that worked just fine a week ago and now are causing me trouble. The...-
Channel: PC-DMIS for CMMs
06-11-2009, 11:52 AM -
Comment