Hi,
General Dynamics
Hi,
I'm using dds_consumer telegraf(inputs.dds_consumer) for consume dds data and trying to insert this data into influxdb2.1 version using telegraf outputs.influxdb_v2 plugin. However, data insertion in influxdb2 is failing with following error.
shapes-telegraf | 2022-04-06T19:55:00Z E! [agent] Error writing to outputs.influxdb_v2: Post http://localhost:8086/api/v2/write?bucket=metrics&org=company: dial tcp 127.0.0.1:8086: connect: connection refused
We have a need to use DynamicData with a custom transport using the modern C++ API.
I was able to generate and run the custom FILE transport example for C++11 but that uses an IDL defined data type, CustomTransport.
I have a HelloWorld publisher and subscriber that use DynamicData that I was hoping to get working with the custom FILE transport instead of the built-ins transports.
I was hoping I might be able to simply use the custom_transportPlugin.cxx and hpp files generated by the custom transport example and change "CustomTransport" to "dds::core::xtypes::DynamicData".
Using the DDS Modern C++ API 6.1.0
I'm trying to use rti::topic::find_topics() to get all the local topics from my local domain participant but I can't get the correct syntax.
The following throws the runtime exception: Can't create an AnyTopic from a native topic. Try a typed Topic<T> instead
std::vector<dds::topic::AnyTopic> topics;
uint32_t topicCount = rti::topic::find_topics(participant, std::back_inserter(topics));
While this gives a various compilation errors:
On the RTI Code Generator 2.0 Architecture Overview powerpoint (RTI_rttiddsgen_architecture.pptx), it says on the 6th slide that "The AST is equivalent to the simplified XML generated with rtiddsgen 1". Does this mean that rtiddsgen 2 (which, as I understand, comes with RTI Connext version 5.1.0) will no longer output the simplified XML?
I can't seem to generate example C# code that doesn't depend upon .net 4.0. Even the sample code, \rticonnextdds-examples\listeners\cd code, generates an example that gives me the following warnings for the publisher and subscriber code.