Re: Peet Mode not working correctly
- Hi Scott,
I have been experimenting and have a bit more data on this issue. I
found that if I type WXINFO and get bogus information and then unplug
the Peet WX Station serial data from the T2, wait 5 seconds and plug
it back in, it will start to report correct data. Once WXINFO is
reporting correct information, then the T2 will start transmitting WX
packets every 5 mintues like I have it programmed to do. Once it
transmits, there is about a 50/50 chance that the next time I type
WXINFO the data will be bad and I will need to start the unplug/plug
process over again. Disconnecting/reconnecting that data makes it
sync up, but it isn't reliable. Sometimes one time will do it,
sometimes it takes up to 10 times to get it to sync up correctly.
This leads me to believe that the T2 is getting lost parsing the data
stream coming in from the Peet after a transmit. If I happen to plug
it in at just the right time, it will sync up.
The humidity reported starts out after power up correctly but once
the data gets out of sync it starts reporting bogus numbers, or
transmits zero - which gets intrepreted by Findu at 100%.
--- In firstname.lastname@example.org, "k0yg" <mpatton5280@...> wrote:
> Hi Scott,
> Several months back we talked about about Peet mode not working
> properly. It seems like most of the issues still remain in this
> release. The humidity reporting problem *may* have gone away but I
> did see it report a wrong humidity today - but only once. That
> can wait until I get the others resolved. To summarize, here are
> issues that I'm seeing with the latest 54100 build:
> 1) Weather not being transmitted as programmed.
> I have the T2 set to report weather every 5 minutes. Sometimes it
> reports, most times it does not. I'll send the log in a private
> email as not to clutter up the list. Basically, it reported
> just once in an hour and status every 5 minutes (as it should).
> 2) Wind Gust missing
> The 5 minute wind gust information is not being reported at all.
> is being reported as "..." even though Peet puts this out in the
> 3) WXINFO command reporting wrong data. I don't know for sure if
> this command is supposed to be working now or not in this release.
> so, this may be a big clue. Sometimes the data is correct, many
> is it is not like this:
> TEMP:2872 WIND 388 AT -1536 GUST 0 BARO 0
> TEMP:83 WIND 180 AT 0 GUST 0 BARO 10245 * (this appears to be
> TEMP:64 WIND 256 AT 0 GUST 0 BARO 53
> If I had to make a guess, it looks like the data is getting
> somehow. It is possible that there is some sort of issue on my end
> of nobody else is seeing this. One idea could be a noisy data
> into the T2 although I looked at the data going into the processor
> with a scope and it appeared to be OK.