![]() ![]() However it should use the next expected sequence number which is associated with the reader history. When handling the GAP message the sequence number contained in the GAP message is used to evaluate if all history data has been received. In a particular situation when there are several readers for the same transient_local topic created and the transient_local writer sends a GAP message which makes the history of one of these readers complete it may occur that the corresponding dds reader is not notified that it has become complete causing the wait_for_historical_data function to time out. ![]() ![]() When ddsi has received all the history data from a transient_local writer it will set the associated dds readers complete which signals the wait_for_historical_data. The function wait_for_historical_data may fail for reliable transient-local topic. The 'dds_sample_info_t' array of the Vortex DDS Reader block is now initialized correctly. Therefore, on the generated code from a Simulink model, the members of the ' dds_sample_info' bus were incorrectly assigned to a value when there was no data available. The 'dds_sample_info_t' array on the Vortex DDS Reader block for Simulink was not initialized properly. Incorrect behavior on the members of 'dds_sample_info' bus of Simulink Vortex DDS Reader block. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |