Note if you are not in the project repository, you will receive an error "could not find launcher".
When the gateway starts, the configuration file helps the launcher build the devices and interfaces. After the interfaces are loaded, the program launches the terminal app, where motor controller data points are displayed. In addition depending on your configuration logging will begin immediately on all interfaces.
Logging will take place immediately after the gateway program has started. The track logs are located in Gateway,root/log where each file will contain information from both interfaces. If freshFlogFileOnRun is true, then each time the gateway is started, another track file will appear with a number appended to it, (eg track1, track2 and so on). There are several important steps when it comes to logging and troubleshooting.
To avoid corruption of the log file or the irregularity of recorded data, try not to have abrupt shut downs.
If you are unsure whether the program is logging data, move into the log folder and execute tail -f logfile, replacing log file with the latest log file within the folder. You should see a stream of data pour as the program writes to that file.
Make sure the interfaces are correctly assigned the right controller. Not doing so will make the data incoming unreadable.