All Activity

We had one of our Conturas have this error just a few weeks ago. We had a tech come out and he diagnosed the problem as a malfunctioning sensor control board. After it was replaced, our machine was fixed. Hope this helps.

same issue here. Tried to unistall the latest KB installed yesterday, not working either

Go to: Plan -> Measurement run Info for CNC start -> Select ..... you can choose a set-up picture, a word file, power point file, etc. Then in the autorun program icon under Measurement Plan Definition, click on checkbox for Force measurement run information at CNC start.

We want to see the model, which contains our setup fixture (part orientation) in the Autorun module.

All GD&T values are zone of tolerance, not a pure linear deviation. So a +0.300 deviation from nominal results in a 0.600 zone of tolerance consumption of the profile.

It looks like there is some invalid character that it doesn't like that you are using.

This is great. Confusion was why does is it multiply by 2. If the actual dimension deviates .300 from nominal, why does at measure at .600 profile. Thank you for your explanation on this. I appreciate it.

I have very similar star probe on an XTR sensor, I have had no problems with qualifying at all. The only weak link is the Down position, is that a 1.5Ø stylus? I would go with a stepped shaft for that.

Bonjour, Depuis peu, à la fin de la mesure de mon programme, le rapport Piweb ne fonctionne plus et affiche une erreur " valeur hexadécimal 0x0C est un caractère non valide. Ligne 46, position 619." Je n ai aucune idée du pourquoi et du comment. Si j active le protocole standard, cela fonctionne parfaitement. Savez de quoi cela peut venir ?

These are all settings in qdasconv.con, where you specify whether it's dfq, dfd+dfx. As Martin says, everything is contained in dfq, and dfd and dfx are divided into attributes and results. The path is also set there and is valid. If you want to do it temporarily, I would make a copy of the file, change it, and then restore the original later.

The same here, would be nice to have a solution in time.

Hello, same problem, no login possible at Quality Soite

I'm pretty sure Cory did a complete uninstall and re-install of Calypso 2025 with the latest patch "8.0.1203" then created a new master probe + imported other probes and that seems to work in simulation.

@Donny Fraser, Very interesting approach. Thanks for sharing about it. It sounds like this is a strategy that others have found to be effective. My first inclination would be to probe the datum simulator surfaces that the workpiece's datum features contact. This requires that the datum simulators have minimal form error and that the workpiece makes proper contact with them. However, I love hearing alternative approaches including best-fit alignments. Keep us posted on this project, and I would love to hear how it turns out.

As i tested - that Name for output files is only for path - file name is default as program name. Perhaps QDASCONV can solve file name, but i have a workaround with BATCH file to do my things. For us we use DFQ - it's all in one file - DFD and DFX should be separate files i think

Maybe check for a hidden sab file? Would Calypso see a hidden sab file?

Does anybody know how the individual path settings for Q-DAS files under Resources -> Name for output files go together with the output path in QDASCONV.CON? Does one override the other? If so, which one has priority? And if the individual path is in effect, which type of output file(s) (DFD, DFX, DFQ) is written? This setting looks a bit contradictory to me. Has anyone already used it an can enlighten me? I'm looking for a way to have a Q-DAS file of ALL measured chracteristics written to a seperate path whenever needed, but only temporarily. I don't want to change my usual Q-DAS output settings in QDASCOV.CON. Is that possible somehow?

@Bolfin Paiz https://portal.zeiss.com/knowledge-base?id=415735

I love Dark Mode. I'm excited for Calypso to have this.

No change with DeviceActivator. To the hotline....

Not much documentation. The official PCM manual says: From other sources:

Hallo, gibt es zu den PCM Befehl "outputMultiQdas" eine Dokumentation? Gruß, Matthias

@Tom Oakes If i received this issue as an Support Ticket, my first suggestion would be to run the device activator. It just adds ID's to the controller, there is nothing to worry about when installing it. If that doesnt help you should create a Support/Service Ticket and let my colleagues investigate further. To me it looks like a hardware/controller issue since the data loader is based on the controller.

@Marcel Hartmann Based on my posts on the problem, do you feel the device activator would fix my issues?

@Richard Shomaker THAKS