...
If the app cannot parse the config file (usually due to a syntax error, or if the file is empty), no data will be displayed in the app:
...
A cause for this will usually be found in the log file, found in the Logs folder within the Trebuchet exe trebuchet_debug folder. The log file will usually indicate the exact location of any syntax errors. Another common error is to mistype the name of a field, resulting in an error message referencing a mis-matched constructor.
The config file itself consists of two sections: ConnectionConfig and TrebuchetApps, which are the Connection Details and the App Configuration respectively.
Example appConfiguration.json file:
Code Block |
---|
{
"ConnectionConfig": {
"DiscoveryIPAddress": "239.69.69.69",
"DiscoveryInterface": "192.168.0.250",
"DiscoveryPublishPeriod": 5000,
"Port": 6317
},
"TrebuchetApps": [
{
"Name": "change this to name you like",
"Description": "A description of Trebuchet App",
"LaunchCommand": "example.exe",
"ExePath": "C:\\Apps\\example.exe",
"MutualExclusiveGroups": [],
"ParameterGroups": [],
"ExecutionEnv": ""
}
]
} |
Connection Details - ConnectionConfig
The first section of an appConfiguration.json file , - ConnectionConfig, instructs the app on how to listen for radar discovery data for the Radar Discovery section. For example:
...
Code Block |
---|
"ConnectionConfig": { "DiscoveryIPAddress": "239.69.69.69", "DiscoveryInterface": "10.77.3.59", "DiscoveryPublishPeriod": 5000, "Port": 6317 } |
App Configuration - TrebuchetApps
Configuration of a single app The second section of an appConfiguration.json file - TrebuchetApps, consists primarily of providing a name, description, app location, and parameters for a the given app. At the top level, an app entry consists of the following fields:
...