Jump to content
OpenSplice DDS Forum

Search the Community

Showing results for tags 'Opensplice'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • About OpenSplice DDS
    • News and Events
    • Site Feedback
  • Using OpenSplice DDS
    • General
    • Troubleshooting
  • Understanding OpenSplice DDS
    • OpenSplice DDS Slideshows
    • OpenSplice DDS Movies
  • Community
    • Project: SIMD
    • Project: CamelOS
    • Project: DDS Touchstone
    • Project: RESTful DDS
    • Mac OS X

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Company

Found 66 results

  1. I would like to run DDS OpenSplice (https://github.com/ADLINK-IST/opensplice/) with .NET Core instead of .NET Framework. I have created a Visual Studio project from scratch, targeting .NET Core 2.0, added the source files related to the HelloWorld example (https://github.com/ADLINK-IST/opensplice/tree/master/examples/dcps/HelloWorld/cs/src) and referenced the library dcpssacsAssembly.dll shipped in the OpenSplice package. The compilation is doing fine. The release directory belonging to the publisher of the HelloWorld example contains the following files: dcpssacs.netmodule & dcpssacsAssembly.dll ddsapihelper.dll & ddsapihelper.pdb HelloWorldPub.deps.json HelloWorldPub.dll HelloWorldPub.pdb HelloWorldPub.runtimeconfig.dev.json HelloWorldPub.runtimeconfig.json In a command shell I set up the environment variables needed for OpenSplice by executing a script named "release.bat". Finally I try to run the command "dotnet HelloWorldPub.dll" but the following error pops up: Unhanded Exception: System.IO.FileLoadException: Could not load file or assembly 'dcpssacs.netmodule'. The module cannot be loaded because only single file assemblies are supported. (Exception from HRESULT: 0x8013101E) at HelloWorldDataPublisher.HelloWorldDataPublisher.Main(String[] args) Any idea what is going on? Thanks in advance for your help.
  2. ADLINK is pleased to announce the availability of two new introductory Vortex DDS whitepapers Python DDS Binding - download at: http://gag.gl/QSApsi LabVIEW Software DDS Binding - download at: http://gag.gl/MnkVDA
  3. PrismTech's Vortex OpenSplice v6.8.2 software is now available - this release includes C# Language binding supporting use of unions in your IDL data model. Download the evaluation software at http://www.prismtech.com/vortex/software-downloads
  4. PrismTech is pleased to announce the availability of Vortex OpenSplice v6.8.1, its market leading (open source and commercial) implementation of the Data Distribution Service (DDS) standard. This latest release includes further Mathworks MATLAB & Simulink integration enhancements. Read the PrismTech blog on the new release at: https://blog.prismtech.com/2017/06/14/mathworks-matlab-and-simulink-integration-on-the-latest-vortex-opensplice-v6-8-1/ Download the Vortex OpenSplice v6.8.1 evaluation software from PrismTech's website at: http://www.prismtech.com/vortex/software-downloads
  5. Download the latest Vortex OpenSplice v6.8 evaluation software at: http://www.prismtech.com/vortex/software-downloads PrismTech™, a global leader in software platforms for distributed systems, today announced Vortex™ OpenSplice™ support for MathWorks’ MATLAB® and Simulink® products. PrismTech's Vortex OpenSplice is the leading (commercial and Open Source) implementation of the Object Management Group®'s (OMG®) Data-Distribution Service™ (DDS™) standard. Vortex OpenSplice has been designed to optimally address the real-time information distribution and management challenges posed by high performance real-time data-processing systems. Vortex OpenSplice is a key enabler for systems that have to reliably and securely deliver high volumes of data with stringent end-to-end qualities-of-service (QoS). Vortex OpenSplice plays a crucial role in many mission and business-critical systems by ensuring that the right information is delivered to the right place at the right time all the time. MathWorks is the leading developer of mathematical computing software. MATLAB is a programming environment for algorithm development, data analysis, visualization, and numeric computation. Simulink is a graphical environment for simulation and Model-Based Design for multidomain dynamic and embedded systems. Engineers and scientists worldwide rely on these product families to accelerate the pace of discovery, innovation, and development in automotive, aerospace, electronics, financial services, biotech-pharmaceutical, and other industries. Via its standardized DDS interface, Vortex OpenSplice now provides integration with MATLAB and Simulink. MATLAB classes as well as Simulink BUS definitions are mapped to their corresponding Topic definitions in DDS. To ensure type agreement between DDS and MATLAB / Simulink applications, Simulink BUS definitions can be automatically generated from the corresponding Topic types defined in the IDL format that is standard for DDS applications. MATLAB classes can be defined in the MATLAB workspace with the class name, fields and field types corresponding to the DDS IDL Topic definition. The integration allows users to create DDS entities in their MATLAB / Simulink model and associate them with desired QoS in separate XML files to provide maximum flexibility and control how and when data is exchanged. These capabilities allow users to transparently share any data between different MATLAB / Simulink applications and / or pure DDS applications no matter where they have been deployed in the network. "We are delighted to be able to add MATLAB and Simulink support to Vortex OpenSplice," said Andrew Foster, Product Marketing Manager, PrismTech. "This integration of truly world-class products will enable our customers to seamlessly share DDS data from anywhere in a network with MATLAB and Simulink.” Further information about PrismTech’s Vortex OpenSplice is available at: http://www.prismtech.com/vortex/vortex-opensplice.
  6. PrismTech’s Vortex OpenSplice Selected by DexROV Project to Help Deliver Safer and More Cost-effective Dexterous Undersea Operations with Remotely Operated Vehicles Vortex OpenSplice provides the robust low latency communications needed by the project Newcastle upon Tyne, UK – February 13, 2017 – PrismTech™, a global leader in software platforms for distributed systems, today announced that its Vortex™ OpenSplice™ product has been selected by the DexROV project for dexterous undersea operations with Remotely Operated Vehicles (ROV). Part of the long-term EC Horizon 2020 Blue Growth strategy to support sustainable growth in the European marine and maritime sectors DexROV brings together seven different organisations from all over Europe to challenge what is possible in the realms of undersea operations. DexROV is using and evaluating new technologies to allow safer, more cost-effective undersea operations with ROVs. DexROV will greatly reduce the costs, hazards, and number of offshore personnel needed in underwater operations in the fields of energy, communications infrastructure, science, archaeology and shipwreck recovery by enabling delocalized supervision for deep-sea inspection and maintenance work. The goals of the project are to: move control of ROVs to shore, from a safe distance; overcome the latency involved between onshore control centres and ROVs through autonomous operations; and develop advanced dexterous tools with the capacity to grip and manipulate in ways similar to a human hand. The main challenges of the project include: undersea perception and modeling; navigation and manipulation control; deep water capable dexterous manipulators; far distance teleoperation; and haptic user interfaces. PrismTech’s Vortex OpenSplice is the leading commercial and open source implementation of the Object Management Group®'s (OMG®) Data-Distribution Service™ (DDS™) standard. DexROV has selected PrismTech’s Vortex OpenSplice DDS implementation for the project because of its rich set of Qualities of Service (QoS). Vortex OpenSplice is robust to disruptions allowing very low bandwidth network connectivity information sharing between the ROV, satellite and piloting centres. “PrismTech’s Vortex Innovator Program has allowed us to use Vortex OpenSplice on our project,” said Shashank Govindaraj, Robotics Software Engineer, Space Applications Services NV/SA. “We have been very satisfied with the low latency communications and QoS that Vortex OpenSplice has been able to deliver to the project.” The outcomes of the project will be demonstrated in a series of test campaigns culminating in a 1,300 meter deep representative trial in the Mediterranean Sea. Further information about the DexROV project is available from the website at: http://www.dexrov.eu. Full press release at: http://www.prismtech.com/news/prismtech-vortex-opensplice-selected-dexrov-project-undersea-remotely-operated-vehicles
  7. G Shenton

    PrismTech Releases Vortex 2.3

    Download Vortex 2.3 at: http://www.prismtech.com/vortex/software-downloads PrismTech Releases Vortex 2.3 the Most Efficient and Scalable Data Connectivity Solution for Integrating Device, Edge and Cloud Systems - Vortex provides low latency real-time data connectivity, combined with exceptional scalability and ease-of-use to simplify the integration of complex Industrial Internet of Things systems Boston, MA, USA – October 4, 2016 – PrismTech™, a global leader in software platforms for distributed systems, today announced the availability of its Vortex™ 2.3 Intelligent Data Sharing Platform for the Internet of Things (IoT). This latest version of its award winning data connectivity solution provides the ideal solution for connecting Industrial IoT systems. Vortex is based on the Object Management Group®'s (OMG®) Data-Distribution Service™ (DDS™) standard and builds on proven technologies to provide an efficient solution for real-time device, edge and cloud IoT data sharing. Vortex is a crucial enabler for systems that have to reliably and securely deliver high volumes of data with stringent end-to-end qualities-of-service (QoS). Key Vortex capabilities such as automatic discovery, shared memory architecture, configurable QoS framework, and portability of the platform, together enable system-wide scalability and save valuable development time, particularly when integrating legacy systems. With the support of PrismTech’s world-class tooling and professional services, Vortex customers are able to successfully meet stringent development milestones. Vortex 2.3 includes enhancements that simplify the challenge of connecting nodes and sharing real-time data in complex Industrial IoT environments that consist of a combination of device, edge and cloud networks. Vortex 2.3 includes the following new functionality and improvements: * Vortex Cloud and Fog include a number of optimizations that simplify deployment, reduce routing latency and improve scalability significantly * The elegant C99 API will be supported by both Vortex Lite and Vortex OpenSplice as of version 6.7.1 * Vortex now fully supports the Java 8 platform * Google Protocol Buffer (GPB) extensible data types are now supported by Vortex OpenSplice Tuner * Group coherence support has been added to Vortex OpenSplice Tuner and Tester * Vortex Cafe can now use UDP and TCP transports simultaneously * Instance lifecycle support has now been added to Vortex Web, providing access to SampleInfo in Javascript * Vortex OpenSplice includes an Open Source reference implementation of the Future Airborne Capability Environment (FACE™) Consortium’s v2.1 Transport Services Segment (TSS) API
  8. I would like to have DDS running on the INTEGRITY real-time operating system, which is a product of GreenHills Software for which the MULTI IDE and C++11 compiler is available. Anyone else considered this or have porting tips for me? Has anyone tried this? Thanks for all information. General information about portability of OpenSplice DDS is also of interest. By the way, it looks to me like the OpenSplice DDS 6.4 Community Edition involves 483 .cpp and .hpp source files containing 44386 lines of C++ code. Thanks, -Gary
  9. Thales has selected PrismTech’s Vortex™ OpenSplice™ as the data-sharing platform for the sighting systems implemented in the AJAX fleet of armored vehicles, which is being delivered to the British Army by General Dynamics Land Systems-UK. Thales is the supplier of sighting systems and ancillary equipment for the AJAX fleet. The UK MOD’s Generic Vehicle Architecture (GVA) Standard mandates that such vehicles adhere to the Data Distribution Service (DDS) standard for their data communication protocol. Vortex OpenSplice is based on DDS and will enable high-level communications and interoperability between the vehicles’ advanced onboard systems. “Vortex provides an extremely cost-effective solution,” said Steve Jennis, PrismTech’s Senior Vice President of Corporate Development. “We’re pleased to be working with Thales on such ground-breaking work. Vortex will be making a significant contribution to the performance of these vehicles.” Vortex OpenSplice provides device-to-device data sharing in real time – secure, reliable delivery of voluminous data. Vortex is a comprehensive and intelligent data-sharing platform for highly distributed real-time systems such as those found in aerospace and defense. “The Thales Sights and associated image processing units are part of a real-time network that communicates via DDS,” said David Low, Head of Land Optronics UK for Thales. “Vortex OpenSplice provides the dependable communication means in this complex environment enabling the full power of the Thales subsystems to be realised.” AJAX is an agile, highly adaptable fighting and reconnaissance vehicle for the British Army. Thales is supplying 245 vehicle sets of sights during the five-year program. “All the complexity built into these vehicles calls for a solution that will integrate the various systems smoothly and seamlessly,” Jennis said. “When troops are in the field and their lives depend on systems communicating with one another, reliability, accuracy and real-time performance are essential and that’s what Vortex OpenSplice delivers.” Further information about Vortex is available from PrismTech’s website at: http://www.prismtech.com/vortex.
  10. How to use eclipse for openSplice DDS v6.4 in Wndows 7 32 bit?
  11. Vortex OpenSplice provides robust Qualities of Service, including shared-memory capabilities, for developing class of open architecture weapons Boston, MA, USA – May 4, 2016 – PrismTech™, a global leader in software platforms for distributed systems, today announced that its award-winning Vortex™ OpenSplice™ software platform has been selected by WINTEC for its Small Business Innovation Research (SBIR) project involving the development of a software architecture for universal plug-and-play of weapons. Existing air-to-ground weapon architectures are generally based on point designs that are unique to individual weapons and / or contractors. These weapons cannot be readily modified or upgraded, or easily reconfigured to different capability levels for cost-effective performance of varying missions. WINTEC is developing a modular open architecture that offers significant promise for alleviating or minimizing such limitations. The new architecture will support the implementation of weapons from various combinations of common functional modules through standard interfaces and associated plug-and-play features for self-discovery and initialization. The technology will facilitate more flexible and cost-effective development and implementation of weapons. It also has significant potential for use in commercial applications such as unmanned vehicle integration and special test equipment. PrismTech’s Vortex OpenSplice enables components – such as sensors, seekers and propulsion systems – within a developing class of weapon architectures to be able to accommodate emerging technologies and allow seamless communication of updated plug-ins. “Vortex OpenSplice is the backbone that is able to connect these major interchangeable components,” said Steve Jennis, Senior Vice President of Corporate Development at PrismTech. “WINTEC is evaluating the DDS benefits that Vortex OpenSplice provides as their project scales and evolves.” To initiate the first phase of this project, WINTEC turned to PrismTech’s open source DDS Community Edition, a version of Vortex OpenSplice high-performance messaging technology designed for small companies and those projects that may not yet require a full complement of services and support. As the project progressed, however, so did WINTEC’s need for Vortex OpenSplice’s advanced capabilities and services. “Thanks to the DDS Community version, we had become very familiar with Vortex OpenSplice and its robust quality of service levels,” said Greg Fountain, President, WINTEC. “We were specifically looking for a DDS based solution with a shared memory capability — and Vortex OpenSplice was our choice.” PrismTech’s Vortex OpenSplice is the leading commercial and open source implementation of the Object Management Group™'s Data Distribution Service for Real-Time Systems (DDS) standard. Vortex OpenSplice has been designed to optimally address the real-time information distribution and management challenges posed by high-performance, real-time data-processing systems. Vortex provides efficient, secure and interoperable internet scale real-time data sharing. It is a key enabler for systems that have to reliably and securely deliver high volumes of real-time data with stringent end-to-end qualities-of-service. Further information about Vortex OpenSplice available from PrismTech’s website at: http://www.prismtech.com/vortex. http://www.prismtech.com/news/wintec-selects-prismtechs-vortex-opensplice-open-architecture-modeling-weapon-systems
  12. vmayoral

    OpenSplice IPv6

    Hello, We're trying to get OpenSplice working with IPv6 but found that some attributes don't seem to be implemented. The issue has been described at https://github.com/PrismTech/opensplice/issues/24. Can someone inform about what's the status of IPv6? We are happy contributing but will need a few pointers. What's the quickest route to get it working? Many thanks,
  13. Download the evaluation software at: http://www.prismtech.com/vortex/software-downloads PrismTech Announces Vortex 2.1 the Most Comprehensive Real-Time Data Sharing Platform for the Internet of Things - Vortex provides an ideal data connectivity solution for business critical and industrial IoT systems PrismTech today announced the availability of its Vortex 2.1 Intelligent Data Sharing Platform for the Internet of Things (IoT). This latest version of its award winning IoT platform provides the ideal solution for integrating real-time distributed systems. Vortex is based on the Object Management Group’s (OMG) Data Distribution Service (DDS) for Real-time Systems open standard and builds on proven technologies to provide an efficient solution for real-time device, edge and cloud IoT data sharing. Vortex is a crucial enabler for systems that have to reliably and securely deliver high volumes of data with stringent end-to-end qualities-of-service (QoS); hence its suitability for delivering the right information to the right place at the right time. Vortex 2.1 includes the following new functionality: * Client side Durability is now supported by both Vortex Lite and Vortex Café. This means that TRANSIENT and PERSISTENT Durability QoS policies can now be used by both Vortex Lite and Vortex Café applications provided that at least one Vortex OpenSplice™ Durability Service is deployed in the same system. * Vortex Lite now includes support for extensible data models based on Google Protocol Buffers (GPB). GPB is a language-neutral, platform-neutral extensible mechanism for serializing structured data developed by Google. The benefit of using GPBs is that they are extensible and can be updated without breaking programs that are compiled against “older” data structure definitions. This ability enables systems and their data models to evolve dynamically without major application re-engineering. GPB support in Vortex Lite is currently available for the ISO C++ API. GPB support is already available in Vortex OpenSplice (Java, C and ISO C++) and will be available shortly in Vortex Café. * Vortex OpenSplice also includes a number of new features, including: - It is now possible to detach from all domains. A new operation has been added to the DomainParticipantFactory in the DDS API that allows you to detach your application safely from all Domains it is participating in with one single call. - The naming of DomainParticipant, Publisher, Subscriber, DataWriter and DataReader entities has been improved. When visualized with one of the Vortex tools (Insight, Tuner or Tester) the improved naming makes it easier for users to relate entities to their applications. - A new section called "Controls" has been introduced to Vortex OpenSplice Launcher. This section contains buttons to easily start and stop an OpenSplice domain based on the active ospl config file in Launcher. When the user clicks on the start/stop button, a progress bar is displayed in the bottom tool bar to indicate that Launcher is processing the request. When Launcher has completed the operation, notification pop-up messages are displayed indicating the result of the requested operation. - Windows 10 is now supported. Read the full press release at: http://www.prismtech.com/news/prismtech-announce-vortex-21-most-comprehensive-real-time-data-sharing-platform-internet-things
  14. HGL Dynamics Selects PrismTech's Vortex OpenSplice for Next Generation Data Acquisition Unit Vortex OpenSplice provides high performance real-time data management solution for HGL Dynamics PrismTech, a global leader in software platforms for distributed systems, today announced that HGL Dynamics has selected its Vortex OpenSplice product for its next generation Data Acquisition Unit. HGL Dynamics is a leading developer of high-specification, real-world dynamic data acquisition, analysis visualisation, and storage systems for industrial and engineering applications, particularly turbines and rotating equipment. HGL Dynamics’ products have a proven track record of providing acquisition, storage and analysis equipment for civil and military jet engines, including systems for the Joint Strike Fighter program, in the UK and USA. PrismTech’s Vortex OpenSplice is the leading (commercial and Open Source) implementation of the Object Management Group's (OMG) Data Distribution Service (DDS) for Real-Time Systems standard. Vortex OpenSplice has been designed to optimally address the real-time information distribution and management challenges posed by high performance real-time data-processing systems. Vortex OpenSplice was chosen by HGL Dynamics for its next generation Data Acquisition Unit as it could leverage the extensive performance, scalability and interoperability that are inherent in the product. The broad range of qualities of service (QoS) supported in Vortex OpenSplice also helped to guarantee predictable and reliable delivery of real-time data within its measurement systems. “We have seen an increase in customers asking us to provide DDS-based vendor interoperability as part of our product range; with PrismTech's support and using Vortex OpenSplice's modern C++ API we have been able to quickly achieve this. We have plans to make even more use of Vortex OpenSplice in our product range in the future," said Duncan Crutchley, Principal Software Engineer, HGL Dynamics. “I’m very pleased to be able to add HGL Dynamics to our extensive global list of customers who are using Vortex OpenSplice in demanding real-time data-processing systems,” said Keith Steele, Founder, PrismTech. “HGL Dynamics’ customers, including those within the global flight testing market, are converging on DDS as a proven, interoperable data sharing solution to realise significant reductions in integration costs.” Read the full press release at: http://www.prismtech.com/news/hgl-dynamics-selects-prismtech-vortex-opensplice-next-generation-data-acquisition-unit
  15. Hi everyone, I recently started to use the Vortex Opensplice version. We are developing a small application in order to play around it. But I am encountering a weird error, that I have never seen previously. This is related to the durability service, and what happens is that persistent data are not actually written on disk, but only the relative *_meta.xml. Also, everytime I restart my application, without having previously deleted the content of the StoreDirectory, I get the following error: ======================================================================================== Report : ERROR Date : Thu Nov 19 17:56:47 W. Europe Standard Time 2015 Description : Unable to resolve persistent data version. Node : 9727H12 Process : java.exe <9224> Thread : durability 8684 Internals : V6.5.0p1/72b8738/b16d292/persistentStoreReadTopicXML/d_storeXML.c/3871/0/1447952207.578610300 ======================================================================================== Report : ERROR Date : Thu Nov 19 17:56:47 W. Europe Standard Time 2015 Description : Unable to insert persistent data from disk for group 'topic.DDSBBItem'. Reason: '6'. Removing data for this group... Node : 9727H12 Process : java.exe <9224> Thread : durability 8684 Internals : V6.5.0p1/72b8738/b16d292/DurabilityService/d_storeXML.c/4907/0/1447952207.578610300 ======================================================================================== Where "topic" is actaully the name of the partition I am using, while DDSBBItem is the topic name. Thanks! Burnout
  16. Vortex OpenSplice provides real-time data sharing capabilities for aircraft flight simulation within Atech’s SAGITARIO ATC training program PrismTech™, a global leader in software platforms for distributed systems, today announced that its award-winning Vortex™ OpenSplice™ software platform has been selected by Atech for the Brazilian Air Traffic Control (ATC) training simulation system. Vortex will be used as the data sharing layer for the PLATAO (simulation system for air traffic controllers training). “The Atech award confirms the value of Vortex OpenSplice especially in the highly distributed and mission-critical systems found in aerospace and aviation,” said Spiros Motsenigos, Vice President of US Sales, PrismTech. “Vortex is already in use in similar training simulation systems in Europe and the US. Thanks to the high performance of Vortex, PrismTech continues to serve as a trusted DDS innovator for a variety of simulation systems providers throughout the industry.” For Atech, key features of Vortex OpenSplice are its support for automatic discovery, shared memory architecture, configurable Quality-of-Service (QoS) framework and portability of the platform, which together enable system-wide scalability and save valuable development time, particularly when integrating legacy systems. With the use of PrismTech’s world-class tooling and professional services, Atech is able to successfully meet stringent development milestones. “Vortex OpenSplice provides significant performance capabilities in our solution,” said Fabio Cocchi S. Eiras, Project Director at Atech, a subsidiary of Embraer Defense & Security. “We were specifically interested in a data sharing platform based on the Data Distribution Service standard because of its proven performance, reliability and security, and Vortex delivers the right DDS-based solution for our requirements.” Vortex OpenSplice is a key component of PrismTech’s Vortex Intelligent Data Sharing Platform, a suite of interoperable Internet of Things (IoT) enabling technologies based on the Object Management Group™’s (OMG) Data Distribution Service (DDS) for Real-time Systems standard. Vortex provides secure, real-time data connectivity independent of network configuration (LAN or WAN, wired, wireless, mobile) or underlying platform technologies. It can be used by applications to enable seamless data sharing across server, embedded, web, mobile, fog and cloud environments. Read the press release at: http://www.prismtech.com/news/atech-selects-prismtech-vortex-opensplice-brazilian-air-traffic-control-simulation-platform
  17. Smarter Grid Solutions Deploys PrismTech’s Vortex OpenSplice in Active Network Management Portfolio to Deliver More Efficient Power Distribution Solutions Vortex OpenSplice provides high performance, real-time data sharing for next generation smart grid and power management systems PrismTech, a global leader in software platforms for distributed systems, today announced that Smarter Grid Solutions is deploying its Vortex OpenSplice in its Active Network Management product portfolio to deliver more efficient power distribution solutions. Smart Grids are increasingly being seen as a solution for the challenges currently being faced by power companies and utilities, from connecting higher volumes of renewables and low carbon technologies such as electric vehicles and demand response, to finding more economic ways to meet peaks in electricity demand. Smarter Grid Solutions’ patented Active Network Management (ANM) technology can help the power industry overcome many of the technical challenges involved in delivering a smart grid. ANM allows power distribution networks to be managed in real-time, thus maximizing existing infrastructure capacity through active management of power generators and associated network assets. This allows for predictable, efficient power flow through grids, and reliable power for end users. Due to the increasingly distributed nature of power generation, real-time management of these systems is required in order to avoid grid malfunctions. Renewable power is partially responsible for the increasingly distributed nature of power generation, as power distributors seek to take full advantage of it by monitoring real-time changes in demand and matching supply efficiently to meet this demand. To cater for this, Smarter Grid Solutions needed a solution that could provide high levels of real-time data and system scalability to accommodate far greater numbers of generators than is currently possible. PrismTech’s Vortex OpenSplice is the leading (commercial and Open Source) implementation of the Object Management Group's (OMG) Data Distribution Service (DDS) for Real-Time Systems standard. Vortex OpenSplice has been designed to optimally address the real-time information distribution and management challenges posed by high performance real-time data-processing systems. Vortex OpenSplice was chosen by Smarter Grid Solutions as it allowed it to leverage the performance and scalability benefits that are inherent in the product. The extensive quality of service (QoS) support in Vortex OpenSplice helps guarantee predictable and reliable delivery of real-time data, which is vital in energy distribution management. The scalable nature of Vortex OpenSplice enables Smarter Grid Solutions to integrate their network management technology into an increasing variety of energy grids regardless of size. This results in increased efficiency and helps maximize the capacity of current infrastructure. “As a company, Smarter Grid Solutions is proactive in selectively leveraging proven, best of breed technologies and approaches to the design, development and deployment of our industry leading solutions. The increasing penetration of smart Distributed Energy Resources (DER), and associated high dependence upon these network assets means that both innovative and scalable control philosophies are needed in both the near and medium term to enable a whole new raft of service capabilities for energy provision, storage and delivery. Smarter Grid Solutions is increasingly embedding the DDS standard within their product portfolio, both within the platform at the Inter-Process Communications layer and as a key mechanism for real-time data exchange, with intelligent nodes dispersed upon the physical power networks. The provenance of Vortex OpenSplice has been invaluable in the evolution of the ANM Platform and operates at the heart of the company’s mission critical systems, currently deployed in both the UK and North America,” said Neil McNeill, Head of Technology, Smarter Grid Solutions. Read the full press releast at: http://www.prismtech.com/news/smarter-grid-solutions-deploys-prismtech-vortex-opensplice-active-network-management-portfolio
  18. Hi, following the examples of the Tutorial fo isocpp I create a publisher and a writer in this way: dds::pub::qos::PublisherQos pubQos = dp.default_publisher_qos() << dds::core::policy::Partition(partition_name); dds::pub::Publisher pub(dp, pubQos); dds::pub::qos::DataWriterQos dwqos = topicQos; dwqos << dds::core::policy::WriterDataLifecycle::ManuallyDisposeUnregisteredInstances(); dds::topic::Topic<DATA::MY_DATA> my_topic(dp, "DATA_MY_DATA", topicQos); my_dw = dds::pub::DataWriter<DATA::MY_DATA>(pub, my_topic, dwqos); As soon as I create the DataWriter my_dw, the liveliness on the subscriber changes reflecting the presence of a new publisher. How can my publisher leave and re-join a topic without destroy the c++ object? Massimo.
  19. PrismTech’s Vortex OpenSplice Selected by Fujitsu for 1FINITY Networking Platform - Vortex OpenSplice will help enable a data-centric provisioning framework for new Fujitsu product Boston, MA, USA – September 14, 2015 – PrismTech™, a global leader in software platforms for distributed systems, today announced that Fujitsu has selected Vortex™ OpenSplice™ as its data-centric middleware solution for a new provisioning framework for its revolutionary 1FINITY™ Networking Platform. This new category of network equipment spans access, packet and optical technologies. The revamped provisioning solution supports the Fujitsu SDN/NFV architecture, building upon open industry standards such as NETCONF and YANG. The vital task of robust data connectivity between platform components is provided by PrismTech’s Vortex OpenSplice, a product proven in numerous business and mission-critical environments in markets such as Aerospace & Defense, Smart Energy, Industrial Automation, Transportation, Healthcare and Telecommunications. Vortex OpenSplice enables decoupling between interfaces, making the provisioning framework easier to maintain and extend. Loose coupling will help reduce system complexity and make the integration of new components much easier. It will also help enable applications that are portable across products. Fujitsu expects to be able to make more frequent product updates and release new features to market more quickly, something that is key to maintaining market leadership in a highly competitive and fast evolving market. Once deployed, the new provisioning framework will allow the next generation of network equipment based on the 1FINITY platform to be configured more quickly and easily, with the benefit that providers will be able to provision new services more efficiently, responding to the changing needs of their end users in a much more responsive way. “PrismTech is proud to be a partner of Fujitsu and supports their agile services network vision. Fujitsu is once again shaping the future of trusted communication networks whilst maintaining the highest standards of development and release management; we are delighted that they have selected PrismTech’s Vortex to be part of their innovative vision,” said Spiros Motsenigos, VP US Sales, PrismTech. Vortex OpenSplice is a key component of PrismTech’s Vortex Intelligent Data Sharing Platform, a suite of interoperable Internet of Things (IoT) enabling technologies based on the Object Management Group’s (OMG) Data Distribution Service (DDS) for Real-time Systems standard. Vortex provides secure, real-time data connectivity independent of network configuration (LAN or WAN, wired, wireless, mobile) or underlying platform technologies. It can be used by applications to enable seamless data sharing across server, embedded, web, mobile or cloud environments. http://www.prismtech.com/news/prismtech-vortex-opensplice-selected-fujitsu-1finity-networking-platform
  20. profanter

    Vortex Web + OpenSplice

    Hi, I've a problem connecting Vortex Web with Vortex OpenSplice and would be very happy if you could help me solving the problem. (We have an academic evaluation license and thus not eligible for direct support) Following simple test setup: Vortex OpenSplice uses the default ospl.xml NodeCpp: ISO C++ node which should listen on a topic. NodeJS: JavaScript Application on the browser which should talk through Vortex Web to NodeCpp. It just sends out a message every second. Vortex Web is started with the included play server (start script) and default settings (as descript in the Chat example). Node1 (ISO C++): Creates a DataReaderListener and listens on the topic. Nothing more. (Domain ID: 0, Topic: Chatter) Node2: (JavaScript): Uses Vortex Web client libraries to create a DataWriter (same as the example Chat code) (Domain ID: 0, Topic: Chatter) Unfortunately NodeCpp doesn't receive messages from NodeJS, at least not always (see below). Tests: I tested adding a DataReader to NodeJS in JavaScript and started a new Web Browser instance. Both instances get all the messages originated by a JavaScript node, but NodeCpp doesn't get any. Then I created an additional C++ node which publishes data. This data is successfully sent to NodeCpp, but not to NodeJS. When I start NodeCpp after NodeJS (including Vortex Web), NodeCpp gets about 8 to 10 messages (i.e. transmission works for about 10 seconds), then there are no more messages received. I've attached the output log of Vortex Web below: - First only the Vortex Web Play server is started - At line 227 (after about 15 seconds) the C++ node (NodeCpp) is started - Line 371 to 403: Those messages are successfuly received by NodeCpp - Line 404: from here onwards NodeCpp doesn't get any more messages from NodeJs It's not really clear to me why Vortex Web says: Remove remote Participant [1b52ac4d.000002b3.00000001 PARTICIP] (disposed or lease duration expired). Related entities are removed. If I now just restart NodeCpp it doesn't even get one messages, even if Vortex Web and NodeJs are still publishing. Problem Source: It looks to me that Vortex Web is not properly configured. Do you have any clue what the problem might be? Thanks for any Help! Stefan -------------------------------------------------------------------------------------------------- 1 Play server process ID is 11803 2 [info] play - Application started (Prod) 3 [debug] o.j.n.c.s.n.SelectorUtil - Using select timeout of 500 4 [debug] o.j.n.c.s.n.SelectorUtil - Epoll-bug workaround enabled = false 5 [info] play - Listening for HTTP on /0:0:0:0:0:0:0:0:9000 6 [info] a.e.s.Slf4jLogger - Slf4jLogger started 7 [debug] vortex.web.ctrl - -- listing properties -- 8 java.runtime.name=Java(TM) SE Runtime Environment 9 sun.boot.library.path=/opt/Oracle_Java/jdk1.8.0_45/jre/lib/... 10 java.vm.version=25.45-b02 11 java.vm.vendor=Oracle Corporation 12 java.vendor.url=http://java.oracle.com/ 13 path.separator=: 14 java.vm.name=Java HotSpot(TM) 64-Bit Server VM 15 file.encoding.pkg=sun.io 16 user.country=US 17 sun.java.launcher=SUN_STANDARD 18 sun.os.patch.level=unknown 19 java.vm.specification.name=Java Virtual Machine Specification 20 user.dir=/home/user/workspace/InRoPE 21 java.runtime.version=1.8.0_45-b14 22 java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment 23 java.endorsed.dirs=/opt/Oracle_Java/jdk1.8.0_45/jre/lib/... 24 os.arch=amd64 25 java.io.tmpdir=/tmp 26 line.separator= 27 28 java.vm.specification.vendor=Oracle Corporation 29 os.name=Linux 30 sun.jnu.encoding=UTF-8 31 java.library.path=/home/user/workspace/VortexOpenS... 32 sun.nio.ch.bugLevel= 33 java.specification.name=Java Platform API Specification 34 java.class.version=52.0 35 sun.management.compiler=HotSpot 64-Bit Tiered Compilers 36 os.version=3.18.2-031802-generic 37 user.home=/home/user 38 user.timezone=Europe/Berlin 39 java.awt.printerjob=sun.print.PSPrinterJob 40 file.encoding=UTF-8 41 java.specification.version=1.8 42 user.name=user 43 java.class.path=/home/user/workspace/VortexPlatf... 44 java.vm.specification.version=1.8 45 sun.arch.data.model=64 46 java.home=/opt/Oracle_Java/jdk1.8.0_45/jre 47 sun.java.command=play.core.server.NettyServer /home/pr... 48 java.specification.vendor=Oracle Corporation 49 user.language=en 50 awt.toolkit=sun.awt.X11.XToolkit 51 java.vm.info=mixed mode 52 java.version=1.8.0_45 53 java.ext.dirs=/opt/Oracle_Java/jdk1.8.0_45/jre/lib/... 54 sun.boot.class.path=/opt/Oracle_Java/jdk1.8.0_45/jre/lib/... 55 java.vendor=Oracle Corporation 56 dds.types.classpath=/home/user/workspace/InRoPE/buil... 57 file.separator=/ 58 java.vendor.url.bug=http://bugreport.sun.com/bugreport/ 59 sun.cpu.endian=little 60 sun.io.unicode.encoding=UnicodeLittle 61 sun.desktop=gnome 62 sun.cpu.isalist= 63 64 [info] vortex.web.ctrl - Setting Property: Tuple2(_1: dds.listeners.useTransportThread, _2: false) 65 [info] vortex.web.ctrl - Setting Property: Tuple2(_1: ddsi.timer.threadPool.size, _2: 1) 66 [info] vortex.web.ctrl - Setting Property: Tuple2(_1: ddsi.receiver.threadPool.size, _2: 1) 67 [info] vortex.web.ctrl - Setting Property: Tuple2(_1: ddsi.dataProcessor.threadPool.size, _2: 1) 68 [info] vortex.web.ctrl - Setting Property: Tuple2(_1: ddsi.acknackProcessor.threadPool.size, _2: 1) 69 [info] vortex.web.ctrl - Setting Property: Tuple2(_1: ddsi.receiver.udp.buffer.size, _2: 8192) 70 [info] vortex.web.ctrl - Setting Property: Tuple2(_1: ddsi.participant.leaseDuration, _2: 300000) 71 [info] vortex.web.ctrl - file:/home/user/workspace/InRoPE/build/gui_web/gui_web_idls.jar loaded 72 [debug] c.dds.monitor - Monitor not found 73 [info] cafe.dds - Unlimited license software. 74 [debug] cafe.ddsi - Unlimited license software. 75 [debug] cafe.ddsi.net - Will use network interface wlan0 with address /192.168.20.142/24 [/192.168.20.255] 76 [info] c.ddsi.entities - Created a new participant 'P0' with GUID: [007f0101.00002e1b.00000000 PARTICIP] 77 [info] cafe.ddsi.net - P0 uses networking interface: name:wlan0 (wlan0) 78 [info] cafe.ddsi.net - P0 listens Discovery protocol on multicast IP: 239.255.0.1:7400 79 [info] cafe.ddsi.net - P0 listens Discovery protocol on unicast IP : 192.168.20.142:7410 80 [info] cafe.ddsi.net - P0 listens Data protocol on multicast IP : 239.255.0.1:7401 81 [info] cafe.ddsi.net - P0 listens Data protocol on unicast IP : 192.168.20.142:7411 82 [debug] cafe.ddsi.disc - Discovered a remote Participant: [007f0101.00002e1b.00000000 PARTICIP] 83 [debug] cafe.ddsi.net - Waiting 2 seconds for DDSI discovery 84 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 PUBLI_WR] send historical data (0 samples) to Reader [007f0101.00002e1b.00000000 PUBLI_RE] 85 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 TOPIC_WR] send historical data (0 samples) to Reader [007f0101.00002e1b.00000000 TOPIC_RE] 86 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 SUBSC_WR] send historical data (0 samples) to Reader [007f0101.00002e1b.00000000 SUBSC_RE] 87 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 SUBSC_WR] send historical data (0 samples) to Reader [007f0101.00002e1b.00000000 SUBSC_RE] 88 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 SUBSC_WR] send historical data (0 samples) to Reader [007f0101.00002e1b.00000000 SUBSC_RE] 89 [debug] vortex.web.ctrl - Creating a new EntityManager. 90 [info] vortex.web.ctrl - Entity Manager: Controller Connection Request 91 [info] vortex.web.ctrl - Authorization Token = uid:pwd 92 [info] vortex.web.auth - AccessControlService - No service access controller configured. Using default. 93 [info] vortex.web.auth - Default Service Access - login with token : uid:pwd 94 [debug] o.j.n.h.c.h.w.WebSocketServerHandshaker13 - Channel -1909197818 WS Version 13 server handshake 95 [debug] o.j.n.h.c.h.w.WebSocketServerHandshaker13 - WS Version 13 Server Handshake key: LVQ0daZVJFITuT90E4JF+Q==. Response: 9AR8K4Odylo7o5Vk0Jb/lf6oVoU=. 96 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 97 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=147 98 [info] play - Starting application default Akka system. 99 [debug] vortex.web.ctrl - EntityManagerActor - new for session id: uid:pwd 100 [info] vortex.web.ctrl - EntityManagerActor#onReceive - handling {"h":{"cid":2,"ek":0,"sn":0},"b":{"did":0,"tn":"Chatter","tt":"domain.idl.Chat.ChatMessage","trt":"domain::idl::Chat::ChatMessage","qos":[null]}} 101 [info] vortex.web.ctrl - EntityManagerActor - Received create Topic command. 102 [debug] vortex.web.ctrl - DSParticipant, 0, creating web topic, Chatter : domain.idl.Chat.ChatMessage : domain::idl::Chat::ChatMessage. 103 [debug] vortex.web.ctrl - DSParticipant, 0, new web topic, Chatter : domain.idl.Chat.ChatMessage : domain::idl::Chat::ChatMessage. 104 [debug] vortex.web.ctrl - DSParticipant, 0, create dds topic, Chatter : domain.idl.Chat.ChatMessage : domain::idl::Chat::ChatMessage. 105 [debug] v.web.entity - Encoded policies: 106 [debug] v.web.entity - WebTopic - new - Chatter 107 [debug] v.web.entity - WebTopic - created - Chatter ==> 100787ca-dcb2-4e0d-a92d-8a58b5561bb1 108 [info] vortex.web.ctrl - EntityManagerActor - replying with command: {"h":{"cid":0,"ek":0,"sn":0},"b":{"eid":"100787ca-dcb2-4e0d-a92d-8a58b5561bb1"}} 109 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=80 110 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 111 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=71 112 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 113 [info] vortex.web.ctrl - EntityManagerActor#onReceive - handling {"h":{"cid":2,"ek":1,"sn":1},"b":{"did":0,"tn":"Chatter","qos":[null]}} 114 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=71 115 [debug] vortex.web.ctrl - EntityManagerActor - Received create DataReader command. 116 [debug] vortex.web.ctrl - DSParticipant, 0, create web reader, Chatter. 117 [debug] v.web.entity - Encoded policies: 118 [debug] vortex.web.ctrl - DSParticipant, 0, create subscriber, . 119 [debug] vortex.web.ctrl - DSParticipant, 0, creating a new subscriber, . 120 [debug] c.ddsi.entities - Created local Subscriber '[007f0101.00002e1b.00000000 0000014a]': 121 [debug] vortex.web.ctrl - DSParticipant, 0, looking up topic, Chatter. 122 [debug] v.web.entity - Encoded policies: 123 [debug] vortex.web.ctrl - DSSubscriber(0,), create web reader, Chatter : . 124 [info] c.ddsi.entities - Created local Reader [007f0101.00002e1b.00000000 00000207] on Topic 'Chatter' 125 [debug] v.web.entity - WebReader - new - 0:Chatter:: 126 [debug] v.web.entity - WebReader - created - 0:Chatter:: ==> cb3974d0-f749-420e-bc69-ee8d9758e884 127 [debug] vortex.web.ctrl - DSSubscriber(0,), created a new web reader, Chatter : . 128 [info] vortex.web.ctrl - EntityManagerActor - replying with command: {"h":{"cid":0,"ek":1,"sn":1},"b":{"eid":"cb3974d0-f749-420e-bc69-ee8d9758e884"}} 129 [debug] cafe.ddsi.disc - Discovered a remote Reader [007f0101.00002e1b.00000000 00000207] on Topic 'Chatter' 130 [info] vortex.web.ctrl - EntityManagerActor#onReceive - handling {"h":{"cid":2,"ek":2,"sn":2},"b":{"did":0,"tn":"Chatter","qos":[null]}} 131 [debug] cafe.ddsi.disc - Topic 'Chatter' has type: domain::idl::Chat::ChatMessage 132 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=80 133 [debug] vortex.web.ctrl - EntityManagerActor - Received create DataWriter command. 134 [debug] vortex.web.ctrl - DSParticipant, 0, create web writer, Chatter. 135 [debug] v.web.entity - Encoded policies: 136 [debug] vortex.web.ctrl - DSParticipant, 0, create publisher, . 137 [debug] vortex.web.ctrl - DSParticipant, 0, creatin a new subscriber, . 138 [debug] c.ddsi.entities - Created local Publisher '[007f0101.00002e1b.00000000 0000034b]': 139 [debug] vortex.web.ctrl - DSParticipant, 0, looking up topic, Chatter. 140 [debug] v.web.entity - Encoded policies: 141 [debug] vortex.web.ctrl - DSPublisher(0,), create web writer, Chatter : . 142 [info] vortex.web.ctrl - Request to connect to Web Reader: cb3974d0-f749-420e-bc69-ee8d9758e884 143 [debug] v.web.entity - WebReader - lease - cb3974d0-f749-420e-bc69-ee8d9758e884 144 [debug] v.web.entity - WebReader - connect - cb3974d0-f749-420e-bc69-ee8d9758e884 145 [debug] v.web.entity - WebReader - start - cb3974d0-f749-420e-bc69-ee8d9758e884 146 [debug] v.web.entity - RichDataReader - Adding listener to reader; com.prismtech.cafe.sub.if@1d197148 147 [debug] v.web.entity - RichDataReader - Reader does not have any existing listeners. Adding multicast listener; com.prismtech.cafe.sub.if@1d197148 148 [info] c.ddsi.entities - Created local Writer [007f0101.00002e1b.00000000 00000402] on Topic 'Chatter' 149 [debug] cafe.ddsi.disc - Check if remote Reader [007f0101.00002e1b.00000000 00000207] matches local Writer [007f0101.00002e1b.00000000 00000402] 150 [info] cafe.ddsi.disc - New match between remote Reader [007f0101.00002e1b.00000000 00000207] and local Writer [007f0101.00002e1b.00000000 00000402] 151 [debug] v.web.entity - WebWriter - new - 0:Chatter:: 152 [debug] v.web.entity - RichDataReader - Done adding listener to reader; com.prismtech.cafe.sub.if@1d197148 153 [debug] o.j.n.h.c.h.w.WebSocketServerHandshaker13 - Channel 1098148721 WS Version 13 server handshake 154 [debug] o.j.n.h.c.h.w.WebSocketServerHandshaker13 - WS Version 13 Server Handshake key: zdp2xYkRvffJjIpZAo7etA==. Response: F5gk+8D7mRLNrl9LRL+N4++QxQw=. 155 [debug] v.web.entity - WebWriter - created - 0:Chatter:: ==> a9b9007c-d5cb-4612-813d-ebbb8a6c48bb 156 [debug] vortex.web.ctrl - DSPublisher(0,), created a new web writer, Chatter : . 157 [debug] cafe.ddsi.disc - Discovered a remote Writer [007f0101.00002e1b.00000000 00000402] on Topic 'Chatter' 158 [debug] cafe.ddsi.disc - Topic 'Chatter' has type: domain::idl::Chat::ChatMessage 159 [info] vortex.web.ctrl - EntityManagerActor - replying with command: {"h":{"cid":0,"ek":2,"sn":2},"b":{"eid":"a9b9007c-d5cb-4612-813d-ebbb8a6c48bb"}} 160 [debug] cafe.ddsi.disc - Check if remote Writer [007f0101.00002e1b.00000000 00000402] matches local Reader [007f0101.00002e1b.00000000 00000207] 161 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=80 162 [info] cafe.ddsi.disc - New match between remote Writer [007f0101.00002e1b.00000000 00000402] and local Reader [007f0101.00002e1b.00000000 00000207] 163 [info] vortex.web.ctrl - EntityManager#writer - Request to connect to WebWriter: a9b9007c-d5cb-4612-813d-ebbb8a6c48bb 164 [debug] v.web.entity - WebWriter - lease - a9b9007c-d5cb-4612-813d-ebbb8a6c48bb 165 [debug] o.j.n.h.c.h.w.WebSocketServerHandshaker13 - Channel 352770408 WS Version 13 server handshake 166 [debug] o.j.n.h.c.h.w.WebSocketServerHandshaker13 - WS Version 13 Server Handshake key: Di54n0d61OLn8nfUvCH6sw==. Response: xuBnn7M6/PB8Hu8+E8c1GQDcMF8=. 167 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 168 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 169 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 170 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 171 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 172 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 173 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 174 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 175 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 176 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 177 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 178 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 179 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 180 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 181 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 182 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 183 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 184 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 185 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 186 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 187 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 188 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 189 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 190 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 191 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 192 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 193 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 194 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 195 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 196 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 197 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 198 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 199 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 200 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 201 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 202 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 203 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 204 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 205 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 206 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 207 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 208 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 209 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 210 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 211 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 212 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 213 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 214 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 215 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 216 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 217 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 218 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 219 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 220 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 221 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 222 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 223 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 224 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 225 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 226 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 227 [debug] cafe.ddsi.disc - Discovered a remote Participant: [1b52ac4d.000002b3.00000001 PARTICIP] 228 [debug] cafe.ddsi.disc - Discovered a remote Participant: [1b52ac4d.00000099.00000001 PARTICIP] 229 [debug] cafe.ddsi.disc - Discovered a remote Participant: [1b52ac4d.00000094.00000001 PARTICIP] 230 [debug] cafe.ddsi.disc - Discovered a remote Participant: [1b52ac4d.00000053.00000001 PARTICIP] 231 [debug] cafe.ddsi.disc - Discovered a remote Participant: [1b52ac4d.00000005.00000001 PARTICIP] 232 [debug] cafe.ddsi.disc - Discovered a remote Participant: [1b52ac4d.0000009f.00000001 PARTICIP] 233 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 PUBLI_WR] send historical data (1 samples) to Reader [1b52ac4d.0000009f.00000001 PUBLI_RE] 234 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 TOPIC_WR] send historical data (1 samples) to Reader [1b52ac4d.0000009f.00000001 TOPIC_RE] 235 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 CMPAR_WR] send historical data (1 samples) to Reader [1b52ac4d.0000009f.00000001 CMPAR_RE] 236 [warn] cafe.ddsi.msgs - Received DATA message for unknown Reader: CMPAR_RE 237 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 CMPUB_WR] send historical data (1 samples) to Reader [1b52ac4d.0000009f.00000001 CMPUB_RE] 238 [warn] cafe.ddsi.msgs - Received DATA message for unknown Reader: CMPUB_RE 239 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 CMSUB_WR] send historical data (1 samples) to Reader [1b52ac4d.0000009f.00000001 CMSUB_RE] 240 [warn] cafe.ddsi.msgs - Received DATA message for unknown Reader: CMSUB_RE 241 [warn] cafe.ddsi.msgs - Local Writer [007f0101.00002e1b.00000000 SUBSC_WR] received an AckNack message from an unknown Reader: [1b52ac4d.0000009f.00000001 SUBSC_RE] 242 [debug] cafe.ddsi.msgs - Writer [007f0101.00002e1b.00000000 SUBSC_WR] send historical data (1 samples) to Reader [1b52ac4d.0000009f.00000001 SUBSC_RE] 243 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000099.00000001 00000202] on Topic 'd_status' 244 [debug] cafe.ddsi.disc - Topic 'd_status' has type: durabilityModule2:_status_s 245 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000099.00000001 00000202] matches local Reader [007f0101.00002e1b.00000000 00000207] 246 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000099.00000001 00000202] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 247 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000099.00000001 00000302] on Topic 'd_newGroup' 248 [debug] cafe.ddsi.disc - Topic 'd_newGroup' has type: durabilityModule2:_newGroup_s 249 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000099.00000001 00000302] matches local Reader [007f0101.00002e1b.00000000 00000207] 250 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000099.00000001 00000302] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 251 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000202] on Topic 'DCPSParticipant' 252 [debug] cafe.ddsi.disc - Topic 'DCPSParticipant' has type: kernelModule::v_participantInfo 253 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000202] matches local Reader [007f0101.00002e1b.00000000 00000207] 254 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000202] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 255 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000099.00000001 00000402] on Topic 'd_groupsRequest' 256 [debug] cafe.ddsi.disc - Topic 'd_groupsRequest' has type: durabilityModule2:_groupsRequest_s 257 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000099.00000001 00000402] matches local Reader [007f0101.00002e1b.00000000 00000207] 258 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000099.00000001 00000402] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 259 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000302] on Topic 'CMParticipant' 260 [debug] cafe.ddsi.disc - Topic 'CMParticipant' has type: kernelModule::v_participantCMInfo 261 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000302] matches local Reader [007f0101.00002e1b.00000000 00000207] 262 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000302] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 263 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000099.00000001 00000502] on Topic 'd_sampleRequest' 264 [debug] cafe.ddsi.disc - Topic 'd_sampleRequest' has type: durabilityModule2:_sampleRequest_s 265 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000099.00000001 00000502] matches local Reader [007f0101.00002e1b.00000000 00000207] 266 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000099.00000001 00000502] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 267 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000402] on Topic 'DCPSSubscription' 268 [debug] cafe.ddsi.disc - Topic 'DCPSSubscription' has type: kernelModule::v_subscriptionInfo 269 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000402] matches local Reader [007f0101.00002e1b.00000000 00000207] 270 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000402] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 271 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000099.00000001 00000602] on Topic 'd_nameSpaces' 272 [debug] cafe.ddsi.disc - Topic 'd_nameSpaces' has type: durabilityModule2:_nameSpaces_s 273 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000099.00000001 00000602] matches local Reader [007f0101.00002e1b.00000000 00000207] 274 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000099.00000001 00000602] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 275 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000502] on Topic 'CMDataReader' 276 [debug] cafe.ddsi.disc - Topic 'CMDataReader' has type: kernelModule::v_dataReaderCMInfo 277 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000502] matches local Reader [007f0101.00002e1b.00000000 00000207] 278 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000502] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 279 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000602] on Topic 'DCPSPublication' 280 [debug] cafe.ddsi.disc - Topic 'DCPSPublication' has type: kernelModule::v_publicationInfo 281 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000602] matches local Reader [007f0101.00002e1b.00000000 00000207] 282 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000602] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 283 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000702] on Topic 'CMDataWriter' 284 [debug] cafe.ddsi.disc - Topic 'CMDataWriter' has type: kernelModule::v_dataWriterCMInfo 285 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000702] matches local Reader [007f0101.00002e1b.00000000 00000207] 286 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000702] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 287 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000802] on Topic 'CMSubscriber' 288 [debug] cafe.ddsi.disc - Topic 'CMSubscriber' has type: kernelModule::v_subscriberCMInfo 289 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000802] matches local Reader [007f0101.00002e1b.00000000 00000207] 290 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000802] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 291 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000902] on Topic 'CMPublisher' 292 [debug] cafe.ddsi.disc - Topic 'CMPublisher' has type: kernelModule::v_publisherCMInfo 293 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000902] matches local Reader [007f0101.00002e1b.00000000 00000207] 294 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000902] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 295 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000a02] on Topic 'DCPSTopic' 296 [debug] cafe.ddsi.disc - Topic 'DCPSTopic' has type: kernelModule::v_topicInfo 297 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000a02] matches local Reader [007f0101.00002e1b.00000000 00000207] 298 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000a02] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 299 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.000002b3.00000001 00000207] on Topic 'Chatter' 300 [debug] cafe.ddsi.disc - Topic 'Chatter' has type: domain::idl::Chat::ChatMessage 301 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.000002b3.00000001 00000207] matches local Writer [007f0101.00002e1b.00000000 00000402] 302 [info] cafe.ddsi.disc - New match between remote Reader [1b52ac4d.000002b3.00000001 00000207] and local Writer [007f0101.00002e1b.00000000 00000402] 303 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000b02] on Topic 'DCPSHeartbeat' 304 [debug] cafe.ddsi.disc - Topic 'DCPSHeartbeat' has type: kernelModule::v_heartbeatInfo 305 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000099.00000001 00000b07] on Topic 'd_nameSpaces' 306 [debug] cafe.ddsi.disc - Topic 'd_nameSpaces' has type: durabilityModule2:_nameSpaces_s 307 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000099.00000001 00000b07] matches local Writer [007f0101.00002e1b.00000000 00000402] 308 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000099.00000001 00000b07] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 309 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000b02] matches local Reader [007f0101.00002e1b.00000000 00000207] 310 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000099.00000001 00000c07] on Topic 'd_nameSpacesRequest' 311 [debug] cafe.ddsi.disc - Topic 'd_nameSpacesRequest' has type: durabilityModule2:_nameSpacesRequest_s 312 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000b02] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 313 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000099.00000001 00000c07] matches local Writer [007f0101.00002e1b.00000000 00000402] 314 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000099.00000001 00000c07] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 315 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000099.00000001 00000702] on Topic 'd_nameSpacesRequest' 316 [debug] cafe.ddsi.disc - Topic 'd_nameSpacesRequest' has type: durabilityModule2:_nameSpacesRequest_s 317 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000099.00000001 00000d07] on Topic 'd_status' 318 [debug] cafe.ddsi.disc - Topic 'd_status' has type: durabilityModule2:_status_s 319 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000099.00000001 00000702] matches local Reader [007f0101.00002e1b.00000000 00000207] 320 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000099.00000001 00000d07] matches local Writer [007f0101.00002e1b.00000000 00000402] 321 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000099.00000001 00000d07] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 322 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000099.00000001 00000702] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 323 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000099.00000001 00000e07] on Topic 'd_groupsRequest' 324 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000c02] on Topic 'DCPSCandMCommand' 325 [debug] cafe.ddsi.disc - Topic 'd_groupsRequest' has type: durabilityModule2:_groupsRequest_s 326 [debug] cafe.ddsi.disc - Topic 'DCPSCandMCommand' has type: kernelModule::v_controlAndMonitoringCommand 327 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000099.00000001 00000e07] matches local Writer [007f0101.00002e1b.00000000 00000402] 328 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000099.00000001 00000e07] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 329 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000c02] matches local Reader [007f0101.00002e1b.00000000 00000207] 330 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000c02] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 331 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000099.00000001 00000f07] on Topic 'd_deleteData' 332 [debug] cafe.ddsi.disc - Topic 'd_deleteData' has type: durabilityModule2:_deleteData_s 333 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000099.00000001 00000f07] matches local Writer [007f0101.00002e1b.00000000 00000402] 334 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000099.00000001 00000802] on Topic 'd_deleteData' 335 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000099.00000001 00000f07] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 336 [debug] cafe.ddsi.disc - Topic 'd_deleteData' has type: durabilityModule2:_deleteData_s 337 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000099.00000001 00000802] matches local Reader [007f0101.00002e1b.00000000 00000207] 338 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000099.00000001 00001007] on Topic 'd_newGroup' 339 [debug] cafe.ddsi.disc - Topic 'd_newGroup' has type: durabilityModule2:_newGroup_s 340 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000099.00000001 00000802] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 341 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000099.00000001 00001007] matches local Writer [007f0101.00002e1b.00000000 00000402] 342 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000099.00000001 00001007] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 343 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000005.00000001 00000d03] on Topic 'DCPSDelivery' 344 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000099.00000001 00001107] on Topic 'd_sampleRequest' 345 [debug] cafe.ddsi.disc - Topic 'DCPSDelivery' has type: kernelModule::v_deliveryInfo 346 [debug] cafe.ddsi.disc - Topic 'd_sampleRequest' has type: durabilityModule2:_sampleRequest_s 347 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000005.00000001 00000d03] matches local Reader [007f0101.00002e1b.00000000 00000207] 348 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000099.00000001 00001107] matches local Writer [007f0101.00002e1b.00000000 00000402] 349 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000005.00000001 00000d03] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 350 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000099.00000001 00001107] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 351 [debug] cafe.ddsi.disc - Discovered a remote Writer [1b52ac4d.00000099.00000001 00000902] on Topic 'd_sampleChain' 352 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000099.00000001 00001207] on Topic 'd_sampleChain' 353 [debug] cafe.ddsi.disc - Topic 'd_sampleChain' has type: durabilityModule2:_sampleChain_s 354 [debug] cafe.ddsi.disc - Topic 'd_sampleChain' has type: durabilityModule2:_sampleChain_s 355 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000099.00000001 00001207] matches local Writer [007f0101.00002e1b.00000000 00000402] 356 [debug] cafe.ddsi.disc - Check if remote Writer [1b52ac4d.00000099.00000001 00000902] matches local Reader [007f0101.00002e1b.00000000 00000207] 357 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000099.00000001 00001207] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 358 [debug] cafe.ddsi.disc - Remote Writer [1b52ac4d.00000099.00000001 00000902] and Local Reader [007f0101.00002e1b.00000000 00000207] have different Topics 359 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000053.00000001 00000204] on Topic 'DCPSDelivery' 360 [debug] cafe.ddsi.disc - Topic 'DCPSDelivery' has type: kernelModule::v_deliveryInfo 361 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000053.00000001 00000204] matches local Writer [007f0101.00002e1b.00000000 00000402] 362 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000053.00000001 00000204] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 363 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.0000009f.00000001 00000607] on Topic 'DCPSCandMCommand' 364 [debug] cafe.ddsi.disc - Topic 'DCPSCandMCommand' has type: kernelModule::v_controlAndMonitoringCommand 365 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.0000009f.00000001 00000607] matches local Writer [007f0101.00002e1b.00000000 00000402] 366 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.0000009f.00000001 00000607] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 367 [debug] cafe.ddsi.disc - Discovered a remote Reader [1b52ac4d.00000053.00000001 00000307] on Topic 'DCPSCandMCommand' 368 [debug] cafe.ddsi.disc - Topic 'DCPSCandMCommand' has type: kernelModule::v_controlAndMonitoringCommand 369 [debug] cafe.ddsi.disc - Check if remote Reader [1b52ac4d.00000053.00000001 00000307] matches local Writer [007f0101.00002e1b.00000000 00000402] 370 [debug] cafe.ddsi.disc - Remote Reader [1b52ac4d.00000053.00000001 00000307] and Local Writer [007f0101.00002e1b.00000000 00000402] have different Topics 371 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 372 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 373 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 374 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 375 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 376 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 377 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 378 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 379 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 380 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 381 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 382 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 383 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 384 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 385 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 386 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 387 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 388 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 389 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 390 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 391 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 392 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 393 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 394 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 395 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 396 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 397 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 398 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 399 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 400 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 401 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 402 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 403 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 404 [debug] cafe.ddsi.disc - Remove remote Participant [1b52ac4d.000002b3.00000001 PARTICIP] (disposed or lease duration expired). Related entities are removed. 405 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.000002b3.00000001 00000207] 406 [info] cafe.ddsi.disc - Unmatch of remote Reader [1b52ac4d.000002b3.00000001 00000207] with local Writer [007f0101.00002e1b.00000000 00000402] 407 [debug] cafe.ddsi.disc - Remove remote Participant [1b52ac4d.00000099.00000001 PARTICIP] (disposed or lease duration expired). Related entities are removed. 408 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000099.00000001 00000b07] 409 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000099.00000001 00000c07] 410 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000099.00000001 00000d07] 411 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000099.00000001 00000e07] 412 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000099.00000001 00000f07] 413 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000099.00000001 00001007] 414 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000099.00000001 00001107] 415 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000099.00000001 00001207] 416 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000099.00000001 00000202] 417 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000099.00000001 00000302] 418 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000099.00000001 00000402] 419 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000099.00000001 00000502] 420 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000099.00000001 00000602] 421 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000099.00000001 00000702] 422 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000099.00000001 00000802] 423 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000099.00000001 00000902] 424 [debug] cafe.ddsi.disc - Remove remote Participant [1b52ac4d.00000094.00000001 PARTICIP] (disposed or lease duration expired). Related entities are removed. 425 [debug] cafe.ddsi.disc - Remove remote Participant [1b52ac4d.00000053.00000001 PARTICIP] (disposed or lease duration expired). Related entities are removed. 426 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000053.00000001 00000204] 427 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.00000053.00000001 00000307] 428 [debug] cafe.ddsi.disc - Remove remote Participant [1b52ac4d.00000005.00000001 PARTICIP] (disposed or lease duration expired). Related entities are removed. 429 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000302] 430 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000c02] 431 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000202] 432 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000402] 433 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000502] 434 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000602] 435 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000702] 436 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000802] 437 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000902] 438 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000a02] 439 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000b02] 440 [debug] cafe.ddsi.disc - Remove remote Writer [1b52ac4d.00000005.00000001 00000d03] 441 [debug] cafe.ddsi.disc - Remove remote Participant [1b52ac4d.0000009f.00000001 PARTICIP] (disposed or lease duration expired). Related entities are removed. 442 [debug] c.ddsi.entities - Remove remote Reader [1b52ac4d.0000009f.00000001 00000607] 443 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 444 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 445 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 446 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 447 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 448 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 449 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 450 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 451 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 452 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 453 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 454 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 455 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 456 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 457 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 458 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 459 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 460 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 461 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 462 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 463 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 464 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 465 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 466 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 467 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 468 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 469 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 470 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 471 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 472 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 473 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 474 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 475 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 476 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 477 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 478 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 479 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 480 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 481 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 482 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 483 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 484 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 485 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 486 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 487 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 488 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 489 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 490 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 491 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1 492 [debug] o.j.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=67 493 [debug] o.j.n.h.c.h.w.WebSocket08FrameEncoder - Encoding WebSocket Frame opCode=1 length=75 494 ^C[info] play - Shutdown application default Akka system.
  21. bonjefir

    Dynamic topic type discovery

    Hi I have recently read "http://forums.opensplice.org/index.php?/topic/2137-dds-reader-without-data-type/" and found that it was not possible to get one topic type dynamically in previous versions. I want to know whether this feature is available in the latest version of DDS community or even commercial. If it is available, I will appreciate it if you could provide me with an example. I think it is a very important and essential feature (At least I need it now ! ). Thanks in advance for your help. Bonjefir
  22. bonjefir

    Dynamic allocation

    Hi I have written a very simple program containing one class which have only one pointer to domain participant. Given below is the mentioned program: #include <QCoreApplication> #include "publisher.h" #include <QThread> int main(int argc, char *argv[]) { QCoreApplication a(argc, argv); return a.exec(); } #ifndef PUBLISHER_H #define PUBLISHER_H #include <dds/dds.hpp> #include "../IDL/myIDL/myIDL_DCPS.hpp" class Publisher { public: Publisher(); dds::domain::DomainParticipant *dp; }; #endif // PUBLISHER_H #include "publisher.h" Publisher::Publisher() { dp = new dds::domain::DomainParticipant(org::opensplice::domain::default_id()); } But I can not compile this program. The error is: "error: 'static void* dds::core::Reference<DELEGATE>::operator new(size_t) [with DELEGATE = org::opensplice::domain::DomainParticipantDelegate; size_t = long unsigned int]' is private Where does this error come from and what should be done for solving it? Thanks in advance for your help. Bonjefir
  23. bonjefir

    Waitset detach error

    Hi I'm facing an error in my program and I want to know how I can fix it. In my program, I use a waitset for reading data. A readcondition and a guardcondition have been added to this waitset; waitset += readCondition; waitset += guardCond; The scenario is as follows; I am running a function (getData) in a separate thread and wait to receive data in this function by executing "dispatch" function of waitset. template<typename idlType> void myDDS<idlType>::getData() { try { do { // waiting here for the data to be received waitset.dispatch(); } while (getDataLoop == true); // Detaching readCondition and guardCond from the waitset waitset -= guardCond; waitset -= readCondition; } catch (const dds::core::Exception& e) { errorMessage = __PRETTY_FUNCTION__; errorMessage.append(e.what()); #ifdef DEBUG_MODE std::cerr << "Error in " << errorMessage << std::endl; #endif } } Everything look good until I want to exit from my program. At the exit time, I receive the following error: Error in void myDDS<idlType>::getData() [with idlType = myIDLkeyful3KByte::payload] dds::core::AlreadyClosedError : Calling ::wait at /home/bonjefir/HDE/x86_64.linux/include/dcps/C++/isocpp/org/opensplice/core/WaitSetImpl.hpp:87 in org::opensplice::core::WaitSetImpl::ConditionSeqType& org::opensplice::core::WaitSetImpl::wait(org::opensplice::core::WaitSetImpl::ConditionSeqType&, const dds::core::Duration&). DDS API call returned DDS::RETCODE_ALREADY_DELETED Preceding OpenSplice Error Information : Not available - DDS::RETCODE_NO_DATA terminate called after throwing an instance of 'dds::core::Error' what(): dds::core::Error : Calling ::detach_condition at /home/bonjefir/HDE/x86_64.linux/include/dcps/C++/isocpp/org/opensplice/core/WaitSetImpl.hpp:140 in bool org::opensplice::core::WaitSetImpl::detach_condition(const Condition&). DDS API call returned DDS::RETCODE_ERROR Preceding OpenSplice Error Information : Not available - DDS::RETCODE_NO_DATA I don't have any idea what is the problem and how I can fix it. Please help me if you can. Thanks in advance for your help. Bonjefir
  24. bonjefir

    Reliability and History Relation

    Hi I want to know whether history QoS is related to reliability in low rate publishing or not. I have written a program that the interval between two publish is 200 us and set the reliability QoS for both data reader and data writer. But the connection is not reliable until I set the history QoS to KeepLast(10000). So I want to know whether these QoSs are related to each other or not. It's worth mentioning that my connection is reliable for high rate publishing and is independent of history QoS. Thanks in advance for your help. Bonjefir
  25. Hi, I want to know whether there is a function for getting all topics and their related QoSs in one specified domain. I can find all topic names with dbd tool easily but I want to do it directly in my code. Thanks in advance for your help. Bonjefir
×