Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>ICAM</strong> <strong>Virtual</strong> <strong>Machine</strong> ® <strong>Virtual</strong> <strong>Machine</strong> Reference, Model Customization<br />
Simulation Macro Variables, <strong>Virtual</strong> <strong>Machine</strong> Variables<br />
$VMPRCOD Probe cycle return code<br />
Type: Numeric, Read/Write<br />
When probing is active (set using the $FMSPROB function) the $VMPRCOD variable will be<br />
updated at the end of each model motion to indicate the status of the probe device (set using the<br />
$FMSPRID function). The following states are defined:<br />
–1 The probe device was already in a triggered state (i.e., already colliding) at the start of<br />
the motion. No probing data has been returned.<br />
0 The probe device was not triggered (i.e., did not collide) during the last motion. No<br />
probing data has been returned.<br />
1 The probe device was triggered (i.e., collided) during the last motion. $VMXFER<br />
contains collision status information.<br />
2 Same as #1 except that the probe device was triggered against 2 or more objects<br />
simultaneously.<br />
$VMXFER Collision/over-travel return code<br />
Type: Numeric, Read/Write<br />
This variable contains collision and over-travel event information resulting from the last model<br />
motion, including collision information resulting from a probe trigger event. $VMXFER is a<br />
sequence of length 7 as follows:<br />
1 The number of separate collision and/or over-travel events that occurred on the last<br />
motion. Zero if there were no collisions or over-travel events.<br />
2 The time at the start of the motion.<br />
3 The time at the end of the motion.<br />
4 The time at which the first collision or over-travel event occurred during the current<br />
motion. If $VMXFER(1)=0, then $VMXFER(4)=$VMXFER(3).<br />
5 The current feed rate in model units per minute or units per revolution. Zero if the motion<br />
was at rapid.<br />
6 The collision event number of a probe trigger, otherwise -1.<br />
7 The collision pair number of a probe trigger, otherwise -1.<br />
When probing is active (set using the $FMSPROB function), and the probe was triggered (i.e.,<br />
$VMPRCOD>0), then information about the object that was touched by the probe can be obtained<br />
by calling:<br />
$FMSPDAT($VMXFER(6),$VMXFER(7))<br />
208 <strong>ICAM</strong> Technologies Corporation – Proprietary