3.2.5 PDA Configuration |
This chapter describes some of the more important configuration fields. Please also refer to the 5 Programmer's API Reference for details on all available configurations.
The PDA configurations class can set all parameters regarding the PDA and connected cards. Currently only a subset of the PDA's UI is supported. The focus is on signal configuration for acquisition and export, visualization options are not configurable through the API yet.
The configurations can be manually changed in the C:\ProgramData\RAYLASE\ProcessDataAnalyzer\Configurations.json file which is loaded at startup of the service. Alternatively, it can be changed from code by getting the current service configuration (GetPdaConfig) or by loading a configurations.json file from a path with LoadPdaConfig.
Configurations descriptionStarting from the outermost configuration message, these sections will try to explain the meaning behind the configurations messages.
GetPdaConfigReply
Returned from a GetPdaConfig call, the GetPdaConfigReply can be seen as root of the C:\ProgramData\RAYLASE\ProcessDataAnalyzer\Configurations.json file. It contains all card configurations as a list of CardConfigs as well as the TriggerConfig.
CardConfig
The card configuration can be repeated for several connected cards and thus contain different configurations. These are mapped to their respective cards by the ConnectionId which is the IP address used to connect to the card. This allows to swap a card and keep its configuration as long as the new card uses the old card's IP address.
Other than that, the CardConfig also contains a list of configured signals (SignalConfigs) , which will be acquired from this card.
SignalConfig
For now, the SignalConfig only sets the TraceDataSignalConfig.
TraceDataSignalConfig
A TraceDataSignalConfig configures, as the name implies, a signal that will be part of the trace data. Here, a main distinction can be made between BuiltInSignals, which are real world signals which can be retrieved from the card (e.g. BisField0RxX) and virtual signals. The latter are a combination of BuiltInSignals and possibly other already existing virtual signals, fused into a virtual signal by a mathematical calculation of CalculationType (e.g. CtVelocity3D could be computed by the received field positions over time).
TriggerConfig
Configure when to start and stop the data acquisition and if different segments should be recorded with labels.
See Also