• Drivers Erdos Port Devices Lucie
• Drivers Erdos Port Devices Download
• Drivers Erdos Port Devices Gigabit
• Drivers Erdos Port Devices Inc

A library of over 250,000 device drivers, firmware, BIOS and utilities for Windows. Apart from updating your Drivers, installing a Driver Update Tool gives: Up to 3 times faster internet connection and download speeds; Better PC performance for games and audio applications; Smooth-running of all your PC devices such as printers, scanners etc. Better all-round performance of your PC due to automatic driver updates which will.

Supported Devices

Look in the orange area to the left. Click on the link for the type of device you're interested in. There, you'll find a list of devices that have ASCOM drivers available. Some come with the device itself, others are available from the Download Center here.

How to Get Support

If your device (e.g., telescope) shipped with its ASCOM driver, contact the device manufacturer first. Otherwise, if your device has a driver that was developed by a third party developer, the place to get help is either directly from the developer or on the ASCOM Talk group. People on the ASCOM-Talk group are happy to help with problems. Most driver authors want people to use their drivers and will at least lurk on the group. There are a number of things that you can do to help and these will result in getting a suggested fix much faster.

1. Report information accurately and completely. It is almost impossible to help if insufficient information is given. We get error reports that basically say 'ASCOM isn't working, please fix it'. If you are lucky you'll get emails asking questions. More likely you'll not get a reply at all.
2. Read the help that comes with the driver. Many support questions have already been answered in the driver help. This should be accessible from the driver setup or properties window.
3. If you can cause the problem at will, write down the steps you took to cause it, producing a 'repro scenario'. This can be invaluable information.
4. Contact the driver author or supporter directly or on the ASCOM-Talk group. Look in the driver help file for contact info.

Remember that we aren't looking over your shoulder; we can't see things that are totally obvious to you. We need to know:

• What brand of device (e.g. telescope and mount) you are using.
• What driver you have selected, including its version (normally visible on the driver setup or properties window).
• What application you are using.
• What PC operating system you are using, including the SP.
• Exactly what you did, what worked and what did not.
• An exact reproduction of any error messages, with what was done just before the error happened.
• Ideally an exact sequence of actions that will generate the error ( repro scenario).

Things to Try First

If the driver doesn't work at all then in the majority of cases it is one of the following causes:

• The connection cable between the PC and the mount.
• The cable between the PC and the mount (it's worth double checking, this is the source of the majority of problems).
• The USB to serial connector. These are very variable, good ones are fine but there are a lot that aren't so good and it's not obvious which are which.
• Is the right cable being used? (The Meade cable doesn't work with the Celestron and (presumably) vice versa).
• Is the cable connected to the correct port on the scope?
• Is the correct COM port being used? Some (poorly designed) USB to serial connectors can select a different port each time they are connected, especially if they are plugged into a different USB socket or in a different order.
• Is the correct driver being used?
• Installation problems tend to give rather cryptic errors saying that something does not exist or cannot be loaded. If you get these right at the start of trying to connect, or especially if you get this when you are trying to select a driver, then try reinstalling the ASCOM platform, then the driver. It may be necessary to uninstall the current installation and reinstall it.

If the driver connects and some things work but some don't or the driver connects in one application but not in others then the basic connectivity is OK and the challenge is to find out why a particular function isn't working; we need to know:

• What works, let us know what programs or functions work for you.
• What doesn't work, which program and where in the program it fails.
• The exact way it fails, including what you do, what happens and exactly what error messages are shown.
• If you are only trying advanced functions, such as guiding, but haven't tried something simple then it is a good idea to try a simple planetarium program, such as Cartes du Ciel, and see if the basic connectivity and control works.

A good technique, especially for application or script authors, is to post a code fragment that demonstrates the problem. Try to reduce this to the minimum that shows the problem.

Remember that some of the people involved in ASCOM are part time and often have other jobs, so replies can take a few days.

NextPreviousContents

Common serial port names are /dev/ttyS0, /dev/ttyS1, etc. Thenaround the year 2000 came the USB bus with names like /dev/ttyUSB0 and/dev/ttyACM1 (for the ACM modem on the USB bus). Multiport serialcard used somewhat differnt names (depending on the brand) such as/dev/ttyE5.

Since DOS provided for 4 serial ports on the old ISA bus:COM1-COM4, or ttyS0-ttyS3 in Linux, most serial ports on the newer PCIbus used higher numbers such as ttyS4 or ttyS14 (prior to kernel2.6.13). But since most PCs only came with one or two serial ports,ttyS0 and possibly ttyS1 (for the second port) the PCI bus can now usettyS2 (kernel 2.6.15 on). All this permits one to have both ISAserial ports and PCI serial ports on the same PC with no nameconflicts. 0-1 (or 0-3) are reserved for the old ISA bus (or thenewer LPC bus) and 2-upward (or 4-upward or 14-upward) are used forPCI, where older schemes are shown in parentheses . It's not requiredto be this way but it often is.

If you're using udev (which puts only the device you have on yourcomputer into the /dev directory at boottime) then there's an easy wayto change the device names by editing files in /etc/udev/. Forexample, to change the name of what the kernel detects as ttyS3 towhat you want to name it: ttyS14, add a line similar to this to/etc/udev/udev.rules
BUS'pci' KERNEL'ttyS3',NAME='ttyS14'

Drivers Erdos Port Devices Lucie

On-board serial ports on motherboards which have both PCI and ISAslots are likely to still be ISA ports. Even for all-PCI-slotmotherboards, the serial ports are often not PCI. Instead, they areeither ISA, on an internal ISA bus or on a LPC bus which is intendedfor slow legacy I/O devices: serial/parallel ports and floppy drives.

Devices in Linux have major and minor numbers. The serial portttySx (x=0,1,2, etc.) is major number 4. You can see this (and theminor numbers too) by typing: 'ls -l ttyS*' in the /dev directory. Tofind the device names for various devices, see the 'devices' file inthe kernel documentation.

There formerly was a 'cua' name for each serial port and it behavedjust a little differently. For example, ttyS2 would correspond tocua2. It was mainly used for modems. The cua major number was 5 andminor numbers started at 64. You may still have the cua devices inyour /dev directory but they are now deprecated. For details seeModem-HOWTO, section: cua Device Obsolete.

For creating the old devices in the device directory see:

Dos/Windows use the COM name while the messages from the serial driveruse ttyS00, ttyS01, etc. Older serial drivers (2001 ?) used justtty00, tty01, etc.

The tables below shows some examples of serial device names. TheIO addresses are the default addresses for the old ISA bus (not forthe newer PCI and USB buses).

For more info see the usb subdirectory in the kernel documentationdirectory for files: usb-serial, acm, etc.

Drivers Erdos Port Devices Download

On some installations, two extra devices will be created,/dev/modem for your modem and /dev/mouse for amouse. Both of these are symbolic links to the appropriatedevice in /dev.

Historical note: Formerly (in the 1990s) the use of/dev/modem (as a link to the modem's serial port) wasdiscouraged since lock files might not realize that it was really say/dev/ttyS2. The newer lock file system doesn't fall intothis trap so it's now OK to use such links.

Inspect the connectors

Inspecting the connectors may give some clues but is often notdefinitive. The serial connectors on the back side of a PC areusually DB connectors with male pins. 9-pin is the most common butsome are 25-pin (especially older PCs like 486s). There may be one9-pin (perhaps ttyS0 ??) and one 25-pin (perhaps ttyS1 ??). For two9-pin ones the top one might be ttyS0.

If you only have one serial port connector on the back of your PC,this may be easy. If you also have an internal modem, a program likewvdial may be able to tell you what port it's on (unless it's a PnPthat hasn't been enabled yet). A report from setserial (atboot-time or run by you from the command line) should help youidentify the non-modem ports.

If you have two serial ports it may be more difficult. You could haveonly one serial connector but actually have 2 ports, one of whichisn't used (but it's still there electronically). First check manuals(if any) for your computer. Look at the connectors for meaningfullabels. You might even want to take off the PC's cover and see ifthere are any meaningful labels on the card where the internal ribbonserial cables plug in. Labels (if any) are likely to say something like'serial 1', 'serial 2' or A, B. Which com port it actually is willdepend on jumper or PnP settings (sometimes shown in a BIOS setupmenu). But 1 or A are more likely to be ttyS0 with 2 or B ttyS1.

Drivers Erdos Port Devices Gigabit

Send bytes to the port

Labels are not apt to be definitive so here's another method. Ifthe serial ports have been configured correctly per setserial, thenyou may send some bytes out a port and try to detect which connector(if any) they are coming out of. One way to send such a signal is tocopy a long text file to the port using a command like: cpmy_file_name /dev/ttyS1. A voltmeter connected to the DTR pin (seeSerial-HOWTO for Pinout) will display a positive voltage as soon asyou give the copy command.

The transmit pin should go from several volts negative to a voltagefluctuating around zero after you start sending the bytes. If it doesn't(but the DTR went positive) then you've got the right port but it'sblocked from sending. This may be due to a wrong IRQ, -clocal beingset, etc. The command 'stty -F /dev/ttyS1 -a' should showclocal (and not -clocal). If not, change it to clocal.

Another test is to jumper the transmit and receive pins (pins 2 and 3of either the 25-pin or 9-pin connector) of a test serial port. Thensend something to each port (from the PCs keyboard) and see if it getssent back. If it does it's likely the port with the jumper on it.Then remove the jumper and verify that nothing gets sent back. Notethat if 'echo' is set (per stty) then a jumper creates an infiniteloop. Bytes that pass thru the jumper go into the port and come rightback out of the other pin back to the jumper. Then they go back inand out again and again. Whatever you send to the port repeats itselfforever (until you interrupt it by removing the jumper, etc.). Thismay be a good way to test it as the repeating test messages halt whenthe jumper is removed.

Drivers Erdos Port Devices Inc

As a jumper you could use a mini (or micro) jumper cable (sold in someelectronic parts stores) with mini alligator clips. A small scrap ofpaper may be used to prevent the mini clips from making electricalcontact where it shouldn't. Metal paper clips can sometimes be bentto use as jumpers. Whatever you use as a jumper take care not to bendor excessively scratch the pins. To receive something from a port,you can go to a virtual terminal (for example Alt-F2 and login) andtype something like 'cp /dev/ttyS2 /dev/tty'. Then at another virtualterminal you may send something to ttyS2 (or whatever) by 'echotest_message > /dev/ttyS2'. Then go back to the receive virtualterminal and look for the test_message. See Serial Electrical Test Equipment for more info.

Connect a device to the connector

Another way to try to identify a serial port is to connect somephysical serial device to it and see if it works. But a problem hereis that it might not work because it's not configured right. A serialmouse might get detected at boot-time if connected.

You may put a device, such as a serial mouse (use 1200 baud), on a portand then use minicom or picocom to communicate with that port. Thenby clicking on the mouse, or otherwise sending characters with thedevice, see if they get displayed. It not you may have told picocomthe wrong port (such as ttyS0 instead of ttyS1) so try again.

Missing connectors

If the software shows that you have more serial ports than youhave connectors for (including an internal modem which counts as aserial port) then you may have a serial port that has no connector.Some motherboards come with a serial port with no cable or externalserial DB connector. Someone may build a PC from this and decide notto use this serial port. There may be a 'serial' connector and labelon the motherboard but no ribbon cable connects to its pins. To usethis port you must get a ribbon cable and connector. I've seendifferent wiring arrangements for such ribbon cables so beware.

If you don't use devfs (which automatically creates such devices) anddon't have a device 'file' that you need, you will have to create it.Use the mknod command or with the MAKEDEV shell script.Example, suppose you needed to create ttyS0:

The MAKEDEV script is easier to use.See the man page for it. For example, if you needed to make thedevice for ttyS0 you would just type:

If the above command doesn't work (and you are the root user), lookfor the MAKEDEV script in the /dev directory and run it.

This handles the devices creation and should set the correct permissions.For making multiport devices see Making multiport devices in the /dev directory.

NextPreviousContents