All Activity

wenn ich eine Protokollseite erzeugen möchte, egal welche Vorlage oder Format , steht immer " unbekanntes keyword". Ich kann so auch nicht die Titel-Seite ausfüllen. Ist der Pfad weg bzw was muß ich tun ?

You would need to edit table report template. But as i saw - you have to modify many things, because it's not global for every callout. Like distance, width, TP, profile, ... I don't understand why editing table for displaying K2001 value have to be done on so many categories.

Do you want to measure that "R" only or additional 14° line and the other line tangential to that "R"? I would ignore that formula and go straight to definition of basic features, like circle and lines. Define correct strategy. Now just recall those features into new curve and voila - you have nominals for a curve. One mention for that - to have correct nominals you have to do recall measured points on features without measured points - that will recall nominal points from strategy, otherwise you will create nominals from measured points.

Sorry, I forgot to attach the image of the feature.....

Hello everyone, I don't have much experience with PCM and I can't adjust the curve values to measure a 0.004 surface profile. I've attached a Excel and a reference image. I can't seem to create the curve correctly; it's not respecting the formula values. I hope you can help me edit it properly. Regards. Contours.xls

offtsetCoordinates = readListFile(offsetFile) ballFinderOffsetX = (val(getParameterNamed("offtsetCoordinates",1))/1000) ballFinderOffsetY = (val(getParameterNamed("offtsetCoordinates",2))/1000) ballFinderOffsetZ = (val(getParameterNamed("offtsetCoordinates",3))/1000) coordsys = getParameterNamed("offtsetCoordinates",4)

Hey, May I get help for changing table property from symbol to characters in Scanbox report? I want to change all Ø to "Diameter" in exported csv file. Change to: and also change DN/DT to "Nominal" Thanks

I Forgot about that option. Thank you!

Hey Nanno, yes, in live-Mode you can see a few green points.

Hi Jure, is there a reference point detected in the measuring volume?

Hello everyone, I am looking for a solution. I used the record button to create this code, which is supposed to scan automatically. gom.script.atos.set_acquisition_parameters(measurement_temperature=20.0) GOM_MMT_RETRIES = 10 GOM_MMT_ERROR_CODES = ['MPROJ-0037'] while True : try: gom.script.atos.insert_scan_measurement () except RuntimeError as ex: if GOM_MMT_ERROR_CODES and not ex.args[0] in GOM_MMT_ERROR_CODES : raise GOM_MMT_RETRIES -= 1 if GOM_MMT_RETRIES <= 0 : raise else: break Unfortunately, I get the following error message when I run it automatically: RequestError: MATOS-S032: Cannot check online sensor movement. File .... , line 29, in <module> gom.script.atos.insert_scan_measurement () What could be the reason for this and how can I fix the problem (I am using Zeiss Inspect 2026)? Best regards, Jure Baloh

Hi All Is there a way to limit which folders different users have access to in Calypso? I know you can define the default pathway, but I'm interested in limiting Operators to a single source for program retrieval while granting access for Programmer and Master users to all folders. Thank you

ok ... round about way... most likely a better way but found a solution .... I read the protheadpara file into a listfile, then made a loop looking for the line that had my variable name. the counter variable would be that line minus 1... so i set the same loop again with the exit at the counter minus 1 while setting each line to a variable. in the inspection_end_pcm.txt file... i simply deleted the file, then used addFile with the new variable.... programs now run with no errors. messy but it works.

What exactly ist it that doesn't work with your first code? If I simulate it, I get 0, 0 and -0.1d What exactly did you get and what did you expect instead? I never had any problems reading mixed lists with getParameterNamed()

Do you mean you used a different stylus just for simulation, then wanted to go back to the original used on the live machine? What you could do is to export the stylus from the live machine as a PCF and import it in Planner. This way you don't have a stylus model (SSC), but all the tips with the correct names.

I just scanned a bit of a part today and I'm seeing the same issue as you. The scanned surface looked more solid after a scan in the earlier versions. I even called my supplier to ask about it, but they couldn't say why it was such difference.

Hi, i have a .txt that im reading with readListFile() This is what it contains: With this code: offtsetCoordinates = readListFile(offsetFile) ballFinderOffsetX = (val(getParameterNamed(offtsetCoordinates,1))/1000) ballFinderOffsetY = (val(getParameterNamed(offtsetCoordinates,2))/1000) ballFinderOffsetZ = (val(getParameterNamed(offtsetCoordinates,3))/1000) coordsys = getParameterNamed(offtsetCoordinates,4) I get the two "0" values correctly because i guess they are integers and the rest is just "". I could make the file comma seperated and then use offSetStuff=offsetFile.asFilename.contentsOfEntireFile xOffset = val(strElement(1,",",offSetStuff))) yOffset = val(strElement(2,",",offSetStuff))) zOffset = val(strElement(3,",",offSetStuff))) coordSys = val(strElement(4,",",offSetStuff))) But i dont want that tbh. Is there a way to use getParamteterNamed() for that?

Has anyone else had issues scanning in 2026 with a ScanHawk2? Even after installing the new SP1 it still has issues scanning. I In 2025 with a single pass its working normal but with the same setting and same single pass 2026 will not scan.

Yes, for example using this export: https://techguide.zeiss.com/en/zeiss-inspect-2026/article/cmd_internal_sys_export_gom_xml_by_report_pages_csv.html The export will be limited to the elements/inspections on the report page(s) you select. An alternative would be this export via the the table: ZEISS Quality Tech Guide

Open a blank curve and recall the points from the initial curve(s)

Moin, A hack to write the program runtime to the piWeb database in a ‘visible’ and thus evaluable form: The result element with the following formula returns the number of seconds. This is somewhat vague, as it includes the actual runtime including PiWeb report generation. This is therefore a few seconds longer than ${Qdb.Property("MeasurementDuration")} in the piWeb form. (val(subStr(getRecordHead("durationofrun"),4,5)) * 60)+ val(subStr(getRecordHead("durationofrun"),7,8)) The return value of "durationofrun" is something like hh:mm:ss,?. The function subStr grep out the value of mm , convert is to a integer and multiply with 60. Similar for seconds. Now, it needs the real hack: We do not want to see the "result element" within our PiWeb report. To achieve this, select the test element. It will be executed but not displayed in the log. The runtime is now visibly transferred to the PiWeb database. It can now be exported to Excel. Admittedly, this is not exactly practical either. But it is better than looking through individual logs.

Just select with CTRL key first and last point from those segments - aka 1,500,501,1000,1001,... Also i would consider usage of Spline evaluation than Gauss ( it should be on 2nd tab - Rozšířené ) Zkrátka označíš první a poslední bod segmentu tak aby měl černou šipku - tím se eliminuje tento bod k vyhodnocení.

You can find Calypso Monitor here, change Calypso versions as needed. C:\Program Files (x86)\Zeiss\CALYPSO 7.4\bin\Monitor File name: CALYPSOMonitor.exe

@Leonardo Marcone "I'm not sure if this helps, but you can try using the Piano icon at the top. From there, go to Operator information at CNC startup and click on Select to insert the image. Every time you click on Start CNC, you will find the image under User information on the CNC startup screen. PIANO > OPERATOR INFORMATION AT CNC STARTUP > SELECT."

Moin Sven, Der Calypso Monitor ist für uns keine Option, da dieser ja geschlossen werden kann und NICHT mehr neu startbar ist (CALYPSO 7.4.24) es sei denn man startet CALYPSO komplett neu. Ich benötige einfach die durchschnittliche Ablaufzeit z.B. am Ende einer Produktionsreihe. Genau das Problem mit dem programmierbaren Stopp und der Varianz der Ablaufzeit die dadurch entsteht. Ebenso ist die Zeit wichtig für Automatisierung und zur Berechnung des Messaufwandes. Besonders cool wäre es natürlich die so ermittelte Zeit irgendwie in das Autorun Icon einzublenden. Dann weiß der Kollege gleich ob er schon mal einen frischen Kaffee einschenken kann oder die Messung nicht mal mehr einen Wimpernschlag dauert 🙂 Die Ausgabe auf dem PiWeb Protokoll funktioniert soweit, jedoch kann ich die Ablaufzeit (noch) nicht in der SQL-Datenbank selektieren. Das geht bestimmt irgendwie nur möchte ich dafür nun nicht extra einen 2-Tagessatz PiWeb Spezialisten bezahlen ... Gruß Karsten