All Activity
- Today
-
[Ro...] joined the community
-
[Lo...] started following New GD&T Engine: FreeForm Surface Profile and Combining Features for Profile
-
Hello everyone Has anyone else noticed the new GD&T engine will not let you surface profile freeform surfaces? Hopefully this is temporary, I can't find anywhere that the new engine will interact with FF surfaces
-
That is the problem right there. In order to calculate 2 point, it has to be a continuous 360 degrees with an even number of points. You could not do a circle with for instance 17 points but a full 360 degrees. It will not calculate it.
- Yesterday
-
Hello everyone I have a question about combining features for one profile. I have these 2 cylinders, measured as individual cylinders, but there is 1 total profile that applies to the surface as a whole. I am currently recalling the 2 cylinders into 1 point, and this is giving me the combined profile dimension, but it prevents the CAD evaluation graphic display from showing the hits in a heat map. What are your suggestions here? In general, what are your strategies for combining multiple features for one profile? Thank you in advance
-
Seems there is a way with a batch file or hidden PCM ... https://forums.zeiss.com/messtechnik/community/viewtopic.php?p=58354&hilit=run+bat+file#p58354
-
The only edits I made to the original template was changing some header inputs to adapt to our company needs, and removing the additional true position (M.) line. I just tried changing back to the standard protocol and its back to cutting off the last dimension...There must be some miscommunication between the print output and my printer, because the PDF saves perfectly and the PiWeb report window displays fine on the screen (full page, page number included, etc.) The particularly strange thing is, its only the immediate, post inspection run print out that does this (cuts the page short). If I print again from the report display window, it prints out the full report. Standard Protocol.pdf
-
[Br...] started following Calypso REST API Documentation
-
I am new to controlling Calypso via the API. I was shown the XML documentation on how the REST API works. But when I try to access the API at localhost I am not getting the result I am looking for. Can someone provide examples or documentation on how to actually implement these calls? It might be that my API app needs to be configured. Attached is the picture of the results when I try to call: http://localhost:5000/api/inspection/getopenedinspections
-
[Ch...] started following [Mi...]
-
[Ni...] joined the community
-
Im sure these is, I will search when I have some time.. Question : if you're making the parametric program, do you just want to check to make sure these 3 files exist ? fileExists() Is it important for the program to know if there are more files or you just want to check to make sure ?
-
[Je...] started following PiWeb report cutting off last dimension
-
So, Loren, would you say that PiWeb "saves the user time" and that report generation is easy, intuitive and customizable 😏?
-
I want to make a parametric program, that I can edit entirely outside of the program... Is there a function that simply will give me all the file names in a directory? Basically, can I read these 3 files and get them in a list? or is this going to be something that needs done with getParameterNamed() and a loop?
-
[Mi...] joined the community
-
[Ja...] joined the community
-
[Mu...] joined the community
-
Hi guys, I have a program that i want to use in pallet, and i have an issue, as soon as i run first part of this pallet Calypso comes with an error "PCM: Parameter (random parameter name) not defined.", at the same time when i run the same program on our offline laptop the pallet runs with no issues. Can someone give me an idea what to do ? Thanks.
-
That's insane, there has to be a mistake there. For anybody who doesn't know... fans are like bearings, it's all standardized. Look up the specs, voltage, RPM, CFM, match them ( don't forget to compare the connector) and buy from whoever you like.... 23k for a standard fan is insane if that's all it is. Also, for anybody curious... here's some PCM code to play with to grab the controller temps... addToFile("C:\data\cmm\stf\ControllerInfo.txt",cmmInquire("sfmt(#cpuTemperature)"),",",cmmInquire("sfmt(#cpuFanSpeed)"),",",time(),",",dateInNumbers())
-
[Iv...] joined the community
-
[Ch...] changed their profile photo
-
Does anyone want to explain why Zeiss is quoting me $23,000 for this fan. I normally don't mind the Zeiss tax; But these things are about $20 dollars online. I might even splurge and get the $40 ultra-premium oneemium one.
-
Yep, it seems setFit() does something similiar. I've never used these CAD commands so far, so they were not on my radar.
-
Hello Jeff, you can achieve this with setViewDirection(0,0,1) // view from +Z setViewDirection(0,0,-1) // view from -Z setViewDirection(1,0,0) // view from +X setViewDirection(0,1,0) // view from +Y . . . setViewDirection(-1,0.5,0.7) // something like this is also possible
-
[Ia...] started following [DW...]
-
Hello Brad, you can find it in the Online-Help of Calypso: CALYPSO Online Help (Calypso 7.6): Defining features -> Linking features in constructions -> Defining features by recalling -> Reference: Format of the recall files
-
[Lu...] joined the community
-
[Ad...] joined the community
-
'Machine move' in Calypso? PC-DMIS guy learning Calypso...
[Ar...] replied to [Da...] 's topic in General
the Safest way if you have many RDS rotations in your program Run is to declare "Swivel/Rotate Position". With this, you don't have to specify on a either BEFORE or AFTER a Feature specific CMM position. This also helps if you want to easily rearrange all your Features & Characteristics to optimize your measurement Run. -
[St...] joined the community
-
Thank you Jens for the TypeOfScanningPath=Circle tip. I have to try it out.
-
[St...] joined the community
-
[Na...] started following Uninstall help
-
Hello, please make sure nothing is left in C:\Program Files\Zeiss\INSPECT\2025 Then open the registry editor (WIN +R -> regedit or open it from the apps) and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\GOM\2025 and delete the folder. There is also a folder Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Zeiss\INSPECT\2025, which you might have to delete. Then you should be able to run the installer again. Please run it as administrator. Nanno
-
I have a few questions. Was that template with initial problem edited before or it was original template from ZEISS? Would usage of original template get rid of those problems? Was it working from the begining? I am wondering if there is problem with template or printer settings.
-
Thanks for additional info. E >< will lock 2 rotational DoF, A - B will lock 1 rotation left (and 1 translation, but I don't see that translation will be used anyway), C will lock 1 translation, D will lock the last translation. Datum system looks legit, implementing in Calypso might be a challenge.
-
I would create a Best Fit Bore Pattern of the 6 20 mm diameter bores to datum A. This will create a new Best Fit datum system, which I would use as datum system for coaxiality/concentricity. For profile's datum system, [SL] Straight Line is needed. In other words, you need 4 degrees of freedom locked from B-B pattern (2 rotation and 2 translation), but not the 5th rotation. Where exactly on the part are features tolerated with profile?
-
How to programmatically trigger Zeiss dialog's abort function
[Se...] posted a topic in Customizations & App Development
Hi everyone, I'm working on implementing a stop feature that monitors a PLC signal. When the signal is triggered, I want to automatically stop any running Zeiss software commands. I know there's an abort button in the Zeiss dialog that can stop running commands. I'd like to trigger this abort function programmatically when a PLC signal is detected. Here's my current code for monitoring the PLC signal: def monitor_stop_signal(): while True: try: if read_plc_bool(plc_client, 'Q', 600, 0): print("Stop signal triggered!") """Abort here""" os._exit(0) except Exception as e: print(f"Stop signal monitoring error: {e}") break time.sleep(0.1) # Start monitoring thread monitoring_thread = threading.Thread(target=monitor_stop_signal, daemon=True) monitoring_thread.start() Is there a way to programmatically trigger the dialog's abort function when the PLC signal is detected? How can I call this abort function from my code? Thank you for your help -
Probe Kalifikasyon Programı 2018.pdf
- Last week
-
Hello again guys I have another development on this issue. While the suggested fix did prevent the report from cutting off the dimension from the bottom of the page, now it is eliminating the dimension all together. I also noticed the page number is not being displayed on any of the pages. I attached 2 "snips" of the PiWeb reports from the run screen, and scanned in the same 2 reports as they were printed. Any help on this is greatly appreciated. I only recently got management to purchase Calypso training, still working on the PiWeb training... SSCR-SP-HAM24121822241.pdf SSCR-SP-HAM24121822240.pdf Page 3 print.pdf Page 2 print.pdf