The experimental ('E') version differs from previous versions in that the map handling is modified. In all cases, the icon on the map denoring a transmitter whose data is received, is now accompanied by the tii value (i.e. mainId, subId) of the transmitter.
A logical extension was to show (for different channels), all (channel, tiiValue) pairs that are received from the transmitter(location).
The picture shows that - here, using a simple whip, I data from 20 receivers.
Clicking on the icon shows the data from the transmitter location on the side bar.
Note that the configuration widget now has a checkbox (set by default to "checked") that determines whether or not a transmitter shown on the map only gets a single tiiValue (always the most recently detected) or the list (as done in the picture above,
The selector - line 1 from the bottom, left - has as label showAll.
There are hardly other differences between this version and the previous one,, the names of executables and installers is the one used for the previous versions.
On 30 april I uploaded new versions. The main differences are threefold
a. whenever a selection is made on the map, clicking again on the selected transmitter(location) causes an "undo" for the selection
b. when scanning, now a difference is made between the "switch" time, i.e. the duration in which the software looks for some reasonable DAB data, and the "stay" time, i.e. the duration the channel in which an ensemble is detected is active.
Reasonable values for switchtime is somewhere between 5 and 10 seconds, I use 2 minutes for "stay" time, but there is virtually no restriction on th maximum times (Note that "switch" time is in seconds, "stay" time in minutes on the config widget)
c. (Again) When scanning, the scan control widget shows the detected transmitters in the channels where DAB data was discovered
On May 4 I added a small "how to use" document, very introductory
On june 5 I uploaded adapted versions
Changes are twofold
(invisible) improved synchronizing,
(visible) the two spyserver clients now have a possibility for selecting a port of the device widget