07-07-2008 03:12 AM
07-07-2008 09:15 AM
Hello,
The driver only supports serial interface, but the help (in Initialize.vi) mentions USB interface kit included on the CD (below)
Notes:
(1) Either the SCOUT Pro RS232 or USB Interface Kit is required for use with this driver.
(2) The USB Interface kit includes a CD with the software drivers to create the required virtual port on the computer.
When sending a command from a computer to the balance, the application program sends a command to the virtual port as if it were an RS232 port. The computer then directs the command from the virtual port to the computers USB connector where the balance is connected. The Adapter Kit receives the USB signal and reacts to the command.
07-07-2008 09:22 AM
The first thing to determine is whether the USB is emulating an RS-232 port. If it is, then when you installed the driver and plugged the instrument into the pc, you would see a new serial port in windows device manager and in MAX (Measurment & Automation Explorer). If it does, then the driver should work. If a new serial port does not appear, then check in MAX and device manager if the instrument is using USB TMC. The Test and Measurement Class should also allow you to use the driver with a few small modifications. If the instrument is another class (i.e. HID), then you will have quite a bit of work to do. You will have to create an inf file for the instrument that defines it as a VISA connection and then use the USB RAW functions to read/write to the device after you get some pretty detailed information from the vendor.
If not RS-232 or USB TMC, the simplest thing would be to get a simple USB-RS232 converter. They are inexpensive.
07-07-2008 10:10 AM
07-07-2008 10:32 AM
07-07-2008 11:35 AM
07-07-2008 12:04 PM
The FTDI driver is setting the connection as RS232 (Comx) and you do not need to check if it is TMC.
I don't understand how you can remove the FTDI driver and still see a com port. Did you just remove the inf file or did you remove both the inf and pnf?
I would suggest you start by leaving everything as is after installing the USB driver. See if you get the busy error with that. Usually, it means that you have multiple resources tryinbg to access the same port. For example, windows will not allow you to use Hyperterminal and LabVIEW at the same time on the same port.
07-07-2008 03:01 PM