Error 205

[[To...]]

Customer is getting the attached error.  They build a program from CAD, do a manual alignment and then after a couple of runs, they get the error and program will no longer run.  I observed them creating the same program from scratch via zoom and did not see them do anything wrong. Same thing happened.  I see a reference to Command/Macro but didn't observe anything but straight Calypso programming.  They submitted a log to Zeiss and they found the machine was trying move a distance 10x greater than possible for machine just before the error.

Programmer is fairly new at Calypso but has replaced a former programmer.  Is there any setting that the old programmer may have set up in Calypso that would be a default for all new programs? 

Edited January 22

[[Ma...]]

We have that same error from time to time without any reason - no formulas, no pcm, nothing complex - just simple program. Another run is without problems.

[[DW...]]

Please sign in to view this quote.

Anything in the inspection_start_pcm.txt files?

[[To...]]

Please sign in to view this quote.

I will check, but they don't have pcm license.  Wouldn't that be an issue when it runs the first half-dozen times?

Edited January 22

[[To...]]

Please sign in to view this quote.

How do you resolve the issue?

[[DW...]]

Please sign in to view this quote.

Possibly. Just throwing out ideas.

[[Mi...]]

What version of Calypso?

We started getting this issue when we started running Calypso 2017 ( 6.4), and 2018 ( 6.6.28) did not fix it. Most often it happens to use when scanning a plane, especially when the movement is counterclockwise.

We've attempted a very long list of things and it doesn't address it. Rebooting the controller makes it go away for a fairly long period of time, then it returns.

Many of the CMMs in question had 2015 or 2016 on them for years and never had this issue. I'm hoping the next time we do a sweeping upgrade this issue gets fixed along with it.

One difference between cases is, ours exclusively happens on DuraMax CMMs with XXT, and do not have a preceding collision error like your example does.

Edited January 22
More Info

[[ni...]]

Hi,

 

I've had also this error by the past, It was the left joystick of the control panel who was getting mad. 

i've change the control panel beetween the two CMM and the error follow the control panel... , so I bring it to maintenance.

For you does the error come with every program  ?

 

Edited January 22

[[Ma...]]

Please sign in to view this quote.

It's so little occurence i can not replicate. It's occuring on well known programs

[[ni...]]

just before calypso crash, there was a red light on the command (maybe the error light) 

if it arrived when the CMM doesn't run and the command was Locked, the command start to singing (like someones push the jostick with the comand locked)

and amazing thing, if it arrived when the CMM doesn't run AND the command was unlocked, the Z axis goes up by it-self :), 

 

 

Edited January 23

[[Ma...]]

The 205 Syntax error can be caused by various types off different things, just as the 488 Can Device, its more of a general error.

Issues could be:

1. Controller Firmware not compatible, needs to be updated.

2. CALYPSO file issue, uninstall CALYPSO and delete any leftovers under "C:\Program Files (x86)\Zeiss\CALYPSO 7.x / C:\Program Files\Zeiss\CALYPSO 7.8" and reinstall.

(don't delete anything in the "public" folder!!)

3. In another Ticket the issue was caused by the RT, after updating to the latest Servicepack and unmount/mount of the RT the issue was gone (this was in an older Version of CALYPSO, 6.2)

4. RT again, if you reached the maximum turns for a RT it can cause the 205Syntax Error. Solution: RT reference point.

If none of that helps i would recommend contacting your local CALYPSO Software Support.