11-08-2023 08:36 AM - edited 11-08-2023 08:37 AM
@SB_123 wrote:
@rolfk
Thank you. Is *IDN?\r\n the serial command to the device? And, what do I expect in response?
According to the manual that you linked to in your first post in chapter 5.3.4, it is one of the Common Use Commands the instrument understands. However it seems to be not fully 488.2 compatible as this command is documented to be IDN? not *IDN? as I wrongly stated.
The \r\n is the termination character sequence that is normally needed for RS-232 communication. For GPIB it is not really needed since the GPIB bus has an explicit handshake line to indicate "end of message" but in RS-232 this does not exist so you need to use some special end of message indication in the command itself.
It should respond with a string with 4 comma separated values that identify the device and give extra information about the firmware version.
11-12-2023 05:53 PM
Thank you all for your help.
I ended up using the serial command in the device and I was able to validate the device response using VISA Test Panel in NI MAX. This is my first time using the tool and it seems to be great tool to validate the communication with the device.
I needed to find a way to know the test was triggered in the 16502, and then read the test result along with the resistance value, and I was able to find the appropriate command for it going through the device manual. I writing this to close this thread with this update incase someone come across this device in the future and sees this thread.
I am struggling to make it work with VISA functions with LabVIEW and I have started a separate thread for it (link below). Therefore, if anybody can help me troubleshoot the issue it will be highly appreciated.