The following explanation is based on the environment where OpenRTM-aist is installed to the Windows OS environment by using the msi installer with the default options.
We use the sample component set SimpleIO to check if rtshell was installed correctly.
Use a sample set consisting of the RT components ConsoleIn and ConsoleOut. ConsoleIn is a component that outputs the numerical values input from the console from OutPort, and ConsoleOut is a component that displays the numerical values input to InPort on the console. These are samples to show simple I/O (input/output) operations. It works by connecting from ConsoleIn's OutPort to ConsoleOut's InPort and activating these two components.
Start the sample component.
In the case of Windows 10, enter "Python_Examples" in the "Search here by typing here" on the lower right, and open Explorer in the directory of the startup file of the sample component.
If the component does not start, there are several possible causes.
There are cases where there is a problem with the settings of rtc.conf and it cannot start. Open the Examples\SimpleIO\rtc.conf file under the directory where the above sample startup file is located, and check the settings. For example, if settings such as corba.endpoint/corba.endpoints are mismatched with the host address of the currently running PC, CORBA will terminate abnormally.
Please re-write the line to the following minimum rtc.conf line and try again.
corba.nameservers: localhost
The msi installer provided by openrtm.org includes omniORBpy, but if you choose a custom installation, you can install OpenRTM-aist-Python without installing omniORBpy. Also, if you have installed it manually, you may not have omniORBpy installed, so check if omniORBpy is installed.
The file that starts ConsoleIn and ConsoleOut is
C:\Program Files\OpenRTM-aist\1.2. &Color(blue){x};\Components\Python\Examples\SimpleIO\ConsoleIn.py & br; C:\Program Files\OpenRTM-aist\1.2. &Color(blue){x};\Components\Python\Examples\SimpleIO\ConsoleOut.py
So double click on these files. If it does not start well, the file association is wrong.
There are cases where the startup does not work due to problems with the hostname and the address settings. In that case, if you give omniNames.exe the IP address of the PC you are using, it may work. Set the environment variable OMNIORB_USEHOSTNAME as follows (the example below is assumed that the IP address of the local host is 192.168.0.11).
Variable name (N): OMNIORB_USEHOSTNAME Variable value (V): 192.168.0.11
C: \ Users \ openrtm> rtls -R 127.0.0.1 .: ConsoleIn0.rtc ConsoleOut0.rtc
rtcon /localhost/ConsoleIn0.rtc:out /localhost/ConsoleOut0.rtc:in
rtdeact /localhost/ConsoleIn0.rtc /localhost/ConsoleOut0.rtc
rtexit /localhost/ConsoleIn0.rtc rtexit /localhost/ConsoleOut0.rtc