Page History

...

The main Lab PC (IP: 192.168.1.249) must be running (with an Apache Server), ideally before the NUCs are turned on.

...

Setting up the NUCs correctly

The NUCs need to be set up properly. They also need to have an automatically starting task running, which looks for new versions of the required files. This crontab task relies on lab_autostart.bash. 

...

The location of the cpm library is always set using LD_LIBRARY_PATH in the local terminal - you do not need to take care of this in your program, as long as you have linked the library properly in your build script.

Integrated error checking

IDL-Datatype for error checking

The following data type is used to check for NUC-crashes.

struct HLCHello {
    string source_id; //To find out where the msg came from and to not answer to own msg

    boolean script_running; //If true, a Matlab / C++ session is still running
    boolean middleware_running; //If true, a Middleware session is still running
};

Explanation:

Online-indicators for NUCs

...

• You are using the wrong domain ID (DDS) for the LCC. If LCC and NUCs are not within the same DDS domain, they cannot discover each other. Please check which ID you need to use.
• Packages are missing on the NUCs. In this case, upload packages are missing on the main PC or the NUCs have not been set up correctly (e.g. the autostart task, see requirements)
• The NUCs or your PC are not connected to the same network
• You are not using the main Lab PC (which is recommended for remote deployment)
• The NUCs crashed

Crash checks for your programs

As soon as you actually deploy your programs, and after the scripts have been uploaded, the LCC also starts checking if their corresponding tmux sessions (middleware and script) are still running. Errors are reported in the UI if that it not the case anymore (e.g. with a popup).