Why problems sending GPIB from VC++ app via NI GPIB232CVA to a GPIB device?

[Carolus]

We are trying and failing to control a signal generator (Anritsu MG3692A) using GPIB commands sent from a Windows application on a PC. There is an issue of PC slot availability so we are using the NI GPIB-232-CV-A Converter instead of a GPIB card.

The hardware configuration is:

          [PC] ---- RS-232 Cable ---- [NI GPIB-232-CV-A] ----- GPIB Cable ----- [Anritsu MG3692A]

the GPIB-232-CV-A is in Controller (C) Mode, and with Timeout Termination mode (SW1 switches 6 and 7 both off).

The Windows application (MFC Dialog App) can send a GPIB command to the PC's COM port for transmission to the Anritsu. The application uses the ActiveX Control MSComm32 for communication with the COM port (have used before).

The GPIB-232-CV-A's Listen LED is ON prior to sending a GPIB command from the app, but goes out briefly and

the Talk LED goes ON briefly when the command is sent.

Have tried different switch settings on the GPIB-232-CV-A to no avail.

[JamesC]

HI Carolus,

What is the command you have sent?
In the Anritsu manual what do you expect to get back from the command you have sent?
Have you done a read command after the write? Have you told the read block how many bytes to read?
What does *IDN? give you as a return? (only garanteed to work if the device is 488.2 compliant)

Regards
JamesC
NIUK and Ireland

[Carolus]

Problem Solved.

Found that we need to have the COM port on the PC configured parity none, not odd or even. Also, for successful receipt of data from

instrument we need to have the COM port hardshaking set to comRTS.

Message Edited by Carolus on 04-10-2006 10:39 AM

[Carolus]

Found that we need to have the COM port on the PC configured  

[Carolus]

Found that we need to have the COM port on the PC configured