All Activity

Will they continue fixing the bugs in Calypso 2025 after 2026 is release? It sure would suck if they don't.

After re-reading your original post, I see that now😆 Good on you for making that work but yeah, I wouldn't sweat a couple thou! Separately, are you CMMs running from a shared network? The reason I ask is because you'll run into the same issue on your planner seat when you try and open a program that is actively being run from a shared network, even though it's "offline".

Yeah I had to use that section for a couple of my probes lol, we have made some custom probes, and also have many designs that use components i cant find anywhere lol. I imagine my probe locations might be a couple thou off than where they actually are. Great to hear that I can just name every probe the same and it will work. That's what ill do, Thank you very much everyone!

Got it. I was thinking it could use the graphics from the ssc AND the actuals from the pcf together but after some testing I realized you're right; it doesn't actually effect how the ssc functions or "update" it in a way to help avoid simulated collisions. It is possible to import the ssc into the existing probe file and update the system but it would still use the created ssc file for collision detection and the pcf file for the everything else. @Luke Cashman Norbert is also correct in that it's not a huge deal if the stylus system you built in creator is not identical to the one being used at the machine, depending on what kind of clearance you're working with. I.e. if your clearance cube is set to an inch outside of your CAD -- a couple mm difference in length won't really matter for moving around the part. It's just a nice visual and reference. He also mentioned that you could use "generic" components when building a system in the creator if you can't find the exact length/size of component from the list. This seems like the easiest solution. If you build the stylus system in creator and save it with the exact name (system and stylii) as they are online at the machine, the transition should be seamless.

I understand, but is stupid in Inspect there arent "drag and drop" option or similar. We working on eclipse and conturaG2 with Calypso 2025, and scanner is a new to Us. We had a training 2 days but is too short and we must by trial and error method. Anyway thanks for response.

Thanks for a hint. Unfortunatelly i am facing ballons like "01a /u" and some numbers are skipped. I would preffer to have something like "Annotation" to let me name it as i want and have access to it in table ( which now is not )

So, based on my understanding. I would load the PCF (which im assuming is the actual probe information from my online cmm, just confirming this im still pretty new) then import the SSC model in order for the program to be compatible with the online cmm, and to have a semi-accurate model for collision? My main goal is to have all of our probes set up on this planner seat in a way to where i can edit or create programs on planner, and then import the programs into the online seat with little to no issues between probes. Currently we have no models created for our stylus systems so when I bring the stylus system PCF files into planner i would like to add in the SSC models i just created into the stylus systems. Or would i just not bring in the actual stylus information (PCF?) and only import the SSC model, and make sure each probe is named the same as it is in my online CMM?

@Martin Jánský thanks I try use numbers to sorting. Other ways are a bit complicated and I dont had any $ to do it for company, only do it to myself. @Nanno Muehl Operations ► Elements ► and use baloons is the option, and also there are different options but I must had a time do do it. Thanks Guys i will combine on yours method. Have a lead

I had seemingly similar problems with other systems (non metroligy) with cheap and or faulty cabel. Does it only happen when you use the scanner? Maybe a semi-faulty cable leads to data loss everytime you need bandwith to transfer the measurement data.

Out of curiosity ... Why do you have to change your location to USA to access services from a german company?

Sorry, but I still doubt it. 🤔The imported SSC model data is fixed and cannot be updated (as in "changed in dimension") through other data. The actual dimensions from the PCF may be present in the stylus list, but collision detection is still done with the original SSC model.

To load an autorun file automatically, first set Calypso to start with autorun. While doing so you can select an *.arn file to open in the path field below. After selecting the file, switch the setting back to normal Calypso. Now whenever you open autorun, it should automatically load the *.arn you put in the path field. But beware, this setting has to be done seperately for each Calypso user, and you should be prepared to lose it again after certain update procedures.

I noticed that on one of the machines I open auto run from the Start desk and it automatically goes to the .arn file and on the other machine it opens autorun and I have to tell it to open the specific file for the autorun to open, does anyone have any experience with that? So, one machine loads the .arn file automatically and the others go to this and I have to file, open and tell it the .arn file. Not sure why though.

Qmark makes delrin ones (XXT-AP-ID3-D) Primarily for weight but would have some CTE benefits as well!

I see what you're saying but I wouldn't overwrite the values, I'd want to update them. Order of operations would most likely play a big part too. Ideally, you'd already have the ssc file created and then you could update it with the pcf numbers from the actual stylus system. I don't normally use ssc files or simulations but it should work...in theory😎.

Was meinst du mit "Stopp"? Ich steh da gerade auf dem Schlauch. 🤔

Martin, Thank you for your input. You have USA for your location for it to work. See Martin's suggestion below: Go to profile on zeiss portal and edit your location to USA - then relogin

Ich habe noch einige weitere Tests durchgeführt. Dabei ist aufgefallen, dass Änderungen an bestehenden Bildern oder Texten nicht übernommen werden. Füge ich jedoch einen neuen Stopp mit dem Text „Test“ hinzu, erscheint dieser sofort und ohne Neuladen. Ändere ich den Text anschließend auf „Text2“, wird die Änderung nicht mehr aktualisiert. Genau hierin liegt unser Hauptproblem: Unsere Maschinen sind auf drei Werke verteilt. Wenn für jede Änderung oder Aktualisierung ein manueller Eingriff bzw. ein erneutes Laden erforderlich ist, entsteht ein erheblicher zeitlicher Aufwand und die Pflege der Inhalte wird unnötig erschwert.

Hi everyone! I'm having trouble with my hawk2, it keeps loosing the connection to the pc. It happens everytime I use it, sometimes I can just reconnect the scanner and keep going, but most of the times I have to restart the pc to get it working. I can be in the middle of scanning a part and then it just loses the connection and I get a Error MFG-0011 when I cancel the work. Have anyone else had these types of problems with their hawk2? I've been in contact with my local supplier and Zeiss-support about it when the problem started.

go to Resources->Features Representation, pick Circle, change Position to Cylinder coordinates, then recreate your position-characteristics

I think it's not implemented yet in PiWeb protocols - tested on v8.4 original protocol template.

Hi guys, Anyone can help me about the piweb showing aditional report in polar coordinates? if i have in cartesian coordinates its ok, but when i change for polar coordinates i dont have any graphycal indication. Any help will welcome

Genau so machen wir das auch. Nein, das liegt einfach daran, dass die Definition der Autorun-Oberfläche komplett in den Arbeitsspeicher geladen wird und die Datei auf dem Datenträger dann nicht mehr auf Änderungen geprüft wird. So macht es Calypso ja z.B. auch bei Messprogrammen. Da hilft leider nur Oberfläche beenden und neu laden.

Select Preparation ➝ Features representation or click the icon in the toolbar. Mark the feature before so that the desired geometry is selected. See "Checking or modifying the representation of features" in the manual.

No problems in getting the Default PiWeb Reporting, it pops up on the screen after end of program. But then PiWeb continues to read and after a while the below message pop up. We're running with Calypso 7.6.20 and PiWeb 8.4.23.0?