On Friday, 4 August 2017 14:59:55 UTC+1, Calum Macintosh wrote:
>
> Hi Aleksandar,
>
> Thank you for putting this driver together. I can confirm it works with
> Airmar120wx devices. To get it to work I had to change windSpeed_unfilt in
> the code to windSpeed and windAngle_unflilt to windDir on lines 482 and
> 483.
>
> Many thanks,
>
> Calum
>
> On Saturday, 4 July 2015 12:03:25 UTC+1, Aleksandar Tsankov wrote:
>>
>> Hi Rob,
>> I'm glad that someone else has an interest about Airmar driver.
>> As a matter of fact I use a slightly updated driver version from a month
>> (at least) without any hassle.
>> About warnings: they are generated in situations where there are no valid
>> data in the Airmar sentences.
>> Initially I thought that the sentence won't be generated at all if there
>> are no valid data in it but obviously it's not the case. Since these
>> messages greatly rose log-file's size I decided to not throwing it in the
>> last driver's version.
>> I saw your modification of validate_string() subroutine - obviously I
>> missed condition with space in the beginning of the string instead of "0" -
>> thank you.
>> However I cannot get the point of other changes you've made. May be I'm
>> wrong but I think your version just throws error messages without returning
>> an empty string in case of missmatched checksum or garbled message.
>>
>> Nevermind, I'm very glad that someone (you, Rob) opened a github
>> repository for the Airmar driver. Since I do not have enough time, I'll be
>> thankful if you keep maintaining it.
>>
>> And yes, one more thing to mention - since the idea for getting
>> lat/lon/alt from devices which are capable to send them is already
>> discussed (https://github.com/weewx/weewx/issues/32), it's probably time
>> to add processing of GPS-related sentences in the driver.
>>
>> I'm attaching the driver version with suppressed messages for "Wrong data
>> format......."
>>
>
