Feature #161

Support the FrSky Sensor Hub Protocol

Added by Espen Solbu about 7 years ago. Updated about 6 years ago.

Status:NewStart date:02/01/2012
Priority:HighDue date:02/10/2012
Assignee:Espen Solbu% Done:

80%

Category:ParserSpent time:3.00 hours
Target version:3.0 FrSky hub and sensors

Description

Support parsing of data coming from the FrSky Sensor Hub

Ref: http://frsky-rc.com/uploadfile/201107/20110727110301692.pdf


Subtasks

Task #305: Validate byte stuffing method for both telemetry and sens...ResolvedHans Cappelle

Task #306: create channels for sensor hub dataClosedHans Cappelle

Task #307: Implement basic Sensor hub data presentationClosedHans Cappelle

Task #430: Add optional Hub to ModelClosedAndroid Dashboard Developers

Bug #435: Application crash when opening hub activityClosedAndroid Dashboard Developers

Bug #414: prototype Channel support for hubs - seem not to work pro...ClosedAndroid Dashboard Developers

Task #443: Add Hub abstract ClassClosedAndroid Dashboard Developers

Task #444: Refactor FrSkyHub to only take userbytes, not full framesClosedEspen Solbu

Task #445: Refactor Hub to be a instance within a modelClosed

Task #446: Refactor Hub to not broadcast anything itselfClosed

Task #447: Redo Hub Id and Hub Channel id conceptNewEspen Solbu

Bug #488: Hub channels seem to loose their source on resume of appClosedAndroid Dashboard Developers

Task #492: Removing HUB related source channels on removing hub from...New

Task #493: Add name member to abstract hub classClosed

Bug #497: Hub Derived channels sometime stop updatingNewAndroid Dashboard Developers

History

#1 Updated by Espen Solbu almost 7 years ago

  • Target version changed from 2.0 Multiple models to 3.0 FrSky hub and sensors

#2 Updated by Espen Solbu over 6 years ago

  • Tracker changed from Task to Feature

#3 Updated by Hans Cappelle about 6 years ago

Espen

I propose to move ticket 430 to a higher version since I don't expect other sensor hub version/protocols to be implemented soon and as long as this FrskyHub is the default there is no sense in letting the user select.

Unless you want the option to have hub on or off per model?

For now it's just by default the FrskyHub impl.

#4 Updated by Espen Solbu about 6 years ago

Until multiple hubs, i would still like to be able to have dropdown for model config (and stored in DB) if the model uses the FrSkyHub

This should be represented as

Hub
  • None
  • FrSky Hub v1.0
  • ...

#5 Updated by Hans Cappelle about 6 years ago

Espen Solbu wrote:

Until multiple hubs, i would still like to be able to have dropdown for model config (and stored in DB) if the model uses the FrSkyHub

This should be represented as

Hub
  • None
  • FrSky Hub v1.0
  • ...

Ok I'll implement that, makes sense now.

#6 Updated by Hans Cappelle about 6 years ago

and what to do if the model is changed from hub to none and it already had channels set with hub as source?

Just leave them that way?
delete these channels from model config?
ask user what to do?

#7 Updated by Espen Solbu about 6 years ago

Leave channels, but set source channel to "None"

Also available in: Atom PDF