01-28-2008 10:49 AM
01-28-2008 01:56 PM
01-30-2008 04:00 AM
01-31-2008 04:09 PM
01-31-2008 05:10 PM
02-01-2008 02:42 AM - edited 02-01-2008 02:43 AM
A list is an ordered sequence of items of the same size. Lists are very useful for managing arrays of data when the size of the arrays cannot be known ahead of time.
Important: The lists managed by this class of functions are lists of arbitrary data items. They are not related to the User Interface Library functions which operate on List Boxes and Ring Controls.
02-04-2008 11:28 AM
02-07-2008 03:19 AM
Short answer: nothing! You really don't need to use any ListType variable to handle a listbox: simply manage control items using strings to read/write the labels and simple numeric variables to read/write the associated values, as you are already doing. You can simply remove any reference to this variable without effect to your code (apart removing unmanaged errors in tollbox functions
olivier66 wrote:
Hi, Roberto
Ok I do not understand what you are talking about, when you speak about ListType variables, is this ListType LISTBOX you are talking about.
What should I use instead?
DAQ cards normally have only one clock to handle all the acquisitions, so when you try to start a new acquisition task the system tries to define timing characteristics but it finds the clock already allocated and returns an error. The usual solution is to define a single acquisition task with all your channels and manage acquired data according to your needs. In case your tasks need to have different clocks, one possible solution is oversampling: acquire all inputs to the maximum frequency suitable to meet all of your needs and don't consider the samples that your slower task does not need.
olivier66 wrote:
Moreover, I'd like to know why can't I use multiples analog tasks with different timing or acquisiton type, I'd like to keep my speedtorquetask acquisition and load another task for pressure but the hardware seems to be reserved when I do that.
This is not clear to me: is the error related to a file I/O as you say or related to user interface error as the -4 error states? Or are they two different faults?
olivier66 wrote:
I have an issue with my IO file handle I guess it is because I call it in another file than my main.c file and I receieve the error
Datafilepath is not valid ,
NON-FATAL RUN-TIME ERROR: "Analog inputs.c", line 34, col 5, thread id 0x00000218: Library function error (return value == -4 [0xfffffffc]). Panel, pop-up, or menu bar handle is invalid
olivier66 wrote:
Finally I do not understand why my Digital IO acquisition still doesn't work, I made a digital acquisition on the same scheme of the analog one and when I try to put a square wave with 0 to 5v value on the digital input acquisition nothing seems to be moving.( using eventdetection).