08-22-2012 02:00 PM
With the ethernet-based FieldPoint I/O we used previously you could run MAX to examine the state of all the I/O while it was being accessed by a running application. This was very handy for troubleshooting.
With the CompactDAQ system it seems like you're prevented from doing that. Or at least the method isn't as obvious and easy to find as it is with the FieldPoint.
Am I missing something or is this just a limitation of the USB-based platform?
Solved! Go to Solution.
08-22-2012 03:48 PM
If you're using the DAQmx I/O Server to do FieldPoint-style I/O with your cDAQ modules and LabVIEW network-published variables, you can monitor your variables using NI Distributed System Manager. However, note that the DAQmx I/O Server does not work with modules that do not support on-demand timing (single point).
Otherwise, there is no direct equivalent, but NI I/O Trace is useful for monitoring which DAQmx API functions are called.
Brad
08-22-2012 04:06 PM
Ok, thanks.
Maybe we'll just have to design a panel in the main app that can be used to view this sort of information.