Max ADC value 255 - 127 is 128 unsigned, which is actually -128 in a signed int_8.

// sliding_dft(raw_buffer[i] - 127, raw_buffer[i + 1] - 127);
sliding_dft(raw_buffer[i] ^ 0x80, raw_buffer[i + 1] ^ 0x80);

http://jsonlint.com/
says about this snippet
{"addr":"DDA8B9","time":1490684311.182450,"rssi":-15.1,"channel":117,"lat":54.6552640,"lon":0.1440960,"dist":437095.05,"alt":2415,"vs":-300,"type":7,"stealth":0,"no_track":0,"ns":[3,-104,-37,-91],"ew":[-18,7,5,-89]} {"addr":"DDA8B9","time":1490684311.210040,"rssi":-17.8,"channel":118,"lat":54.6552640,"lon":0.1440960,"dist":437095.05,"alt":2415,"vs":-300,"type":7,"stealth":0,"no_track":0,"ns":[3,-104,-37,-91],"ew":[-18,7,5,-89]}
this:
Error: Parse error on line 16: ... [-18, 7, 5, -89]} { "addr": "DDA8B9", ----------------------^ Expecting 'EOF', '}', ',', ']', got '{'

Hi,

Since April 1st the received data seems not correctly decrypted.
I think you are already aware of this, do you know of any effort to reverse engineer the new protocol/encryption scheme?

Thanks!

Because the nrf905_decode binary uses gettime internally, its output does not reproduce.
I'm not sure what the best way is. Preferably, rtl_sdr would write out a format with timestamps inside, but that would require patching rtl_sdr.

Perhaps we can add some kind of 'debug' option to the nrf905_decode binary?
Right now, this is preventing me from unit-testing the binaries.

I am not able to setup a connection between flare an QGroundControl (Ground Control Station).
Which port should I use for that connection ?