Motion editor/Dynamics simulator
Integrated Development Platform
AIST RTC collection
RT-Components collection by AIST
Tokyo Opensource Robotics Association
Middleware for DAQ (Data Aquisition) by KEK
CCM daemon attached to MICO. ccmd installs components on a single host and manages the deployed components. Therefore, if you want to run components on multiple hosts you must run on each host. The mico-ccmd has ComponentInstallation, AssemblyFactory and ServerActivator interfaces (and services) implemented.
The deployment tool first communicates with mico-ccm, uploads the component implementation file, and launches componentserver on that host. (Do you create a process for each component?) Mico-ccmd is a daemon that normally operates in a permanent background, and does not do anything. If it receives an end signal (SIGINT, Ctrl-C), it terminates all assembly and component servers. Finally, delete all installed component implementations and exit.
Standard options of MICO ORB can also be used. With ORBIIOPAddr, it is possible to assign an ORB to a specific IP address (-ORBIIOPAddr hoge.aist.go.jp:1234 etc.). If the port is known, it is also possible to specify mico-ccmd with the object URL. Since the object key of mico-ccmd is "MicoCCMD"
ccmload is a simple deployment tool that can place a single component. ccmload communicates with the MicoCCM daemon, launches a new component server, and loads new components. Then load the home <home name> from the shared library <library file> into the container. Optionally, you can also register home with name servers. <home name> needs to be the full name of the component home to be deployed. <library name> must be a shared library filename containing the implementation of <home name>. ccmload does not upload the shared library of the implementation, but the file name must be accessible by the MicoCCM daemon.