WXforum.net
Miscellaneous Debris => Tech Corner => Topic started by: aleutianman on November 05, 2009, 03:33:25 PM
-
tried to use a keyscan 19 hs to work with my lc 3610 installed the cd loaded the latest driver from key and it doesnt recognize the connection had a moschip serial but for some reason i am not getting anything there either. ive deleted everything from the puter and reloaded it all and am now frustrated. the comp has xp for the os.
-
Are there any other USB to serial drivers loaded on the computer, say an old one that you aren't using. I think there is a potential for conflict if there are multiple drives from different manufacturers.
-
the 3600 station type does not use standard serial communications
and so only a good quality adaptor and driver will work
try seeing if there is a more recent driver available for your adpator
-
I recently switch from my express card-serial to usb-serial.
http://www.wxforum.net/index.php?topic=5694.msg52134#msg52134 (http://www.wxforum.net/index.php?topic=5694.msg52134#msg52134)
-
tried everything and gave up. returned item to store.
-
ordere an iog guc232a online which most everyone here agrees is the way to go
Thank You everyone
-
back to square one. i now have the iog. loaded the cd and still am not getting my lacrosse to recognize it. i loaded the xp driver 2.0 and then tried the hookup from the guc232a to the serial on the ws. nada :? ](*,) :mad: now what? give up.
-
Get the latest IOGear driver from their website.
-
have the latest driver now how do i install or make it work?
-
After the install, you usually need to reboot.
After the reboot, the computer should use the latest software and you should be good to go.
-
wuhu i did that and i can't get the lacrosse to connect it doesnt see or recognize anything at any of the coms. we are limited here in alaska as far as getting the right equipment.(fairbanks) will i have to try to go back to a serial device?
-
Are you sure that you are attempting to connect to the correct port? Have you checked the device driver status under Hardware Manager to see if the driver is functioning? You might want to verify the port number assigned to the adapter by right clicking the port in device manager, select properties, then click the Port Settings tab, then the "Advanced" button. If you are trying to run the USB adapter through a USB hub, I would not recommend doing so, connect it directly to one of the USB ports on the machine.
-
assertion failed see the Visual C + + documentaion on asserts. this is junk to me i am now a comp person so i don't know what to do anymore?
-
What did you run right before the assertion was displayed??
-
heavy weather
-
heavy weather
I would re-install it. If I had to guess, it is trying to open the wrong port.
You could also run WUHU instead of Heavyweather, Heavyweather is a bit of a resource hog. I am assuming you are using a WS-23XX station type?
http://tech.groups.yahoo.com/group/wuhu_software_group/ (http://tech.groups.yahoo.com/group/wuhu_software_group/)
-
ws 3610-al. i have deleted uninstaled reinstellled double checked my com ports?
-
ws 3610-al. i have deleted uninstaled reinstellled double checked my com ports?
Still crashing on startup?
For the WS-36XX You must be running Heavyweather Pro, not Heavyweather or Heavyweather Beta 2.0. Pro is also not to be confused with yet another version, Heavyweather Professional.
http://www.heavyweather.info/
WUHU can also talk directly to the WS-36XX units.
-
wuhu software tried running hvy 2.0 beta as you can see by the pictures i don't know what else to do ](*,) [-o<
-
Firstly, For a WS-36XX, you do not run Heavyweather. The screen shot you are showing is for the WS-23XX station types only, not the WS-36XX.
Kill Heavyweather, do not run any version of it (Pro, Professional, or any other version).
In WUHU General Settings, in the first Box, select WS-36XX Direct Serial, to the right of that, select the com port that the console is connected to. Hit Start.
-
did as told heres where i am at
-
did as told heres where i am at
Are you 100% certain that you have the console connected properly to COM5?
Cables secured?
-
synched the clocks, rechecked the wires, ready to throw the towel in
-
I hear you there.
Can you try connecting to a different computer?
-
did as told heres where i am at
Looking at the picture of the log made me think of what I've been going through the past couple of days. It may or may not be applicable.
I have the 2315. It worked fine for months, then it just stopped (-- for outside temp and wind). I moved it into the next room so that it would be just a couple of feet from the outside transmitter (it's running wireless). Did a complete reset of the console. The sensors started receiving and I thought everything was well again.
However it would not talk to the computer. I started getting "corrupt information" and "cannot match the clock" and "cannot read storm alert" error messages in the log.
I rebooted, changed from serial to usb, reset the console, tried the console on ac only, battery only, tried unplugging and replugging the data cable, etc. I took the batteries out and unplugged the console and let it set for 24 hours. nothing seemed to work.
It wasn't WUHU, because Cumulus wouldn't read the console, either.
This is strange, but the way I got it working was when I did another reset of the console, when I got to setting the barometer alarm (I guess that's what it is), I changed some of those setpoints (I hadn't done that in the past) and low and behold, it started working. I have no idea why.
Anyways, I don't know if the 36XX unit have that feature in the setup, but it might be worth a try.
There's my $0.02
Good luck!
-
i have shut down the pws recalibrated to the nearest pws snyc the closks rebooted tried on two different comps?
-
i have shut down the pws recalibrated to the nearest pws snyc the closks rebooted tried on two different comps?
If you cannot make it work on either computer, and you are certain that you are pointing to the correct serial ports, this would suggest a couple possibilities. Firstly, it could be something simple like the serial cable itself. We can track down the pinout from the PC serial connector to the RJ port if you have a continuity tester. The second possibility is that the console is somehow damaged and refuses to communicate. I do recall some setting in the WS-36xx about enabling the radio time... If that is not set correctly, the console will not communicate although cannot recall what it was... Did you change any setting in the console related to WWVB time?
-
i have shut down the pws recalibrated to the nearest pws snyc the closks rebooted tried on two different comps?
Here is the pinout for the DB-9 to RJ connection that runs between your PC and the console:
I just ran down the pinouts for the cable on the WS-3610. It is also
a 6 conductor (sorry, thought it was 4, I should have known better).
Holding the RJ connector, tab down, cord toward you, numbering left
to right (1-6):
RJ1) DB9 pin 5
RJ2) DB9 pin 3
RJ3) DB9 pin 4
RJ4) DB9 pin 7
RJ5) DB9 pin 6
RJ6) DB9 pin 8
Using a continuity checker (built in to most volt meters), verify that all of the pin to pin connections are good.
-
will look for my tester in the mean time the vvmb radio clock is on and the time is set for alaska. my pc and the pws have the exact same time.