Cyclone interoperate with dynamic type discovery

[elijah-utopia]

I am trying to interoperate with RTI and can successfully publish and subscribe between domain participants that both have the type information. However, I can’t subscribe to any topic published by cyclone with either the rtirecordingservice or the rtiadminconsole. (ie tools that acquire the type dynamically)

You have mentioned in a few other forms that you have to stay far away from rti’s stuff because of their licensing. But I wanted to ask if there are any other ways that DDS passes type information. I read on rti's documentation that they don’t support the type field in the PublicationBuiltinTopicData and SubscriptionBuiltinTopicData. Nor do they support the TypeLookup service. Is there any other way that TypeObjects are sent by DDS?

If not then I suppose that rti just doesn’t support it but if there is then I can try to set it up to interoperate.

Thanks!

[eboasson]

Hi @elijah-utopia, what I have seen in some packet captures from other people dealing with some interoperability issues, it looks like RTI does not use the standardized mechanism for type discovery, or more precisely, stuck to an old version that is not part of the XTypes 1.3 spec (not even as deprecated), while Cyclone only supports XTypes 1.3 ... I find it really weird that RTI is the primary author of the specs and drags their feet on implementing them.

Anyway, there have been a number of interoperability issues where it turned out that RTI had some (almost) hidden configuration option to switch it to implement XTypes 1.3 behaviour. I don't know the details, but it is worth asking them. Hopefully something pops up!