Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No FLARM signal sent #55

Closed
1 of 5 tasks
GliderPil0t opened this issue Apr 3, 2019 · 2 comments
Closed
1 of 5 tasks

No FLARM signal sent #55

GliderPil0t opened this issue Apr 3, 2019 · 2 comments

Comments

@GliderPil0t
Copy link

Hardware

  • Prime Mark II
  • Standalone
  • UAV
  • UAT module
  • SkyView

https://imgur.com/a/KgBDx7L

Firmware version & settings

screenshot of WebUI settings & status page
https://imgur.com/a/J9BjCTn

Describe the bug (or ask a question)

Hi my SoftRF device is receiving FLARM signals of other gliders in legacy mode but it is not sending any signals to the gliders. I tested it on different FLARM devices in my gliding club and none of them received the signal of my SoftRF. Do I have to change something in my settings?

To Reproduce

Expected behavior

Red light on FLARM device if approaching.

@DanD222
Copy link

DanD222 commented Apr 3, 2019

This may be correct behaviour of FLARM units, if the testing was done on the ground on stationary units - see the "THRE" parameter in the FLARM Configuration document:
http://asa-soaring.org/documents/FLARMConfiguration.pdf

Also be aware of the "Nearest" and "Collision" FLARM operating modes:
https://flarm.com/wp-content/uploads/man/FLARM_OperatingManual_E.pdf

A good way to test whether a FLARM unit is receiving SoftRF signals is if the FLARM is connected to a gliding computer such as XCSoar via a Bluetooth module such as the Soartronic modules. Signals received by the FLARM units are then displayed on the XCSoar FLARM display regardless of whether the LEDs on the actual FLARM unit are lit or not.

@GliderPil0t
Copy link
Author

Oh thanks for the response. I'll try that soon :)

Repository owner locked as resolved and limited conversation to collaborators Apr 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants