When not using multicast, you must define your set of ‘peers’ as automatic discovery relies on multicast. So the ‘ddsi2’ section in the configuration should look like this; <DDSI2Service name=”ddsi2″> <General> <NetworkInterfaceAddress>AUTO</NetworkInterfaceAddress> <AllowMulticast>false</AllowMulticast> <EnableMulticastLoopback>false</EnableMulticastLoopback> <CoexistWithNativeNetworking>false</CoexistWithNativeNetworking> </General> <Compatibility> <StandardsConformance>lax</StandardsConformance> </Compatibility> <Discovery> <Peers> <Peer Address=”name_or_address_of_machine1″/> <Peer Address=”name_or_address_of_machine2″/> <Peer Address=”name_or_address_of_machine3″/> </Peers> </Discovery> </DDSI2Service> If you run multiple applications […]

DDSI-Extended (DDSI2E) is an extended version of the DDSI2 networking service, giving extra features for: Network partitions: Network partitions provide the ability to use alternative multicast addresses for combinations of DCPS topics and partitions to separate out traffic flows, for example for routing or load reduction. Security: Encryption can be configured per network partition. This […]

There may be cases where you need to know what ports the DDSi networking service uses. For example if you are using a firewall you will need to open these ports so communication can take place. This article explains how you can work out these values. In order for the participants in a domain to […]

First we need to distinguish between the (Apache license 2 based) open-source Community Edition (CE) and the commercially supported version of Vortex OpenSplice; The  Community-edition only includes our DDSI implementation (implementing the OMG-DDSI rev2.2 specification)  i.e. that assures interoperability with other DDS-vendors based on the standardized OMG-DDSI (also called ‘RTPS’) protocol.   The DDSI protocol […]

This article contains some user submitted Vortex OpenSplice general communication questions that may prove useful to others. See the Vortex OpenSplice Homepage for more information or see the Vortex OpenSplice documentation. [cmtoc_table_of_contents] Does OpenSplice have the ability to support many to one reliable communication? Yes, OpenSplice supports the RELIABLE OMG-DDS QoS policy that implies reliable […]

In DCPS, a domain is uniquely identified by a non-negative integer, the domain id. DDSI maps this domain id to UDP/IP port numbers to be used for communicating with the peer nodes — these port numbers are particularly important for the discovery protocol — and this mapping of domain ids to UDP/IP port numbers ensures […]

In computer networking, a wire protocol refers to a way of getting data from point to point: A wire protocol is needed if more than one application has to interoperate. It generally refers to protocols higher than the physical layer The purpose and scope of the Data-Distribution Service Interoperability (DDSI) Wire Protocol is to ensure that applications based on different […]

The Vortex OpenSplice DDS Wireshark plugin allows you to use the wireshark ‘dissector’ when using the  RTNetworking network protocol.  When used with the publicly available DDSI dissector users can watch and trace any Data Distribution Service (DDS) related packet that goes on the wire from your Vortex OpenSplice DDS-based system. Vortex OpenSplice Wireshark thus allows […]