Jump to content
OpenSplice DDS Forum

Search the Community

Showing results for tags 'discovery'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


Last Updated

  • Start


Filter by number of...


  • Start





Website URL








Found 7 results

  1. Hi, I'm trying to understand helloworld examples's rtps discovery protocol(SPDP and SEDP) using wireshark. I ran pub and sub on different VM connected each other. each VM has only one network interface(enp0s3). tested in ubuntu 16.04 desktop 64bit and DDS Community 6.7 1) when I dumped packets, there was a HEARTBEAT packet with writerEntityID 'ENTITYID_BUILTIN_PUBLICATIONS_WRITER' not only 'ENTITYID_BUILTIN_SUBSCRIPTIONS_WRITER'. but that HEARTBEAT packet was sent from helloworld subscriber program. I thought 'BUILTIN_PUBLICATIONS_WRITER' is entity that announces presence of publisher, isn't it? 2) and when I ran only one subscriber, there were many SPDP packets with different GUID prefix(more exactly different appId). so, these are intended implementation that creates unused 'BUILTIN_PUB/SUB_WRITER' and many participant with different GUID? or am I misunderstand RTPS spec? attached pcap file has two rtps pakcets, one with different guid pakcets and one with HEARTBEAT packets with 'PUB/SUB_WRITER'.
  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. urochicken

    Discovery and network disconnections

    Hi I have run into some problems regarding the discovery process, and how it affects entities status after network disconnections. Maybe I have a wrong idea of what is attainable, or I am not using the right services. In short, the "matched subsciption" status of the readers and writers in different machines changes when the network goes down (they stop seeing each other), but they seem not to regain visibility when the network goes back up. Unexpectedly, data messages still arrive to destination if published again. Also new nodes are detected flawlessly. Here is some context to the problem : I have a couple of x86_64 Linux virtual machines on a private lan segment, and I am using an out-of-the-box OpenSplice 6.4. Default ospl.xml configuration: ddsi2 with multicast discovery enabled. Modified Listeners example so that we have status listeners for both the data reader and data writer, masks modified to show interest on subscription matching status. Modified Listeners example so that we can publish new messages and close the applications via keyboard. The topic QoS is the same as in the example: {transient, reliable}. I have removed the duration QoS The operation is the following: Subscriber started in machine A Publisher started in machine B Reader reports matched subscription Writer reports matched publication. Manualy disable network interface in machine B Reader reports matched subscription changed (no suitable publisher present) Writer report matched subscription changed (no suitable subscriber present) Manually enable network interface in machine B No changes in subscription observed Am I making some conceptual error here? I can further expand, as well as provide the offending code. Regards
  4. Hello, I have read about dynamic discovery in DDS, which says, if there is a subscriber client that has DHCP enabled and in the mid of receiving information, gets all together a new IP(since it is dynamically configured), the subscriber client will still receive information even though its IP address has a new value. But I am unable to achieve the same. The test setup done is as follows: Subscriber and publisher are up, wherein subscriber keeps receiving messages, published by the publisher. I somehow make the subscriber client allocate itself a new dynamic IP, but this makes the subscriber client stop receiving messages. The config file entries that have been done for the same are attached herewith as ospl.xml. Please suggest the solutions as to how IP independency is achieved in Opensplice DDS and what more needs to be done to resolve the above mentioned problem? Regards, Suman ospl.xml
  5. Potomane555

    Topic discovering

    Hey ! I have some bad trouble with topic discovering. I have two application with same code. One is running on Windows 7. OpenSplice 6.6.3 x86_64. The other is on Windows 10. OpenSplice 6.6.3 x86_64. I use java api. The topic discovering is not full duplex. First case : I launch my app on Windows 7. In second, I launch my app on Windows 10. This instance see the topic create by Windows 7 app with the method find_topic. Second case : I launch my app on Windows 10. In second, I launch my app on Windows 7. This instance doesn't see the topic create by Windows 10 app. What can be the problem ? In a case, on my Windows 7 app, the firewall can't be desactivate but as in first case, I can't receive publication from de outside, I think the firewall configuration is good. Thank if you can lighten my spirit. Maxime.
  6. Hello, I try to configure OpenSplice to perform discovery with multicast and then data transfert with unicast. I’m using Networking service but I still haven’t found a satisfying configuration. The configuration I’m using is the following: <OpenSplice> <Domain> <Name>ospl_sp_ddsi</Name> <Id>0</Id> <SingleProcess>true</SingleProcess> <Description>Multicast discovery</Description> <Service name="durability"> <Command>durability</Command> </Service> <Service name="cmsoap"> <Command>cmsoap</Command> </Service> <Service name="networking"> <Command>networking</Command> </Service> <Role>PICS</Role> </Domain> <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> <NetworkService name="networking"> <Channels> <Channel enabled="true" name="Reliable" reliable="true"> <PortNr>53400</PortNr> </Channel> <Channel enabled="true" name="BestEffort" reliable="false"> <PortNr>53410</PortNr> </Channel> </Channels> <General> <NetworkInterfaceAddress>eth0</NetworkInterfaceAddress> </General> <Partitioning> <GlobalPartition Address=""/> </Partitioning> <Discovery Scope="PICS" enabled="true"> <PortNr>3369</PortNr> </Discovery> </NetworkService> </OpenSplice> With this configuration, it seems that the data are sent twice, once to the multicast address (what I’d like to avoid) and once to the unicast address, which badly impacts the transfert time. Could you tell me what I’m doing wrong? Thank you very much in advance!
  7. bonjefir

    Dynamic topic type discovery

    Hi I have recently read "http://forums.opensplice.org/index.php?/topic/2137-dds-reader-without-data-type/" and found that it was not possible to get one topic type dynamically in previous versions. I want to know whether this feature is available in the latest version of DDS community or even commercial. If it is available, I will appreciate it if you could provide me with an example. I think it is a very important and essential feature (At least I need it now ! ). Thanks in advance for your help. Bonjefir