Name X

Anxiously awaiting our new license keys.

did you ever get this figured out?  kind of bored and writing a new macro (outside of the regular work type) sounds like fun.  Don't remember off had if the command specifies the tab to which you could write to.  Thinking if so, I could append lines in a text file to get a count for which tab to export to.  Example...if there are no lines in the text file, export to tab 1.  If there are 5 lines, export to tab 6.  Of course, this is entirely dependant on the command.  Just a thought...

My apologies for the delayed response.

Please email me some details and I can discuss with our team.

neat little macro, now if I could just get someone to write that check for a laser scanner...

I was thinking about modifying the barcode on our load tags, so the operator could scan it and pull up the right project for their parts.  Good mistake proofing!

did this help any?

This macro will:
1. create a point
2. read the value of that point
3. write X, Y, and Z to a text file
4. read X, Y, and Z, values from that text file and assign them to X2, Y2, and Z2.

This is just an example of how you would write to a text file and then read from it.  You would need to manually create the text file where you would like it and then assign that path to the file_name variable.  Hope it helps!

version "5.0"
#=======================================================
# ---- InnovMetric Software Inc.
# ---- Module  :    IMInspect
# ---- Version :    12.0.10 ( 12.00.10.5118 )
# ---- Date    :    Thursday, August 23, 2012 - 14:24:06
# ---- Created By:  Jason Reno (Sauder Woodworking Co.)
#-------------------------------------------------------
DECLARE nb_lines
DECLARE x
DECLARE y
DECLARE z
DECLARE x2
DECLARE y2
DECLARE z2
DECLARE file_name "C:\Pointcloud_test.txt"

#Create a dummy point to get values from
FEATURE PRIMITIVE POINT CREATE(10.2,15.2,20.2,"Nominal",,"Test Point")

# Get X, Y, and Z of the dummy point
TREEVIEW PRIMITIVE POINT PROPERTIES POINT GET(x,y,z, "Test Point")

#Write value to a text file
DATA_FILE APPEND LINES($file_name, "$x $y $z")

#Get number of lines in the text file
DATA_FILE PROPERTIES NB_LINES GET("$file_name", nb_lines)

#Read last line in text file and assign those values to a variable.
DATA_FILE READ LINE_FIELD($file_name, $nb_lines, 1, x2,, "On")
DATA_FILE READ LINE_FIELD($file_name, $nb_lines, 2, y2,, "On")
DATA_FILE READ LINE_FIELD($file_name, $nb_lines, 3, z2,, "On")

I have no idea when it comes to scanning.  What I have done is written to an excel file and read values from an excel file, just never in the same macro.  I can try to get a base for you to start with and let you get exactly what you need from that.

Here is what I did with it.  I didn't do a loop to check that the value is 0 or 1, but am doing a check to see that only 1 device is selected.
version "5.0"
#====================================================
# ---- InnovMetric Software Inc.
# ---- Module  :    IMInspect
# ---- Version :    12.0.8 ( 12.00.08.4687 )
# ---- Date    :    Tuesday, June 05, 2012 - 07:29:29
#----------------------------------------------------
DECLARE device_a "Faro Arm"
DECLARE device_a_use
DECLARE device_b "CimCore Arm"
DECLARE device_b_use
DECLARE device_c "PolyWorks Probe Simulator"
DECLARE device_c_use
DECLARE macro_error

MACRO INPUT MULTIPLE_PARAMETERS("Device Selection", "Select a device to use:", {"integer", "  $device_a (0/1)", $device_a_use, "integer", "  $device_b (0/1):", $device_b_use, "integer", "  $device_c (0/1):", $device_c_use}, device_a_use, device_b_use, device_c_use)

MACRO GET_ERROR_STATUS(macro_error)
IF $macro_error == "Error"
    MACRO PAUSE ("Cancel", "Selection Cancelled.")
    MACRO END
ENDIF

IF EXPR_I($device_a_use + $device_b_use + $device_c_use) >= 2
    MACRO PAUSE ("Error.", "Select only 1 Device.")
    MACRO END
ENDIF

IF $device_a_use == 1
    PROBE DEVICE($device_a)
    PROBE DEVICE CONNECT ( "On" )
    MACRO GET_ERROR_STATUS(macro_error)
    IF $macro_error == "Error"
        MACRO PAUSE ("Error", "Could not connect to $device_a.")
    ENDIF
ENDIF

IF $device_b_use == 1
    PROBE DEVICE($device_b)
    PROBE DEVICE CONNECT ( "On" )
    MACRO GET_ERROR_STATUS(macro_error)
    IF $macro_error == "Error"
        MACRO PAUSE ("Error", "Could not connect to $device_b.")
    ENDIF
ENDIF

IF $device_c_use == 1
    PROBE DEVICE($device_c)
    PROBE DEVICE CONNECT ( "On" )
    MACRO GET_ERROR_STATUS(macro_error)
    IF $macro_error == "Error"
        MACRO PAUSE ("Error", "Could not connect to $device_c.")
    ENDIF
ENDIF



Not a problem, I'll post it when I get back to work tomorrow.

I agree, I have been hoping that there would be some radio and dropdown options coming.  I have only been using PW for about a 18 months and that is my only gripe.  With all of the other capabilities, I'm very pleased.  Let me know if you would like the code for this.

How about this?

I wrote this little macro because we kept forgetting to connect to our device(s) before clicking the device properties button to calibrate.  We primarily use FARO arms and we have a few Romer arms, so that is what the macro is written for.  Enjoy!
version "5.0"
#=======================================================
# ---- InnovMetric Software Inc.
# ---- Module  :    IMInspect
# ---- Version :    12.0.6 ( 12.00.06.4483 )
# ---- Date    :    Wednesday, March 14, 2012 - 10:01:54
#-------------------------------------------------------

DECLARE macro_error

PROBE DEVICE ( "Faro Arm" )
PROBE DEVICE CONNECT ("On")

MACRO GET_ERROR_STATUS(macro_error)

IF $macro_error == "Error"
    PROBE DEVICE ( "CimCore Arm" )
    PROBE DEVICE CONNECT ("On")
    MACRO GET_ERROR_STATUS(macro_error)
    IF $macro_error == "Error"
        MACRO PAUSE ("Error", "Could not connect to FARO arm or CimCore arm.")
        MACRO END
    ENDIF
   
ENDIF

PROBE DEVICE PROPERTIES

How partial are you to using radios?  I could do something with a dialogue box where you would enter either 1 or 0.  If interested, let me know which devices to add to the list. Would you want to just select the device or select and connect?

Solution:

DOS prompts must be used in order for this to happen:

SYSTEM ("START EXCEL.EXE ${_QUOTES}Insert path to file here${_QUOTES}")