VISA read problem

[yoli]

hi,

i am using labview 8.2.1 and trying to send commands to my microscope, olympus ix81.

im using the drivers i downloaded from NI.

i noticed that i can't preform a certain visa read, attached as Ol_control.vi

however i can preform other visa reads to the microscope and see them working in the microscope. for example - SET OBJECTIVE.vi

can someone look at these vi's and tell me what it the diffrence? and why can't i preform the action in ol_control.vi ?

[Dennis_Knutson]

In OI_Control, the command is terminated with just a CR and in Set Objective, the command is terminated with a CR and LF. This is the same solution in the other thread you posted to.

[yoli]

thank you very much, it worked.

another problem i have is that there are vi's in the olxxx2 that requires "OLXXX2 Olympus Command.vi" however i can not find it in the olxxx2 pack i downloaded from here.

where can i find it?

[Dennis_Knutson]

In _olxxx2.llb that was part of the zip file you downloaded.

[yoli]

Thank you again!

I

[yoli]

Thank you again!

I have

[yoli]

Thank you again!

I have another

[yoli]

Thank you again!

I have another problem though: In the Olympus Command.vi I Sometimes get from the visa read's read buffer 1x which ends in an error (and doesnt do anything).

it happends in the Select Filter Wheel.vi, OLXXX2 Configure Jog.vi, however it doesn't happen in the configure lamp.vi

here are the drivers

[NathanT]

Hello Yoli,
    I took a look at the driver, but did not see any differences in particular that would be obviously problematic.  Could you please provide more information as to the conditions that are present when the error occurs, and also please elaborate on "Sometimes"?  Ideally, you could reduce the code down to the bare minimum that reproduces the error everytime.  To go a step further, you can use highlight execution and/orr breakpoints to find out exactly which command is generating the errors.  After doing that, you have the power to look at the programming manual for your device and see if the driver is incorrect.  If it is, you can make the necessary changes and let us know, so that we can also change the driver.
    Something that is worth doing before all of that investigation, is upgrading the devices firmware.  Please let us know how it goes.

Cheers,

NathanT

[yoli]

Thank you very much on all of your help.

So far we manage to overcome all the issues we had.

Apparently the last problem was a definition problem.

Thank you again,

Cheers,

Yoli