[X] Updated to Bad Elf firmware to latest version.
[X] Updated platform to latest compatible version.
[X] Browsed open/resolved tickets to find similar issue.
Issue Description
Sending more than one data rate change does not work. The first one is accepted correctly.
Repro:
Compile the sample app.
Connect to the GPS.
Tap any of the buttons to change the data rate.
Observe that the data rate and/or message contents change as expected (but note that the code as it stands reverses the with/no satellite commands).
Tap any other button.
Observe a momentary pause in the data stream, which then resumes with the same data as originally requested.
I have tried changing the "pingJunk" value to byte { 13, 10 } in case the EOL marker is expected by the GPS. Also tried an explicit flush on the OutputStream. Neither had any effect. I have confirmed in the debugger that the send() call is actually sending the data. The pingjunk calls don't seem to affect things because the first data change command sent invariably works, no matter how many pings have happened beforehand.
New Issue Checklist
Issue Description
Sending more than one data rate change does not work. The first one is accepted correctly.
Repro:
I have tried changing the "pingJunk" value to byte { 13, 10 } in case the EOL marker is expected by the GPS. Also tried an explicit flush on the OutputStream. Neither had any effect. I have confirmed in the debugger that the send() call is actually sending the data. The pingjunk calls don't seem to affect things because the first data change command sent invariably works, no matter how many pings have happened beforehand.
ENVIRONMENT
Bad Elf Model:
Firmware Version:
Platform:
Protocol String: