Bug in `tdma_scripted`. Node uses params from launch (rate/max_bytes) for first transmit then, uses test plan for transmits going forward.

Bug in tdma_scripted. Node uses params from launch (rate/max_bytes) for first transmit then, uses test plan for transmits going forward.

When there is only 1 packet per active slot, this is less apparent. When more than one packet per slot, this causes the test plan to start "off by 1" because the first transmit was using the params passed in the launch file

Bug Behavior:

• test plan dataframe_rates: [1, 3, 5]
• observed dataframe_rates cycled: [5, 1, 3, 5, 1, 3]
• default dataframe rate: 5
  • if 3 packets per slot:
    • [5, 1, 3], first active slot 3 packet dataframe_rates in order
    • [5, 1, 3], second active slot "
  • expected from the test plan:
    • [1, 3, 5], first active slot 3 packet dataframe_rates in order
    • [1, 3, 5], second active slot "
• initial dataframe_rate used for first transmit in bold: [5, 1, 3, 5, 1, 3]
• plan for bug fix
  • tdma_scripted sets the dataframe_rate etc.. before first transmit so rates cycled are in order laid out in test_plan e.g., [1, 3, 5, 1, 3, 5]