FlexLogger is aimed for test, validation and verification, and Instrumentation, with the advantage of enabling quick and easy data acquisition without any programming and automatic synchronization. Therefore, before troubleshooting, consider how much programming and editing are you trying to implement? Are there more effective tools available?
Interface Troubleshooting:
When “Exporting Automatically or Manually” to CSV, it is expected to take additional time for the text-based file format. Is it possible to consider alterations to the export?
Within FlexLogger, although it’s not possible to add extra interface functionalities if they are not already programmed in the properties tab, it is possible to change some aspects of the interface by exploring the item panel on the right-hand side of the window.
Specific Examples:
The following example is not intended to be a comprehensive list of all potential problems. However, it can be used to help identify useful search terms by introducing keywords important to the troubleshooting of this topic
- When trying to approach a task that you are not certain is possible in FlexLogger, for example finding a nonlinear scale in channel configuration, consult the manual first. For this example “Calculated Channels” are the best approach.
- Can you create an external LabVIEW code and integrate it into FlexLogger?
- When working between NI Measurement Automation Explorer (MAX) and FlexLogger, there is no direct link between DAQmx tasks and FlexLogger. How has the hardware configuration been set up within FlexLogger?
- For more advanced DAQ functionality, such as sampling, it may be necessary to enlarge the data set and run a post-processing application.
- How much programming and editing are you trying to implement? Are there more effective tools available?