From Lab view 6.0 to 7.0

[pathman]

Sir/Madom
I used modified Hioki impedencemeasurement.vi with labview 6.X .That was working well. Now I installed the Labview 7.0 and try to measure , But I didn't get correct result.
It is not working.
Ther is no error message.
thank you
regards
pathman

[Ray.R]

Hi pathman,

Can you provide us with more details? If your vi worked in LV6, it should (in theory) work with LV7.

You have a Hioki Impedance Meter, right? What do you mean by "modified impedancemeasurement.vi"?

The first thing is: how do you communicate with the instrument? (GPIB, serial, other?)

Can you define what you mean by incorrect result and "not working"?

If you didn;t get an error message, do you mean that it ran, made measurements, completed it's task (vi) and provided measurement values without giving you an error? That would mean that it is working but could provide incorrect results....

So:

1. Can you communicate with the instrument?
2. Does the vi run?
3. Does the vi make measurements from the instrument?
4. Incorr
ect results. What type of results are you getting?

The more info we have, the easier it will be to help you.

Regards,

JLV

[pathman]

Sir¨
First of all thank your quick responds .
I Have a Hiohi impedence meter. A measurement.Vi down loaded from hioki's net side. I couldn't used directyly that Vi for my purpose.
I add other VI's for write in text files.(that was modification). This is serial communication.
It was working well with Labview 6.x.
If I press the measure button , then contact with instrument , ther is no changes in frequqncy value.
Same value shows all time.
I didn't check inside the VI with probe values ...
1.Yes I can communicate with instrument.
2.Vi is working - contact with instrument,change the instrument values through VI
3. I want to measure the Impedence for frequency between for example 30KHz - 50KHz for 64 points . But It measure 64 times. But frequecy
did not change therefore other impedence values also no change.
may be some sub vi's not working. Ther is no incorrect
result. It will not change the frequency value .
Thank you.
regards
pathman

[pathman]

Sir
I test SUB vi's, and ckecked the prob values for FREQ
sub VI . It show same value in LV7.0 ,and LV6.1.
But in LV7.0 , this value not send to the instrument.
LV6 don't have any problems.
Her I attach all impedence.vi
thank you
regards
pathman

[Ray.R]

Hi pathman,

Thanks for the vi. Unfortunately the sub-vi's were not included, therefore I could not see the entire code. But I do have some comments.

One difference from LV6 to LV7 is the serial communication. LV7 targets using VISA to communicate with the serial port. Since you mentioneed that you were using the serial port, I looked at your code to see how you initialized it. I suspect it is done in a sub vi called in your first stacked sequence structure (block).

Although I didn;t see how you initialize your COM port, I can offer some comments. The first thing to do it to use VISA Open to select and open the COM port, then use VISA Configure Serial Port.

Other comments:

I would suggest that each block contains a small description of what you are doing inside the block (comments). It can include inputs and outputs as well as case description.

A good practice is to have a single "Error In" that goes from the beginning to the end of your vi. I noticed that you have many fragments which start independently with "No Error". Doing so prevents the vi from capturing and stopping if there is an error and prevents displaying error codes.

Also there are many items scattered within the blocks which are not defined by "flow"... especially property / invoke nodes. I would suggest that you set the flow by using the Error cluster (Error In to Error Out). By wiring the Error cluster continously throughout your vi, you'll be able to control the flow within your vi and catch anything that might prevent the normal (expected) operation of the vi.

The flow is important: For instance, maybe the frequency change occurs after an event instead of before. Maybe it is never triggered (if there was a previous error which is later reset in the vi). An idea is to include some sort of indication of where the vi is running (what paths), especially when using multiple levels.

Start by looking at how you configure the serial communication. It may provide a quick solution. Do consider wiring the entire vi with an error cluster which starts from the beginning (Error In) to the very end.

Regards,

JLV