![]() |
|
|||||||
| Register | Search | Today's Posts | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Registered Member
Join Date: Aug 2003
Posts: 4
|
Stumbleverter crashes with GPS on virtual Ports
hi!
i'm using Comfoolery & DeviceComm Manager to share the GPS -Signal from COM5 to COM1, COM2 and COM6...works fine to have GPS in Netstumbler (using COM1), in navigations-software (using COM2) ...but not in Stumbleverter (using COM6). The same prob occurrs when using MS MapPoint 2002...which seems to be the REAL problem.... I get a runtime error approx. 1 second after program start after first GPS sequences are received by the apps. The problem ONLY occurrs, when using the virtual COM-Ports...if i do not share the COM-Port from the GPS and directly assign it to MapPoint or Stumbleverter it works perfekt. Any hints, HOW to get workaround and get it work with shared virtual COM-ports ? Paulchen |
|
|
|
|
|
#2 (permalink) |
|
Registered Member
Join Date: Aug 2003
Location: Orange County, CA
Posts: 10
|
Some applications (especially mapping programs, it seems) choke on virtual serial ports. I have had the same problem that you've reported with MapPoint and ComFoolery)
The alternatives (that I've found) seem to be: 1 - Other virtual port software: I am using ELTIMA (http://www.eltima.com) Serial Splitter right now. But, don't know what I'll do when the trial runs out, as the $99 price tag is too hefty for me. Some GPS applications VisualGPSXP (http://www.visualgps.net/VisualGPSXP/) for one, also can split the GPS signal. VisualGPSXP broadcasts on a TCP port just like ComFoolery, so it may not work well either. 2 - Connect NetStumbler directly to a com port and use a Script from the Scripts forum to relay information to MapPoint. 3 - Hardware solution through Y splitter cable and possible use of additional com port through USB / PCMCIA / other hardware. 4 - .... ???? RedDot |
|
|
|
|
|
#5 (permalink) | |
|
Registered Member
Join Date: Aug 2003
Posts: 8
|
Quote:
Now if someone knows of a serial<->USB cable that really works ... (Who's the genius who decided that laptops don't need RS-232 ports or floppies?) |
|
|
|
|
|
|
#6 (permalink) | |
|
Registered Member
Join Date: Aug 2003
Location: Orange County, CA
Posts: 10
|
Quote:
![]() Are serial->USB adaptors known for being flaky? I haven't actually tried one myself, just seen them around. RedDot |
|
|
|
|
|
|
#7 (permalink) | ||
|
Registered Member
Join Date: Aug 2003
Posts: 8
|
Quote:
Quote:
|
||
|
|
|
|
|
#8 (permalink) |
|
Too many secrets...
Join Date: Apr 2002
Location: Barcelona, Spain
Posts: 204
|
Hi,
For your general information, there are problems with the mscomm32.ocx control, used in Visual Basic programs for serial port control, in which the serial port interrupts are not received by the control, thus not firing the data received event. This causes the application to become deaf to incoming data. The devices that *can* be affected by this include, but are not limited to (snigger snigger, EULA-talk): - USB-to-serial converters. - Some low-cost PCMCIA adapters. - USB so-called docking stations. - Some virtual serial port software solutions, I've not tested them, so I can't tell you which. So, if you can, always use either a "real" serial port or a good PCMCIA adapter (Socket or Quatech work really well). Cheers, Mother |
|
|
|
|
|
#9 (permalink) |
|
Registered Member
Join Date: Aug 2003
Posts: 8
|
We'll find out in a week or so ... I just ordered one of those mouse-type GPS receivers with USB and a virtual serial port driver. And thanks for the tip on the VB bug. One more to add to the overstuffed VB bug bag. It's almost as full as the .Net bug bag.
|
|
|
|