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

Re: [wuhu_software_group] Re: Runtime error

Expand Messages
  • Karl Kingston
    Yup... Might have been a glitch on my end or even the NetCom drivers being out of sync (I could connect just got crap). So I just took care of that and
    Message 1 of 8 , May 17, 2009
    • 0 Attachment
      Yup... Might have been a glitch on my end or even the NetCom drivers
      being out of sync (I could connect just got crap). So I just took care of
      that and reinstalled WUHU so I'm all set now.

      Now I've got to wait for a power failure while I'm at work and see if the
      startup delay will take care of my startup issue.

      Thanks again!


      On Sun, 17 May 2009, wuhu_software wrote:

      >
      > You are running Ok with the latest version?
      >
      > Thanks
      >
      >
      > --- In wuhu_software_group@yahoogroups.com, Karl Kingston <kkingsto@...> wrote:
      >>
      >> Did that. Even tried going back and working my way up. Seems to be OK
      >> now.
      >>
      >>
      >>
      >> On Sun, 17 May 2009, wuhu_software wrote:
      >>
      >>>
      >>> Karl,
      >>>
      >>> I cannot remember the last time that the WS-23XX communication was touched... Perhaps it was a fluke. Maybe try a reboot before installing new version. With Windows, it is hard to say have the serial port and drivers clean up after a port was in use.
      >>>
      >>>
      >>> --- In wuhu_software_group@yahoogroups.com, Karl Kingston <kkingsto@> wrote:
      >>>>
      >>>> OK. Just downloaded the B71 version from the website and seems to be OK.
      >>>> Wonder if there's a difference between the B71 and the full version.
      >>>>
      >>>>
      >>>> On Sat, 16 May 2009, Karl Kingston wrote:
      >>>>
      >>>>> OK just added this to the config file and looks OK. BUT at the same time, I
      >>>>> also upgraded to the latest version that was on the website. Now I can't
      >>>>> talk to the console. (I'm running the Netcom device).
      >>>>>
      >>>>> Here's what I get:
      >>>>>
      >>>>> Sat May 16 15:11:48 2009 > WUHU monitoring started (WUHU21623XXSP).
      >>>>> Sat May 16 15:11:48 2009 > Weather Underground ID: KNYMINOA1
      >>>>> Sat May 16 15:11:48 2009 > Weather Underground URL:
      >>>>> http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=KNYMINOA1
      >>>>> Sat May 16 15:11:48 2009 > CWOP ID: CW8614
      >>>>> Sat May 16 15:11:48 2009 > CWOP URL:
      >>>>> http://www.findu.com/cgi-bin/wxpage.cgi?call=CW8614
      >>>>> Sat May 16 15:11:48 2009 > PWSWeather ID: KNYMINOA1
      >>>>> Sat May 16 15:11:48 2009 > PWSWeather URL:
      >>>>> http://www.pwsweather.com/obs/KNYMINOA1.html
      >>>>> Sat May 16 15:11:48 2009 > Opened serial port COM3 successfully.
      >>>>> Sat May 16 15:11:55 2009 > User has skipped initial boot up pause. Proceeding
      >>>>> to history retrieval immediately.
      >>>>> Sat May 16 15:12:41 2009 > Could not fetch last record time from console.
      >>>>> Aborting.
      >>>>> Sat May 16 15:12:41 2009 > Console history was not read completely. 0 records
      >>>>> were collected. 0 records were stored. 0 records were uploaded. 0 records
      >>>>> were uploaded to PWSWeather
      >>>>> Sat May 16 15:12:50 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:12:50 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>> Sat May 16 15:12:59 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:12:59 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>> Sat May 16 15:13:08 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:13:08 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>> Sat May 16 15:13:17 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:13:17 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>> Sat May 16 15:13:26 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:13:26 2009 > Communications error or invalid/corrupt data
      >>>>> retrieved from console.
      >>>>> Sat May 16 15:13:26 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>> Sat May 16 15:13:35 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:13:35 2009 > Communications error or invalid/corrupt data
      >>>>> retrieved from console.
      >>>>> Sat May 16 15:13:35 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>> Sat May 16 15:13:44 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:13:44 2009 > Communications error or invalid/corrupt data
      >>>>> retrieved from console.
      >>>>> Sat May 16 15:13:44 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>> Sat May 16 15:13:44 2009 > Detected consecutive communications failures.
      >>>>> Attempting to recover by re-opening the port.
      >>>>> Sat May 16 15:13:54 2009 > Attempting to re-open port COM3.
      >>>>> Sat May 16 15:13:54 2009 > Port COM3 re-opened successfully, attempting to
      >>>>> resume communications.
      >>>>> Sat May 16 15:13:58 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:13:58 2009 > Communications error or invalid/corrupt data
      >>>>> retrieved from console.
      >>>>> Sat May 16 15:13:58 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>> Sat May 16 15:14:07 2009 > An error occurred reading the storm alert from the
      >>>>> console.
      >>>>> Sat May 16 15:14:07 2009 > Communications error or invalid/corrupt data
      >>>>> retrieved from console.
      >>>>> Sat May 16 15:14:07 2009 > Time to next console communication: 5000
      >>>>> milliseconds.
      >>>>>
      >>>>>
      >>>>> I have fired up HeavyWeather (had to install it) and it is retrieving data
      >>>>> fine. Wonder if something changed between the version I had running before
      >>>>> and the updated version.
      >>>>>
      >>>>>
      >>>>> On Thu, 14 May 2009, wuhu_software wrote:
      >>>>>
      >>>>>>
      >>>>>> Karl,
      >>>>>>
      >>>>>> On some systems, for whatever reason, the printer drivers are not loaded
      >>>>>> immediately on boot.
      >>>>>>
      >>>>>> You can exit WUHU and edit the WUHU Configuratio.ini and add a key to delay
      >>>>>> the startup.
      >>>>>>
      >>>>>> [General Settings]
      >>>>>> .
      >>>>>> .
      >>>>>> .
      >>>>>> Startup Delay=60
      >>>>>>
      >>>>>> Where Startup Delay is the number of seconds to delay before attempting to
      >>>>>> start (at which point Teechart.ocx wants to see the printer drivers
      >>>>>> loaded).
      >>>>>>
      >>>>>> Give that a shot, let me know if it works for you.
      >>>>>>
      >>>>>>
      >>>>>> --- In wuhu_software_group@yahoogroups.com, Karl Kingston <kkingsto@>
      >>>>>> wrote:
      >>>>>>>
      >>>>>>> OK and was trying to figure out why WUHU wasn't working. We had a power
      >>>>>>> failure and thus, my computer went down (but promptly restarted when power
      >>>>>>> was restored). When I checked the computer, I saw a popup box with:
      >>>>>>>
      >>>>>>> Runtime error 217 at 00021AEE
      >>>>>>>
      >>>>>>> Clicking on that gets me:
      >>>>>>>
      >>>>>>> Unable to create chart dialog. Program will now terminate.
      >>>>>>>
      >>>>>>> Reclicking on the WUHU icon starts up normally.
      >>>>>>>
      >>>>>>> What's happening here? Do I need some kind of delay or something? If so,
      >>>>>>> how?
      >>>>>>>
      >>>>>>> Running 1.0.216.61
      >>>>>>>
      >>>>>>> Thanks
      >>>>>>>
      >>>>>>
      >>>>>>
      >>>>>>
      >>>>>
      >>>>
      >>>
      >>>
      >>>
      >>
      >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.