Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AD5933 to measure change in impedance #4

Open
AdarshGouda opened this issue Nov 18, 2017 · 1 comment
Open

AD5933 to measure change in impedance #4

AdarshGouda opened this issue Nov 18, 2017 · 1 comment

Comments

@AdarshGouda
Copy link

AdarshGouda commented Nov 18, 2017

Dear Experts,

I am trying to measure change in dielectric property (degradation of vegetable oil) by measuring the impedance using a simple parallel plate capacitor. The expectation is that the real and imaginarychange as the the oil degrades with temperature. This is continuously monitored over time.

I first need to find an optimum frequency (which i kinda know based on earlier literature) and continuously monitor the changes in complex impedance at that optimum frequency and display real and imaginary values (intend to use arduino with AD5933). How can i modify this code to achieve that?

If i understand correctly, i need to use frequencySweepEasy(); or frequencySweepRaw(); and not both- is that right?

What if i dont want to perform a sweep everytime and rather find img and real values at a fixed frequency? Is this possible? or do i need to perform a frequency sweep everytime?

Being a mechanical engineer, I'm not much of an expert in this regard.

Any help would be much appreciated.

Regards,

AdzTheDemon.

@mjmeli
Copy link
Owner

mjmeli commented Nov 21, 2017

Hi,

frequencySweepEasy() and frequencySweepRaw() are just two different alternatives to handling the data. The easy method performs the entire sweep, stores the data in an array, and then returns to you to handle that data. This is a lot easier to deal with but means that you have to wait for the entire sweep to finish before processing and you must have large enough data arrays to hold the entire sweep data. The raw method avoids these problems by being a bit more complex and allowing you to handle the data at each individual frequency step at a time. For your application, it sounds like the easy method should be sufficient, but again, either will work.

One of the variables you can set for a sweep is the number of increments. You can probably set this to 1 and perform a single test at a single frequency. I am not sure if this is an intended use case of the device though and so I'd recommend reading the data sheet to make sure there isn't anything that makes this a bad idea and trying through experimentation. If you aren't sure of an optimal frequency, this is a good reason why you might want to use a sweep, though.

The example program should be a great resource in getting started for an application like this. If things don't make sense then the data sheet is pretty easy to understand and followed closely by the examples.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants