Skip to main content

I have a new scoreboard/computer question that has me tearing my hair out.

I have a USB to serial connector that I finally got working, except for when there is something plugged into my first serial port. For instance, I can test the scoreboard through the USB to serial rig, but then when I plug the timer cable in, the scoreboard stops and freezes. I can designate the port, but it's when you plug it
in that it stops working.

My device manager says everything's working and my port conflict wizard says there's not a conflict. I read somewhere that you can change the port name (from Com3 to something else) but I can't figure out how to do that. Any ideas?


Originally posted 2 Jan 2002 by Margaret Brady margaretb@jacksonhole.com
Original Post

Replies sorted oldest to newest

It appears that you have some very weird stuff happening. Get another PC and try it again. It is not uncommon for the drivers of various devices to confuse each other.

Next time:

1) Read ALL of the instructions. Sometimes USB devices need to be plugged in after a certain point in the install

2) Disable your virus protection. sometimes Norton will prevent certain parts of drivers from beiong correctly installed

3) Ditch the USB adapter and get a PCMCIA adapter like the ones written about here.


Originally posted 2 Jan 2002 by Fred Patton
Keep in mind that laptops have a lot of kludgy hardware work-arounds to save space and power. The 80x86 design is kludgy to begin with, and with laptops the shortcomings of the basic Wintel PC design are exacerbated. Many of the more aggravating kludges involve video, but serial comms can get nasty as well.

Serial ports in the 80x86 design use what's known as cascading interrupts, which means a master, usually IRQ 2, actually serves as a conduit (so to speak) for an additional 8 interrupts (the slave). This can mean any interrupt above 7 can potentially interfere with IRQ2. If your motherboard is poorly engineered, IRQ2 can even
interfere with IRQ3, which are usually the two interrupts used for serial comms. USB further complicates matters, because for the 12-18 months or so of its existence, the USB spec had gray areas in it and some of the USB hardware on the market was buggy, even with normally well-engineered brands such as IBM and Compaq.

Imagine a wall outlet (AC power) with 8 plugs. Then some bonehead comes along and plugs a power strip with 8 additional outlets into plug #2. That's the basic idea behind cascading interrupts, and it's rife with problems.

In general, problems of this nature usually cause interference between COM1 and COM3, and between COM2 and COM4. What I would suggest is as follows:

1. Uninstall your USB serial device drivers.

2. Disable the device currently occupying COM2, which will be either your modem or your infrared port.

3. Re-install your USB serial driver, which will hopefully grab COM2, leaving you with timer data IN on COM1 and GAZ data OUT on COM2.

If you can get your two devices working as COM1 and COM2, or COM3 and COM4, that will eliminate the problem of a cascade-induced disruption.

The Fred's suggestion to use a serial comm PCMCIA card rather than USB is also a very good one. I'm not a big fan of USB in general, especially under some of the more unstable flavors of Windows such as 95, 98 and Millenium. Under Win2000, USB seems a bit more solid. USB is not supported under NT.


Originally posted 3 Jan 2002 by James Broder
james@skunkware.tv
Hey Guys -

Thanks for the lesson interrupt lesson - I must be closing in, huh?

I gave up on the USB in order to eliminate variables. I have a Socket I/O card, but I'm still having the same problem. I managed to configure my timer as com3 and my scoreboard as com4. I can get my scoreboard to work in either port, but only when the timer's not plugged in. I can get my timer to work in either port and it
ignores whether the scoreboard is plugged in or not. (But the scoreboard won't work because the timer's plugged in!) I have a feeling I'm short an interrupt, but I can't find a way to disable the infrared interrupt - I can't even find one.

This run-around happens with two different laptops that both run 98 - a dell and a toshiba. I haven't tried Chase's suggestion, but I'll get back to you.


Originally posted 6 Jan 2002 by Margaret Brady

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×