CHIRP

For Jim, et al,

I'm also seeing this occasionally on my mac with latest daily, where the ACK is sometimes 0x48 (failing). Other times it's in the expected group of acks (0x78).
Interestingly, for my radio, if I add 0x48 to allowed acks, all of the acks for that session are the same. The data downloads ok, and looks fine.
The next download might be 0x48, or it might be 0x78. I have tried playing with some small sleeps in the do_download function to induce timing behavioral differences, but it doesnt seem to have any noticeable impact. I haven't really figured out a pattern yet…

a hackish thought occurred - as whatever the radio uses the ack is consistent throughout the download, we could follow this logic:
if the first ack received is not in the "known good" list of acks, use that as the ack for the rest of the session, with the thought that if there was a NAK, it would be different?
(This completely bypasses the obvious question of what do those different acks mean, and why are they different!)

This issue has been marked as resolved for about 2 years now. Is it safe to move this to Closed now?