Loading ...
Sorry, an error occurred while loading the content.

Re: Having OFL problem

Expand Messages
  • RickN
    Another Possibility could be a cracked wire from the Wind sensor to the Thermo unit. Rick KOHWAPAK1 www.wapakweather.com
    Message 1 of 8 , Sep 27, 2009
    View Source
    • 0 Attachment
      Another Possibility could be a cracked wire from the Wind sensor to the Thermo unit.

      Rick
      KOHWAPAK1
      www.wapakweather.com


      --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...> wrote:
      >
      >
      > Are you running the remote thermo on batteries?
      >
      > The remote thermo actually communicates over serial lines to the wind sensor. That take a bit of energy to do. Perhaps your batteries are a bit weak and the warmer temps allow it to function for a bit.
      >
      >
      > --- In wuhu_software_group@yahoogroups.com, "MtMan1849" <mtman1849@> wrote:
      > >
      > > --- In wuhu_software_group@yahoogroups.com, "MtMan1849" <mtman1849@> wrote:
      > > >
      > > > --- In wuhu_software_group@yahoogroups.com, "MtMan1849" <mtman1849@> wrote:
      > > > >
      > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@> wrote:
      > > > > >
      > > > > >
      > > > > > The way WUHU works is that it expects to receive all of the weather data before accepting information from the console. Missing sensor data is generally un-acceptable and unless you disable the sensor (under the tweak screen), all sensor data must report in.
      > > > > >
      > > > > > For whatever reason, your remote thermo is losing it's connection to the wind sensor. Perhaps you have moisture (dew) in the telephone line that runs up to it and the moisture burns off eventually during the day.
      > > > > >
      > > > > > It might also be interference caused by things like ham radio or some other source of extreme RF interference. I would initially suspect the moisture problem unless you know of some device that might disrupt communications over the wire between the remote thermo and the wind sensor.
      > > > > >
      > > > > > You can either track down the underlying problem or try the tweak option "Disable Wind Sensor Temporarily if it fails to report". That might get you by temporarily if the wind sensor is the only real problem.
      > > > > >
      > > > > >
      > > > > > --- In wuhu_software_group@yahoogroups.com, "MtMan1849" <mtman1849@> wrote:
      > > > > > >
      > > > > > > Sun Sep 27 09:21:33 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:21:33 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:21:33 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:21:33 2009 > Detected consecutive communications failures. Attempting to recover by re-opening the port.
      > > > > > > Sun Sep 27 09:21:43 2009 > Attempting to re-open port COM1.
      > > > > > > Sun Sep 27 09:21:43 2009 > Port COM1 re-opened successfully, attempting to resume communications.
      > > > > > > Sun Sep 27 09:22:39 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:22:39 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:22:39 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:23:38 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:23:38 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:23:38 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:24:42 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:24:42 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:24:42 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:25:41 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:25:41 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:25:41 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:26:42 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:26:42 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:26:42 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:27:43 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:27:43 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:27:43 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:28:43 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:28:43 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:28:43 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:28:43 2009 > Detected consecutive communications failures. Attempting to recover by re-opening the port.
      > > > > > > Sun Sep 27 09:28:53 2009 > Attempting to re-open port COM1.
      > > > > > > Sun Sep 27 09:28:53 2009 > Port COM1 re-opened successfully, attempting to resume communications.
      > > > > > > Sun Sep 27 09:29:49 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:29:49 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:29:49 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:30:49 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:30:49 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:30:49 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > > Sun Sep 27 09:31:49 2009 > An error occurred reading the wind speed and direction from the console.
      > > > > > > Sun Sep 27 09:31:49 2009 > Communications error or invalid/corrupt data retrieved from console.
      > > > > > > Sun Sep 27 09:31:49 2009 > Time to next console communication: 5000 milliseconds.
      > > > > > >
      > > > > > > It does this for 6 hrs or more at a time then just start working again
      > > > > > > while this is going on everything on the console is working except the wind speed and direction it has 2 dashes instead of 0
      > > > > > > any help will be great
      > > > > > > thanks
      > > > > > >
      > > > > >
      > > > > wind sensor is working now gremlins ???
      > > > >
      > > > took wind sensor down clean and wd40 propellor unpluged it from temp sensor had a bunch of cobwebs built up around and in plug cleaned them out and put wind sensor back up everything working fine again
      > > >
      > > ok now what one time I look wind sensor is working look again and it is not go figure
      > >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.