Jump to content
OpenSplice DDS Forum
The search index is currently processing. Activity stream results may not be complete.

All Activity

This stream auto-updates

  1. Today
  2. 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
  3. Yesterday
  4. 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
  5. Last week
  6. Payne, Did you find the solution for this? I am facing a similar problem. Thanks, Maria
  7. 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
  8. 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.
  9. Earlier
  10. 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
  11. 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
  12. 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
  13. 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.
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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 →
  24. Hi Trs91, Here is the fix for similar problem: Regarding nature of create_topic() API : It creates a reference to a new or existing Topic under the given name, for a specific type, with the desired QosPolicy settings and if applicable, attaches the optionally specified TopicListener to it. You can get details from below link: http://download.ist.adlinktech.com/docs/Vortex/apis/ospl/cs_api/html/a00928.html#a83346dafb28e1fe8f7f3aa5c545fe97f With best regards, Vivek Pandey Solutions Architect Adlink Technology
  25. UPDATE: I have been able to run this successfully using a computer with less restriction (i.e. a 'personal' rather than 'company' laptop), meaning I believe that the issue is not a DDS or code one, rather an IT infrastructure one. I am not sure what specifically the problem may be and how/what I need to ask the IT department to look into. Can anyone advise? Thanks
  26. Hi, I am using the community version of OpenSlice DDS and am having issues with the basic HelloWorld example. My config is: Windows; building in Visual Studio 2019; using the C# examples; with the OSPL_SP_DDSI.xml config file. I have successfully built the example and can run both the _sub and _pub exe's fine, however the messages published by the publisher are not received by the subscriber. My method for running is to either run both exe's at once from within VS, or to use two Windows CMD command lines, run the release.bat script in each, and then execute the two exe's.
  27. Thank you for the suggestion. Unfortunately I tried it and was not able to get it work: yes the query was accepted, but it did not behave as it was supposed to. Fortunately this is a short-term issue. Eventually I can get rid of the test for the empty string, at which point I'll be able to use a query again. I am quite surprised that this is accepted: qc = QueryCondition(reader, mask, "identity=%0 OR identity=%1", ["foo", ""]) but this is not: qc = QueryCondition(reader, mask, "identity='foo' OR identity=''") I realize for real SQL queries it is important to sanitize in
  28. I am trying to perform a read query that a field either matches a fixed value OR is empty. This is using the Python dds library, though I hope that doesn't affect the answer. What I have tried: (identity = 'saluser@2e2a97a8cda0') OR (identity = '') The problem appears to be in the second part identity = '' Using double quotes instead of single quotes doesn't help. If I add a space between two single quotes then the query is built, but does not do what I want. Any suggestions?
  1. Load more activity
×
×
  • Create New...