Thread: [Openrti-devel] Run of a simple federation with OpenRTI
Brought to you by:
frohlich
From: CHAUDRON Jean-b. <Jea...@is...> - 2016-05-18 19:43:21
|
Dear Mathias, First, I'd like say that I am very impressed per your hard work developing your own RTI, great work. I have been working with CERTI for a long time and now I would like to run some comparison test with OpenRTI. So far, I do have a simple federation running with CERTI (very basic two federates doing ping-pong and measuring latencies, two attributes, Reliable communications, no Time management and HLA13) which I would like to migrate to OpenRTI. OpenRTI is up and running on my laptop and the federation has been compiled and linked properly with the OpenRTI libraries and include. However I am not able to get the federation running... My understanding is that: - the "rtinode" component is acting like the certi rtig component (central component) - for hla13 there is no need to specify path for fed file (hla 13 fom file) neither rtinode IP address (here it's the local one). These are the my steps to try to run the federation (Under Linux Fedora Fc23 64 bits) - Opening three gnome terminals - Setting up correctly the environment variables (LD_LIBRARY_PATH,...) - Calling rtinode without arguments (it will wait for any connection even a local one on the local loopback IP address) - Calling the Fed 1 (Ping) and then Fed 2 (Pong) --> At this step, all is stuck I believe that rtinode is waiting for connection. --> The same application is running with certi Am I missing any steps here? Many thanks for your time, Best regards, Jean-Baptiste |
From: Mathias F. <Mat...@gm...> - 2016-05-19 16:11:43
|
Hi, On Wednesday, May 18, 2016 21:43:02 CHAUDRON Jean-baptiste wrote: > First, I'd like say that I am very impressed per your hard work developing your own RTI, great work. > I have been working with CERTI for a long time and now I would like to run some comparison test with OpenRTI. > > So far, I do have a simple federation running with CERTI (very basic two federates doing ping-pong and measuring latencies, two attributes, Reliable communications, no Time management and HLA13) which I would like to migrate to OpenRTI. > > OpenRTI is up and running on my laptop and the federation has been compiled and linked properly with the OpenRTI libraries and include. However I am not able to get the federation running... > > My understanding is that: > - the "rtinode" component is acting like the certi rtig component (central component) Yes, I do not recall the exact name of the processes that had to be started for certi, but basically rtinode is the server component to connect to. > - for hla13 there is no need to specify path for fed file (hla 13 fom file) neither rtinode IP address (here it's the local one). Well, I think you need to specify a path. The fed file itself is read from the ambassador that creates the federation. So if the fed file is in the local directory of this federate ambassador a local file name should work. > These are the my steps to try to run the federation (Under Linux Fedora Fc23 64 bits) > - Opening three gnome terminals > - Setting up correctly the environment variables (LD_LIBRARY_PATH,...) > - Calling rtinode without arguments (it will wait for any connection even a local one on the local loopback IP address) > - Calling the Fed 1 (Ping) and then Fed 2 (Pong) > > --> At this step, all is stuck I believe that rtinode is waiting for connection. > --> The same application is running with certi OpenRTI needs some information where to connect. The default transport is for process internal threading. So you should be able to specify a federation execution name in an url format like: rti://localhost/FederationExecutionName for create as well as for join. I was several times inclined to make a local network connect the default, but currently it is not. > Many thanks for your time, You are welcome! Greetings Mathias |
From: Jean-Baptiste C. <jea...@is...> - 2016-05-20 11:33:02
|
Dear Matthias, I specified the federation execution name in an url like format (for each federate) as you suggested and now....it works like a charm! :) Super! Many thanks for your help! Best regards, Jean-Baptiste On 05/19/2016 06:11 PM, Mathias Fröhlich wrote: > > Hi, > > On Wednesday, May 18, 2016 21:43:02 CHAUDRON Jean-baptiste wrote: > > > First, I'd like say that I am very impressed per your hard work > developing your own RTI, great work. > > > I have been working with CERTI for a long time and now I would like > to run some comparison test with OpenRTI. > > > > > > So far, I do have a simple federation running with CERTI (very basic > two federates doing ping-pong and measuring latencies, two attributes, > Reliable communications, no Time management and HLA13) which I would > like to migrate to OpenRTI. > > > > > > OpenRTI is up and running on my laptop and the federation has been > compiled and linked properly with the OpenRTI libraries and include. > However I am not able to get the federation running... > > > > > > My understanding is that: > > > - the "rtinode" component is acting like the certi rtig component > (central component) > > Yes, I do not recall the exact name of the processes that had to be > > started for certi, but basically rtinode is the server component to > connect to. > > > - for hla13 there is no need to specify path for fed file (hla 13 > fom file) neither rtinode IP address (here it's the local one). > > Well, I think you need to specify a path. The fed file itself is read > > from the ambassador that creates the federation. So if the fed file is > in the > > local directory of this federate ambassador a local file name should work. > > > These are the my steps to try to run the federation (Under Linux > Fedora Fc23 64 bits) > > > - Opening three gnome terminals > > > - Setting up correctly the environment variables (LD_LIBRARY_PATH,...) > > > - Calling rtinode without arguments (it will wait for any connection > even a local one on the local loopback IP address) > > > - Calling the Fed 1 (Ping) and then Fed 2 (Pong) > > > > > > --> At this step, all is stuck I believe that rtinode is waiting for > connection. > > > --> The same application is running with certi > > OpenRTI needs some information where to connect. > > The default transport is for process internal threading. > > So you should be able to specify a federation > > execution name in an url format like: > > rti://localhost/FederationExecutionName > > for create as well as for join. > > I was several times inclined to make a local network connect the > > default, but currently it is not. > > > Many thanks for your time, > > You are welcome! > > Greetings > > Mathias > |
From: Mathias F. <Mat...@gm...> - 2016-05-20 14:56:06
|
Hi, On Friday, May 20, 2016 13:32:52 Jean-Baptiste Chaudron wrote: > I specified the federation execution name in an url like format (for > each federate) as you suggested and now....it works like a charm! :) > Super! Many thanks for your help! Good to hear! Happy weekend Mathias |