MB PRO to support multiple ISS (like envoy8x)

[admin]

We have beta code running that allows Meteobridge with Meteostick and MB PRO (red) to receive RF data from a free selection of up to eight Davis sensors. Like envoy8x it can be any mixup, multiple ISS, etc.

Selection is done in this way:

sh0.png (34.65 KiB) Viewed 3660 times

Message window shows data logger being started with these parameters:

sh1.png (45.06 KiB) Viewed 3660 times

This is how live data is looking like (MB PRO also has system data attached):

sh2.png (135.69 KiB) Viewed 3660 times

Anyone who wants to test this code on his rig as well? Please email to "info(at)meteobridge.com".
I just need the MAC to make beta code available to your Meteobridge on next reboot.

[admin]

Rules of enumeration and visibility of sensors are as follows:

1) first transmitter with an ISS is mapped to the primary sensors (th0, thb0, wind0, rain0, uv0, sol0)
2) all other sensors are mapped according to their transmitter ID
3) when a wind station is defined, its wind sensor is taken as primary sensor (mapped to wind0) as it is assumed that this specialized station should report primary data
4) same for rain station (mapped to rain0) and for leaf/soil station (mapped to th10, th11, th12, th13, th14, th15, th16, th17, th18)
5) temp, temp/hum, soil/leaf stations are not reporting rain, wind, uv, solar data. If combinations are needed, define station as ISS. In that case all sensors are evaluated.

This should make standard installs correctly mapped with primary sensors from scratch and also gives the pro user room to evaluate larger sensor arrays.

While MB PRO does make all data persistent, on a standard Meteobridge selectors on time ranges like (max60, min2h) will only work for primary sensors. Reason is that standard Meteobridge does not have enough RAM/Storage to keep data sequences for on demand analyzes reaching into the past for more than a few sensors. Saying that, going with a MB PRO makes much sense when more than a primary sensor set is used.

[PWS]

Looks like the basis for a big step forwards in functionality. But to make it clear to simple-minded people like me, could you spell out how the enumeration will work in a concrete example - I think part of the uncertainty is defining what constitutes an ISS. Take the following example, which could be reasonably common I suspect:

Channel #1 = 6332 Anemometer transmitter with wind, solar and UV fitted;
Channel #2 = ISS (well, residual ISS with no anemometer and so transmitting just T/H and rain)

NB 6332 assigned to #1 since this is supposed to give marginally better % reception for wind. Solar and UV both fitted to this Tx on the assumption that it will be mounted fairly high up and hence have a good view of the sky.

I guess this counts as a 2 x ISS configuration? So:

#1 reports wind0 plus uv0 and sol0;
#2 reports th1 and rain1;

Would that be correct?

[admin]

Exactly, both need to be defined as ISS and the ordering will be as you describe.

[admin]

Todays update has the feature now public available.