Lines Matching full:ni

9   NI hardware using comedi.  The major reason for this is that the actual
15     increasingly hard to find and the NI-MHDDK (comments in in example code).
34     information is through the proprietary NI-MAX software, which currently only
36     cannot be exported from NI-MAX, except by screenshot.
48   directory are chosen to be consistent with (a) the NI's user level
49   documentation, (b) NI's user-level code, (c) the information as provided by
50   the proprietary NI-MAX software, and (d) the user interface code provided by
92         simplify/clarify signal routing on NI devices, a corresponding
98         Windows software, NI-MAX.  Also, as noted above, this information can
99         only be visually conveyed from NI-MAX to other media.  To make this
101         similar to the naming conventions as presented by NI-MAX.
121      software, NI-MAX.  Also, as noted above, this information can only be
122      visually conveyed from NI-MAX to other media.  This make target creates
125      visual comparison to the NI-MAX "Valid Routes" tables.
128      correct when entire families of NI devices are shown side by side in table
156 plagued NI's previous version of their own proprietary drivers.  Earlier than
157 2003, NI greatly simplified the situation for users by releasing a new API that
160 for most of NI hardware.
164 abstracting much more of the use cases for NI hardware, but allowing users _and_
165 developers to directly refer to NI documentation (user-level, register-level,
166 and the register-level examples of the NI-MHDDK).
174 NI-STC with those naming conventions used here.
179   shows the mapping between the names used in comedi for NI and those names
180   typically used within the NI-STC documentation.
182   (comedi)                      (NI-STC input or output)    (NOTE)