1. I am unsure if my Device Server is working, is there any type of diagnostic program I can use to test it?

2. I received an adapter labeled Q232/Q432, but I do not know what this should be used for.

3. What are the Operating Systems under which my Device Server is supported?

4. Why do I get a warning screen when I install Windows XP drivers downloaded from your website? What should I do?

5. How do I disable the Windows XP Driver Signing check?

6. Why can't I get my Quatech Device Server to perform at 921.6 kbps?

7. Do I need local administrator rights to install a Quatech Device Server?

8. I can't get my Device Server to turn on and no LEDs light up. What is the problem?

9. My serial device will not respond even though the Device Server is functioning, what is the problem?

10. Do I need special software or a specific web browser in order to administer my SDS?

11. Do I need to use a null modem cable between the Device Server and my serial device? What about on the Ethernet jack?
    
    
12. I see you list support for Linux. Does it support my kernel?
    
    
13. What security protocols are supported by your wireless device servers?
    
    
14. I have an application that uses the modbus protocol but I am unable to successfully communicate to my device what could be wrong?
    
    
15. I have several SDS units installed one one PC. How do I know what IP address goes to which virtual com port?
    
    
16. Can I view my SDS device server on more than one PC?
    
    
17. Why are all my system settings returning to default when my SDS device is reset?
    
    
18. Can I have my multiport ThinQ device unit set up with slave and master ports?
    
    
19. Does my ThinQ device support SSH protocol?
    
    
20. How many PC ’s can send data to a ThinQ device simultaneously?
    
    
21. I am trying to make changes in my web browser serial port properties but each time I try to submit a change I receive a “failed; invalid parameters” message.
    
    
22. Why am I not getting proper data from my SDS tunnel?
    
    
23. I am using a Raw TCP connection and have noticed that the connection goes away after inactivity on the serial port what could be the issue?
    
    
24. Is it possible to send breaks through the web interface?
    
    
25. Is it possible to reboot the SDS programmatically?
    
    
26. I am trying to install my SDS under Windows 2k/XP/Vista and when I run the NT DeviceManager.exe I receive the following error: “NT V4 service pack or higher"
    
    
27. Can you tell me the max cable distance that we can run rs232 devices from your SDS?
    
    
28. I do not remember the username/password I setup for my SDS what can I do to reset the password?

Q1. I am unsure if my Device Server is working, is there any type of diagnostic program I can use to test it?

A. There are several ways to go about testing the product. The easiest way for Windows users is to connect a Loopback on the port and use HyperTerminal to test it. RS-232 Loopback Instructions

Q2. I received an adapter labeled Q232/Q432, but I do not know what this should be used for.

A. This is a loopback adapter used to help troubleshoot issues you may be having with your Quatech card and your end device. You can attach the loopback adapter to your D-9 connection on your Quatech card and open a hyperterminal session. Please use the hyperterminal.pdf for further instructions on testing your Quatech card with the loopback adapter and hyperterminal application. Please note that Quatech provides a Q232 loopback adapter. If you have this adapter you can replace “the making a loopback” section of the hyperterminal.pdf with your Q232 already made loopback adapter.

Q3. What are the Operating Systems under which my Device Server is supported?

A. View the latest OS support matrix for Device Servers.

Q4. Why do I get a warning screen when I install Windows XP drivers that I downloaded from your website? What should I do?

A.Windows XP keeps a registry of all "Microsoft Certified" drivers, and provides a warning during any installation of an uncertified driver. This warning has nothing to do with the quality of the driver or its ability to function properly in your system. If any changes-even minor ones-- are made to a Microsoft Certified driver, that driver must go through the Microsoft Certification process again, which can take some time. The warning screen appears when the driver update has not yet made its way through the entire Certification process. Because we want to provide the best possible service for our customers, Quatech makes all driver updates available on our website prior to receiving Microsoft certification--this gets them into your hands faster! However, we always continue to make the most current signed version of the driver available.

When you see this warning during installation of a Quatech Windows XP driver, simply tell Windows that you want to install the driver and continue the standard installation process.

Q5. How do I disable the Windows XP Driver Signing check?

A. To disable Windows XP driver signing warnings, follow the steps below:

1. Double click on the System icon in Control Panel.
2. Left click on the Hardware tab.
3. Left click on the Driver Signing button. (click here for a screen cap of the Driver Signing Options Window
4. Choose the Ignore option. Click on O.K. and then Apply and O.K.
5. Windows will not warn anymore about driver signing.

Q6. Why can't I get my Quatech Device Server to perform at 921.6 kbps?

A. Data rates (or baud rates) are highly system dependent. It is impossible for Quatech to know exactly how one of our products will perform in your specific system. Some major factors that affect baud rate are cabling, OS, and FIFOs. For more information about maximum data rates, see the Quatech "Serial Data Rate Information Sheet".

Q7. Do I need local administrator rights to install a Quatech Device Server?

A. Yes. When installing most kinds of hardware, you must have local admin rights or equivalent on the PC. If your computer is part of a Domain or participates in a networked environment, please contact your local LAN Administrator for assistance.

Q8. I can't get my Device Server to turn on and no LEDs light up. What is the problem?

A. Your Device Server is not getting power. Make sure that the power adapter is properly connected to the power jack and that the power adapter is connected to a functioning electrical outlet.

If all your power connections seem ok, then you may have a damaged power adapter. Please contact our technical support department for assistance.

Q9. My serial device will not respond even though the Device Server is functioning, what is the problem?

A. Typically this means that there is a problem with the application software, serial interface cable or the serial device itself. Try the following to determine what is causing the problem:

1. Make sure the serial device is powered up.
2. Make sure the serial cable is properly connected to the serial device and to the SDS.
3. Try a different serial cable.
4. Try a different port on the SDS Device Server.
5. Review your serial device literature. Make sure that the settings it specifies match those the Device Server is using (check the serial port settings for the Device Server using the Web interface).
6. Try plugging the serial device directly into a PC using the same cable used with the Device Server’s serial port. If that works but the Device Server does not, then it’s likely that the application software is hard-coded to work with a built-in COM port. If it does not, then your serial device is malfunctioning or the serial cable is defective / incorrectly wired for the DTE interface

Q10. Do I need special software or a specific web browser in order to administer my SDS?

A.In order to ensure maximum compatibility with the Web interface provided by the Real-Time Operating System embedded in the SDS, please use Internet Explorer to change settings and view charts correctly.

Q11. Do I need to use a null modem cable between the Device Server and my serial device? What about on the Ethernet jack?

A. If the serial device has a DCE interface (like a modem), then you will need a straight-through serial cable. If the serial device has a DTE interface (like a PC), you will need a null modem cable. As for the Ethernet side, the Quatech premium line of device servers have an Auto MDI/MDIX interface, which means it will automatically adapt to either cable. So, whether connecting to a hub, switch, router or directly into a PC’s NIC, the Device Server is “smart” enough to know whether to crossover signals or not.

Q12. I see you list support for Linux. Does it support my kernel?

A. There are so many distributions of Linux and so many kernel modifications (one of the good and bad things about Open Source operating systems) that it’s impossible to tell with certainty whether our Linux drivers will work right out of the box for you. What we can say is that we internally test with the leading distributions/kernel releases and will be happy to help you use our products in your own customized application when possible. Please contact Technical Support for more information.

Q13. What security protocols are supported by your wireless device servers?

A. At this time, Quatech wireless device servers support 64/128-bit WEP and WPA protocols. We are currently working on WPA2 and a suite of EAP-based protocols, and will make announcements of their availability when finished. In the meantime, if you already have Quatech wireless device servers, please upgrade to the latest firmware version listed on our website to ensure that you have the best protection available.

Q14. I have an application that uses the modbus protocol but I am unable to successfully communicate to my device what could be wrong?

A. Quatech currently has not tested using any Modbus protocol so we are unable to provide any support for these type of applications.

Q15. I have several SDS units installed one one PC. How do I know what IP address goes to which virtual com port?

A. You can change your device manager view option to “view devices by connection.” This will show the individual unit with it’s corresponding IP address and virtual com port.

Q16. Can I view my SDS device server on more than one PC?

A. Yes, each PC would have to have the SDS software installed to view the Ethernet device.

Q17. Why are all my system settings returning to default when my SDS device is reset?

A. Please be sure you have selected a static IP address. The DHCP is used for the Ethernet unit to receive an unused IP address on the network. If the unit is reset while using a DHCP address all changes will be lost and your SDS device may take a new IP address.

Q18. Can I have my multiport SDS device unit set up with slave and master ports?

A. One unit can have both slave and master ports.

Q19. Does my SDS device support SSH protocol?

A. SSH protocol is used in a telnet session it packs up telnet data to send to a device. The SDS device line does not support this protocol.

Q20. How many PC ’s can send data to a SDS device simultaneously?

A. Only one PC can talk to the SDS device at a time.

Q21. I am trying to make changes in my web browser serial port properties but each time I try to submit a change I receive a “failed; invalid parameters” message.

A. You must use IE Internet Explorer. If you use Firefox, Mozilla, or any other web browser you will get this error message.

Q22. Why am I not getting proper data from my SDS tunnel?

A. Tunneling Mode does NOT support Auto Baud Rate Detection so you must set the baud rate accordingly.

Q23. I am using a Raw TCP connection and have noticed that the connection goes away after inactivity on the serial port what could be the issue?

A. The heartbeat does this to keep the port available to other computers should the original host hang.  This might be interfering with your application if it senses that the TCP connection goes away but doesn't know it's simply waiting for more data to reconnect automatically. To troubleshoot please set the heartbeat timer to 0 to disable it. Please let us know your results.

Q24. Is it possible to send breaks through the web interface?

A. No, it is not possible to send breaks (or any other serial data) via the web interface.

Q25. Is it possible to reboot the SDS programmatically?

A. Yes, it is possible to reboot the SDS programmatically with a UDP packet.  Your installation CD has detailed information on how to do this. This can be found in the Intellisock directory of the SDS installation CD.

Q26. I am trying to install my SDS under Windows 2k/XP/Vista and when I run the NT DeviceManager.exe I receive the following error:

“NT V4 service pack or higher"

A.The .exe you are trying to run is for Windows NT only. The proper .exe for Windows 2K/XP/Vista is labeled QTEWizard.exe.

Q27. Can you tell me the max cable distance that we can run rs232 devices from your SDS?

A. It depends greatly on the characteristics of the cable used.  Maximum resistance is 25 ohms and maximum capacitance is 2500 pF.  Appendix A of the specification gives a detailed description of how to calculate maximum length for a given cable.  It can be found here:
http://global.ihs.com/search_res.cfm?RID=TIA&INPUT_DOC_NUMBER=TIA-232

Q28. I do not remember the username/password I setup for my SDS what can I do to reset the password?

A. You will need to reset the unit. Please hold down the reset button and you will see the led slowly flash continue holding in the reset until the led starts flashing fast. Then release button and unplug the power. The unit should return back to factory defaults.