Jump to content

Error when running Fitting Position on simulation seat.


---
 Share

Recommended Posts

---
Hi there,

I am currently trying to set up a plan simulation on our offline seat. I have gotten it to run, however the little CAD model of our VAST-XXT unit doesn't match up with the position of the probe tip on any of the probes I've set up.

As far as I can tell from looking at this forum, I unintentionally skipped a step and didn't run "Fitting Position" on the master probe when I first created the simulation. However, when I try to, I get this error:

[img]https://imgur.com/a/FLYxCYI[/img]

I am unsure but I assume this is causing my problem, as I've followed the other instructions for setting up a simulation environment to a "T". I am running Calypso 7.6 if it helps.

Any help would be appreciated. Thanks!

Fitting Position.PNG

Link to comment
Share on other sites

---
Hi Zachary,

Simulation can be tough to set up initially. On first setup, I would recommend, if you run into errors such as the one you're seeing, it is usually best to just start the machine tab from scratch. It sounds like you have some instructions for setting it up, but, if not, the Knowledge Base in the US ZEISS Portal has some instructions for setting up simulation (and an e-learning) that can be found at this link: https://portal.zeiss.com/knowledge-base?id=2127111

If you're continuing to have issues even with a new machine tab, it may be good to try a fresh config folder. Once CALYPSO is closed, you can do that by navigating to C:\Users\Public\Documents\Zeiss\CALYPSO 7.6 and renaming the config in there "config_old" and when you startup CALYPSO again a new config will be created and you will be starting CALYPSO from scratch.

Also, make sure you have the latest service pack installed, I see you have 7.6, you can see the exact version under ? - About. The latest service pack is 7.6.12.
Link to comment
Share on other sites

  • 4 weeks later...
---
I have fixed this issue and wanted to update this thread in case someone else comes across this issue in the future: In short, I tried a bunch of different things to try and solve this, but the only thing that fixed it was to nuke the simulation environment and make a new one from scratch.
Link to comment
Share on other sites

 Share

×
×
  • Create New...