Jaaaky

Actually, signing are only for uplink messages to verify the source. It's for "authority verification", so othesr can actually connect and "see/read" the UAV info/status/location but cannot "modify or change"...

If the ez-wifibroadcast just works as a general network proxy/repeater between user's PC GCS and UAV, it should work. And the ground-pi could parse the received data to get the...

I have the equipment, yes. So I can test.

@barbeau They work with the mentioned library.

> Closing this. Please reopen if you believe it should be addressed. Thank you for your contribution. Please re-open this.. I see no reason for close.. It was already scheduled...

I can confirm the `LOG_DISARMED,1` bug can be reproduced on Pixhawk5x too. I've done the following, to make sure nothing else is interfering: 1. Create fft.param file with the following...

I actually found a more serious problem Pixhawk5X too. The reboot command after activating `LOG_DISARMED,1` following the mentioned steps, does not work fine, I've to do a power cycle..

@andyp1per Have you seen my update on Pixhawk5x it has free mem of over 180KBs at least as seen on mavproxy while reproducing the bug? The board has 512kb of...

@peterbarker Yes, this issue still exists on Stable branch - currently arduplane 4.2.3 -, it's not on master. Also, another issue which was reported against master about fft rpm not...

@peterbarker Also, with ARMING_REQUIRE,0 FFY is not started/calibrated on boot too, even with LOG_BACKEND_TYPE,0 and accelerometers are calibrated. Confirmed on master and stable