Discovery

Hi. I use connext dds version6.

I use unicast domain participant discovery.

I realized that sending too many discovery packets  ( to any other domain paticipant in the network)  without any delay between them, makes effect on sending other packets and makes my network inefficient.

I want to make about 10ms time space between sending discovery packet. Is there any normal solution to do that? Is there any qos related to that?

I am having trouble getting a subscriber to receive data from a publisher. Both entities are on the same machine and my firewall is off.

* Subscriber has a listener with StatusMask as all().
* set NDDS_DISCOVERY_PEERS=4@shmem://
* Using HighThroughput profile.

I guess the more unusual thing about this app is that there are two domain participants with a pub on one and a subscriber on the other. Yet, they are both on the same domain's id, 0. I assume that's ok.

Hi,

Hello,

when I  want to use DDS publish and subscribe with different IP, I find  DISCOVERY mode in the document, but actually I still have no idea to deal with it.

Hi,

I can't get my DDS Micro project to interoperate with my client's DDS Connext. Below are some information, and hope somebody can help me please. My project deadline is approaching.

I'm running a DDS micro client (v 2.4.10) on a linux ARM system (compiled from source).  It produces topic data on one second intervals, and I have a windows 7 system with the Connext Pro version 5.3.0 running the Admin Console that should be able to watch the data.

Hi all.

I’ve been developing a set of apps with one server and three different clients. Everything works fine while running all of them on the same machine. Now I put one of those clients in another machine B, connected to the same router, and the first message of this client -a login request- is never received by the server in machine A. The on_publication_matched method in the client is never executed, but in the Administration Console, the client turns from Healthy to Warning: Reader-only Topic. Topic contains only DataReaders when the message is sent.

Hello,

we are migrating from old Suse with kernel 3.0 to a new version with kernel 3.12. One of the changes are ARP limits:

Hi everybody,

I have written a simple application which discover all domains with the help of dds::topic::ParticipantBuiltinTopicData. When a domain joins my LAN network, my program detects it but it cannot detect leaving domains. Is there any way to detect leaving domains? 

I bring some of my application code below for further uses: