Jump to content
OpenSplice DDS Forum

Search the Community

Showing results for tags 'interoperability'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • About OpenSplice DDS
    • News and Events
    • Site Feedback
  • Using OpenSplice DDS
    • General
    • Troubleshooting
  • Understanding OpenSplice DDS
    • OpenSplice DDS Slideshows
    • OpenSplice DDS Movies
  • Community
    • Project: SIMD
    • Project: CamelOS
    • Project: DDS Touchstone
    • Project: RESTful DDS
    • Mac OS X

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Company

Found 3 results

  1. Hello, I already posted this question in the general discussion section but maybe posting it here is more appropriate. I have two programs, one using OpenSplice 6.7.1 and the other using OpenDDS 3.10. They are both using rtps as protocol, but they are not communicating. They are both using the same domain id and the destination port is the same for both programs (I verified using wireshark). I don't know if I am doing anything wrong with the config... I am using the basic config for OpenDDS and for OpenSplice I used the provided ospl.xml after changing the domain ID. Here are my config files. For OpenDDS: [common] DCPSGlobalTransportConfig=$file DCPSDefaultDiscovery=DEFAULT_RTPS [transport/the_rtps_transport] transport_type=rtps_udp For OpenSplice: <OpenSplice> <Domain> <Name>ospl_sp_ddsi</Name> <Id>223</Id> <SingleProcess>true</SingleProcess> <Description>Stand-alone 'single-process' deployment and standard DDSI networking.</Description> <Service name="ddsi2"> <Command>ddsi2</Command> </Service> <Service name="durability"> <Command>durability</Command> </Service> <Service name="cmsoap"> <Command>cmsoap</Command> </Service> </Domain> <DDSI2Service name="ddsi2"> <General> <NetworkInterfaceAddress>AUTO</NetworkInterfaceAddress> <AllowMulticast>true</AllowMulticast> <EnableMulticastLoopback>true</EnableMulticastLoopback> <CoexistWithNativeNetworking>false</CoexistWithNativeNetworking> </General> <Compatibility> <!-- see the release notes and/or the OpenSplice configurator on DDSI interoperability --> <StandardsConformance>lax</StandardsConformance> <!-- the following one is necessary only for TwinOaks CoreDX DDS compatibility --> <!-- <ExplicitlyPublishQosSetToDefault>true</ExplicitlyPublishQosSetToDefault> --> </Compatibility> </DDSI2Service> <DurabilityService name="durability"> <Network> <Alignment> <TimeAlignment>false</TimeAlignment> <RequestCombinePeriod> <Initial>2.5</Initial> <Operational>0.1</Operational> </RequestCombinePeriod> </Alignment> <WaitForAttachment maxWaitCount="100"> <ServiceName>ddsi2</ServiceName> </WaitForAttachment> </Network> <NameSpaces> <NameSpace name="defaultNamespace"> <Partition>*</Partition> </NameSpace> <Policy alignee="Initial" aligner="true" durability="Durable" nameSpace="defaultNamespace"/> </NameSpaces> </DurabilityService> <TunerService name="cmsoap"> <Server> <PortNr>Auto</PortNr> </Server> </TunerService> </OpenSplice> Any help is appreciated! Thanks !
  2. Hello, I have two programs, one using OpenSplice 6.7.1 and the other using OpenDDS 3.10. They are both using rtps as protocol ( I verified it using wireshark), but they are not communicating. I don't know if I am using the right config and I don't know what documentation I should read to help me. Here are my config files. For OpenDDS: [common] DCPSGlobalTransportConfig=$file DCPSDefaultDiscovery=DEFAULT_RTPS [transport/the_rtps_transport] transport_type=rtps_udp For OpenSplice: <OpenSplice> <Domain> <Name>ospl_sp_ddsi</Name> <Id>223</Id> <SingleProcess>true</SingleProcess> <Description>Stand-alone 'single-process' deployment and standard DDSI networking.</Description> <Service name="ddsi2"> <Command>ddsi2</Command> </Service> <Service name="durability"> <Command>durability</Command> </Service> <Service name="cmsoap"> <Command>cmsoap</Command> </Service> </Domain> <DDSI2Service name="ddsi2"> <General> <NetworkInterfaceAddress>AUTO</NetworkInterfaceAddress> <AllowMulticast>true</AllowMulticast> <EnableMulticastLoopback>true</EnableMulticastLoopback> <CoexistWithNativeNetworking>false</CoexistWithNativeNetworking> </General> <Compatibility> <!-- see the release notes and/or the OpenSplice configurator on DDSI interoperability --> <StandardsConformance>lax</StandardsConformance> <!-- the following one is necessary only for TwinOaks CoreDX DDS compatibility --> <!-- <ExplicitlyPublishQosSetToDefault>true</ExplicitlyPublishQosSetToDefault> --> </Compatibility> </DDSI2Service> <DurabilityService name="durability"> <Network> <Alignment> <TimeAlignment>false</TimeAlignment> <RequestCombinePeriod> <Initial>2.5</Initial> <Operational>0.1</Operational> </RequestCombinePeriod> </Alignment> <WaitForAttachment maxWaitCount="100"> <ServiceName>ddsi2</ServiceName> </WaitForAttachment> </Network> <NameSpaces> <NameSpace name="defaultNamespace"> <Partition>*</Partition> </NameSpace> <Policy alignee="Initial" aligner="true" durability="Durable" nameSpace="defaultNamespace"/> </NameSpaces> </DurabilityService> <TunerService name="cmsoap"> <Server> <PortNr>Auto</PortNr> </Server> </TunerService> </OpenSplice> I appreciate it if you can help me with the configs or point me to the right documentation to read! Thanks !
  3. Stanislaw

    Discovery and reliabilty over WAN

    Hi, I consider DDS as a reliable data exchange mechanism in WAN so I have couple of questions. After reading a lot of stuff (presentations, articles, DDS standard), doing some experiments I am still not convinced that DDS really fits my requirements.The assumed network supports multicast but could be partially prone to degradation, latencies, low bandwidth etc. RTPS specifies two modules: behavior and discovery that are strongly interrelated. The behavior part (reliable/best effort, messages, GUIDS, sequence numbers) looks very well but is tightly dependent on discovery. The reliability will work only if discovery mechanism will work well. The standard defines SPDP and SEDP as a minimum for interoperability, so if am am not wrong Splice implements SPDP and SEDP and all interoperability tests between vendors are based on that??? Or Splice offers other PDP and EDP ( for example for WAN ) and they are interoperable??? Unfortunately SPDP and SEDP seems to be not sufficient for WAN and scalability in WAN. Other issue is interpretation of reliability offered by DDS, is this only reliable mechanism based on ack messages ??? In this kind of systems (pub-sub is group communication) for me reliable means mechanism that support correlation between acknolegments and group/topic participation. For example, I am sending a message to GROUP/topic and do I have the mechanism which tells me that the message were not delivered to a GROUP or even to which participant? Stanislaw
×