We are excited to announce the availability of RTI Connext® 7.3 LTS, the newest release under the long-term support (LTS) model designed to empower you to create the intelligent distributed applications of the future.
New Capabilities in Connext 7.3 LTS:
We are excited to introduce RTI Connext® 7.2, the latest edition to the RTI Connext Product Suite, including Connext Anywhere, Connext Secure, and Connext Professional. This release brings an array of features designed to enhance your experience and accelerate your application development.
Python3 str type is unicode UTF-8 by default. The bytes or bytearray types are more appropriate to communicate with a peer expecting C strings. In the Connector Python binding, there is a lot of round-tripping between C strings and UTF-8 Python str. This has the possibility of corrupting data or throwing errors when the content is not meant to be UTF-8. On top of that, those operations are slow. There are lower-level and "native" functions within Connector, but I can't find much information about their semantics and best practices.
I have successfully built the Connext Python API package for version 7.0 under Ubuntu 18.04 (for, and using, Python 3.6.9).
I have successfully built the Connext Python API package for version 7.1 under Ubuntu 22.04 (for, and using, Python 3.10.5).
I have not been able to build version 7.1 under Ubuntu 18.04 using either version of Python. Later this year, we'll be upgrading the OS department-wide, but for now still mostly stuck on Ubuntu 18. The target for our project using Connext Python will be Ubuntu 22 but that environment is not widely available yet.
I would like to make use of `find_by_name()` byt I can't determine how to set a name for the reader. Passing the topic name or type name does not work.
`find_by_topic()` and `find_all_by_topic()` does work using topic name, and probably is sufficient for my needs. I'm just trying to understand the API.
Hi,
I'm trying to port my applications over to the new Python API that runs on RTI DDS 7.0.0.
I have other applications running RTI for Java and the messages are using Bytes but are translated to Octets.
The Octets I have replicated and the built-in one has different TypeObject.
I have tried using the built-in Bytes message type but it seems to be incompatible with Octets.
I've also tried defining the Octets in the XML and using it but DynamicData doesn't work as expected.
Hi all,
I am currenlty testing the 7.0.0 EAR version with the new Python API Connext-Py and I have encountered several issues/bugs and was wondering what should/could I do to report them.
Here is the list:
hi,
I'm currently using connextpy, and trying to publish a topic that contains both FLAT_DATA language binding and SHMEM_REF transfer mode.
Through RTI Admin Console, I can see that I can write into basic fields of this message ("id" field below), however for some reason, the data I write in the arrays ("attribute.distance" field below) are not showing up.
hi
im trying to solve the problem where im using the same program to publish and subscribe to the same topic.
the usage is i get a cmd from the topic so i will reply to it using the same message with data populated in it.
i saw there is this ignore_participant fn that can be used to ignore the local publisher so the message wont be received by itself.
is there another method or something equivalent that i can do in the python api provided by rti.
Hi,
I am currently evaluating Connext DDS 6.0.1, especially also the Python version.
It seems that the usage of Python with IDL (converted to XML) is currently broken?!
If you follow the steps mentioned here https://github.com/rticommunity/rticonnextdds-getting-started/tree/master/2_hello_world/python you will get an error.
First I use rtiddsgen -convertToXml ../hello_world.idl
And then python3 HelloWorldPublisher.py which fails with:
