LCR-Meter Freezes during Measurement

[jobstulus]

Hello!

First things first: I'm Jobstulus and I'm some kind of junior researcher from an small german university.

My Problem:
I can't run the LCR-Meter (0.94-400, official app) properly.
I've downloaded the latest version of the app and tried to run a similar configuration as shown in the blog. ( http://blog.redpitaya.com/?p=650 ). When I push the "Start" Button from the frequency sweep section, the window "Measuring..." appears. And stays for hours. I've tried several different settings, but the result was always the same. It seems to hang up at this point.
Additionally I took a look with an seperate oscilloscope at the outputs (of course with an internal termination in 50 Ohm inside the oscilloscope settings). And there is not a single signal or waveform to see.

My Setup:
I've attached the cables as shown in the User Guide. My input scaling jumpers are both in the HV position. I've not terminated the outputs with 50 Ohm in the LCR-Meter setup. Only the shown shunt of 1k Ohm is in the circuit.

Please can someone help me out?

[jobstulus]

or to ask a simple question for the start:

is there anybody who got the lcr-meter working with the current firmware 0.94?

A simple yes or no would be nice for the beginning

[redpitaya]

Hi,

No.
We are working on it.
The fixed version of LCR meter will be avaliable on bazaar ASAP.

Best, Red Pitaya

[jobstulus]

Thanks for the info!

So i stay tuned

[job8]

I am new to the Red Pitaya, but have an immediate application for the LCR. Is there any guess as to the timeframe for a working version?

John

[jobstulus]

The new version (0.94-431) works now really fine for me.
Except the feature to save the parameter data. In my eyes only a minor issue.
For further work you'll find the data of the last plot in the /tmp/lcr-data/ directory of RedPitaya.

Thanks a lot to everybody who pushed the App towards success.

[drey]

Has anyone see documentation describing why the LCR GUI limits the output to 1MHz? You can run it manually with a higher frequency limit, but the GUI will not output anything above it.

If there are inaccuracies, what is their source?

Thanks