Lines Matching +full:convert +full:- +full:sample +full:- +full:format
15 increasingly hard to find and the NI-MHDDK (comments in in example code).
22 varying purposes, but the end-user had to gain a knowledge of register
26 programming manuals and vendor-provided documentation are _not_ even
27 close to the same names that are in the end-user documentation.
32 NIDAQmx(-base) c-libraries, nor with register level programming, _nor_
34 information is through the proprietary NI-MAX software, which currently only
36 cannot be exported from NI-MAX, except by screenshot.
41 of signal routing capabilities of National Instruments data-acquisition and
42 control hardware. In order to facilitate the transfer of register-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
51 the user-land comedilib library.
60 collections (i.e. sub-directories) of tables stored in c source files:
62 (a) ni_route_values/ni_[series-label]series.c
84 (b) ni_device_routes/[board-name].c
93 [board-name].c file must be created. This file should reflect the known
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
100 easier, the naming conventions used in the [board-name].c file are
101 similar to the naming conventions as presented by NI-MAX.
108 When adding a new [board-name].c file, be sure to also add in the line in
112 4) Several tools have been included to convert from/to the c file formats.
114 (a) `make csv-files`
115 Creates new csv-files using content of c-files of existing
117 sub-directory.
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.
127 Furthermore, the register-level information is much easier to identify and
129 format. This is made easy by using a file-storage format that can be
135 spreadsheet-like .csv format to c-files that follow the kernel coding
139 (b) `make c-files`
140 Creates new c-files using content of csv sub-directory. These
141 new c-files can be compared to the active content in the
143 (c) `make csv-blank`
150 Build all csv-files, then all new c-files.
162 Comedi already provides such a common interface for data-acquisition and control
165 developers to directly refer to NI documentation (user-level, register-level,
166 and the register-level examples of the NI-MHDDK).
170 --------------------------------------------------------------------------------
172 --------------------------------------------------------------------------------
174 NI-STC with those naming conventions used here.
175 --------------------------------------------------------------------------------
177 Signal sources for most signals-destinations are given a specific naming
180 typically used within the NI-STC documentation.
182 (comedi) (NI-STC input or output) (NOTE)
183 ------------------------------------------------------------------------------
187 NI_AI_SampleClockTimebase AI_SI If internal sample
190 NI_AI_ReferenceTrigger AI_START2_Select for pre-triggered
191 acquisition---not
195 NI_AI_ConvertClockTimebase AI_SI2 If internal convert
229 NI_CtrA(0) G0_A_Select see M-Series user
230 manual (371022K-01)
231 NI_CtrA(1) G1_A_Select see M-Series user
232 manual (371022K-01)
233 NI_CtrB(0) G0_B_Select, up/down see M-Series user
234 manual (371022K-01)
235 NI_CtrB(1) G1_B_Select, up/down see M-Series user
236 manual (371022K-01)
237 NI_CtrZ(0) see M-Series user
238 manual (371022K-01)
239 NI_CtrZ(1) see M-Series user
240 manual (371022K-01)