Important Notes Be sure to read the XData Overview section for important information and notes concerning XData. Commands below marked "[Hidden]" will not appear on the Choose Command drop-down menu unless "Show advanced XData items" is checked: Some XData items have "Start" in their name. For these, XData is applied for all entities that follow until either the corresponding "End" XData is encountered, or the end of the path is hit. XData items that do not have "Start" in them are applied for the entity only, and do not propagate down the path. Also note that XDatas that "Start" something also have a green colored glyph. An important note about XData commands [008], [009], [010], [011], [028], [029], and [033]: even though a part can be rotated in Layout, it does not necessarily mean it is a good idea to do so. Rotation is allowed in Layout only with the assumption that the user is still working on the part and may want to try it. Index of XData Items: Note [Number in brackets] represents the code number used to store the XData item in an OMAX OMX file, which is listed here for ease of reference for those writing software to output OMAX OMX files. Speed and Pause Commands [006] Pause [007] Delay [013] Force Percent Speed [014] Force Absolute Speed Z-Axis Commands [019] Move Z [Requires Motorized Z] Bevel and Tilt Commands Note: Intelli-MAX software automatically compensates for the increased cutting distance required to penetrate the material when cutting a bevel. [017] Tilt Axes: Start tilting by tilt and direction angle [018] [Advanced] Tilt Axes: Start tilting by tilt in X and tilt in Y [A-Jet or Tilt-A-Jet required] [020] Tilt Axes: Start beveling at angle [A-Jet or Tilt-A-Jet required] [021] Tilt Axes: End all XData tilting [A-Jet or Tilt-A-Jet required] [023] Tilt Axes: Set tilt for single entity by tilt and direction angles (for both endpoints) [A-Jet or Tilt-A-Jet required] [024] [Advanced] Tilt Axes: Set tilt for single entity by tilt in X and tilt in Y (for both endpoints) [A-Jet or Tilt-A-Jet required] [025] Tilt Axes: Set bevel angle for single entity [A-Jet or Tilt-A-Jet required] [026] [Hidden] Tilt Axes: Start tilting by a vector [A-Jet or Tilt-A-Jet required] [027] [Hidden] Tilt Axes: Set tilt for single entity by a vector. [A-Jet or Tilt-A-Jet required] [028] [Hidden] Tilt Axes: Set tilt for an entity by defining the focus point of the corners [A-Jet or Tilt-A-Jet required] [029] [Hidden] Tilt Axes: Set Reference for Bottom Point [A-Jet or Tilt-A-Jet required] [032] [Hidden] Tilt Axes: Set the type of taper compensation [033] [Hidden] Tilt Axes: Set tilt for the start of a single entity by defining the bottom point of the corner [A-Jet or Tilt-A-Jet required] Bitstream Commands [034] Bitstream: Insert Bitstream File [035] Bitstream: Insert Latched Output [036] Bitstream: Insert OR mask [037] Bitstream: Insert AND NOT mask [038] Bitstream: Insert any frame Tool Offset Commands [039] [Advanced] Set tool offset value [040] [Advanced] Modify tool offset amount [041] [Advanced] Clear offset overrides Rotary Axis Commands [008] Rotary Axis: Incremental rotate by angle [Requires Rotary Axis] [009] Rotary Axis: Absolute rotate to angle [Requires Rotary Axis] [010] Rotary Axis: Start interpretation of Y as rotation [Requires Rotary Axis] [011] Rotary Axis: End interpretation of Y as rotation [Requires Rotary Axis] Comments and Text Attributes [002] Comment on Entity [016] [Hidden] Show Entity CAD Number. [030], [031] Warnings and Errors: Used internally by Make for "warning" and "error" flagging It is not recommended to use these. Misc. [000] No Data Reserved [001] Reserved for future use [003] Reserved for future use [004] Reserved for future use [005] Reserved for future use [012] Reserved for future use [015] Reserved for future use [022] Reserved for future use [042] Reserved for future use XData Reference in Numerical Order The numbers next to each XData item indicate the code number used to categorize the XData item within the software and OMX file, which is what one would use when generating OMAX files, such as through a post processor or script. (In Layout or Make, one would typically ignore these numbers.) [000] No Data No XData is assigned. This is the default condition for all entities when no other XData item has been assigned. To remove XData from an entity, simply set its XData to be "No Data". [001] [Reserved for future use] [002] Comment on Entity This XData item allows a comment to display on entities in the Layout drawing or tool path. This can be a useful way to convey a message to another user. Note As with any XData item, the user must have XData display enabled in order to see it. [003], [004], [005] [Reserved for future use] [006] Pause If an entity has "Pause" assigned to it, the controller will come to a full stop precisely at the start of the entity, and it's up to the operator to press "Continue" should they wish to. This is useful as a way to put in a programmed stop point for purposes such as re-fixturing the material. The pause will occur at the exact location specified (the starting point of the entity with Pause assigned). If the preceding entity is a traverse and the entity assigned to pause is one which fires the jet, the pause occurs before the jet is fired. Compare this with the Insert Pause command in Make, which is not exact. When a Pause occurs, the jet and other relays will shut off, similar to as if the "Pause" button were pressed. Note Unlike the “Insert pause point here” command in Make, this commanded XData is precise, and will pause at the precise location specified, which is the start of the entity for which this XData item was assigned. Note Using this command does NOT set the “Path Interrupted Home” at the paused location. [007] Delay One can insert up to a 2 second delay where the machine will stop, but the pump, jet, and abrasive on/off states will remain unchanged, meaning if the jet is active, it remains active. Once the specified amount of time has elapsed, the machine resumes its motion along the path. Delays are limited to a maximum of 2 seconds (2000 milliseconds). Delay time is specified in units of milliseconds (1/1000 of a second). [008] Rotary Axis: Incremental rotate by angle [Requires Rotary Axis] Important Note: Paths containing this XData cannot be rotated in XY (about Z) in Make, because it would corrupt the intent of the path to do so. This command causes the Rotary axis to rotate by the specified angle in degrees. The angle is rotated incrementally by the specified amount. Values can be positive or negative: a positive number indicates a rotation where the top of a tube would rotate towards the front of the machine, and a negative number would cause the rotation in the opposite direction. The sign convention follows the Right Hand Rule about the positive X-axis. The entered angle must be between -360 and +360 degrees; however, the advanced user for specialty uses, can override this to "spin" more than 360 degrees by hand-editing the value in the OMX file. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [009] Rotary Axis: Absolute rotate to angle [Requires Rotary Axis] Important Note: Paths containing this XData cannot be rotated in XY (about Z) in Make, because it would corrupt the intent of the path to do so. Rotates the rotary axis to an absolute angle relative to the start of the tool path, regardless of the present angle of the rotary axis. Values can be positive or negative, or zero. Important Note The direction of rotation is the shortest distance required to achieve the desired angle. If you wish to force a particular direction, it is recommended to use the Incremental Rotate by Angle command. As with any commanded motion, be aware of potential collision hazards and plan and verify your paths accordingly. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [010] Rotary Axis: Start interpolation of Y as rotation [Requires Rotary Axis] Important Notes: Paths containing this XData cannot be rotated in XY (about Z) in Make, because it would corrupt the intent of the path to do so. The use of two rotary operations (rotary indexing and rotary interpolation) in the same cutting project is not supported. For rotary axis owners, this command is easy to use relative to traditional tube cutting methods. It simply says, "Take my XY drawing and cut it on the surface of a cylinder with the specified radius". To use it, draw tool paths in the manner familiar for X and Y pathing (or take an existing XY drawing), and then assign this command to the very start of the path and specify the radius of the tube to be cut. When Make reaches this command, it turns the rotary axis instead of moving in Y, causing the pattern to be cut on the surface of the round object. The distance drawn in Y becomes the distance along the circumference of the tube. Be careful to not try cutting a large drawing on a tiny tube. Also, if you wish, you can make things like springs by drawing angular lines whose Y dimension is several circumferences. Tip It is often useful to draw a box in Layout where the width of the box represents the length of the tube to be cut, and the height of the box represents the circumference of the tube. One can then draw inside of this box as a reference, but not include the box as part of the final path. When previewing to the screen in Make, the rotary motions will show as XY motions in an alternate color to help distinguish them from normal XY motions. (See notes below.) It is possible to change the radii, or have multiple radii on the same path. This allows operations such as cutting a non-uniform radius tube. Notes This command will work with nearly any path, including paths that already have tilts and other XData attributes assigned to them. In the context of this command, “radius” is defined as the distance from the center of rotation. By specifying “radius” instead of “diameter”, one is able to machine to the surface of a non-circular work-piece. When cutting paths containing multiple radii, "live view" (the white cross hair that follows the path when the machine is running) may be out of synch with what the machine is actually doing, so one will find the actual nozzle to be a better visual reference in this case. When running paths that contain a radius or multiple radii, it is up to the programmer to ensure proper Z distance. As in all 3D cutting, it is possible to make parts that can't be separated from one another. Think about the full geometry before cutting the part. One may need to make additional cuts in the scrap part to remove it. See the XData Tutorial for an example. See also Live View for information on how previewing is affected by paths with more than one rotary radius specified. If the specified radius is too small (for example, less than 0.01" or 0.254 mm), the path will not compile and a compiler message will display. Negative radii are not supported. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [011] - Rotary Axis: End interpolation of Y as rotation [Requires Rotary Axis] Important Note: Paths containing this XData cannot be rotated in XY (about Z) in Make, because it would corrupt the intent of the path to do so. This is simply a way to restore normal Y motion after using the Start Interpolation of Y as Rotation command. This command is optional, and is assumed whenever an end of tool path is reached. It is useful when you want to rotate to cut something, and then do some XY cutting. It allows you to mix and match. Note If this command is never specified in a path, it will be assumed at the termination of the path. [012] [Reserved for future use] [013] Force Percent Speed This command specifies the nominal speed of the entity by percentage of a given speed. It can range from 0.001% to 20000%. Acceleration and deceleration ramps and machine specific speed limits (maximum cutting speed) will still be applied. The command is applied to a single entity. The percent speed is determined relative to the entity quality type as follows: Quality 1-5, Minimum Taper: Percentage of Separation Speed Etch Quality: Percentage of operator entered Etch Speed Scribe Quality: Percentage of operator entered Scribe Speed Water-Only Quality: Percentage of operator entered Water-Only Speed Traverse and Heads-Up-Traverse Quality: Percentage speed overrides are ignored This command can be useful to help vary etch depths, or for cutting tests, or to more closely match the results of non-OMAX generated OMAX Routed Data file formats that have been imported (see also Non-OMAX ORD files). For cutting entities, if the specified speed is greater than the separation speed, in order to provide a more even depth of cut, the accelerations used for corners will be based on the Newtonian constraints of the machine instead of the cutting model constraints, since you are no longer cutting all the way through. Note This XData command specifies the maximum speed of an entity. Due to machine acceleration limits, short entities may not reach the commanded speed. If the specified speed is greater than the maximum allowed cutting speed (as defined in Advanced / Administrator Setup), it will run at the maximum cutting speed. If the specified speed is greater than the maximum allowed machine speed (as defined in Advanced / Administrator Setup), it will run at the maximum machine speed. [014] Force Absolute Speed Set the speed for the cutting entity to some exact value, overriding whatever Make would have otherwise chosen based on cutting models or otherwise. This has no effect on traverses or Heads Up Traverse entities. This can be useful for running experiments, controlling etch depth, etc. If the specified speed is greater than the separation speed calculated for the given pump, nozzle, and material setup, the accelerations used for corners will be based on the Newtonian constraints of the machine instead of the cutting model constraints, in order to provide a more even depth of cut, since you are no longer fully separating. Because this overrides key features of the OMAX controller, it is generally not recommended to use this for cutting. Use it instead for specialty purposes such as multi-depth etching or cutting tests. Note This XData command specifies the maximum speed of an entity. Due to machine acceleration limits, short entities may not reach the commanded speed. If the specified speed is greater than the maximum allowed cutting speed (as defined in Advanced / Administrator Setup), it will run at the maximum cutting speed. If the specified speed is greater than the maximum allowed machine speed (as defined in Advanced / Administrator Setup), it will run at the maximum machine speed. [015] - [Reserved for future use] [016] - [Hidden] Show Entity CAD Number. Shows the internal CAD Entity Number on the entity. This XData item is not available in normal use and is hidden from the interface in Layout, but can be useful for special purposes such as when debugging a post processor, or writing scripts. It simply causes the entity number to be drawn on top of the entity itself. Note that the entity number is simply the numerical order in which the entity is stored in memory and has little meaning for most purposes. It is not meant to represent the tool path order.  [017] Tilt Axes: Start tilting by tilt and direction angle [A-Jet or Tilt-A-Jet required] Parameters: Tilting Angle, Direction Angle This sets the tilting of the jet by specifying the jet direction and tilt. This is useful for doing things such as cutting holes or slots at an angle when it is desired that the angle is fixed, and while the machine moves around in XY. The tilt angle is the angle between the jet and the machine's negative Z-axis. The sign convention of the tilt angle is always positive. The direction angle is the angle between the positive X-axis and the projection of the jet onto the machine's XY plane. The sign convention of the direction angle follows the right hand rule about the positive Z-axis. This command will override the orientation of adjacent corners of neighboring entities. Tilt Interpolate Orientation is being used. Tip This command is a "Start" command that means "From now until I tell you otherwise, move with the tilt specified". Because of this, it is unnecessary to add multiple "start" commands on individual entities unless you intend to change the angle. For a path with a 45 degree tilt along 10 entities, only one "Start" command is needed, not 10! Example of [017]: Tilt Axes: Start tilting by Tilt and Direction Angle. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [018] [Advanced] Tilt Axes: Start tilting by tilt in X and tilt in Y [A-Jet or Tilt-A-Jet required] Parameters: Tilt in X, Tilt in Y Allows one to set the tilt of the axis by specifying the X and Y components of the tilt. This is useful for doing things such as cutting holes or slots at an angle, where it is desired that the angle is fixed, while the machine moves around in XY. It is an alternate method of setting the head tilt to [017] above. The Tilt in X angle is the angle between the negative Z-axis and the projection of the jet onto the machine's XZ plane. The sign convention of the Tilt in X angle follows the Right Hand Rule about the NEGATIVE Y axis. The Tilt in Y angle is the angle between the negative Z-axis and the projection of the Jet onto the machine's YZ plane. The sign convention of the Tilt in Y angle follows the Right Hand Rule about the POSITIVE X axis. Tilt Interpolate Orientation is being used. This command will override the orientation of the adjacent corners of the neighboring entities. Tip This command is a "Start" command that means "From now until I tell you otherwise, move with the tilt specified". Because of this, it is unnecessary to add multiple "start" commands on individual entities unless you intend to change the angle. For a path with a 45 degree tilt along 10 entities, only one "Start" command is needed, not 10! Example of [018]: Tilt Axes: Start tilting by tilt in X and tilt in Y. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [019] Move Z [Requires Motorized Z] Parameters: Distance, Speed Moves the Z-axis the specified distance vertically (with no horizontal motion). Use a positive value to move the Z up (+Z) and a negative value to move the Z down (-Z). The Z-axis will not automatically return to its original height following a traverse. A Z down negative value must be assigned. Note: Z height can also be set using Motion Preferences. Note: If a speed is not specified or a "0" entered, the speed will remain undefined, and the Z speed will be set to the maximum. Warning! All relays will remain in their present state while the motion is performed, just like for XY motions. On a traverse, the jet will remain OFF and on a cutting entity the jet will remain ON. Moving Z while cutting can cause excessive splash. Warning! Do not use this command in conjunction with the Terrain Follower accessory. Doing so may result in collisions, incompatibilities with the tool path and/or "backup" and "ahead" features, as well as other unwanted behaviors. See also Heads-up Traverse.  [020] - Tilt Axes: Start beveling at angle [A-Jet or Tilt-A-Jet required] Parameters: Bevel Angle Causes the selected and all subsequent entities to be beveled (cut at an angle) with the edge of the material cut at the specified angle in degrees. This command is useful for cutting tapered holes, cones, or similar geometry. The Bevel Angle is a geometrical angle between the machine's negative Z axis and the waterjet cut side of the part. It is positive if the bottom side of the cut is larger than the top. Tilt Interpolate Bevel is being used. Tip This command is a "Start" command that means "From now until I tell you otherwise, move with the bevel specified". Because of this, it is unnecessary to add multiple "start" commands on individual entities unless you intend to change the angle. For a path with a 45 degree bevel along 10 entities, only one "Start" command is needed, not 10! Example of [020]: Tilt Axes: Start beveling at angle See Also: Tilt-A-Jet limits to purposely adding tilt to a part [021] - Tilt Axes: End all XData tilting [A-Jet or Tilt-A-Jet required] Causes all previous “Start tilt…” and “Start Bevel…” commands to turn off. The following entities will be cut according to its specified angles in the OMX file. Caution This command is best used on traverses. To return to zero on a cutting entity, always use the same XData type as used to achieve the angle. Note If this command is never specified in a path, it will be assumed at the termination of the path. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [022] - [Reserved future use] [023] - Tilt Axes: Set tilt for single entity by tilt and direction angles (for both endpoints) [A-Jet or Tilt-A-Jet required] Parameters: Tilting Angle Start, Direction Angle Start, Tilting Angle End, Direction Angle End This command sets the selected entity (or entities) to be tilted by a specific angle and direction. Use this for per-entity control of tilt settings. Note that one can specify the tilt at both the start of the entity, as well as the end of the entity, resulting in some quite complex “twisted” motions in some cases. The orientation of the cutting edge is interpolated in a similar manner as Tilt in X and Tilt in Y. The tilt angle is the angle between the jet and the machine's negative Z-axis. The sign convention of the tilt angle is always positive. The direction angle is the angle between the positive X-axis and the projection of the jet onto the machine's XY plane. The sign convention of the direction angle follows the Right Hand Rule about the positive Z-axis. This command will override the orientation of the adjacent corners of the neighboring entities. Tilt Interpolate Orientation is being used. Example of [023]: Tilt Axes: Set tilt for single entity by Tilt and Direction Angles See Also: Tilt-A-Jet limits to purposely adding tilt to a part [024] - [Advanced] Tilt Axes: Set tilt for single entity by tilt in X and tilt in Y (for both endpoints) [A-Jet or Tilt-A-Jet required] Parameters: Tilt In X Start, Tilt In Y Start, Tilt In X End, Tilt In Y End This command sets the selected entity (or entities) to be tilted by a specific tilt in the X and Y directions. Use it for per-entity control of tilt settings. Note that one can specify the tilt at both the start of the entity, as well as the end of the entity, resulting in some quite complex “twisted” motions in some cases. The Tilt in X angle is the angle between the negative Z-axis and the projection of the Jet onto the machine's XZ plane. The sign convention of the Tilt in X angle follows the Right Hand Rule about the NEGATIVE Y-axis. The Tilt in Y angle is the angle between the negative Z axis and the projection of the jet onto the machine's YZ plane. The sign convention of the Tilt in Y angle follows the Right Hand Rule about the POSITIVE X axis. This command will override the orientation of the adjacent corners of the neighboring entities. Tilt Interpolate Orientation is being used. Example of [024]: Tilt Axes: Set tilt for single entity Note XData keywords can be used with this XData type. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [025] - Tilt Axes: Set bevel angle for single entity [A-Jet or Tilt-A-Jet required] Parameters: Bevel Angle Start, Bevel Angle End This command sets the bevel angle (or “tilt to the side”) for a single entities start and end point. Use it when desired to have per entity control, or per end-point control of an entity. If the adjacent corners are (near) tangential, this command will override the orientation of the adjacent corners of the neighboring entities. Tilt Interpolate Bevel is being used. Note XData keywords can be used with this XData type. Example of [025]: Tilt Axes:Set Bevel Angle for single entity. See Also: Tilt-A-Jet limits to purposely adding tilt to a part  [026] - [Hidden] Tilt Axes: Start tilting by a vector [A-Jet or Tilt-A-Jet required] Parameters: X Component, Y Component, Z Component This command allows one to specify, for this entity and all following, that the tilt angle should be set to a specific vector orientation. This command will override the orientation of the adjacent corners of the neighboring entities. Tilt Interpolate Orientation is being used. Note This command is not visible in the Layout user interface. It is intended to make post processor development easier.  [027] - [Hidden] Tilt Axes: Set tilt for single entity by a vector. [A-Jet or Tilt-A-Jet required] Parameters: X Component Start, Y Component Start, Z Component Start, X Component End, Y Component End, Z Component End This command allows one to specify that for this entity the tilt angle should be set to a specific vector orientation. This command will override the orientation of the adjacent corners of the neighboring entities. Tilt Interpolate Orientation is being used. Note This command is not visible in the Layout user interface. It is intended to make post processor development easier. Note XData keywords can be used with this XData type. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [028] - [Hidden] Tilt Axes: Set tilt for an entity by defining the focus point of the corners. [A-Jet or Tilt-A-Jet required] Important Note: Paths containing this XData cannot be rotated in XY (about Z) in Make, because it would corrupt the intent of the path to do so. Parameters: U Component Start, V Component Start, W Component Start, U Component End, V Component End, W Component End This command generates the corner vector from the difference of the top point [x, y, z] to the focus point [u, v, w]. The focus point is specified relative to the reference point, which typically is ‘Start Path Home’. The reference point can be modified using XData command [029]. If the second point is not assigned, it is assumed that it is the same as the first point. Since the length of the vector is not being used, this command can be used to specify a focus point relative to the reference point. This command will override the orientation of the adjacent corners of the neighboring entities. This command is not visible in the Layout user interface. It is intended to make post processor development easier. Since the start path location can be arbitrarily assigned, and this reference point is relative to the part to be machined, this reference point should be set relative to an entity on the work piece using XDATA type [029]. Tilt Interpolate Orientation is being used. Note XData keywords can be used with this XData type. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [029] - [Hidden] Tilt Axes: Set Reference for Focus/Bottom Point [A-Jet or Tilt-A-Jet required] Important Note: Paths containing this XData cannot be rotated in XY (about Z) in Make, because it would corrupt the intent of the path to do so. Parameters: X Offset, Y Offset, Z Offset The bottom point in XData [028] is defined relative to a reference point. By default, this is the start of the tool path. This command moves the reference point to the start of the entity where it is applied. The offset parameters do move the reference point away from the start point of the entity to the specified relative location. Note This command is not visible in the Layout user interface. It is intended to make post processor development easier. Since the start path location can be arbitrarily assigned, and this reference point is relative to the part to be machined, this reference point should be set relative to an entity on the work piece. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [030], [031] , Used internally by Make for “warning” and “error” flagging It is not recommended to use these. [032] - [Hidden] Set the type of Taper Compensation Parameters: Tapercompensation Type This command changes the type of taper compensation for the following entities. This may be useful to increase precision in some parts of the cutting path and increase speed in others. This command changes the taper compensation type only if your machine has an A-Jet attached and enabled. Machines with the Tilt-A-Jet will not change taper compensation type, nor would it be necessary since, unlike A-Jets, Tilt-A-Jets are not subject to cutting speed penalties when taper compensation is enabled. The options are: -1 = Restore taper compensation back to the value set in Make (see the Cutting Model Optimizations Setup page). 0 = Taper Compensation OFF 1 = Smart Taper Compensation 2 = Intelli-TAPER compensation Note This command is visible when the "Show advanced XData items" option is checked. [033] - [Hidden] Tilt Axes: Set tilt for the start of a single entity by defining the bottom point of the corner [A-Jet or Tilt-A-Jet required] Important Note: Paths containing this XData cannot be rotated in XY (about Z) in Make, because it would corrupt the intent of the path to do so. Parameters: U Component Start, V Component Start, W Component Start, U Component End, V Component End, W Component End This command is very similar to the XDATA type [028]. Instead of a focus point that can be anywhere in space, here the bottom point of the corner is used to define the corner vector. This command generates the corner vector from the difference of the top point [x, y, z] to the bottom point [u, v, w]. The bottom point is specified relative to the reference point, which typically is 'Start Path Home'. The reference point can be modified using XData command [029]. If the second point is not assigned, it is assumed that it is the same as the first point. Since the length of the vector is not being used, this command can be used to specify a focus point relative to the reference point. This command will override the orientation of the adjacent corners of the neighboring entities. This command is not visible in the Layout user interface. It is intended to make post processor development easier. Since the start path location can be arbitrarily assigned, and this reference point is relative to the part to be machined, this reference point should be set relative to an entity on the work piece using XDATA type [029]. Tilt Interpolate Orientation is being used. Example of [033] Tilt Axes: Set tilt for the start of a single entity by defining the bottom point of the corner. See Also: Tilt-A-Jet limits to purposely adding tilt to a part [034] - [Hidden] Bitstream: Insert Bitstream File Parameters: Absolute file path of a bitstream file This command inserts a full bitstream file at the beginning of the assigned entity (after the end event). It is a handy way to insert pre-recorded / pre-calculated bitstreams into your tool paths. This might be used, for example, to insert an Intelli-ETCH pattern into your vector based cutting path, or to insert advanced bitstreams for activating nonstandard hardware, or for research and development purposes, etc. This is an advanced feature. You may need some help from OMAX Technical Support for many uses of this powerful command. See also: Glossary BTS File and Bitstream Stitching [035] - [Hidden] Bitstream: Insert Latched Output Parameters: Number of IO, 1=On/0=off This command inserts a bitstream frame that will turn a Latched Output on or off. The relay will remain in this position until it is overridden by another Latched Output command. Notes This command is not visible in the Layout user interface.  Data keywords can be used with this XData type. [036] - [Hidden] Bitstream: Insert OR mask Parameters: IOword This command inserts a bitstream frame that will mask the Latched Output to turn ON the defined relays. Example: IOword= 256: this is the equivalent of binary (0000000100000000). This example will mask relay number 8 to be ON. Notes This command is not visible in the Layout user interface.  OMAX Tester can be used to determine the bit numbers to use. [037] - [Hidden] Bitstream: Insert AND NOT mask Parameters: IOword This command inserts a bitstream frame that will mask the Latched Output to turn off the defined relays. Example: IOword= 256: this is the equivalent of binary (0000000100000000). This example will mask the relay number 8 to be OFF. Note This command is not visible in the Layout user interface. [038] - [Hidden] Bitstream: Insert any frame Parameters: Setting, Ntime, Ctime This command inserts an arbitrary bitstream frame. This is a highly advanced command and is typically not used by the normal user. It could, for example, be used for future bitstream commands. Note This command is not visible in the Layout user interface. Note 2 When using XData to override the tool offset amount, it is possible to cause blemishes at the lead locations if the leads are shorter than the offset amount. (This is typically an issue only when working with exceptionally large offset amounts.) To avoid this issue, draw your lead in and lead outs such that the ends of them that connect to the traverses are beyond the area where the offset will occur (so draw them longer than you might normally). Note 3 This XData item is only applied when a tool offset other than zero is entered by the operator. If a tool offset of 0 is used, then no offsets, and no offset overrides are used at all. [039] - [Advanced] Set tool offset value Parameters: Tool offset distance Forces the tool offset to the specified amount. This command can be applied only to leads and traverses. Note XDatas are applied at the START of an entity, and for this command, it is a Traverse. Since it applies to the start, it also effects the prior entity because the prior entity must match the desired offset of the entity that you are on. If you have a cut quality entity and then a traverse, and you put this command on the traverse, the preceeding cut will also be affected. It is suggested to use this XData command only when connected to traverses or leads where such modifications will not cause conflicts. If necessary, consider dividing your traverse in half and assign this XData to the second half only. Note 2 When using XData to override the tool offset amount, it is possible to cause blemishes at the lead locations if the leads are shorter than the offset amount. (This is typically an issue only when working with exceptionally large offset amounts.) To avoid this issue, draw your lead in and lead outs such that the ends of them that connect to the traverses are beyond the area where the offset will occur (so draw them longer than you might normally). Note 3 This XData item is only applied when a tool offset other than zero is entered by the operator. If a tool offset of 0 is used, then no offsets, and no offset overrides are used at all. [040] - [Advanced] Modify tool offset amount Parameters: Tool offset distance to add or subtract (if negative) Modifies the tool offset by the specified amount. This command can be applied only to leads and traverses. Note XDatas are applied at the START of an entity, and for this command, it is a Traverse. Since it applies to the start, it also effects the prior entity because the prior entity must match the desired offset of the entity that you are on. If you have a cut quality entity and then a traverse, and you put this command on the traverse, the preceeding cut will also be affected. It is suggested to use this XData command only when connected to traverses or leads where such modifications will not cause conflicts. If necessary, consider dividing your traverse in half and assign this XData to the second half only. Note 2 This XData item is only applied when a tool offset other than zero is entered by the operator. If a tool offset of 0 is used, then no offsets, and no offset overrides are used at all. [041] - [Advanced] Clear offset overrides Parameters: None Removes any changes to the tool offset made by commands [39] and [40]. Note XDatas are applied at the START of an entity, and for this command, it is a Traverse. Since it applies to the start, it also effects the prior entity because the prior entity must match the desired offset of the entity that you are on. If you have a cut quality entity and then a traverse, and you put this command on the traverse, the preceeding cut will also be affected. It is suggested to use this XData command only when connected to traverses or leads where such modifications will not cause conflicts. If necessary, consider dividing your traverse in half and assign this XData to the second half only. [042] and up - [Reserved for future use] Reserved Parametric Shape Keywords for XData XData can be programmed parametrically when making Parametric Shapes, or when crafting .OMX files by hand, etc. There are special key words and considerations when doing this that allow for additional power and capability. Please read "Parametric Programming with XData" for details.