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

Inhale and propagate Flarm data stream to XCSoar-type devices #106

Open
degeflija opened this issue Jul 23, 2024 · 2 comments
Open

Inhale and propagate Flarm data stream to XCSoar-type devices #106

degeflija opened this issue Jul 23, 2024 · 2 comments

Comments

@degeflija
Copy link

degeflija commented Jul 23, 2024

Receive Flarm NMEA datastream on RS232 jack and merge these packets into outgoing NMEA datastream created by the LARUS sensor.
This would facilitate showing Flarm targets and Flarm warnings on connected XCSoar type devices like OpenSoar or SteFly without any additional soft/hard-ware.
This feature would substitute "IOIOBox"-es.
This should be fairly easy for Klaus to integrate into his "Wunderwerk der Technik"

@realtimepeople
Copy link
Collaborator

To integrate this feature has been planned for the system, but not for the sensor firmware,
Presently we have the idea to prepare a RS232->CAN gateway for this purpose.
Nevertheless it may be an option to support reception of FLARM's NMEA stream on the RS232
and forward it into the CAN data stream.

@degeflija
Copy link
Author

Ad 1 : As far as I know, there is no device on the horizon which might digest Flarm type data on the CAN data stream. So, I do not understand the purpose of a planned R232 - CAN gateway in inbound direction. Outbound, yes, if you have an elaborated frontend device which serves as source for task definition data to be used to set a task in Flarm. But that is also a far fetched idea. Is the purpose of the gateway described somewhere ?

Ad 2 : In addition to my original issue : I was wrong in assuming that Stefly-s machine could benefit from my proposal. SteFly needs the RS232 as Sensor output of NMEA data, as it is not connected via BlueTooth. My proposal is good only for BlueTooth coupled XCSoar devices.
Since these two use cases (SteFly OpenSoar or handheld smartphone XCSoar/OpenSoar) are mutually exclusive, the issue is still worth a thought. It could be implemented via compile time switch or a startup switch ala sensor.readings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants