LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Visa session problem

Hello,
I am quite new to LabView. I have to control a Nikon microscope TE2000E with a RS-232. Before writing the program I have opened a VISA session with MAX (basic I/O) to check that I can communicate with the microscope. But when I type a command (e.g. [r][S][P][R][CR], [r]=status request, SPR = function, CR=delimiter) the microscope send an error. I think that this is because I don't write the question in the correct format. Does anybody know the correct format for sending commands?

Thanks in advance
Raimon
0 Kudos
Message 1 of 4
(3,081 Views)
Have you checked the command syntax first in something like Hyperterminal? The CR delimiter is probably a carriage return and not the characters C and R. Make sure that you are sending the control code. You can use the CR constant on the string palette and append this to your command or turn on '\' Codes display for the string control and use a \r for the carriage return.
Message 2 of 4
(3,077 Views)


@Raimon wrote:
Hello,
I am quite new to LabView. I have to control a Nikon microscope TE2000E with a RS-232. Before writing the program I have opened a VISA session with MAX (basic I/O) to check that I can communicate with the microscope. But when I type a command (e.g. [r][S][P][R][CR], [r]=status request, SPR = function, CR=delimiter) the microscope send an error. I think that this is because I don't write the question in the correct format. Does anybody know the correct format for sending commands?

Thanks in advance
Raimon





Hi Raimon

I am in a similar situation, new to labview and I have to set up a system to control the TE2000E via Labview. I was wondering if you had any luck getting things going, and if you could pass along any words of wisdom or sample vi's.

Thanks very much,
Jason
0 Kudos
Message 3 of 4
(3,056 Views)
Your instrument's user manual should have the correct format of commands. In general, in MAX if you click on the "Scan for instrument" button and the instrument is found and returned with descriptions, then the instrument should be able to respond to the command: *IDN? Just open the instrument communicator and query the device with this command, it should work.
0 Kudos
Message 4 of 4
(3,038 Views)