CQC Problem: "connected to the device" when its not really connected

[Juan]

I was trying to test the ADA through the CQC driver but for some reason it shows that it is "connected to the device" even when it physically isn't connected. Let me know if you know what the problem might be since I'm trying to start the programming of the Suite 16. Also is there a way to know in which port a device is physically located in?

[Sergio D]

With serial connections, it very hard to determine if the device is actually connected or not. On most RS232 drivers, it will show as connected even if it's not. You should be able to tell if it can actually communicate with the ADA by changing one of the fields such as the current source or the power field. If nothing happens, then you know you aren't controlling it.

I'm not a 100% sure on your build but com port 1 is usally the port on the motherboard. Then your serial card should start with com3. So com3 should be port1 on the serial card and so on and so forth.

Lastly, on the ADA, make sure that you have the correct switches set on the ISO CAT set otherwise you won't be talking to the ADA. In your case I think it should be switch 1 and switch 3 that should be pressed.

Also, you need to wire everything correctly. The RackServer gets connected to the ISO CAT. The ISO cats plugs in to the WH-2000 using the special wire harness provided with the suite16. The suite16 also plugs into the WH-2000 using the special wire harness.

[Sergio D]

Another way to map out the ports is to use the GC-IRL be we sold you and plug into the different ports and add a GC-IRL driver to a specific COM port. That driver happens to know when it is or isn't connected to the device.