Jump to content
OpenSplice DDS Forum

All Activity

This stream auto-updates

  1. Earlier
  2. Hi, I've been trying to use the Vortex OpenSplice Community edition with Python (version 3.6 within a PyEnv virtual environment) on Ubuntu 20.04.2 LTS. I've followed the PythonDCPSAPIGuide and been able to get the python examples in ($OSPL_HOME/tools/python/examples) working. However I can't figure out how to create a topic in a domain participant for a statically generated topic class using 'idlpp'. How would I be able to do this (I also can't see this in the documentation)? What I have done so far: I have an IDL file that has include paths for quite a few other IDL files. I have
  3. This is a tutorial introducing you into the world of zenoh. It explains how to quickly setup and get writing code. View the full article
  4. I am using vs2017 and followed the installation guide https://github.com/ADLINK-IST/opensplice in Cygwin installed the following packages to use Opensplice DDS with c++ in VS gcc-core gmake perl bison flex gawk zip unzip also, I have TAO_ROOT set up already I used the following commands, in Cygwin terminal Opensplice directory, $ export VS_HOME='/cygdrive/C/Program Files (x86)/Microsoft Visual Studio/2017/Community’ $ export WINDO
  5. I filed a case and an ADLink engineer said that the manual is in error. The correct range for domain IDs is 0 <= id <= 230.
  6. ADLink's configuration guide /lsstdata/offline/teststand/NCSA_comcam/gen3repo says "Note - for maximum interoperability it is recommended that you only select a domain Id from the range 0 < n < 230". However, the default files from ADLink use domain ID 0. Is 0 a safe domain ID? If so, should the manual say "0 <= n..."?
  7. I did encounter the same error when loading dds in a python script using a shebang (#!/usr/bin/env python3). I managed to fix it by using install_name_tool to change the @rpath reference to an absolute path, like this: $> install_name_tool -change @rpath/libdcpsc99.dylib ${OSPL_HOME}/lib/libdcpsc99.dylib <path>/site-packages/dds-6.9.190925OSS-py3.7-macosx-11.0-x86_64.egg/dds.cpython-37m-darwin.so $> install_name_tool -change @rpath/libdcpssac.dylib ${OSPL_HOME}/lib/libdcpssac.dylib <path>/site-packages/dds-6.9.190925OSS-py3.7-macosx-11.0-x86_64.egg/dds.cpython-37m-darw
  8. A big thanks to Erik Boasson for contacting us offline. He showed that using homebrew python 3.9 this error doesn't happen. I was able to replicate it with homebrew python 3.7 and 3.9 and indeed no errors happen there. It turned out to be an issue with pyenv which downloads and compiles its own python binaries. I switched to virtualenv, which allows me to use the homebrew versions of python, and now the error has gone. Wouter
  9. A presentation give at the European H-Cloud Conference to motivate decentralisation as a mean to improve energy efficiency, privacy, and opportunity for monetisation for your digital footprint. View the full article
  10. Payne, Did you find the solution for this? I am facing a similar problem. Thanks, Maria
  11. To be more specific, I recompiled from source on Big Sur and then get $> otool -L /usr/local/opt/OpenSplice/v6.9.190925/HDE/x86_64.darwin10_clang-dev/lib/libdcpsc99.dylib /usr/local/opt/OpenSplice/v6.9.190925/HDE/x86_64.darwin10_clang-dev/lib/libdcpsc99.dylib: @rpath/libdcpsc99.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.0.0) @rpath/libdcpssac.dylib (compatibility version 0.0.0, current version 0.0.0) @rpath/libddskernel.dylib (compatibility version 0.0.0, current version 0.0.0) The libSy
  12. Has anyone figured out how to build OpenSplice for Big Sur? Apple changed the way system libraries are found and it seems to have broken the installer.
  13. Dear Dalcelay, .NET core isn't officially supported but we already did some tests with it. In our commercial version we can support it if customer requires. With best regards, Vivek Pandey Solutions Architect ADLINK Technologies
  14. Hi, Unless I've been confused, currently .net core is not supported. Is there a plan to support it? if yes, is there a scheduled date for it? Thanks in advance
  15. Dear Mr. ChatrapatiGV, May I know which version of Opensplice DDS you are using. also let me know which DDS API (C, C++, ISOC++,...) you are using. This information is required to address your queries. With best regards, Vivek
  16. Sorry about the duplicates of the same post! The forum was throwing an error but it was getting posted anyway in the background. By the time I realized, I have posted it 3 times. I could figure out how to delete the duplicates.
  17. Hello All, I am trying to use the UserDataQoSPolicy of DataReader for distributing information about different data readers in the domain For that I have done the following: 1. Created a separate thread for receiving built-in topic messages. 2. During thread initialization, Obtained the handle of built-in topic data reader by using DDS_DomainParticipant_get_builtin_subscriber and DDS_Subscriber_lookup_datareader by passing "DCPSSubscription" as topic name. 3. Calling DDS_SubscriptionBuiltinTopicDataDataReader_take in the thread and printing the following when a m
  18. Hello All, I am trying to use the UserDataQoSPolicy of DataReader for distributing information about different data readers in the domain For that I have done the following: 1. Created a separate thread for receiving built-in topic messages. 2. During thread initialization, Obtained the handle of built-in topic data reader by using DDS_DomainParticipant_get_builtin_subscriber and DDS_Subscriber_lookup_datareader by passing "DCPSSubscription" as topic name. 3. Calling DDS_SubscriptionBuiltinTopicDataDataReader_take in the thread and printing the following when a m
  19. Hello All, I am trying to use the UserDataQoSPolicy of DataReader for distributing information about different data readers in the domain For that I have done the following: 1. Created a separate thread for receiving built-in topic messages. 2. During thread initialization, Obtained the handle of built-in topic data reader by using DDS_DomainParticipant_get_builtin_subscriber and DDS_Subscriber_lookup_datareader by passing "DCPSSubscription" as topic name. 3. Calling DDS_SubscriptionBuiltinTopicDataDataReader_take in the thread and printing the following when a m
  20. You can go though the below link to understand the firewall and ddsi networking port controlling in dds communication. https://istkb.adlinktech.com/article/ddsi-networking-service-ports/ Thanks
  21. Hi Hans, that makes sense. So if all the data is deliver, order is guaranteed for a single topic single publisher case. Thanks a lot! Luca
  22. Indeed thats correct. Just don't confuse 'ordering' with 'delivery' as - as explained - not all (ordered-) data may show-up at the reader-side for the following reasons: data was downsampled at the (KEEP_LAST) writer .. for reliable data this is also often called 'last-value-reliability' meaning that in this pattern, the latest data for each instance will be reliably delivered (note 'for each instance' as the 'overwrite behavior', both at sending as well as receiving side' is 'per instance') data was downsampled at the (KEEP_LAST) reader, which should be not a suprise and actu
  23. Hi Hans, Thanks for your answer, as usual very detailed and very clear! This means that in a system with one publisher and multiple subscribers (assuming that the readers can keep the pace of the writer) there should be no manual configuration required to order the incoming messages on a single topic (case 1). Is that correct? Thanks, Luca
  24. Thanks Vivek. It seems then that the firewall is the problem. Are you able to point me towards any info/documentation that describes how or why the firewall could be interfering with the DDS implementation? This would help me describe the problem to our IT department! Thanks
  25. generic 'what' is being received (independent from ordering) is driven by multiple aspects such as reliability and history 'history' settings at both the sender and receiver might impact what is eventually delivered when a writer exploits a KEEP_LAST history and its writing faster than the system/network can handle, data will be 'downsampled' when a reader exploits a KEEP_LAST history and is reading slower than the data arrives, data will be 'downsampled' note that the above does not constitute 'message-loss' .. its just
  26. Hi everyone, I would like to understand what is the best way of guarantying that messages are received in the same order in which they are pubblished. In our system we have publishers and subscribers on different nodes, communicating wirelessly. Nodes communicate over different topics. All the messages sent on the same topic have the same value for the key (i.e. #pragma keylist). What are the right configurations for these two problems: Making sure messages on the same topic are received in the order they are published (i.e. publisher send messages 1, 2, and 3 on topic A →
  1. Load more activity
×
×
  • Create New...