I've only used the RS232/GPIB converter to go from a GPIB bus to a serial instrument so I can't speak for going the other direction but I would give it a try. However, you have big problems with the driver if its the same one I just downloaded from NI. It's not really what I would call a driver at all but an application program meant to be used stand alone. There is no breakout of instrument functions into subVIs and none of the controls or indicators are on the connector so you can't even use the high level app as a subVI without a lot of work. It is a contributed driver but I'm surprised NI accepted it because it doesn't follow any of the published rules for an instrument driver. It's not even a good example of program design, imho. There is a VISA dr
iver available from Agilent
here and I would try that instead. To use a VISA driver with a serial port, you just specify the VISA resource name for that port instead of the GPIB resource name. For example, a GPIB resource name of an instrument with an address of 5 would be "GPIB::5::INSTR". To communicate to your instrument over com port 1, the VISA resource name is "ASRL1::INSTR". If the instrument has a serial port in addition to the GPIB, you could also try skipping the converter. Some VISA drivers work fine either way.