Getting PC-DMIS to read a value from a CSV file

**AndersI** · 01-14-2020, 04:43 AM

Originally posted by kinko View Post

...but I'm fearful that maybe it just isn't possible for PC-DMIS to read anything other than the =(A1-A2)*24.

That's correct. PC-DMIS can only read the text that is actually stored in the file. But you should be able to do the subtraction in PC-DMIS, I'm almost sure there is a thread somewhere here on the forums about that.

**bfire85** · 01-14-2020, 07:55 AM

If you want to do the math in PC-DMIS, I am thinking that the dates would need to change to Julian and the time would need to be converted into minutes. But run your math in a variable first then put that variable in your third write line.

PC-DMIS is not Excel. I'm sure there's a script that would do this. Maybe Kp61dude! has one.

**JEFMAN** · 01-14-2020, 10:36 AM

You can look here :
https://www.pcdmisforum.com/forum/pc...n-basic-script
But comparing two dates is a little complex because months don't have the same length, so a calibration performed the marsh 1st could be 48 hours after the february 28th, on a bisextile year.
You have to create assignments with arrays of days, months...
I'll give it a try, but it's really complex !

**kinko** · 01-14-2020, 10:48 AM

Thank you both for your help. I did find a couple helpful threads. One was "Code for comparing calibration times between probes" by Evan.Smith. The other one was "Parameter set AutoCal" by Rookie. Both were very helpful and seem to work fine. I just thought and hoped that I was on to something that would make this simple and straight forward. If @Kp61dude or someone else has something, awesome. Otherwise, I can go with the suggestions in the two threads that I found and make myself more familiar with that coding.

**kinko** · 01-14-2020, 10:51 AM

Here are the two threads if anyone else is interested.
https://www.pcdmisforum.com/forum/pc...between-probes

https://www.pcdmisforum.com/forum/pc...er-set-autocal

**bfire85** · 01-14-2020, 06:43 PM

This is what I did to make sure the fixture I am using is within calibration, which is on a 6 month (182 day) cycle. I pulled this off the forums here:

https://www.pcdmisforum.com/forum/pc...om-system-date

Code:

ASSIGN/DAY=SYSTEMDATE("dd")
ASSIGN/MONTH=SYSTEMDATE("MM")
ASSIGN/YEAR=SYSTEMDATE("yy")
ASSIGN/LY=0
IF/YEAR==20 OR YEAR==24 OR YEAR==28 OR YEAR==32 OR YEAR==36 OR YEAR==40
ASSIGN/LY=1
END_IF/
IF/MONTH==1
ASSIGN/COUNT=0
ASSIGN/TOTAL_DAYS=COUNT+DAY
END_IF/
ELSE_IF/MONTH==2
ASSIGN/COUNT=31
ASSIGN/TOTAL_DAYS=COUNT+DAY
END_ELSEIF/
ELSE_IF/MONTH==3
ASSIGN/COUNT=59
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==4
ASSIGN/COUNT=90
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==5
ASSIGN/COUNT=120
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==6
ASSIGN/COUNT=151
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==7
ASSIGN/COUNT=181
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==8
ASSIGN/COUNT=212
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==9
ASSIGN/COUNT=243
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==10
ASSIGN/COUNT=273
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==11
ASSIGN/COUNT=304
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ELSE_IF/MONTH==12
ASSIGN/COUNT=334
ASSIGN/TOTAL_DAYS=COUNT+DAY+LY
END_ELSEIF/
ASSIGN/TODAY=STR(YEAR)+TOTAL_DAYS
CAL_READ =FILE/OPEN,C:\Users\Public\Documents\CMM Files\Scripts\Fixture Calibration Trigger.txt,READ
CAL_VAR =FILE/READLINE,CAL_READ,{LINE}
ASSIGN/CAL_DATE=LINE
FILE/CLOSE,CAL_READ,KEEP
IF/CAL_DATE>TODAY
GOTO/SKIP_CAL
END_IF/

--------------------------
PROGRAM CODE
--------------------------

ASSIGN/END_YEAR=STR(YEAR)+365+LY
ASSIGN/YR_DAYS=(365+LY)/2
ASSIGN/MATH=END_YEAR-TODAY
IF/MATH>=YR_DAYS
ASSIGN/ADD_TO=TOTAL_DAYS+182
ASSIGN/NEXT_CAL=STR(YEAR)+STR(ADD_TO)
END_IF/
IF/MATH<YR_DAYS
ASSIGN/DIFF=182-MATH
ASSIGN/ADD_YEAR=YEAR+1
ASSIGN/NEXT_CAL=STR(ADD_YEAR)+STR(DIFF)
END_IF/
COMMENT/REPT,
"NEXT CAL: "+NEXT_CAL
WRITE_CAL =FILE/OPEN,C:\Users\Public\Documents\CMM Files\Scripts\Fixture Calibration Trigger.txt,WRITE
FILE/WRITELINE,WRITE_CAL,NEXT_CAL
FILE/CLOSE,WRITE_CAL,KEEP
IF/FLAT1.OUTTOL==0 AND FLAT2.OUTTOL==0
COMMENT/OPER,NO,FULL SCREEN=NO,AUTO-CONTINUE=YES,TIME DELAY=3,
FIXTURE PASSED INSPECTION
END_IF/
IF/FLAT1.OUTTOL>0 OR FLAT2.OUTTOL>0
COMMENT/OPER,NO,FULL SCREEN=NO,AUTO-CONTINUE=NO,
FIXTURE FAILED INSPECTION. PLEASE SEE CMM PROGRAMMER.
CLICK OK TO CONTINUE OR CANCEL TO STOP INSPECTION.
END_IF/
PRINT/REPORT,EXEC MODE=END,$
TO_FILE=ON,AUTO=1,AUTO OPEN=OFF,$
TO_PRINTER=OFF,COPIES=1,$
TO_DMIS_REPORT=OFF,FILE_OPTION=INDEX,FILENAME=,$
REPORT_THEORETICALS=NONE,REPORT_FEATURE_WITH_DIMEN SIONS=NO,$
TO_EXCEL=OFF,$
PREVIOUS_RUNS=DELETE_INSTANCES

SKIP_CAL =LABEL/

**Kp61dude!** · 01-15-2020, 12:38 PM

I calibrate probes every 2 months, if then bahaha! I would do it just like OP has started.

If calibrating: output information
Normal runs: read information and test/calc, if true prompt for fresh calibration

If you're wanting to put it in a sub, just:
open a new routine and save it as SubroutineLibrary or something meaningful
paste contents in there
encapsulate contents with Subroutine and End Subroutine (this defines a sub, you can have multiple subs in your sub library)
fill in inputs/outputs
viola!

In your main routine:
call sub routine fill in inputs/outputs.
like this

Code:

L3         =CALLSUB/CREATE_POINT_PATTERN,C:\Users\Public\Documents\WAI\PC-DMIS\2015.1\Subroutines\SubroutineLibrary_AutoFeatures.PRG:1.69,-.24,-.05,0,-1,0,,

Call from any and all routines...save yourself the haggle of copy/pasting and perhaps human error.

Getting PC-DMIS to read a value from a CSV file

Getting PC-DMIS to read a value from a CSV file

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Related Topics