Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add RTT update interval.

Script

...

Output Folder

Scripts that you have started from within the LCC (as well as the middleware) are managed using tmux sessions (which is similar to screen).

...

Info
titleRemote

On HLCs, the same folder exists (for the guest user), also at .../software/../lcc_script_logs. It gets deleted and recreated (including its contents) every time a new remote simulation is started.

...

Further Log-

...

Zusätzlich zu obigem Output erzeugt der CPM Logger mit jeder Ausführung Log-Dateien mit dem Namen Log_#Datum_#Uhrzeit.csv. Diese werden im selben Ordner erstellt, in dem das LCC aufgerufen wurde. 

...

Files

Additionally to the ouput mentioned above, the CPM Logger creates log files with the name Log_#Date_#Time.csv for each execution. These are created in the folder from which the LCC was called.

You can also find Logs of the LCC child there, which takes care of calling external programs. These logs are called Log_child_process_#Datum#Date_#Uhrzeit#Time.csv und beinhalten ausschließlich Fehlermeldungen für schwerwiegende Fehler. Sie werden auch in der Kommandozeile ausgegeben, sind jedoch hier auch nach bspw einem Absturz des LCC zu sehen (falls es während der Laufzeit zu Fehlern im Child kam). They only include serious error messages, which can also be seen in the command line. In case of a crash of the LCC (e.g. due to errors occuring in the LCC child during runtime), you may only see these errors in the log files though.

Crash Checker

Most scripts started by the LCC run in tmux sessions (for more information, see aboveScript Output Folder). These sessions have distinct names.

...

Remote Deployment

Take a look at this page. The crash checker also monitors running tmux sessions on the NUCs, if they have been deployed and the simulation is still running.

...

The LCC regularly sends RTT measurement requests as long as no simulation is running (to prevent network overload). The RTT measurement gets updated at least every 2.5 seconds and at most every 0.5 s, depending on the time the longest RTT message takes to get received.

These messages are received by different participants, which can send an answer to this request. It consists of their source_id (e.g. vehicle or hlc), and additional information to make sure that the answer is up-to-date etc.

...