You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using my forked checkout of the latest master (801c0d6) I setup two Faraday radios and ran proxy connected to both of them. They were only sending out UART telemetry and configured not to send RF telemetry. Also, I started up two separate instances of faraday-telemetry from which I saved two discrete logs.
Log: Omitting since it has my GPS location in it and I want to keep that more private. Do note that the unit was sitting inside my house near a window on the computer desk. The GPS locked at EPOCH 1499354525.252, briefly lost lock a few minutes later to regain lock again until test stopped at EPOCH 1499403381.213
Summary
Using my forked checkout of the latest master (801c0d6) I setup two Faraday radios and ran proxy connected to both of them. They were only sending out UART telemetry and configured not to send RF telemetry. Also, I started up two separate instances of
faraday-telemetry
from which I saved two discrete logs.@kb1lqd @el-iso @reillyeon
Problem Explanation
Just a nifty test to see where we stand on Faraday software reliability (and firmware)
Environment
Software
801c0d6
Firmware
686490f6d23c8a9634d8f08192576f0073c773a9
Hardware
Faraday Rev D1 SN
Supporting Information
Proxy Server
KB1LQC-1 Telemetry Server
Log: Omitting since it has my GPS location in it and I want to keep that more private. Do note that the unit was sitting inside my house near a window on the computer desk. The GPS locked at EPOCH 1499354525.252, briefly lost lock a few minutes later to regain lock again until test stopped at EPOCH 1499403381.213
KB1LQC-2 Telemetry Server
Log: https://faradayrf.com/wp-content/uploads/2017/07/kb1lqc2_7-6-17.zip
The text was updated successfully, but these errors were encountered: