[OSPL-Dev] Communicating with applications using RTI DDS

Discussion:

Tyson Marchuk

2010-08-20 18:43:49 UTC

Hello,

I'm looking into the use of DDS and have read that there is
interoperability between RTI DDS and OpenSplice DDS using DDSI/RTPS but
the information on how to do this seems to be scarce. Specifically I
don't know how to setup OpenSplice DDS to use the same Domain as RTI
DDS. From what I've read it seems like I need to use the ospl_ddsi.xml
example configuration given as a starting point but there doesn't seem
to be any documentation on how the DDSIService settings map to the
integer domain IDs used by RTI DDS so I have a RTI DDS application
using, for example, Domain ID = 232, but I don't know what needs to be
changed in the ospl_ddsi.xml file so that OpenSplice DDS talks on the
same Domain.

I've noticed that there appears to be an upcoming new ISO C++ PSM for
OpenSplice DDS which uses integer domain IDs but can't find a link to
get this version of OpenSplice DDS (perhaps it's only available
internally for now or via the source repository?)

If anyone has a link to any documentation or examples of how to get
these two products to communicate that would be very helpful.

Thank you,
-Tyson

Tyson Marchuk

2010-08-23 21:30:03 UTC

Permalink

I've done some more looking into this and it appears that RTI is
following the default values specified in the DDSI/RTPS specification
(2.1 June 2008.) There it is specified that the ports should default to
the following to enable interoperability:
Discovery ports:
Multicast = PB + DG * domainId + d0
Unicast = PB + DG * domainId + d1 + PG * participantId
User ports:
Multicast = PB + DG * domainId + d2
Unicast = PB + DG * domainId + d3 + PG * participantId

The default values for the constants are given as:
PB = 7400
DG = 250
PG = 2
d0 = 0
d1 = 10
d2 = 1
d3 = 11

Staring up RTI DDS with domainId = 232 binds to 65400, 65410, and 65411
so I assume it's setting up the multicast and unicast discovery ports
(participantId = 0) and connecting with a unicast data port
(participantId = 0) although I'm not sure.

So I guess I just need to figure out how the config files for OpenSplice
work. Is there an XML schema or documentation available for this?

Thanks,
-Tyson

Post by Tyson Marchuk
Hello,
I'm looking into the use of DDS and have read that there is
interoperability between RTI DDS and OpenSplice DDS using DDSI/RTPS
but the information on how to do this seems to be scarce. Specifically
I don't know how to setup OpenSplice DDS to use the same Domain as RTI
DDS. From what I've read it seems like I need to use the ospl_ddsi.xml
example configuration given as a starting point but there doesn't seem
to be any documentation on how the DDSIService settings map to the
integer domain IDs used by RTI DDS so I have a RTI DDS application
using, for example, Domain ID = 232, but I don't know what needs to be
changed in the ospl_ddsi.xml file so that OpenSplice DDS talks on the
same Domain.
I've noticed that there appears to be an upcoming new ISO C++ PSM for
OpenSplice DDS which uses integer domain IDs but can't find a link to
get this version of OpenSplice DDS (perhaps it's only available
internally for now or via the source repository?)
If anyone has a link to any documentation or examples of how to get
these two products to communicate that would be very helpful.
Thank you,
-Tyson
_______________________________________________
OpenSplice DDS Developer Mailing List
Developer at opensplice.org
Subscribe / Unsubscribe
http://www.opensplice.org/mailman/listinfo/developer

Hans van't Hag

2010-08-25 11:50:06 UTC

Permalink

Hi Tyson

The provided example configuration file 'ospl_ddsi.xml' configures the
ports for 'default' connectivity with RTI using multicast discovery for
domain_ID 0 (i.e. port-nr 7400). The user-ports will be discovered then
dynamically.

So for other domains, you'll have to set the discoery-portNr accordingly

Regardsx,
Hans

Hans van 't Hag
OpenSplice DDS Product Manager
PrismTech Netherlands
Email: hans.vanthag at prismtech.com
Tel: +31742472572
Fax: +31742472571
Gsm: +31624654078

PrismTech is a global leader in standards-based, performance-critical
middleware. Our products enable our OEM, Systems Integrator, and End User
customers to build and optimize high-performance systems primarily for
Mil/Aero, Communications, Industrial, and Financial Markets.

-----Original Message-----
From: developer-bounces at opensplice.org
[mailto:developer-bounces at opensplice.org] On Behalf Of Tyson Marchuk
Sent: Monday, August 23, 2010 11:30 PM
To: developer at opensplice.org
Subject: Re: [OSPL-Dev] Communicating with applications using RTI DDS

I've done some more looking into this and it appears that RTI is
following the default values specified in the DDSI/RTPS specification
(2.1 June 2008.) There it is specified that the ports should default to
the following to enable interoperability:
Discovery ports:
Multicast = PB + DG * domainId + d0
Unicast = PB + DG * domainId + d1 + PG * participantId
User ports:
Multicast = PB + DG * domainId + d2
Unicast = PB + DG * domainId + d3 + PG * participantId

The default values for the constants are given as:
PB = 7400
DG = 250
PG = 2
d0 = 0
d1 = 10
d2 = 1
d3 = 11

Staring up RTI DDS with domainId = 232 binds to 65400, 65410, and 65411
so I assume it's setting up the multicast and unicast discovery ports
(participantId = 0) and connecting with a unicast data port
(participantId = 0) although I'm not sure.

So I guess I just need to figure out how the config files for OpenSplice
work. Is there an XML schema or documentation available for this?

Thanks,
-Tyson

Tyson Marchuk

2010-08-25 14:32:19 UTC

Permalink

Thanks Hans. So the OpenSplice/DDSIService/Channels/Channel/PortNr
element then isn't required? Does it override the port used if provided?

Thanks,
-Tyson

Post by Hans van't Hag
Hi Tyson
The provided example configuration file 'ospl_ddsi.xml' configures the
ports for 'default' connectivity with RTI using multicast discovery for
domain_ID 0 (i.e. port-nr 7400). The user-ports will be discovered then
dynamically.
So for other domains, you'll have to set the discoery-portNr accordingly
Regardsx,
Hans
Hans van 't Hag
OpenSplice DDS Product Manager
PrismTech Netherlands
Email: hans.vanthag at prismtech.com
Tel: +31742472572
Fax: +31742472571
Gsm: +31624654078
PrismTech is a global leader in standards-based, performance-critical
middleware. Our products enable our OEM, Systems Integrator, and End User
customers to build and optimize high-performance systems primarily for
Mil/Aero, Communications, Industrial, and Financial Markets.
-----Original Message-----
From: developer-bounces at opensplice.org
[mailto:developer-bounces at opensplice.org] On Behalf Of Tyson Marchuk
Sent: Monday, August 23, 2010 11:30 PM
To: developer at opensplice.org
Subject: Re: [OSPL-Dev] Communicating with applications using RTI DDS
I've done some more looking into this and it appears that RTI is
following the default values specified in the DDSI/RTPS specification
(2.1 June 2008.) There it is specified that the ports should default to
Multicast = PB + DG * domainId + d0
Unicast = PB + DG * domainId + d1 + PG * participantId
Multicast = PB + DG * domainId + d2
Unicast = PB + DG * domainId + d3 + PG * participantId
PB = 7400
DG = 250
PG = 2
d0 = 0
d1 = 10
d2 = 1
d3 = 11
Staring up RTI DDS with domainId = 232 binds to 65400, 65410, and 65411
so I assume it's setting up the multicast and unicast discovery ports
(participantId = 0) and connecting with a unicast data port
(participantId = 0) although I'm not sure.
So I guess I just need to figure out how the config files for OpenSplice
work. Is there an XML schema or documentation available for this?
Thanks,
-Tyson

_______________________________________________
OpenSplice DDS Developer Mailing List
Developer at opensplice.org
Subscribe / Unsubscribe
http://www.opensplice.org/mailman/listinfo/developer

Hans van't Hag

2010-08-27 11:57:28 UTC

Permalink

Hi Tyson,

The channel portnumbers must be specified as they are required for any
communication over those channel(s). It's just that the port-number values
themselves are 'discovered' by other/remote DDSI nodes that all use a
'standardized' discovery-portnumber to advertise their respective
'locators' (that include the configured port-numbers as part of this
'advertisement')

Regards,
Hans

Hans van 't Hag
OpenSplice DDS Product Manager
PrismTech Netherlands
Email: hans.vanthag at prismtech.com
Tel: +31742472572
Fax: +31742472571
Gsm: +31624654078

PrismTech is a global leader in standards-based, performance-critical
middleware. Our products enable our OEM, Systems Integrator, and End User
customers to build and optimize high-performance systems primarily for
Mil/Aero, Communications, Industrial, and Financial Markets.

-----Original Message-----
From: developer-bounces at opensplice.org
[mailto:developer-bounces at opensplice.org] On Behalf Of Tyson Marchuk
Sent: Wednesday, August 25, 2010 4:32 PM
To: OpenSplice DDS Developer Mailing List
Subject: Re: [OSPL-Dev] Communicating with applications using RTI DDS

Thanks Hans. So the OpenSplice/DDSIService/Channels/Channel/PortNr
element then isn't required? Does it override the port used if provided?

Thanks,
-Tyson

_______________________________________________
OpenSplice DDS Developer Mailing List
Developer at opensplice.org
Subscribe / Unsubscribe
http://www.opensplice.org/mailman/listinfo/developer

Tyson Marchuk

2010-08-27 19:34:29 UTC

Permalink

Thanks Hans.

I must be doing something wrong with the OpenSplice DDSI XML
configuration file. I've attached an example one I've been using. I
wrote a test program using OpenSplice DDS and one using RTI DDS. They
both can publish/subscribe to themselves but I don't see them
communicating between each other even though they're using the same
topic name and passing the same data structure on that topic (I've
included the IDL file used for the data structure as well.)

In terms of the configuration file I've tried adding channels for ports
65410, 65411, 65412 and for having a single channel and changing the
port but it doesn't seem to make any difference. Removing all of the
channels causes my OpenSplice DDS example program to hang fairly hard so
I'm guessing that's not the answer.

In terms of the RTI example I'm just passing DomainId = 232 which when I
run it alone opens ports 65400, 65410, and 65411 and can then
communicate with itself.

Any pointers you can provide would be great. If you want I can zip and
attach all the other source for the two examples but the OpenSplice one
is fairly bare bones and simple. The RTI one is using Qt for a GUI front
end but I can make one comparable to the OpenSplice one fairly easily if
it will help.

Thanks,
-Tyson

Post by Hans van't Hag
Hi Tyson,
The channel portnumbers must be specified as they are required for any
communication over those channel(s). It's just that the port-number values
themselves are 'discovered' by other/remote DDSI nodes that all use a
'standardized' discovery-portnumber to advertise their respective
'locators' (that include the configured port-numbers as part of this
'advertisement')
Regards,
Hans
Hans van 't Hag
OpenSplice DDS Product Manager
PrismTech Netherlands
Email: hans.vanthag at prismtech.com
Tel: +31742472572
Fax: +31742472571
Gsm: +31624654078
PrismTech is a global leader in standards-based, performance-critical
middleware. Our products enable our OEM, Systems Integrator, and End User
customers to build and optimize high-performance systems primarily for
Mil/Aero, Communications, Industrial, and Financial Markets.
-----Original Message-----
From: developer-bounces at opensplice.org
[mailto:developer-bounces at opensplice.org] On Behalf Of Tyson Marchuk
Sent: Wednesday, August 25, 2010 4:32 PM
To: OpenSplice DDS Developer Mailing List
Subject: Re: [OSPL-Dev] Communicating with applications using RTI DDS
Thanks Hans. So the OpenSplice/DDSIService/Channels/Channel/PortNr
element then isn't required? Does it override the port used if provided?
Thanks,
-Tyson

User

Post by Hans van't Hag
customers to build and optimize high-performance systems primarily for
Mil/Aero, Communications, Industrial, and Financial Markets.
-----Original Message-----
From: developer-bounces at opensplice.org
[mailto:developer-bounces at opensplice.org] On Behalf Of Tyson Marchuk
Sent: Monday, August 23, 2010 11:30 PM
To: developer at opensplice.org
Subject: Re: [OSPL-Dev] Communicating with applications using RTI DDS
I've done some more looking into this and it appears that RTI is
following the default values specified in the DDSI/RTPS specification
(2.1 June 2008.) There it is specified that the ports should default to
Multicast = PB + DG * domainId + d0
Unicast = PB + DG * domainId + d1 + PG * participantId
Multicast = PB + DG * domainId + d2
Unicast = PB + DG * domainId + d3 + PG * participantId
PB = 7400
DG = 250
PG = 2
d0 = 0
d1 = 10
d2 = 1
d3 = 11
Staring up RTI DDS with domainId = 232 binds to 65400, 65410, and 65411
so I assume it's setting up the multicast and unicast discovery ports
(participantId = 0) and connecting with a unicast data port
(participantId = 0) although I'm not sure.
So I guess I just need to figure out how the config files for OpenSplice
work. Is there an XML schema or documentation available for this?
Thanks,
-Tyson

_______________________________________________
OpenSplice DDS Developer Mailing List
Developer at opensplice.org
Subscribe / Unsubscribe
http://www.opensplice.org/mailman/listinfo/developer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ospl_ddsi_config.xml
Type: text/xml
Size: 978 bytes
Desc: not available
URL: <http://dev.opensplice.org/pipermail/developer/attachments/20100827/107041ba/attachment.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: VehicleTypes.idl
URL: <http://dev.opensplice.org/pipermail/developer/attachments/20100827/107041ba/attachment.txt>

Tyson Marchuk

2010-11-08 22:16:30 UTC

Permalink

Just thought I'd reply to the list in case anyone stumbles across this
while searching the web.

I was able to get a demo app running OpenSplice 5.2.0 talking with a
demo app running RTI DDS 4.5c. It turns out that for whatever reason the
OpenSplice daemon (ospl) has to be started after the RTI application for
this to work and you have to choose a port that isn't in use at the time
it starts (not sure why it can't auto-choose one for the next
participant ID according to the spec but that's another discussion.) So
I've attached an updated ospl_ddsi_config.xml file using port 65420
(participant ID 10) which will work if you start RTI up first using
Domain ID 232 for example.

It seems to me like this is probably a bug in that the OpenSplice daemon
should detect the startup of other DDS participants even if they aren't
using OpenSplice but perhaps it's a configuration issue or a problem
with RTI's implementation. Either way, it seems to work if I start the
OpenSplice daemon after the RTI demo so this is good enough for now.

-Tyson

Post by Tyson Marchuk
Thanks Hans.
I must be doing something wrong with the OpenSplice DDSI XML
configuration file. I've attached an example one I've been using. I
wrote a test program using OpenSplice DDS and one using RTI DDS. They
both can publish/subscribe to themselves but I don't see them
communicating between each other even though they're using the same
topic name and passing the same data structure on that topic (I've
included the IDL file used for the data structure as well.)
In terms of the configuration file I've tried adding channels for
ports 65410, 65411, 65412 and for having a single channel and changing
the port but it doesn't seem to make any difference. Removing all of
the channels causes my OpenSplice DDS example program to hang fairly
hard so I'm guessing that's not the answer.
In terms of the RTI example I'm just passing DomainId = 232 which when
I run it alone opens ports 65400, 65410, and 65411 and can then
communicate with itself.
Any pointers you can provide would be great. If you want I can zip and
attach all the other source for the two examples but the OpenSplice
one is fairly bare bones and simple. The RTI one is using Qt for a GUI
front end but I can make one comparable to the OpenSplice one fairly
easily if it will help.
Thanks,
-Tyson

User

_______________________________________________
OpenSplice DDS Developer Mailing List
Developer at opensplice.org
Subscribe / Unsubscribe
http://www.opensplice.org/mailman/listinfo/developer

_______________________________________________
OpenSplice DDS Developer Mailing List
Developer at opensplice.org
Subscribe / Unsubscribe http://www.opensplice.org/mailman/listinfo/developer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.opensplice.org/pipermail/developer/attachments/20101108/1b4c3fc0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ospl_ddsi_config.xml
Type: text/xml
Size: 978 bytes
Desc: not available
URL: <http://dev.opensplice.org/pipermail/developer/attachments/20101108/1b4c3fc0/attachment.bin>