Stop VISA from automatically sending termination characters on read

[SeanNorbury]

Is there a way to stop VISA from sending the termination characters on read? The instrument I am trying to communicate with (Olympus IX-81) requires 2 of them and it seems to be quite the hassle to implement them both during one command. I think it would be easier to just manually write them in with each command. 

[Dennis_Knutson]

VISA does not send any termination characters on a read. VISA stops a read when the specified termination character is detected in the received string. As mentioned in your other post, you can append them manually or automatically.

[caro16av]

Hi SeanNorbury,

As Dennis_Knutson said, VISA stops a read when the specified termination character is detected in the received string, which can be configured, please take a look at the following  tutorial and Knowledge Base article 

Termination Characters in NI-VISA
http://www.ni.com/tutorial/4256/en/

How Do I Add Termination Characters to VISA Serial Writes in LabVIEW?

http://digital.ni.com/public.nsf/allkb/862567530005F09C862565BE005AB500

Regards,

Carolina 

[SeanNorbury]

I have been on the phone with NI LabVIEW engineers 3 times trying to solve this issue. I am a physics student doing a favor for the biology department. I have many projects going on right now, and this one is taking up way too much of my time. I am looking for some assistance in solving this issue. The VI's provided by NI for this microscope do not work. I am not a LabVIEW specialist, nor do I have the time right now to learn all of the "ins and outs" of LabVIEW. I will be attending one of the training courses they offer when the opportunity arises, but right now I just need to get this problem solved. Dennis, your answers are vague just like 99% of the other programmers online giving advice to others. I understand that you are trying to get people to "learn", but I do not have the time for that right now. I just need to get this project done. Olympus is secretive about how software communicates with their devices, and I am assuming that is why this problem was never fixed. There are VI's for all of the microscope's functions in the package downloaded from NI, but none of them work. I am going to learn how to code properly in LabVIEW as soon as I can find the time, but I do not have that right now. I would really just appreciate some help solving this issue if either of you are up to it. Thank you.

[SeanNorbury]

Here is the link for the site that gives the ASCII codes for communication with the scope

http://madhadron.com/posts/2009-06-27-olympus-ix-81-chassis-commands.html

[crossrulz]

Do you have any code to show what you have tried?  And a manufacturer being sercretive is a huge obstacle.  I have been known to reverse engineer the protocol, but it can be difficult.

[Dennis_Knutson · Accepted solution]

Please do what I asked you to do in your other thread. Simply right click on the string control and report whether it says Normal Display, \ Codes Display, or Hex Display. Place a probe on the string input to the VISA Write and report exactly what the probe has. You have the instrument and the code and these are basic troubleshooting steps. You can also turn on NI Trace in MAX and attach the trace or report what it says. You said it was working with MAX so a comparison to the string sent there and what the VI is sending is an important step in isolating the problem.