New release?

[MCancellier]

Can we expect a new release to go with the latest version of the main package? I'd love to integrate the ADS-B module and have the Titan Astro hat arriving soon.

[Alex-developer]

The entire module and overlay system is going thru a large scale refactoring to fix a few annoying issues so it will be a little while before there is a full release.

The adsb module is pretty stable, I have been running it for a few months so if you want to try and manually install it I can give you some details

[MCancellier]

Works fine! I used the OpenSky data set as I am feeding them already.

[Alex-developer]

Works fine! I used the OpenSky data set as I am feeding them already.

Glad you got it working :-)

If you have any suggestions / feedback then feel free to let me know

[MCancellier]

One thing I just noticed is that it's reporting Flight Level in meters instead of feet in the long text string.
Example: the module is reporting an aircraft at FL120 when it is actually at FL410. While it's ok to report altitude in meters in some parts of the world, Flight level is reported as feet/100 everywhere except Russia, China and some former Soviet countries.

[MCancellier]

Just noticed the airspeed is weird too. An aircraft is showing at 220 knots via the module, and my tracker is showing 430 knots.

[Alex-developer]

I think with both of those I need to check the variables that are being used from the adsb data, its also possible the height to Fl conversion is broken !

Thanks for the feedback I will have a look

[jcauthen78]

Is it going to change the internal structure/rules of the modules themself?

[Alex-developer]

Is it going to change the internal structure/rules of the modules themself?

Jim

I am trying to keep it all 100% backwards compatible. There are additions that module developers can use.

The only potential breaking change I have made is to standardise the name of the extra data files.

For all of the modules that are in the modules repo I am converting them to the new system

Alex

[Alex-developer]

Some of the key changes

In the metaData

centersettings - Determines if the settings dialog is centered on the screen or aligned with the top
testable - Does the module support testing (Some don't)
extradatafilename - The name of the extra data file
extradata - Defines the structure of the extra data thats written. This help get rid of the 'All variables' and 'Allsky variables' tabs in the overlay editor - There is now just a list of variables you select from, see screenshot below

There are more options available in the argument definitions as well
filters - these are used to show and hide fields depending upon whats selected, helps reduce the number of files

There are new variable types that allow for easier selection of data. The types include

• gpio - Allows for graphical selection of a gpio pin
• host - Allows for selection of an ip address and port
• Location - Displays a map allowing you to select a location
• Variable - Allows another allsky variable to be selected
• i2c - Allows an i2c devide to be selected, this scans the devices on your pi and tells you what you have installed
• onewirwe - Allows a one wire device to be selected

Another key change is to remove all of the various sensors from the modules and integrate them into one module that can read multiple sensors. The idea is that you define all of the sensors in one module and then allow them to be reused in other modules

Some images

The i2c selector

The one wire selector

The GPIO selector

The location selector

The variable selector

This is used in the overlay editor to add variables, you dont need to add them from the 'All variables' tab anymore just select them from the list. The list also provides a lot more information about the variable.