Davis forecast text strings

[BCJKiwi]

Steve,
We seem to be in a rather fixed weather pattern at present with only 9 different forecasts generated in 6 days.
Of these 9;
2 are in the 'list of 200'
5 are in the list but with different punctuation ( ','s and '.'s - mostly missing but one added )
2 are not there at all.
Some of these variations may be due to newer firmware versions having fixed some of the errors in older firmware.

In the meantime the routine published in post 1, if added to a system, will happily log every new forecast that appears on that system.
Simulating a station would speed up this process but it would seem that simulating all the combinations of weather conditions and the time factors that make up a forecast would be rather complex.

[steve]

Simulating a station would speed up this process but it would seem that simulating all the combinations of weather conditions and the time factors that make up a forecast would be rather complex.

My proposed simulator would simply generate fake LOOP packets with each possible value of forecast rule in them. And if it was just a case of generating LOOP packets, I'd go ahead and do it, but unfortunately the simulator would also have to handle the other types of requests that the DLL sends.

[mcrossley]

Is there another way to tackle this? It means more work for Steve, but if Cumulus is set to use the Davis forecast, return the Davis forecast number in the <#forecastnumber> rather than zero?

[steve]

Cumulus has no way of obtaining the Davis forecast number.

[mcrossley]

Doh! Yes, I forgot the DLL does the conversion
More coffee needed