Probe Message

[Screechy]

We use PC-DMIS 3.7
When we use two different Probes in the Alignment say 4mm and 1mm PC-Dmis will not show when to change Probes. (we use measure all once).

After we do the Iterative Alignment and the program goes through to do DCC Alignment the darn thing doesn't pop up and tell you when to change probe tips. It skips the tip change and keeps on going. You have to manually stop it and change tips untill it gets past the DCC alignment.

Anyone have any solutions?
Mr. Screechy

[JamesMannes]

We use PC-DMIS 3.7
When we use two different Probes in the Alignment say 4mm and 1mm PC-Dmis will not show when to change Probes. (we use measure all once).

After we do the Iterative Alignment and the program goes through to do DCC Alignment the darn thing doesn't pop up and tell you when to change probe tips. It skips the tip change and keeps on going. You have to manually stop it and change tips untill it gets past the DCC alignment.

Anyone have any solutions?
Mr. Screechy

Please post some code.

[PaulB]

We use PC-DMIS 3.7
When we use two different Probes in the Alignment say 4mm and 1mm PC-Dmis will not show when to change Probes. (we use measure all once).

After we do the Iterative Alignment and the program goes through to do DCC Alignment the darn thing doesn't pop up and tell you when to change probe tips. It skips the tip change and keeps on going. You have to manually stop it and change tips untill it gets past the DCC alignment.

Anyone have any solutions?
Mr. Screechy

No clue, maybe you clue simplify your initial alignment so that you only utilize one probe?

[AJHVW93]

I Had The Same Thing Going On For A Brief Time.try The Simple Things First .close Out Prog And Go Back In Make Sure Line Is Marked.

[bob mappes]

might be you still need to "mark" the probe change

do a shift + F3 and do a "mark all"

then see what happens

[than_357]

I used to get this when we were fighting to get the Gear package to work. It would overwrite our preferences and the next program would be a heart stopper...

Go "preferences"-"setup"-"warnings" (the box on the right).

About 13 places from the top click the box for "OK Please load probe =%$"

Fixed our PH9's near suicidal tendency for a time.

Tom

[JamesMannes]

I used to get this when we were fighting to get the Gear package to work. It would overwrite our preferences and the next program would be a heart stopper...

Go "preferences"-"setup"-"warnings" (the box on the right).

About 13 places from the top click the box for "OK Please load probe =%$"

Fixed our PH9's near suicidal tendency for a time.

Tom

Good answer!, good answer! (with the Family Feud music going)

[than_357]

Momentary "WTH ever happened to Richard Dawson" moment...

[#2#]

I am not doing what you're doing but mine often times misses a load probe command. It mostly does it when it is the first one in the program but not always. I have found though that if I put an operator comment "Sorry for the extra comment. This is just here to get the machine to not skip the next step." directly ahead of the loadprobe command that it will hit the loadprobe every time. Pain in the ... because then it stops twice in a row but hey, better than crashing with the wrong probe.

I'm not sure if that will work in your case but you could give it a try.

[rangerboat72]

I have found though that if I put an operator comment "Sorry for the extra comment. This is just here to get the machine to not skip the next step." directly ahead of the loadprobe command that it will hit the loadprobe every time. Pain in the ... because then it stops twice in a row but hey, better than crashing with the wrong probe.

Unfortunately, I have to do this too. It's just one of the many work-arounds I have to do...

[Gregl]

Unfortunately, I have to do this too. It's just one of the many work-arounds I have to do...

I have got by with a move point right before the probe change.

[Wes Cisco]

I have got by with a move point right before the probe change.

This is what I do too. I extra line of code, machine does not stop and wait for input.

[cmmguy]

This is what I do too. I extra line of code, machine does not stop and wait for input.

Youre just padding your post count....

[Gregl]

Youre just padding your post count....

No, I might have got the work around from one of Wes's posts. If my memory is right.

[Wes Cisco]

Youre just padding your post count....

It's deja vu all over again.