LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

agilent 4395a impedance analyzer

For some reason the author of the code wrote an auto-detect sequence for the instrument.  Rather than just hard code GPIB addresses, it goes out and searches for all instruments on the bus that respond to the *IDN?.  Then it tries to match the responses to *IDN? with the string that describes the particular instrument and when it finds a match it saves that instrument address as a global to be used in all other parts of the code.  Cute, but potentially problem causing if the string changes at all due to firmware or say company name changes HP->Agilent->Keysight.

 

It look like the string its trying to match in the "Address Check.vi" is 4396A, not 4395A.  Try chaning that to 4395A and resaving the VI or it looks like you can specify a string yourself in teh Front panel code as below..4395a.png

 

 

 

Message 41 of 46
(1,468 Views)

Hi everyone Smiley Happy

 

Thanks for your helps. 

The dashboard of the “4395A front panel” is partially working, but for some reason some part of the code doesn’t work. And it is always showing me the same error message “internal error wrong memory zone accessed GPIB controller not addressed correctly” I looked online and apparently GPIB is not addressed correctly (see below).

5.png

 

It's strange because a part of the code is working fine so I don’t believe it's the GPIB that is not addresses correctly, but it is more coming from the code itself,

Below I circled the failure button in red and in green the ones which are working properly.

1.png

Here are some samples of the code which are failing.

  1. Button “single Sweep”

2.png

  1. Get data

 3.png

the string “aaaa” looks weird to me.

  1. (A-B)/R

4.png

Have you ever had this kind of problem ?

Thank in advance for your reply.

0 Kudos
Message 42 of 46
(1,444 Views)

Use debugging mode to watch the code execute, while at the same time watching the instrument for errors.  The code has next no error handling so if the instrument throws an error the code after that probably won't run!

 

 

Post your results and we can go from there.

 

0 Kudos
Message 43 of 46
(1,439 Views)

Hi Smiley Happy

I used the debugging mode for each button which are not working.

If I press “get data” : When the program comes to the bloc "get data" I have the following error message (see below)

1.png

If I press the button "single sweep", When the program comes to the bloc "sweep" I have the following error message (see below)

 2.png

 

When I press “graph for printing” , there is not error message but for some reason the graph is not displaying the values (see below)

3.png

If I press Calibrate, 

4.png

when the code comes to the bloc "net cal" It opens an windows, and than I have the following error message when I press one of the button

5.png

I hope this is more clear.

 

0 Kudos
Message 44 of 46
(1,433 Views)

Ok, so 3/4 are the same error. Did you follow the debugging into the Get Data subVI to see what the problem was internally? 

 

I still think its a GPIB address not being set issue.   But follow the code to the end and use probes on all inputs so you can see what the values are.  Post if that doesn't solve your issues.

 

Craig

0 Kudos
Message 45 of 46
(1,414 Views)

Hi I am using the same driver and have my laptop connected to the impedance analyser. NI MAX shows that it's connected. When I open the driver in LABVIEW and run it I get the following:

 

mmcinnes2021_0-1663237980727.png

After I click continue I get:

 

mmcinnes2021_1-1663238026934.png

 

Not sure what to do to resolve this. Any help would be great thanks. 

0 Kudos
Message 46 of 46
(756 Views)