All Activity
- Past hour
-
Thank you. I did actually figure it out after I posted that.
- Today
-
[ch...] joined the community -
[Fi...] joined the community - Yesterday
-
[Ge...] joined the community -
[El...] joined the community -
I am not catching your intents here. I've found you can use MIN and MAX point flag as a measurable point. This way i am using to get depth of a part marking ( via flatness ). Then just projected distance to that plane. Also you can use user defined evaluation, where you can use this point as a variable.
-
The Contour completion, is so you don't have to do the old method of Ctrl+ click all of the sections. You select the first segment, click on Contour completion, then tell the software if you want a Curve or 3d Curve.
-
Please help. The probe "nothing" has been entered in the machine configuration or the probe "nothing" has been recognized by the control.
[Ja...] replied to [Ra...] 's topic in General
That might be the same problem I had posted about a while ago. -
[PE...] joined the community -
I didn't see a change when trying that refactored version of the script. I feel that there may be something else I'm missing so I decided to look at other files within the program directory. I am currently reviewing the "startfile". Comparing two working programs vs my single non-working one. The working programs each have additional user defined fields at the end of the list. (u_NewVariable6 and u_NewVar BPQ449) Strangely everything else seems to match up with the exception of one of the working copies being TRUE for pdfExport and FALSE for protocolHead. I basically have different settings for all three programs, but I think the user defined fields may be a tell. I do not see these within the programs themselves though. I seem to recall an INI file is needed for that sort of thing.
-
Any possible way to use said min/max points for subsequent calculations?
-
First time I've ever seen something like that. I would probably just keep taking off components one by one to try and isolate the problem child. One stylus off, other stylus off, knuckle off, etc. If it keeps alarming when completely dissasembled, maybe it has something to do with the qualification? Very shocked that changing the adapter plate and rack port didn't help.
-
[An...] joined the community -
@Don M. Try this to fix your filepath to accept the CMM variable correctly (you currently show bpq473RunTracker.txt) cmm="000000" cmm=getRecordHead("dmesn") selectCase cmm case "810021" cmm="BPQ449" case "810475" cmm="BPQ472" case "810480" cmm="BPQ474" caseElse cmm="000000" endSelect read=readListFile(getActualInspectionDir()+"\startfile").asArray.asString Speed=mid((strElement(40,"'",read)),7,10) SpeedStr="Run Speed; "+Speed+" mm/s" StartTime=getRecordHead("time") StartTimeStr="Measurement Start Time; "+StartTime filePath="\\\\nos\\data\\Gear_Lab_Zeiss_Output\\Run_Trackers\\" + cmm + "\\RunTracker.txt" addToFile(filePath,("Measurement Plan Name; "+getRecordHead("planid"))) addToFile(filePath,("Operation Number; "+getRecordHead("u_OpNum"))) addToFile(filePath,("Start Date; "+getRecordHead("date"))) addToFile(filePath,SpeedStr) addToFile(filePath,StartTimeStr) This assumes these folders already exist - \\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\BPQ449\ \\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\BPQ472\ \\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\BPQ474\ \\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\000000\ This version establishes all your variables before writing anything to a file, and should correctly pass the variable "cmm" into the file path.
-
Here is the original script. I also re-ran this script and it gives me the same result after removing the local path. Program runs, no errors, but files are not saved where they should be. read=readListFile(getActualInspectionDir()+"\startfile").asArray.asString Speed=mid((strElement(40,"'",read)),7,10) SpeedStr="Run Speed; "+Speed+" mm/s" StartTime=getRecordHead("time") StartTimeStr="Measurement Start Time; "+StartTime addToFile(("\\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\bpq473RunTracker.txt"),("Measurement Plan Name; "+getRecordHead("planid"))) addToFile(("\\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\bpq473RunTracker.txt"),("Operation Number; "+getRecordHead("u_OpNum"))) addToFile(("\\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\bpq473RunTracker.txt"),("Start Date; "+getRecordHead("date"))) addToFile(("\\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\bpq473RunTracker.txt"),SpeedStr) addToFile(("\\nos\data\Gear_Lab_Zeiss_Output\Run_Trackers\bpq473RunTracker.txt"),StartTimeStr) cmm=getRecordHead("dmesn") if cmm=="810021" then cmm="BPQ449" endif if cmm=="810475" then cmm="BPQ472" endif if cmm=="810481" then cmm="BPQ473" endif if cmm=="810480" then cmm="BPQ474" endif
-
@Don M. Is it possible for you to paste your inspection_PCM file contents here (remove any sensitive information)?
-
The filepath was set for both global and local. I've removed the pathing for the local settings and Calypso seemed to work correctly, no PCM error and the PiWeb report populated afterwards. The issue I have now is, Calypso straight up ignored the global file path location and reverted to the default settings in (Extras>Settings>Environment>Paths).
-
cmmAct=getRecordHead("dmesn") cmm="" selectCase cmmAct case "810021" cmm="BPQ449" case "810475" cmm="BPQ472" case "810480" cmm="BPQ474" caseElse cmm="000000" endSelect
-
@Don M. Is this filepath set in your global file, or in the local program? It looks like something in this program is triggering an output before "cmm" is defined. This gives you the error. Yup, that confirms it. In your global text file, move your case logic to the very top. This sets the variable from the very beginning, before anything begins to output. Put this at the top before anything happens. cmm=“000000” selectCase getRecordHead("dmesn") case "810021" cmm="BPQ449" case "810475" cmm="BPQ472" case "810480" cmm="BPQ474" caseElse cmm="000000" endSelect
-
I've tried to use the mapped address, but Calypso didn't seem to like that. Maybe I'll give it some more testing. More food for thought. We are usually outputting the default report, measuring points and a PiWeb report. All with the same file path and naming convention. I decided to remove measuring points from the list and while I still receive a PCM error, it no longer shows the pcm script as the culprit. The program also generates the piweb report which it previously didn't do. Something strange is afoot.
-
Ahhhh. Progress. You have to create an Element Group from the Points first.
-
I've had issues using raw network paths - instead I prefer to use mapped network paths instead.
-
It appears that Calypso defaults the cmm number to either 9999 or 000000 if it does not find a match case in the script. I did not see a local copy of the script in the program folder, however, the program is responding to changes I make to the global pcm script (ex. message(cmm)). I just can't figure out why the process seems to work on one program and not another given everything appears to be set the same way. Here is the file path in question as well; "\\NOS\Data\Gear_Lab_Zeiss_Output\"+cmm+"\"+getRecordHead("planid")+"\"+getRecordHead("order")+" "+getRecordHead("date")+"\"+"Part_"+getRecordHead("partnbinc")+"_Time_"+getRecordHead("time")+".txt"
-
In Calypso this would be super straightforward. 😞 Either way. I need to measure (6) points and then have the software pull the min/max points, so that those points can be used for subsequent actions. I see that there is a Minimum and Maximum inside of Inspection - Check Dimensions - Positions - Check Y, but I'm unable to get these to work.
-
@Don M. Open the suspect measurement program folder, and look for a local copy of the inspection_start_pcm file. This could be overriding the global file, so no matter what you do to the global file it will never work. Also, @Henrik Lindahl's snippet is the one to use. It is cleaner, it scales, and will always return something (000000), avoiding an error.
-
[Ju...] joined the community -
@Don M. Something is missing here. Where in your inspection_start_PCM file does it address the offline seat (000000)? The PCM you showed us only addresses online seats.
-
It shows 000000
-
Thank Henrik. I seem to get the same error message stating the cmm is not defined even with that updated script.
-
@Don M. In your troublesome program, what does this output? cmm=getRecordHead("dmesn") message(cmm)
-
A little unsure about the syntax but selectCase will help you. The correct syntax might be case is "810021" for each case-row the thing is the caseElse that will handle everything else and never give cmm undefined. selectCase getRecordHead("dmesn") case "810021" cmm="BPQ449" case "810475" cmm="BPQ472" case "810480" cmm="BPQ474" caseElse cmm="000000" endSelect
-
Yes measured with a 3mm stylus.
