There are new laptops without serial port, but a RS232-USB adaptor can be used to connect the IDE-Series to PCs. This adaptor creates a virtual COM port that can be selected on the program to work with the unit as usual. Theoretically any RS232-USB adaptor will work with this device, requirements are 9,600 baud transfer. We can supply a well-tested adaptor if you can not find a suitable one. See similar questions...

Yes, because the SignaLink doesn't require a connection to the computer's serial port! Unlike other interfaces, the SignaLink never requires a serial port connection. This is particularly handy if your computer doesn't happen to have one! In addition to simplifying your installation, this feature also reduces the likelihood of the computer's RF noise getting into your radio. It also eliminates serial port related transmit problems that plague other interfaces. See similar questions...

This is a communication port on the back of the computer where your cable will plug into the computer. See similar questions...

Some laptop computers don't have serial ports, but they do usually have at least one USB port. There are a number of very inexpensive converter cables available. They use a device driver to create a serial port under windows operating system. The driver that comes with the converter cable must be compatible with your version of windows of course, and the USB ports must be functioning, both in hardware and in the operating system and in the drivers for the convertor cable. See similar questions...

The serial port should be located on the back of your computer. An example of a serial port image is provided here. See similar questions...

You can buy a USB-to-serial adapter cable that plugs into the USB port on your computer. Radio Shack sells one for $40. The program's internal timer is very easily disrupted by other applications running on your computer. If another program takes control of the CPU for as little as 30 milliseconds, it will be cause a noticeable glitch in the sound of your bug. If this happens often enough, it sounds like there's something wrong with the bug. See similar questions...

The IBM ThinkPad also has a IrDA port that can collide with your serial/COM port. The best way to solve this problem is to disable the IrDA port. This can be done in the Device Manager (varies per operating system version). While you're there, verify that the serial/COM port is enabled. When asked, reboot the PC. This will re-enable the serial/COM port. After the computer reboots, return to the Device Manager and determine which port number the serial/COM is now on. See similar questions...

If you are still using MATLAB 5.x, you might find something on this page: http://www.mathworks.com/matlabcentral/fileexchange/Category.jsp?type=category&id=34 See similar questions...

A#8.15: This is usually caused by serial port configuration problems. Common symptoms may be: % copycat .ttyco .ttya Error opening tty .ttya, aborting. or % /usr/sbin/getty 8bit.38400 .ttya getty: .ttya: I/O error The first thing to check is that the following GNO serial port drivers exist: /dev/modem /dev/printer Next, ensure the following two lines are in your /etc/tty.config file, and that they are uncommented: modem 2 .ttya printer 1 . See similar questions...

I've connected the USB to Serial adapter but it's on Com Port 5 (or higher) and your software only has Ports 1-4. This issue applies to the c\temp software only. This has been resolved with the new version of the MDAS-Pro software. If you do not have a copy of this software, please contact us. See similar questions...

Some unnamed clone cards have also been known to work, especially those that claim to be AST compatible. USB device support was added to FreeBSD 3.1. However, it is still in preliminary state and may not always work as of version 3.2. If you want to experiment with the USB keyboard support, follow the procedure described below. Add the following lines to your kernel configuration file, and rebuild the kernel. See similar questions...

Remove the “pvr” driver from your kernel configuration, rebuild your kernel, and you'll automatically fall back to serial console. See similar questions...

For Unix, see a Usenet post by Mitch Chapman: http://groups.google.com/groups?selm=34A04430.CF9@ohioee.com See similar questions...

It's system-dependent. Under Unix, you typically open, read, and write a device file in /dev, and use the facilities of the terminal driver to adjust its characteristics. (See also questions 19.1 and 19.2.) Under MS-DOS, you can use the predefined stream stdaux, or a special file like COM1, or some primitive BIOS interrupts, or (if you require decent performance) any number of interrupt-driven serial I/O packages. See similar questions...

It allows the application to interface to the GPS receiver through the same interface (commands and logs) as an external controller would through a physical com port. See similar questions...

The serial port is a 9-pin D shaped connector, similar to the video connector except with less pins. Usually, there are two on a PC. One may possibly be in use by the mouse (mainly on older machines). They are also referred to as Com ports or Communications ports. They are identified in Windows as Com1, Com2 etc. Look in the device manager under "ports" and you will see if you have any set up - if not, you may have to enable them in you motherboard's bios via the CMOS setup utility. See similar questions...

Answer: Three serial ports are provided. One can be used for external control from a modem or other serial device. The other ports can connect to managed serial devices (such as routers, PCs, servers, or other RS-232 devices). Port 3 is the default control port. Ports 1 & 2 use the PC standard DTE pinout, with RXD on pin 2, and TXD on pin 3 of the male DB-9. Port 3 has TXD on pin 2, and RXD on pin 3 of the female DB-9. Port 3 offers hardware handshaking; ports 1 & 2 do not . See similar questions...

Johan Bevemyr wrote one which works for unix machines. The code is freely available at the contributions area as serial-1.0. There have been discussions on the mailing list about writing a more general driver which also works on windows machines. Nothing much has come of this (lack of interest?). See similar questions...