Use the Advanced VIs to access advanced features for FlexLogger plugin development

Set Plugin Timing VI
Specify the timing configuration for the plugin's Process VI.
Set Plugin Resampling VI
Configure the plugin input resampling. These parameters control how input waveforms are aggregated. Since inputs to a plugin may be from multiple sources running at different rates, some kind of resampling strategy is required. Maximum or Minimum mode pick a rate based on the rate of the inputs mapped to this plugin. Custom rate specifies a fixed rate that the inputs will be resampled to regardless of the rate of the inputs. Block size and drift tolerance are also configurable. Block size determines the minimum amount of overlapping data to wait for until data is passed to the plugin. Drift Tolerance determines the maximum amount of data to save waiting for overlapping data. A larger Drift Tolerance potentially results in more memory usage while a small Drift Tolerance may result in issues aggregating data whose time bases have drifted relative to one another.
Remove Channels VI
Remove channels from the plugin.
Replace Producer Channels VI
Replaces all existing producer channels with a new list of producer channels. This can be helpful for situations where configuration changes in such a way that all channels need to be recreated. This VI should be called conditionally when something about a channel has changed. Calling it every Configure Session.vi or Process.vi run will result in an infinite configuration loop.
Replace Channel Group VI
Replaces all the channels in the specified group with a new set of channels. This VI should be called conditionally when something about a channel has changed. Calling it every Configure Session.vi or Process.vi run will result in an infinite configuration loop.
Update Channels Unit VI
Updates the unit string for a set of channels. This VI will not cause another pass of the Configure Session state.
Get Data from Stream2 VI
This polymorphic VI contains several options for retrieving specfic pieces of data based on a specific unique identifier (either of a channel or parameter). Each individual VI takes a unique identifier and the results of either a setpoint or waveform read.
Remove Parameter VI
Use this VI to remove a parameter by name from the Plugin's collection of top level parameters.
Write Use Immediate Device Dialog VI
Use this VI to change the type of dialog shown at the group level in FlexLogger. An immediate dialog sends all property value changes immediately to the plugin allowing the plugin developer to add dynamic behaviors. An OK/Cancel dialog waits until OK is pressed to send all property value changes as single batch.
Set File Metadata VI
Use this VI to add top level file metadata into the TDMS log file. The parameters will be added to a group matching the display name of this plugin.
Log Event VI
This VI writes an event string into the Alarms and Events channel in the log file. It can be used to make notes from a plugin during test execution.
Write Trace Log VI
Write Message to DebugView. You will need to download and install DebugView from Microsoft Sysinternals. Then run the executable to see the logged messages. This can be helpful when debugging plugins that run as part of FlexLogger. Use the Format Into String.vi to combine several pieces of information into a single string that can be logged. If there is an error on the error in terminal, the error code and string will also be included in the logged message. Note: When running DebugView, you can use the filter to only see messages that meet certain criteria. You can prefix all your debug messages to make it easy to only see these messages in DebugView since other applications may log messages to DebugView as well. Note: Any program that can view messages from OutputDebugString will be able to view these messages. This includes Visual Studio when it attaches to the NationalInstruments.IoDataPef.Engine.exe process under FlexLogger, which is the executable that runs the plug-ins.

Parent topic: Plug-In Development

FlexLogger Plug-In Development Kit API Reference

Log in to get a better experience