[atlas] Firmware versions (was: Re: (no subject))

Hello,

> Hello Robert,
> 
> The question popped up at our end because we were looking at the plots
> of measurement results generated by different probes. We wanted to make
> sure these probes were comprised of the same hardware and that they run
> the same firmware version. It’s great that each UDM attaches the
> firmware version of the probe as a tag in its results. However:
> 
> a) Although, the hardwares currently are capable of running the same
> firmware revision, but as you mentioned, at times they diverge away.
> 
> b) Would different hardwares always support the latest firmware
> version? I ask because v3 is more capable than v1/v2, and I don’t know
> if you plan to diverge away the firmware at some point to provide more
> measurement capabilities for v3 probes.

As a general rule, we keep the firmware versions in sync across hardware
revisions in order to have the same capabilities available. The current
situation is a bit of an exception, but that's only because we needed to
deploy a new firmware for one hardware version only; functionally there's
no difference.

> Due to a) and b) would it make sense to also attach the hardware
> version (v1, v2, v3) of the probe as a tag in each UDM result as well?
> We don’t know if different hardwares have effects on the measurement
> results. We can cross-confirm this if the UDMs attach a hardware
> version in addition to the firmware revision.

This would be possible, though (with some more documentation from our end
[*]) one could also easily determine the hardware version from the probe ID.

Regards,
Robert

[*] the quick version:
- ID < 1500: v1
- 2000 < ID < 5000: v2
- 6000 < ID < 7000: anchor
- ID > 10000: v3

> Thanks!
> 
> Best, Vaibhav
> 
> ----------------------------------------------------- Vaibhav Bajpai
> 
> Research I, Room 86 Computer Networks and Distributed Systems  (CNDS)
> Lab School of Engineering and Sciences Jacobs University Bremen,
> Germany
> 
> www.vaibhavbajpai.com
>