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

Communication errors

Expand Messages
  • scruzphreak
    I had a problem with my weather station. I mistakenly swapped the 4 conductor phone cord for a 2 conductor cord. I just realized my mistake, and replaced the
    Message 1 of 12 , Mar 26, 2008
    • 0 Attachment
      I had a problem with my weather station. I mistakenly swapped the 4
      conductor phone cord for a 2 conductor cord. I just realized my
      mistake, and replaced the cord with another 4 conductor cord.

      But the wuhu application still won't connect:
      Wed Mar 26 22:31:08 2008 > WUHU monitoring stopped.
      Wed Mar 26 22:32:37 2008 > WUHU monitoring started (WUHU21623XXSP).
      Wed Mar 26 22:32:37 2008 > Weather Underground ID: KCASANTA70
      Wed Mar 26 22:32:37 2008 > Weather Underground URL:
      http://www.wunderground.com/weatherstation/WXDailyHistory.asp?
      ID=KCASANTA70
      Wed Mar 26 22:32:37 2008 > CWOP ID: CW7048
      Wed Mar 26 22:32:37 2008 > CWOP URL: http://www.findu.com/cgi-
      bin/wxpage.cgi?call=CW7048
      Wed Mar 26 22:32:37 2008 > Opened serial port COM1 successfully.
      Wed Mar 26 22:32:44 2008 > Outdoor temperature reading of 177.8 F
      detected. Value out of range (-40.0 to 157.8).
      Wed Mar 26 22:32:44 2008 > Outdoor humidity reading of 110.0 percent
      detected. Value out of range (1 to 100).
      Wed Mar 26 22:32:44 2008 > Dewpoint reading of 182.1 F detected.
      Value out of range (-82.0 to 157.8).
      Wed Mar 26 22:32:44 2008 > Windchill reading of 1360.1 F detected.
      Value out of range (-40.0 to 157.8).
      Wed Mar 26 22:32:44 2008 > One or more data items could not be
      automatically corrected, Ignoring ALL data on this update.
      Wed Mar 26 22:32:44 2008 > Time to next console communication: 63500
      milliseconds.

      I don't really want to have to factory-reset my 2308. Can anyone
      suggest something else to try?

      -ms
    • scruzphreak
      well, this is interesting. I did a factory reset of the unit, and tried plugging it into another computer. I m getting the same errors on this one. Is there
      Message 2 of 12 , Mar 27, 2008
      • 0 Attachment
        well, this is interesting. I did a factory reset of the unit, and
        tried plugging it into another computer. I'm getting the same errors
        on this one.

        Is there something I could have done to damage the 2308 by plugging a
        2 conductor cable into it?

        -ms





        --- In wuhu_software_group@yahoogroups.com, "scruzphreak" <ms@...>
        wrote:
        >
        > I had a problem with my weather station. I mistakenly swapped the 4
        > conductor phone cord for a 2 conductor cord. I just realized my
        > mistake, and replaced the cord with another 4 conductor cord.
        >
        > But the wuhu application still won't connect:
        > Wed Mar 26 22:31:08 2008 > WUHU monitoring stopped.
        > Wed Mar 26 22:32:37 2008 > WUHU monitoring started (WUHU21623XXSP).
        > Wed Mar 26 22:32:37 2008 > Weather Underground ID: KCASANTA70
        > Wed Mar 26 22:32:37 2008 > Weather Underground URL:
        > http://www.wunderground.com/weatherstation/WXDailyHistory.asp?
        > ID=KCASANTA70
        > Wed Mar 26 22:32:37 2008 > CWOP ID: CW7048
        > Wed Mar 26 22:32:37 2008 > CWOP URL: http://www.findu.com/cgi-
        > bin/wxpage.cgi?call=CW7048
        > Wed Mar 26 22:32:37 2008 > Opened serial port COM1 successfully.
        > Wed Mar 26 22:32:44 2008 > Outdoor temperature reading of 177.8 F
        > detected. Value out of range (-40.0 to 157.8).
        > Wed Mar 26 22:32:44 2008 > Outdoor humidity reading of 110.0
        percent
        > detected. Value out of range (1 to 100).
        > Wed Mar 26 22:32:44 2008 > Dewpoint reading of 182.1 F detected.
        > Value out of range (-82.0 to 157.8).
        > Wed Mar 26 22:32:44 2008 > Windchill reading of 1360.1 F detected.
        > Value out of range (-40.0 to 157.8).
        > Wed Mar 26 22:32:44 2008 > One or more data items could not be
        > automatically corrected, Ignoring ALL data on this update.
        > Wed Mar 26 22:32:44 2008 > Time to next console communication:
        63500
        > milliseconds.
        >
        > I don't really want to have to factory-reset my 2308. Can anyone
        > suggest something else to try?
        >
        > -ms
        >
      • Juha Jäntti
        Hi. It s highly unlikely that you have damaged your setup. If you get no readings on the console, make sure all cables are connected and then resynchronize the
        Message 3 of 12 , Mar 27, 2008
        • 0 Attachment
          Hi.

          It's highly unlikely that you have damaged your setup.

          If you get no readings on the console, make sure all cables are
          connected and then resynchronize the Console with the outdoor sensor
          rig by pressing the '+' button on the Console until it beeps. Once it
          beeps, release the button. This should initiate synchronization and
          bring up the readings.

          If you still don't get any readings, check that the 4-conductor cable
          is a standard 4-conductor telco cable and that there are no breaks in
          the wires. If you don't own a continuity tester, visually inspect the
          wiring on both plugs, comparing the wire colors.

          Also, double-check that you haven't mistakenly plugged those cables in
          wrong places on the console itself (Serial cable plugged to COM-port's
          receptacle and other way round). I've done that once. :)

          In addition, check the condition of the batteries in the oudoor
          Thermo/Hygro sensor that they're OK.

          Best Regards,
          Juha
          Finland Weather Exchange (FinWX)
          Helsinki, Finland
          CW4473 / IUUSIMAA2


          --- In wuhu_software_group@yahoogroups.com, "scruzphreak" <ms@...> wrote:
          >
          > well, this is interesting. I did a factory reset of the unit, and
          > tried plugging it into another computer. I'm getting the same errors
          > on this one.
          >
          > Is there something I could have done to damage the 2308 by plugging a
          > 2 conductor cable into it?
          >
          > -ms
          >
          >
          >
          >
          >
          > --- In wuhu_software_group@yahoogroups.com, "scruzphreak" <ms@>
          > wrote:
          > >
          > > I had a problem with my weather station. I mistakenly swapped the 4
          > > conductor phone cord for a 2 conductor cord. I just realized my
          > > mistake, and replaced the cord with another 4 conductor cord.
          > >
          > > But the wuhu application still won't connect:
          > > Wed Mar 26 22:31:08 2008 > WUHU monitoring stopped.
          > > Wed Mar 26 22:32:37 2008 > WUHU monitoring started (WUHU21623XXSP).
          > > Wed Mar 26 22:32:37 2008 > Weather Underground ID: KCASANTA70
          > > Wed Mar 26 22:32:37 2008 > Weather Underground URL:
          > > http://www.wunderground.com/weatherstation/WXDailyHistory.asp?
          > > ID=KCASANTA70
          > > Wed Mar 26 22:32:37 2008 > CWOP ID: CW7048
          > > Wed Mar 26 22:32:37 2008 > CWOP URL: http://www.findu.com/cgi-
          > > bin/wxpage.cgi?call=CW7048
          > > Wed Mar 26 22:32:37 2008 > Opened serial port COM1 successfully.
          > > Wed Mar 26 22:32:44 2008 > Outdoor temperature reading of 177.8 F
          > > detected. Value out of range (-40.0 to 157.8).
          > > Wed Mar 26 22:32:44 2008 > Outdoor humidity reading of 110.0
          > percent
          > > detected. Value out of range (1 to 100).
          > > Wed Mar 26 22:32:44 2008 > Dewpoint reading of 182.1 F detected.
          > > Value out of range (-82.0 to 157.8).
          > > Wed Mar 26 22:32:44 2008 > Windchill reading of 1360.1 F detected.
          > > Value out of range (-40.0 to 157.8).
          > > Wed Mar 26 22:32:44 2008 > One or more data items could not be
          > > automatically corrected, Ignoring ALL data on this update.
          > > Wed Mar 26 22:32:44 2008 > Time to next console communication:
          > 63500
          > > milliseconds.
          > >
          > > I don't really want to have to factory-reset my 2308. Can anyone
          > > suggest something else to try?
          > >
          > > -ms
          > >
          >
        • scruzphreak
          Hi Juha, I think I killed it. My console is in my kitchen, and I have a cat5 da, ta cable that goes from the kitchen to the closet where the server is, and
          Message 4 of 12 , Mar 28, 2008
          • 0 Attachment
            Hi Juha,

            I think I killed it. My console is in my kitchen, and I have a cat5 da,
            ta cable that goes from the kitchen to the closet where the server is,
            and that's how I was running the serial connection.

            Right next to the data jack was a voice jack.

            I'm betting that someone (me, cleaning person, kid?) unplugged the
            console and plugged it into the voice jack. Here in the US, the telco
            network is 24V AC, with a 108V AC ring signal. I don't know what would
            happen if a ring came in while the data port was plugged into the telco
            network, but I'll bet it's not good. I don't know if that's what
            happened, but...

            I debugged with Lacrosse. I took the sensor off the wall outside and
            brought it into the kitchen. After 15 minutes of resetting both
            devices, we were unable to get the console to talk to the sensor.

            Fortunately, LaCrosse is taking the device back under warrantee, and
            we'll figure it what happened.

            -ms


            --- In wuhu_software_group@yahoogroups.com, Juha Jäntti <jjantti2@...>
            wrote:
            >
            > Hi.
            >
            > It's highly unlikely that you have damaged your setup.
            >
          • Juha Jäntti
            Hi. Sorry to hear it. I hoped it would have been something less destructive. It think with a ring signal of 108Vac, the console would probably had gone out
            Message 5 of 12 , Mar 30, 2008
            • 0 Attachment
              Hi.

              Sorry to hear it. I hoped it would have been something less destructive.

              It think with a ring signal of 108Vac, the console would probably had
              gone out with a loud bang and you would have had nothing on the screen
              afterwards, so it think the 24Vac is the killer voltage since there
              was still some sort of life on the console.

              It's a good thing LaCrosse took it under warranty. I think if a
              similar thing would have happened to me, I would have been forced to
              buy a whole station again, since it would have probably been so-called
              "user installation error".

              Let's hope you get the station back up and running soon.
              Best Regards,
              Juha
              Finland Weather Exchange (FinWX)
              Helsinki, Finland
              CW4473 / IUUSIMAA2


              --- In wuhu_software_group@yahoogroups.com, "scruzphreak" <ms@...> wrote:
              >
              > Hi Juha,
              >
              > I think I killed it. My console is in my kitchen, and I have a cat5 da,
              > ta cable that goes from the kitchen to the closet where the server is,
              > and that's how I was running the serial connection.
              >
              > Right next to the data jack was a voice jack.
              >
              > I'm betting that someone (me, cleaning person, kid?) unplugged the
              > console and plugged it into the voice jack. Here in the US, the telco
              > network is 24V AC, with a 108V AC ring signal. I don't know what would
              > happen if a ring came in while the data port was plugged into the telco
              > network, but I'll bet it's not good. I don't know if that's what
              > happened, but...
              >
              > I debugged with Lacrosse. I took the sensor off the wall outside and
              > brought it into the kitchen. After 15 minutes of resetting both
              > devices, we were unable to get the console to talk to the sensor.
              >
              > Fortunately, LaCrosse is taking the device back under warrantee, and
              > we'll figure it what happened.
              >
              > -ms
              >
              >
              > --- In wuhu_software_group@yahoogroups.com, Juha Jäntti <jjantti2@>
              > wrote:
              > >
              > > Hi.
              > >
              > > It's highly unlikely that you have damaged your setup.
              > >
              >
            • dfossler
              I have used WUHU for several years. Last spring I lost my system due to a near lightning strike and just recently replaced it (WS-2310) The WS-2310 is synched
              Message 6 of 12 , Oct 12, 2012
              • 0 Attachment
                I have used WUHU for several years. Last spring I lost my system due to a near lightning strike and just recently replaced it (WS-2310)

                The WS-2310 is synched to WWV (and is working as expected) and my computer is synched to an internet time server.

                I have the WS-2310 hooked direct serial to a COM1 port on my Dell.

                I can not get past the communication errors when starting WUHU.

                Any clues?

                Dave Fossler
              • KNHBRIST1
                I am sure that if you post you error messages here, someone will be able to help. Steve
                Message 7 of 12 , Oct 12, 2012
                • 0 Attachment
                  I am sure that if you post you error messages here, someone will be able to help.
                  Steve

                  --- In wuhu_software_group@yahoogroups.com, "dfossler" <davefossler@...> wrote:
                  >
                  > I have used WUHU for several years. Last spring I lost my system due to a near lightning strike and just recently replaced it (WS-2310)
                  >
                  > The WS-2310 is synched to WWV (and is working as expected) and my computer is synched to an internet time server.
                  >
                  > I have the WS-2310 hooked direct serial to a COM1 port on my Dell.
                  >
                  > I can not get past the communication errors when starting WUHU.
                  >
                  > Any clues?
                  >
                  > Dave Fossler
                  >
                • Dave Fossler
                  Typical Log: Fri Oct 12 23:22:24 2012 WUHU monitoring started (WUHU21623XXSP). Fri Oct 12 23:22:24 2012 Weather Underground ID: KFLTOWNN2 Fri Oct 12
                  Message 8 of 12 , Oct 12, 2012
                  • 0 Attachment
                    Typical Log:
                     
                    Fri Oct 12 23:22:24 2012 > WUHU monitoring started (WUHU21623XXSP).
                    Fri Oct 12 23:22:24 2012 > Weather Underground ID: KFLTOWNN2
                    Fri Oct 12 23:22:24 2012 > Opened serial port COM1 successfully.
                    Fri Oct 12 23:22:34 2012 > An error occurred reading the storm alert from the console.
                    Fri Oct 12 23:22:34 2012 > Communications error or invalid/corrupt data retrieved from console.
                    Fri Oct 12 23:22:34 2012 > Time to next console communication: 5000 milliseconds.
                    Fri Oct 12 23:22:43 2012 > An error occurred reading the storm alert from the console.
                    Fri Oct 12 23:22:43 2012 > Communications error or invalid/corrupt data retrieved from console.
                    Fri Oct 12 23:22:43 2012 > Time to next console communication: 5000 milliseconds.
                    Fri Oct 12 23:22:51 2012 > An error occurred reading the storm alert from the console.
                    Fri Oct 12 23:22:51 2012 > Communications error or invalid/corrupt data retrieved from console.
                    Fri Oct 12 23:22:51 2012 > Time to next console communication: 5000 milliseconds.
                    Fri Oct 12 23:23:00 2012 > An error occurred reading the storm alert from the console.
                    Fri Oct 12 23:23:00 2012 > Communications error or invalid/corrupt data retrieved from console.
                    Fri Oct 12 23:23:00 2012 > Time to next console communication: 5000 milliseconds.
                    Fri Oct 12 23:23:08 2012 > An error occurred reading the storm alert from the console.
                    Fri Oct 12 23:23:08 2012 > Communications error or invalid/corrupt data retrieved from console.
                    Fri Oct 12 23:23:08 2012 > Time to next console communication: 5000 milliseconds.
                    Fri Oct 12 23:23:17 2012 > An error occurred reading the storm alert from the console.
                    Fri Oct 12 23:23:17 2012 > Communications error or invalid/corrupt data retrieved from console.
                    Fri Oct 12 23:23:17 2012 > Time to next console communication: 5000 milliseconds.
                    Fri Oct 12 23:23:25 2012 > An error occurred reading the storm alert from the console.
                    Fri Oct 12 23:23:25 2012 > Communications error or invalid/corrupt data retrieved from console.
                    Fri Oct 12 23:23:25 2012 > Time to next console communication: 5000 milliseconds.
                    Fri Oct 12 23:23:25 2012 > Detected consecutive communications failures. Attempting to recover by re-opening the port.
                    Fri Oct 12 23:23:36 2012 > Attempting to re-open port COM1.
                    Fri Oct 12 23:23:36 2012 > Port COM1 re-opened successfully, attempting to resume communications.
                    Fri Oct 12 23:23:39 2012 > An error occurred reading the storm alert from the console.
                    Fri Oct 12 23:23:39 2012 > Communications error or invalid/corrupt data retrieved from console.
                    Fri Oct 12 23:23:39 2012 > Time to next console communication: 5000 milliseconds.
                    Fri Oct 12 23:23:42 2012 > WUHU monitoring stopped.
                    Dave
                  • Eternal Danation
                    Hmmm, not sure but I would turn off all the storm alerts in WUHU and see what happens next. dan
                    Message 9 of 12 , Oct 12, 2012
                    • 0 Attachment
                      Hmmm, not sure but I would turn off all the storm alerts in WUHU and see what happens next.

                      dan


                      --- In wuhu_software_group@yahoogroups.com, Dave Fossler <davefossler@...> wrote:
                      >
                      > Typical Log:
                      >
                      > Fri Oct 12 23:22:24 2012 > WUHU monitoring started (WUHU21623XXSP).
                      > Fri Oct 12 23:22:24 2012 > Weather Underground ID: KFLTOWNN2
                      > Fri Oct 12 23:22:24 2012 > Opened serial port COM1 successfully.
                      > Fri Oct 12 23:22:34 2012 > An error occurred reading the storm alert from
                      > the console.
                      > Fri Oct 12 23:22:34 2012 > Communications error or invalid/corrupt data
                      > retrieved from console.
                      > Fri Oct 12 23:22:34 2012 > Time to next console communication: 5000
                      > milliseconds.
                      > Fri Oct 12 23:22:43 2012 > An error occurred reading the storm alert from
                      > the console.
                      > Fri Oct 12 23:22:43 2012 > Communications error or invalid/corrupt data
                      > retrieved from console.
                      > Fri Oct 12 23:22:43 2012 > Time to next console communication: 5000
                      > milliseconds.
                      > Fri Oct 12 23:22:51 2012 > An error occurred reading the storm alert from
                      > the console.
                      > Fri Oct 12 23:22:51 2012 > Communications error or invalid/corrupt data
                      > retrieved from console.
                      > Fri Oct 12 23:22:51 2012 > Time to next console communication: 5000
                      > milliseconds.
                      > Fri Oct 12 23:23:00 2012 > An error occurred reading the storm alert from
                      > the console.
                      > Fri Oct 12 23:23:00 2012 > Communications error or invalid/corrupt data
                      > retrieved from console.
                      > Fri Oct 12 23:23:00 2012 > Time to next console communication: 5000
                      > milliseconds.
                      > Fri Oct 12 23:23:08 2012 > An error occurred reading the storm alert from
                      > the console.
                      > Fri Oct 12 23:23:08 2012 > Communications error or invalid/corrupt data
                      > retrieved from console.
                      > Fri Oct 12 23:23:08 2012 > Time to next console communication: 5000
                      > milliseconds.
                      > Fri Oct 12 23:23:17 2012 > An error occurred reading the storm alert from
                      > the console.
                      > Fri Oct 12 23:23:17 2012 > Communications error or invalid/corrupt data
                      > retrieved from console.
                      > Fri Oct 12 23:23:17 2012 > Time to next console communication: 5000
                      > milliseconds.
                      > Fri Oct 12 23:23:25 2012 > An error occurred reading the storm alert from
                      > the console.
                      > Fri Oct 12 23:23:25 2012 > Communications error or invalid/corrupt data
                      > retrieved from console.
                      > Fri Oct 12 23:23:25 2012 > Time to next console communication: 5000
                      > milliseconds.
                      > Fri Oct 12 23:23:25 2012 > Detected consecutive communications failures.
                      > Attempting to recover by re-opening the port.
                      > Fri Oct 12 23:23:36 2012 > Attempting to re-open port COM1.
                      > Fri Oct 12 23:23:36 2012 > Port COM1 re-opened successfully, attempting to
                      > resume communications.
                      > Fri Oct 12 23:23:39 2012 > An error occurred reading the storm alert from
                      > the console.
                      > Fri Oct 12 23:23:39 2012 > Communications error or invalid/corrupt data
                      > retrieved from console.
                      > Fri Oct 12 23:23:39 2012 > Time to next console communication: 5000
                      > milliseconds.
                      > Fri Oct 12 23:23:42 2012 > WUHU monitoring stopped.
                      > Dave
                      >
                    • wuhu_software
                      The storm alert just happens to be the first item read from the console. When it fails, all attempts to communicate for other variables are aborted. Looking at
                      Message 10 of 12 , Oct 13, 2012
                      • 0 Attachment
                        The storm alert just happens to be the first item read from the console. When it fails, all attempts to communicate for other variables are aborted.

                        Looking at the log, my guess is that the console is not responding to any requests.

                        One thing that typically happens with nearby lightning and these La Crosse stations that are in "wired mode" is that the serial port on the PC becomes damaged. The strike probably zaps a transistor and the serial port is forever toasted.

                        You might be surprised to the learn that the console survived and only the serial port is damaged. That happened to me. I then bought an inline serial surge protector. The next time a lightning strike hit the surge protector saved the serial port and toasted the transistors in the console. The console worked but it's communication channel to the PC was toast.

                        Try a different serial port or a different PC and see if it works. My guess is that your old console is still functioning as well.


                        --- In wuhu_software_group@yahoogroups.com, "Eternal Danation" <weatherbear@...> wrote:
                        >
                        > Hmmm, not sure but I would turn off all the storm alerts in WUHU and see what happens next.
                        >
                        > dan
                        >
                        >
                        > --- In wuhu_software_group@yahoogroups.com, Dave Fossler <davefossler@> wrote:
                        > >
                        > > Typical Log:
                        > >
                        > > Fri Oct 12 23:22:24 2012 > WUHU monitoring started (WUHU21623XXSP).
                        > > Fri Oct 12 23:22:24 2012 > Weather Underground ID: KFLTOWNN2
                        > > Fri Oct 12 23:22:24 2012 > Opened serial port COM1 successfully.
                        > > Fri Oct 12 23:22:34 2012 > An error occurred reading the storm alert from
                        > > the console.
                        > > Fri Oct 12 23:22:34 2012 > Communications error or invalid/corrupt data
                        > > retrieved from console.
                        > > Fri Oct 12 23:22:34 2012 > Time to next console communication: 5000
                        > > milliseconds.
                        > > Fri Oct 12 23:22:43 2012 > An error occurred reading the storm alert from
                        > > the console.
                        > > Fri Oct 12 23:22:43 2012 > Communications error or invalid/corrupt data
                        > > retrieved from console.
                        > > Fri Oct 12 23:22:43 2012 > Time to next console communication: 5000
                        > > milliseconds.
                        > > Fri Oct 12 23:22:51 2012 > An error occurred reading the storm alert from
                        > > the console.
                        > > Fri Oct 12 23:22:51 2012 > Communications error or invalid/corrupt data
                        > > retrieved from console.
                        > > Fri Oct 12 23:22:51 2012 > Time to next console communication: 5000
                        > > milliseconds.
                        > > Fri Oct 12 23:23:00 2012 > An error occurred reading the storm alert from
                        > > the console.
                        > > Fri Oct 12 23:23:00 2012 > Communications error or invalid/corrupt data
                        > > retrieved from console.
                        > > Fri Oct 12 23:23:00 2012 > Time to next console communication: 5000
                        > > milliseconds.
                        > > Fri Oct 12 23:23:08 2012 > An error occurred reading the storm alert from
                        > > the console.
                        > > Fri Oct 12 23:23:08 2012 > Communications error or invalid/corrupt data
                        > > retrieved from console.
                        > > Fri Oct 12 23:23:08 2012 > Time to next console communication: 5000
                        > > milliseconds.
                        > > Fri Oct 12 23:23:17 2012 > An error occurred reading the storm alert from
                        > > the console.
                        > > Fri Oct 12 23:23:17 2012 > Communications error or invalid/corrupt data
                        > > retrieved from console.
                        > > Fri Oct 12 23:23:17 2012 > Time to next console communication: 5000
                        > > milliseconds.
                        > > Fri Oct 12 23:23:25 2012 > An error occurred reading the storm alert from
                        > > the console.
                        > > Fri Oct 12 23:23:25 2012 > Communications error or invalid/corrupt data
                        > > retrieved from console.
                        > > Fri Oct 12 23:23:25 2012 > Time to next console communication: 5000
                        > > milliseconds.
                        > > Fri Oct 12 23:23:25 2012 > Detected consecutive communications failures.
                        > > Attempting to recover by re-opening the port.
                        > > Fri Oct 12 23:23:36 2012 > Attempting to re-open port COM1.
                        > > Fri Oct 12 23:23:36 2012 > Port COM1 re-opened successfully, attempting to
                        > > resume communications.
                        > > Fri Oct 12 23:23:39 2012 > An error occurred reading the storm alert from
                        > > the console.
                        > > Fri Oct 12 23:23:39 2012 > Communications error or invalid/corrupt data
                        > > retrieved from console.
                        > > Fri Oct 12 23:23:39 2012 > Time to next console communication: 5000
                        > > milliseconds.
                        > > Fri Oct 12 23:23:42 2012 > WUHU monitoring stopped.
                        > > Dave
                        > >
                        >
                      • KNHBRIST1
                        I lost just my serial port also, all checks showed it was working, but it was not. A new serial port did the trick. Steve
                        Message 11 of 12 , Oct 13, 2012
                        • 0 Attachment
                          I lost just my serial port also, all checks showed it was working, but it was not. A new serial port did the trick.
                          Steve

                          --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...> wrote:
                          >
                          >
                          > The storm alert just happens to be the first item read from the console. When it fails, all attempts to communicate for other variables are aborted.
                          >
                          > Looking at the log, my guess is that the console is not responding to any requests.
                          >
                          > One thing that typically happens with nearby lightning and these La Crosse stations that are in "wired mode" is that the serial port on the PC becomes damaged. The strike probably zaps a transistor and the serial port is forever toasted.
                          >
                          > You might be surprised to the learn that the console survived and only the serial port is damaged. That happened to me. I then bought an inline serial surge protector. The next time a lightning strike hit the surge protector saved the serial port and toasted the transistors in the console. The console worked but it's communication channel to the PC was toast.
                          >
                          > Try a different serial port or a different PC and see if it works. My guess is that your old console is still functioning as well.
                          >
                          >
                          > --- In wuhu_software_group@yahoogroups.com, "Eternal Danation" <weatherbear@> wrote:
                          > >
                          > > Hmmm, not sure but I would turn off all the storm alerts in WUHU and see what happens next.
                          > >
                          > > dan
                          > >
                          > >
                          > > --- In wuhu_software_group@yahoogroups.com, Dave Fossler <davefossler@> wrote:
                          > > >
                          > > > Typical Log:
                          > > >
                          > > > Fri Oct 12 23:22:24 2012 > WUHU monitoring started (WUHU21623XXSP).
                          > > > Fri Oct 12 23:22:24 2012 > Weather Underground ID: KFLTOWNN2
                          > > > Fri Oct 12 23:22:24 2012 > Opened serial port COM1 successfully.
                          > > > Fri Oct 12 23:22:34 2012 > An error occurred reading the storm alert from
                          > > > the console.
                          > > > Fri Oct 12 23:22:34 2012 > Communications error or invalid/corrupt data
                          > > > retrieved from console.
                          > > > Fri Oct 12 23:22:34 2012 > Time to next console communication: 5000
                          > > > milliseconds.
                          > > > Fri Oct 12 23:22:43 2012 > An error occurred reading the storm alert from
                          > > > the console.
                          > > > Fri Oct 12 23:22:43 2012 > Communications error or invalid/corrupt data
                          > > > retrieved from console.
                          > > > Fri Oct 12 23:22:43 2012 > Time to next console communication: 5000
                          > > > milliseconds.
                          > > > Fri Oct 12 23:22:51 2012 > An error occurred reading the storm alert from
                          > > > the console.
                          > > > Fri Oct 12 23:22:51 2012 > Communications error or invalid/corrupt data
                          > > > retrieved from console.
                          > > > Fri Oct 12 23:22:51 2012 > Time to next console communication: 5000
                          > > > milliseconds.
                          > > > Fri Oct 12 23:23:00 2012 > An error occurred reading the storm alert from
                          > > > the console.
                          > > > Fri Oct 12 23:23:00 2012 > Communications error or invalid/corrupt data
                          > > > retrieved from console.
                          > > > Fri Oct 12 23:23:00 2012 > Time to next console communication: 5000
                          > > > milliseconds.
                          > > > Fri Oct 12 23:23:08 2012 > An error occurred reading the storm alert from
                          > > > the console.
                          > > > Fri Oct 12 23:23:08 2012 > Communications error or invalid/corrupt data
                          > > > retrieved from console.
                          > > > Fri Oct 12 23:23:08 2012 > Time to next console communication: 5000
                          > > > milliseconds.
                          > > > Fri Oct 12 23:23:17 2012 > An error occurred reading the storm alert from
                          > > > the console.
                          > > > Fri Oct 12 23:23:17 2012 > Communications error or invalid/corrupt data
                          > > > retrieved from console.
                          > > > Fri Oct 12 23:23:17 2012 > Time to next console communication: 5000
                          > > > milliseconds.
                          > > > Fri Oct 12 23:23:25 2012 > An error occurred reading the storm alert from
                          > > > the console.
                          > > > Fri Oct 12 23:23:25 2012 > Communications error or invalid/corrupt data
                          > > > retrieved from console.
                          > > > Fri Oct 12 23:23:25 2012 > Time to next console communication: 5000
                          > > > milliseconds.
                          > > > Fri Oct 12 23:23:25 2012 > Detected consecutive communications failures.
                          > > > Attempting to recover by re-opening the port.
                          > > > Fri Oct 12 23:23:36 2012 > Attempting to re-open port COM1.
                          > > > Fri Oct 12 23:23:36 2012 > Port COM1 re-opened successfully, attempting to
                          > > > resume communications.
                          > > > Fri Oct 12 23:23:39 2012 > An error occurred reading the storm alert from
                          > > > the console.
                          > > > Fri Oct 12 23:23:39 2012 > Communications error or invalid/corrupt data
                          > > > retrieved from console.
                          > > > Fri Oct 12 23:23:39 2012 > Time to next console communication: 5000
                          > > > milliseconds.
                          > > > Fri Oct 12 23:23:42 2012 > WUHU monitoring stopped.
                          > > > Dave
                          > > >
                          > >
                          >
                        • Dave
                          Well, that appears to be the issue. I hooked the unit to my laptop s serial port and everything is working as expected. I should have thought of doing they
                          Message 12 of 12 , Oct 13, 2012
                          • 0 Attachment
                            Well, that appears to be the issue. I hooked the unit to my laptop's serial port and everything is working as expected. I should have thought of doing they first.

                            Thanks

                            Dave

                            Sent from my iPad
                          Your message has been successfully submitted and would be delivered to recipients shortly.