Bitmapped versus Per-Resource Functions

There are two basic types of NI-Motion functions—those that operate on one resource at a time, and those that operate on multiple axes, vector spaces, I/O bits, and so on simultaneously.

Per-resource functions typically send numeric values to, or read numeric values from, the selected axis or resource. They operate identically on each axis or member in the resource family.

In contrast, functions that operate on multiple bits send and return bitmaps, where each bit (axis, vector space, I/O bit, and so on) is represented by one bit in the bitmap.

Some functions set and reset bits in the bitmap using the Must On/Must Off (MOMO) protocol. This tri-state protocol allows you to set/reset one or more bits without affecting the other bits in the bitmap. Refer to any of the MOMO function descriptions for complete information about this protocol.

Bitmapped functions act on all bits simultaneously. Do not use these functions incrementally because each execution completely reconfigures all bits in the bitmap.

Note  Bitmapped functions can only be used for simultaneous action involving axes one through fifteen.