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

17828Re: Communications error or invalid/corrupt data retrieve

Expand Messages
  • wuhu_software
    Nov 18, 2010
    • 0 Attachment
      Anything is possible. If you have a USB to serial adapter, that is the first usual suspect.

      If you are running wireless, this might be an issue however I see indoor reading errors, these are supplied by the console. This isolates the problem to the console or the PC or the link between them.

      Weak batteries in the console may or may not have an effect, I am not sure. The power pack should be plugged in to the same power strip as the computer otherwise there can be grounding issues.

      If the computer is very old, this could lead to a problem, especially if there is real-time anti-virus protection installed. I am running an old 900Mhz machine running Windows 2000 with anti-virus, and I do not have a problem.

      External noise could be an issue if you have some type of large appliances running on the same AC circuit like air compressors, refrigerators, or other high current devices.

      Nearby high power transmitters like Ham or CB could contribute however unless you are the source of such transmissions, that is fairly unlikely.

      Noise from other devices such as monitors or even the computer itself might be generating noise. Try moving the console as far away as possible from all other electronic devices that could be generating noise of some kind.


      --- In wuhu_software_group@yahoogroups.com, "donaho.robert@..." <donaho.robert@...> wrote:
      >
      > No. The computer is remote (at my farm) and basically runs the WUHU application on a pretty much dedicated basis. I checked the Scheduled Tasks and the only item that runs frequently (every hour) is the Google Updater (can't image this would cause the problem). Virus scan runs once a week. I did increase the priority of the WUHU process to Above Normal but no significant change - still getting errors about once an hour. Could this be a problem with the LaCrosse console? I'm connecting to the sensors wirelessly.
      > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@> wrote:
      > >
      > >
      > > That is interesting that the problem happened starting at 3:18pm until 8:55pm then stopped.
      > >
      > > This does not happen to coincide with the use of the computer (the monitor being turned on for example), virus scan, or something else that you can think of?
      > >
      > >
      > > --- In wuhu_software_group@yahoogroups.com, "Stephanie Donaho" <donaho.robert@> wrote:
      > > >
      > > > Here's an example from my log today. No errors after this. Did eventually
      > > > re-open the port.
      > > >
      > > >
      > > >
      > > > Wed Nov 17 15:18:38 2010 > An error occurred reading the wind speed and
      > > > direction from the console.
      > > >
      > > > Wed Nov 17 15:18:38 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 15:18:50 2010 > An error occurred reading the outdoor humidity
      > > > from the console.
      > > >
      > > > Wed Nov 17 15:18:50 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 15:19:11 2010 > An error occurred reading the wind speed and
      > > > direction from the console.
      > > >
      > > > Wed Nov 17 15:19:11 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 15:19:24 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 15:19:24 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 15:19:36 2010 > An error occurred reading the outdoor humidity
      > > > from the console.
      > > >
      > > > Wed Nov 17 15:19:36 2010 > Communications error or invalid/corrupt data
      > > > retrieved from console.
      > > >
      > > > Wed Nov 17 15:19:36 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 16:29:12 2010 > An error occurred reading the weather tendency
      > > > and forecast from the console.
      > > >
      > > > Wed Nov 17 16:29:12 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 16:29:25 2010 > An error occurred reading the indoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 16:29:25 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 16:29:39 2010 > An error occurred reading the outdoor humidity
      > > > from the console.
      > > >
      > > > Wed Nov 17 16:29:39 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 16:29:55 2010 > An error occurred reading the wind chill from the
      > > > console.
      > > >
      > > > Wed Nov 17 16:29:55 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 16:30:09 2010 > An error occurred reading the outdoor humidity
      > > > from the console.
      > > >
      > > > Wed Nov 17 16:30:09 2010 > Communications error or invalid/corrupt data
      > > > retrieved from console.
      > > >
      > > > Wed Nov 17 16:30:09 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 16:30:22 2010 > An error occurred reading the indoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 16:30:22 2010 > Communications error or invalid/corrupt data
      > > > retrieved from console.
      > > >
      > > > Wed Nov 17 16:30:22 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 16:30:34 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 16:30:34 2010 > Communications error or invalid/corrupt data
      > > > retrieved from console.
      > > >
      > > > Wed Nov 17 16:30:34 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 16:30:34 2010 > Detected consecutive communications failures.
      > > > Attempting to recover by re-opening the port.
      > > >
      > > > Wed Nov 17 16:30:44 2010 > Attempting to re-open port COM1.
      > > >
      > > > Wed Nov 17 16:30:44 2010 > Port COM1 re-opened successfully, attempting to
      > > > resume communications.
      > > >
      > > > Wed Nov 17 16:46:38 2010 > An error occurred reading the indoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 16:46:38 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 17:44:00 2010 > An error occurred reading the wind speed and
      > > > direction from the console.
      > > >
      > > > Wed Nov 17 17:44:00 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 17:44:13 2010 > An error occurred reading the indoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 17:44:13 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 17:44:25 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 17:44:25 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 18:43:54 2010 > Alarm High Dewpoint has been deactivated.
      > > >
      > > > Wed Nov 17 19:37:26 2010 > An error occurred reading the indoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 19:37:26 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 19:37:38 2010 > An error occurred reading the storm alert from
      > > > the console.
      > > >
      > > > Wed Nov 17 19:37:38 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 19:37:50 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 19:37:50 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 19:38:01 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 19:38:01 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 19:38:13 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 19:38:13 2010 > Communications error or invalid/corrupt data
      > > > retrieved from console.
      > > >
      > > > Wed Nov 17 19:38:13 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 19:38:24 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 19:38:24 2010 > Communications error or invalid/corrupt data
      > > > retrieved from console.
      > > >
      > > > Wed Nov 17 19:38:24 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 19:38:36 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 19:38:36 2010 > Communications error or invalid/corrupt data
      > > > retrieved from console.
      > > >
      > > > Wed Nov 17 19:38:36 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 19:38:36 2010 > Detected consecutive communications failures.
      > > > Attempting to recover by re-opening the port.
      > > >
      > > > Wed Nov 17 19:38:46 2010 > Attempting to re-open port COM1.
      > > >
      > > > Wed Nov 17 19:38:46 2010 > Port COM1 re-opened successfully, attempting to
      > > > resume communications.
      > > >
      > > > Wed Nov 17 19:38:51 2010 > An error occurred reading the storm alert from
      > > > the console.
      > > >
      > > > Wed Nov 17 19:38:51 2010 > Communications error or invalid/corrupt data
      > > > retrieved from console.
      > > >
      > > > Wed Nov 17 19:38:51 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 20:16:33 2010 > An error occurred reading the indoor humidity
      > > > from the console.
      > > >
      > > > Wed Nov 17 20:16:33 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 20:16:44 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 20:16:44 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 20:16:57 2010 > An error occurred reading the outdoor humidity
      > > > from the console.
      > > >
      > > > Wed Nov 17 20:16:57 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 20:33:50 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 20:33:50 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 20:55:04 2010 > An error occurred reading the storm alert from
      > > > the console.
      > > >
      > > > Wed Nov 17 20:55:04 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 20:55:21 2010 > An error occurred reading the rainfall total from
      > > > the console.
      > > >
      > > > Wed Nov 17 20:55:21 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 20:55:33 2010 > An error occurred reading the outdoor temperature
      > > > from the console.
      > > >
      > > > Wed Nov 17 20:55:33 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > > > Wed Nov 17 20:55:46 2010 > An error occurred reading the outdoor humidity
      > > > from the console.
      > > >
      > > > Wed Nov 17 20:55:46 2010 > Time to next console communication: 5000
      > > > milliseconds.
      > > >
      > >
      >
    • Show all 22 messages in this topic