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

Re: Communication errors

Expand Messages
  • 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 1 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 2 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 3 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 4 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 5 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.