Msg 136: Train Position Report - carries Packet 0 OR Packet 1 (Subset-026 8.6.4: "Packet 0 or 1"), never both. @position_report is ALWAYS populated regardless of which packet actually arrived (the decoder mirrors Packet 1's own core fields into it too - see ab_gp_ertms_train_message_codec.c's own decode case) so every EXISTING reader that only ever looked at @position_report (written before Packet 1 existed) keeps working unchanged; @has_packet1/@packet1 exist for a caller that specifically needs to tell the two apart (ab_gp_proc_dispatch.c's own handle_msg_136() does, for the post-EoM idle heartbeat - see that function's own comment). More...

#include <ab_gp_ertms_train_messages.h>

Collaboration diagram for rbc_msg_136_position_report_t:

[legend]

Data Fields
rbc_train_to_track_header_t	header
rbc_packet_0_position_report_t	position_report
bool	has_packet1
rbc_packet_1_position_report_2bg_t	packet1

Detailed Description

Msg 136: Train Position Report - carries Packet 0 OR Packet 1 (Subset-026 8.6.4: "Packet 0 or 1"), never both. @position_report is ALWAYS populated regardless of which packet actually arrived (the decoder mirrors Packet 1's own core fields into it too - see ab_gp_ertms_train_message_codec.c's own decode case) so every EXISTING reader that only ever looked at @position_report (written before Packet 1 existed) keeps working unchanged; @has_packet1/@packet1 exist for a caller that specifically needs to tell the two apart (ab_gp_proc_dispatch.c's own handle_msg_136() does, for the post-EoM idle heartbeat - see that function's own comment).

Definition at line 268 of file ab_gp_ertms_train_messages.h.