Load Google Translate Don't forget to sign up for email notifications under the "Actions" box so you'll see when Nick answers your question.
Nicholas Gray
Nicholas has worked in the Semiconductor industry for over 30 years and has authored a number of published articles about data converters (ADCs and DACs) and signal integrity issues.
If not already, you'll need to or ![]()
to ask your question. Otherwise, click reply below. |
Nicholas,
I have been looking for an ADC for quite some time. Read here.
Can you recommend some data acquisition systems that come with easy to use software? I don't want to spend a lof of time developing the backbone software or the GUI, so quick setup is key.
Currently, my only option is the Picologger software and hardware. The software is fine, but it has a couple bugs and is complicated to use. However, the software is free, another deciding factor for me.
Cabe
My understanding is that a handful of companies are working on implementing analog-to-digital converters as IP in FPGAs. Do you have any thoughts about cost, performance and applications where this approach might be beneficial?
Nicholas,
Thank you for the advice. I am going to contact Picotech and see if they can correct the bugs.
As for programming, I could do it, but I want to finish this project and get it to market quickly. Writing a GUI and backend would take longer than I want to spend. If you could connect me with your friend in California, I would greatly appreciate it.
Cabe
Hello Nick,
I have to monitor voltage of each battery in the battery stack of 150 lead acid batteries. Each battery have voltage range from 1.5V to 3V. Can you suggest me the best method.
Balakrishna Nuthakki.
Mr Gray,
I contacted Picotech, and they said that the software, "Picolog," is at the end of its lifespan. Only critical patches will be applied. And apparently, my concerns are not that.
So, my search continues, and I need to deliver my product ASAP.
Can you suggest another product like Picolog?
Cabe
I am sorry that Picotech will not support their software. Unfortunately, I know of no one who is doing something similar. Hopefully, you and Rob can work something out. I sent him your email address. He is quite busy, but might be able to help you if the task is not too large.
- Nick Gray
I am not really an expert in voltage monitoring, but I may still be able to help. What you do not indicate is just what level of monitoring do you need. Do you need to continually know the voltage level of each individual battery, or whether any battery in the stack is above or below a certain level.
Monitoring each and every resistor is quite a task. The voltages of all but the one or two cells nearest ground will have to be divided down with a couple of resistors, then these voltages connected to an array of analog multiplexers before being presented to an ADC input. When cascading multiplexers, it is important to include a resistor to ground at the connection of the output of one multiplexer to the input of another multiplexer.
If you only want to know if any voltage is above or below a certain level, the voltages will again have to be divided down, then use voltage comparators to determine if the voltages are above or below a threshold. You can use some OR gates after the comparators to present a single node to a processor or controller, perhaps to an interrupt pin. After an interrupt is generated, you could scan the entire array for the problem cell with a series of multiplexers.
Any way you look at it, the circuit is going to be quite large if you must look at each cell separately.
I do hope this helps. If not, please give me more detail as to what you are trying to do and I will try to help further.
- Nick
I am sorry that I somehow missed your question.
Yes, some manufacturers of FPGAs are attempting to implement ADCs in their FPGAs. My personal feeling is that this will be a little difficult for them to do because the digital noise generated by the gates will cause the die substrate (on-chip common) to be quite noisy, which will add noise to the ADC conversion. Noise will most probably also find its way into the ADC reference voltage, further exacerbating the noise problaem. There are ways to get around this, however, but the result in any case is a relatively low conversion rate. Cost wise it should be beneficial to the end user, especially since more than one company is doing this and competition should keep the cost down. Performance is another story. If the ADCs are 8 or perhaps 10 bit resolution, there should be little problem with reasonable performance, although a stand-alone ADC should perform better than an imbedded one. At resolutions of 12 bits and more, I believe that performance will be no better than perhaps 10 bits.
What this means is, basically, that only the most significant 8 to 10 bits will be reliable, with the rest being mostly noise. The way around this would be to average many samples, but I doubt that this will increase performance beyond the 12 bit level, or 14 bit level at the most. And this would be satisfactory for most applications. Another approach would be to use converter topology that is relatively immune to noise, like a multi-slope ADC.
The problem I see is that there may not be provision to adjust for the offset and gain error of the ADC and the manufacturers will have the task of being sure that the user knows how to do this to prevent a lot of complaints and disgruntled users. These companies are digital and may not appreciate the analog problems unless they hire the right analog engineers. Some of the offset and gain errors can be done with conditioning circuitry before the ADC input of the FPGA, but these errors can vary from one individual part to another, so could probably more effectively be handled in the system processor.
As for applications where this might be beneficial, any system that takes input from the outside world and needs the versatility of an FPGA could potentially benefit.
- Nick
Dear Sir,
Thanks for the reply. I would like to measure the voltage of each cell continuously. I have found some ICs like LTC6802 and equivalent but they only support for Lead acid. I have to now design new circuit for this.
Hello, Balakrishna -
I have studied the LTC6802-1 and the LTC6802-2 data sheets and find no reason to believe that these devices are only for lead acid batteries. There is mention of "primary cell" but the data sheet also says that the cell voltage can be anywhere between zero and 5V, with specified performance for cell voltages up to 4.2V. It seems to me that the LTC6802 is well-suited to your application. I called Linear Technology [ (408)432-1900 ] and was told that this device is just a battery monitor and does not care about the battery chemistry (type of battery) and their customers are using it for all types of batteries, including super caps. I would try to get some samples and try it out. the LTC6802-1 is for daisy chaining the SPI communications, requiring fewer I/O lines on a processor than the LTC6802-2, which uses individual SPI lines so are individually addressable. the LTC6802-1 is the more popular version.
- Nick Gray
Hi Nick,
I am designing an FPGA based PC scope, and have got a prototype up and running at up to 200Msps with one ADC.
I am now looking at interleaved sampling to bring the real time up to hopefully 1Gsps and beyond, and also equivalent time sampling too.
I have done some simulation and spent a lot of time researching/reading as much as I could find on the net from big players like HP/Agilent etc. While there is some great info on the theory behind things, certainly enough to get on with, there are hardly any actual circuit examples or chip info (for obvious reasons I guess) Also we are not trying to compete with scopes like that so many of the techniques are a little overkill for our specs.
So a couple of questions which I understand are not that easy to answer given the huge and complex subject of scopes, but anything however small is much appreciated.
The first is on a decent, low jitter clock IC (preferably low cost too
) for up to 4 outputs which can be adjusted timing wise (for calibration) and also any tips you may have/things to watch out for. I don't want to generate the clocks from the FPGA for jitter reasons, and using a CMOS oscillator/PLL and clock buffer with delay line seems a bit messy, but might do okay.
The second is do you have any links or info on circuits for ETS (or for that matter interleaving circuits..), and the best way to do this in a reasonably simple fashion, but a better solution than just interpolation between last/first sample after trigger. I was thinking of a constant current, 100:1 dual slope setup or something along those lines, but would be interested to hear any advice on the subject.
I think I am heading in the right direction, but it would be nice to have some actual real examples to compare against/learn from, which is the case with most other stuff I design, but this is heading into the more "elite" territory where secrets seem to be guarded carefully (and I don't blame them I suppose) :-)
Thanks,
Oli
Hi, Oli -
The first thing you need to know is that interleaving of ADCs is extremely tricky. Slight differences in the signal delay along the signal lines and clock traces cause timing errors, leading to spurs in the Time Domain (FFTY) Plot. These timing differences arise primarily out of the differences in trace lengths, but also in the differences in line capacitances. Unfortunately, simulation can not show this. What you might try for simulation is putting an RC delay in the clock line to one of the ADCs to simulate this.
Scopes currently on the market use custom gigasample ADCs, the ADC083000RB/NOPB ADC083000RB/NOPB from National Semiconductor, or the TS8388B from Atmel. There may be others that I do not know about. Sometimes ADCs are time interleaved and there is some digital post processing used to minimize spurs.
The National Semiconductor ADC083000RB/NOPB ADC083000RB/NOPB is four 750 MHz ADCs time interleaved to provide 3 gigasamples per second. They have a proprietary, patented method of on-chip timing adjustment to minimize the skew problems. Atmel and National also have 10-bit gigasample ADCs and National and TI have 12-bit gigasample ADCs.
To develop low jitter clock signals, the most common method is to start with a low jitter CMOS oscillator and use a PLL-based Jitter Cleaner/Buffer. This does sound messy, but need not be so bad. As an example, the circuitry around National’s LMK series (perhaps the LMK02000 or LMK02002) is fairly simple and provides jitter down to less than 0.2 ps. The LMK03000CISQ/NOPB LMK03000CISQ/NOPB is another excellent choice.
As for links to circuits for time interleaved ADCs, I suggest you Google “Time Interleaving ADC” without the quote marks. I tried this and found a lot of information. Some information you may find especially useful includes the following two links:
http://www.analog.com/library/analogdialogue/archives/37-08/post_processing.html
http://www2.spsc.tugraz.at/people/cvogel/TIADC.html
I do not think that your difficulty in finding information is so much a matter of guarding secrets, although that might have some effect, as it is in the difficulty of explaining what is happening and how to avoid the problems. The way this kind of information is passed along is from mentor to mentee in a one-on-one setting. It is difficult to pass this information on otherwise.
I do hope that you find this helpful.
- Nick
© 2009 Premier Farnell plc. All Rights Reserved
Premier Farnell plc, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE