vxWorks clock bug

4 posts / 0 new
Last post
Offline
Last seen: 2 years 4 months ago
Joined: 07/12/2012
Posts: 51
vxWorks clock bug

In rev 4.5f of the Connect core libraries for vxWorks there was a bug in that the properties for the clock could not

be set. The properties for the clock is set in the a domain participant QoS with the names "dds.clock.external_clock"

and "dds.clock.internal_clock". with possible values monotonic and/or realtime. In 4.5f this did not work correctly and a

workaround was necessary.

I would just like to know if this was fixed in 5.0 - the release notes does not mention it.

Thanks

Organization:
Juanjo Martin's picture
Offline
Last seen: 10 months 1 week ago
Joined: 07/23/2012
Posts: 48

Nico,

Did anyone provide you a reference code for this bug? I would say that if it is not in the release notes, it is not fixed. However, with the reference code I can check it.

Juanjo

Offline
Last seen: 2 years 4 months ago
Joined: 07/12/2012
Posts: 51

Hi Juanjo,

No, I do not have a reference number.

Nico.

 

Juanjo Martin's picture
Offline
Last seen: 10 months 1 week ago
Joined: 07/23/2012
Posts: 48

Nico,

I would need more information to handle this. Can you please send an email to support@rti.com with all the information you have about the bug?

Thanks,

Juanjo