Products > Test Equipment
AR- 488 first time.
<< < (3/3)
HKJ:

--- Quote from: simba15 on December 16, 2022, 02:56:58 pm ---So see the attached screen cap,

I can communicate with the AR488 with Putty but cant get any data with Testcontroller.

Any ideas what I may have set incorrectly?

--- End quote ---

TC do not always support directly communicating with a device, it depends on the device configuration. Only for SCPI devices are there direct communication and answers are only expected on commands that ends with ?. All other device drivers has a internal SCPI like layer that translates a couple of commands* to something the device understands and translates the answers back to ascii.
*These commands are often defined in the definition file, but not always and will for many drives be shown in the help window.

On the "Load devices" page it look like this (With the AR488 definition posted above):


But it is not support for the 34401A.

It can easily be added, open the file: AgilentHP34401A.txt and change the line: "#port com" to "#port com gpib"
Then restart test controller (If the HP34401A is already added, remove it and add it again).

I have no idea if it works, but if somebody can report here that it works it will be added to the next release version of TC.

Also note: I still have a bug in the GPIB implementation, that means only one loaded device for each GPIB interface.
simba15:
Thanks HJK,

I set the def file as stated but unfortunately it seems it is still not working,

I cant see why tho, as the com port responds when I use putty. With TC I get no RX in the debug (you can see it send the correct gpib commands and *idn? but there is no RX.)

Any ideas what the issue could be? It seems to be related to the com port setup.

Thanks.
HKJ:

--- Quote from: simba15 on December 16, 2022, 04:36:42 pm ---I set the def file as stated but unfortunately it seems it is still not working,

I cant see why tho, as the com port responds when I use putty. With TC I get no RX in the debug (you can see it send the correct gpib commands and *idn? but there is no RX.)

Any ideas what the issue could be? It seems to be related to the com port setup.

--- End quote ---

Is the baudrate correct?

You can start TC with the debug .bat file and get more information about the communication (Note: Many errors will go to the DOS window, not the log).
simba15:
Hi HJK,

The baud rate is 115200, same is it is set in putty

Attached is the debug console and putty working with the same commands. ( I'm pretty sure i tried 9950ms and was the same result but will confirm)

If you have any ideas, I wonder if it is a setting related to the gpib.

Thanks.
HKJ:

--- Quote from: simba15 on December 21, 2022, 12:35:21 am ---Attached is the debug console and putty working with the same commands. ( I'm pretty sure i tried 9950ms and was the same result but will confirm)

If you have any ideas, I wonder if it is a setting related to the gpib.

--- End quote ---

I have no idea why it fails, everything looks correct.
Navigation
Message Index
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod