Another D/A converter chip had the pleasure of spending some time with the Audio Precision. This time it was the ADAU1966, on the official evaluation board from Analog Devices. Continue reading
The following measurements were taken with an M-audio Delta 1010 sound card, using channels 7 and 8. These cards have an AKM AK4393 D/A converter. The M-audio has an otherwise fault-free design and is a great converter for the price.
Input was S/PDIF, output balanced -4 dBV.
I’m dropping the raw measurements here with little comments as long as the results are in line with what you’d expect from a device like this, since I’m mostly interested in the IMD measurements, after the last post… Continue reading
I’ve been looking at designing a D/A converter for a while now. In my experience these are some of the hardest audio components to do right. It started with building output stages over a decade ago and at some point I even found myself in a company designing a D/A converter transistor by transistor.
However, as recent experiments have shown, I still have a lot to learn.
When you are using consumer-grade sound equipment to measure consumer-grade sound equipment you are potentially setting yourself up for a major pitfall: how do you know you will be able to see the DUT‘s performance and not that of your measurement gear? The first way to make sure is of course to use measurement gear of very high performance, outclassing most of the stuff that will be measured with it, leading to the choice of the delta 1010. But that’s only step 1. Therefore I decided to make some measurements to see what the 1010 is capable of. We should be able to get close to specifications of the D/A (and/or) A/D converter used, but how close and what that looks like remains to be seen! Continue reading
So, the scopemeter has a serial port for transferring measurements and even remote control. Cool!
Not cool: charging an arm and a leg for said cable (not to mention the software!). Boo, Fluke.
Of course I’m far from the first who got pissed off and figured out how to roll their own: Jan Wagner wrote a very concise page. I decided to one-up the laziness and went with the ready-made CP2101 USB-to-TTL solution. You can’t make a PCB yourself for that price. Of course the Chinese eBay supplier had a different pinout in his picture and on the silk screen, and on top of that… both were incorrect. Nothing a few measurements can’t fix, but did cost some time. Saved a buck, lost an evening. Oh well.
The IR transistor and photodiode I bought may well work with each other (825 and 900 nm? Really?), but not with the fluke. The culprit turned out to be diode. It needs to be really close to 800 nm. Unwilling to order one online and wait another week, I butchered a useless IR remote control and scavenged its diode.
Here’s a top tip: If you want to see if an IR diode is working, use a camera. Cameras see IR and on the screen it will look blueish/white. That’s also how to determine that the lower hole in the Fluke is the transmitting LED.
I had to alter some values slightly to get a good signal and arrived at the schematic below.
The circuit is straightforward, the trick is in the mounting. A serial plug without plate, sides shortened, just about grabs onto the recesses in the optical port and very nicely hangs on to the scope.
- The CP2102 driver doesn’t work on windows 7, at least using these low baud rates. We do use it at work and it seems to be fine there under win7 but we use much higher speeds. It works fine under windows XP and linux though.
- Upon reset, the Fluke defaults to 1200 baud, so if you set it to 19200 and then play around with remote commands such as ‘gd’ (off) and ‘so’ (on) don’t be surprised if your remote line suddenly doesn’t work.
- The older scopegrab is my tool of choice for grabbing screens. Scopegrab32 works unreliably for me and often conks out right at the end of the transfer. It could be argued my cable doesn’t work properly, but then why do all the other programs run fine?
- I managed to update the fluke’s firmware. Fluke themselves, being the masters of customer service, don’t provide the utility anymore, but I found it on an obscure chinese site. Not having a windows XP box around at the time, I flashed it using wine on linux.
- Obviously, if you flash a scopemeter using a spiderweb prototype cable, with an unverified flash image, using wine under linux, you need your head checked. But… it worked! 🙂
Spend roughly 7 euros and an evening and you can have your 150 euro cable. Now unless your evening hours are very profitable, I’d call that a reasonable deal. In any case, sticking it to Fluke and getting this thing working was very rewarding 🙂
As you may have noticed, there’s not much audio content here yet. That’s because I’m currently not only bubbling with ideas, but also working without good tools. So before we design anything, we need to have the right tools in order.
Priority one was a useful desk scope / multimeter: check.
Priority two is a spectrum / audio analyzer.
Now I actually do own one, I never threw away my trusty Spectral Dynamics SD375 . But as with my big Tektronix o’scope, it’s a bit of a boat anchor to keep around the house. So rest assured both of these are safely in storage, and I’m busy training my son to appreciate them so he can inherit and care for them one day hopefully far from today.
I’ve been scouting for an Audio Precision on eBay a bit, but without much success. I’m not ready to shell out thousands of bucks for something that is extremely cool, but still flawed. You see, the one thing an AP has going for it is credibility. You show any old weird curve and as long as it has the AP logo on the right hand top corner, you’re golden. And let’s not forget the bragging rights. “Yeah sure, I’ve got an AP at home” – gets all the girls!
But foregoing that, it has to be admitted that especially the system one machines are showing their age. The user interface runs under DOS or windows 98. Wow. forget attaching an internet enabled network cable to those beasts.
AP themselves do not recommend buying one. Of course if I was selling system twos, I’d also recommend against buying a machine I’m no longer selling. But they do have a point: there is some custom hardware in there and when that breaks, you’re done for. No support, no parts.
Reflecting on all of that for a bit, I pondered what the alternative could be. A good sound card with a PC sounds like the logical choice. A quick inventory actually turned up some quite decent parts:
- M-audio Delta 1010. One of my favourite sound cards. I can safely say that now that I have gathered at least enough of them for my own use. I scoured them in parts, buying the cards and the break-out boxes separately, and built internal power supplies in each of them. SNR is around 110 dB which is very good but of course not stellar. However for distortion it’s more than enough, and if it is about finding noise floors all I have to add is a low noise preamp. The Delta range is excellently supported under both windows and linux, and built for heavy duty use (some clearly showing signs of it). At least a 15 year production run with minimal changes shows that this was a very good basic design. There are some potential tweaks that I’m sure will show up here one day, but as a rule of thumb you cannot go wrong with this card and for the (used) price, it’s simply a winner.
- VIA EVCM-F mini-ITX motherboard with a 1 GHz CPU and a VT8235M chipset. It seems they were made for POS (point-of-sale aka cash registers) and I do agree about the POS part. I bought this off eBay hundreds of years ago. Unfortunately I could only find a 256MB stick of RAM but bigger ones should cost pennies if I’m feeling frisky to supercharge this beast. I don’t even know the original purpose I had for it anymore (I think it did have to do something with a Delta card), but the great thing is it runs warm but not hot with just a few small heat sinks. Together with a 12V power supply adapter fed from a laptop brick and a compact flash to PATA adapter with a 4GB Sandisk extreme III card it is quiet. Quiet as in SILENT. Your move, Audio Precision.
That should do it! As slow as this junk hardware is, it probably runs circles around the machines that AP had to work with. The downside is of course that this box will have to do all the heavy analysis (FFT, deconvolution, averaging, etc) lifting. Well, it’s an experiment.
Even though there are a few very nice audio analysis programs for windows, this box is going to run linux. No discussion. Hobby is supposed to be fun, not torture.
Due to the limited hardware capabilities it would have to be a pretty small foot print version, but at the same time it would have to be able to run some exotic software. That led me to Archlinux. Their modular design and custom package manager ticks the right boxes, and the support on their wiki is just stellar.
Getting Arch to run was easy enough. One hiccup was that the disk was formatted as a GPT partition and syslinux is not a good bootloader for that. At least I could not get it to run. GRUB2 did just fine and in just a few hours I had a running machine. Less time than a fresh windows install needs to pull in its 8,000 updates.
The first analysis programs I installed are Jaaa and baudline. More on that in a subsequent post. It’s not exactly APone style functionality yet, but at least jaaa and japa are open source and that means what you don’t have, you can build. In this case it is unfortunately true that I only trust AP to do a proper implementation, and all others have to be open source and if not, I guess I have little choice but to lead the way. This story is just beginning…
All in all, spending a day or so installing some very nice software and re-using dust-gathering equipment now means I can do some pretty impressive and reproducible measurements. As soon as I’ve cleared my desk and built this all into some enclosure…
What’s a hobby desk without a good ‘scope? A car with no engine. A fondue with no cheese. A church with no minister. A threesome with no, erm let’s get back to the topic.
Now, I have a good Tektronix rig but it’s a bit unwieldy to have in the house. So a nice scopemeter would do 99.999% of the time. Besides, it can also serve as a -very- good multimeter. Want!
Caveat: I have worked often with scopemeters and I love ’em. I know quite a few folk who don’t. It seems to be a matter of taste. So try one and decide which side you’re on.
I managed to shoot a broken Fluke 123 for beer money on the old Fleabay and it arrived pretty soon after, and it was immediately obvious: this poor bugger has lived a hard life. It was described as ‘does not power up’ which I prefer to ‘does power up but does not do XYZ’. The latter can give you big trouble, the former means it’s either a simple fix or simple to find out that it’s dead forever. In any case, simple. Simple is good. Simpler is good-er.
The second thing I noticed is that it had a weird switch attached on the bottom left side. Bad news. Someone had been tampering with it in a very unprofessional way.
Time to undress it and get to work. Now, credit where due: before buying the scopemeter I did a search on the internet for service manuals and found the one for the Fluke 123, downloaded it and read it from A to Z. And seriously, this is what service manuals should look like. Not just a schematic, no, explanations of what each circuit does AND a complete fault finding guide with extra care of what to when it doesn’t power up! Winners!
The first problem was not that hard to find: a broken diode with a very dodgy repair.
Yeah, that one let out the magic smoke so soldering the die to the cathode is not going to do very much (which is what was done to it when I found it!). Now of course the question is why did the diode break? Not knowing the answer I ordered 10 diodes and hoped they wouldn’t all blow up the same way. And they didn’t. The first replacement diode is still in there. Anyone need 9 diodes?
As you can see the diode was part of the switch mode power supply for supplying juice from the charger.
Unfortunately, applying a charger voltage still only yielded a gut-wrenching whine from the flyback transformer. Not there yet!
Simply following the service manual’s suggestions led me to check the battery, its wiring and all related components. The battery turned out to hold no charge even when charged externally, not very surprising for its age. But then I found that the battery current measuring resistor (3x 1Ohm in parallel) measured 3.8 kOhm. That is plain odd.
Now, without a proper voltage across these resistors the P-asic thinks that the battery is either full or over voltage, not that it’s empty so it tries to start up. The battery does not allow that it since it’s empty and even though the adapter circuit works, it’s not used (because a full battery is assumed present). So the whine is the flyback converter desperately trying to run on a dying battery with little help from the adapter since its supply isn’t running as the D-asic thinks its help is not necessary. Poor little flyback.
Resistors replaced and the whine is gone! Instead we get a nice beep from the loudspeaker indicating the software bootloader is active, and a second or two later I hear the relays in the input pathways click. Good news! This sounds like a working scopemeter! Alas close but no cigar… the screen is on, the backlight works, but it’s all black…
This is where you are on your own as the service manual says ‘sorry dude, the screen is not serviceable’. In other words, Fluke bought it from an external supplier and didn’t develop it by themselves. And you really can’t expect them to write a faultfinding guide on a part they did not design.
Connecting my trusty Tektronix told me that there is activity on all the connector pins such as framesync, line sync, the voltages are all good, actually it should just work. What in the world…
And then I saw it.
A drop of soldering tin, I will maintain until my dying breath not dropped by me (I had the display board covered), had fallen on the board. Right across a bypass capacitor of some sort. And probably shorted a nice data or supply line. Simply scratching it off with a screwdriver was all that was needed, and voila!
Time for a little dance; you just earned about five hundred bucks!
Oh and for those who wonder about the weird switch; it turns out the foil cable from the keyboard had been damaged. Probably by the same person who broke the diode. Simply melted one conductor on the outsdide. So a crude makeshift power switch had been added. I instead fitted an iPhone switch under the real power key. Of course the best solution is to simply order a new foil from Fluke. I might do that one day, but it works just fine without and not only are they expensive, it’s hard to order them. Fluke if you’re listening: put up an online spare parts order page!
I did some reading on the internet and it turns out these scopemeters are not at all happy to live with a fully discharged battery. The battery needs to hold some charge and build up some voltage quickly because the charger supply can deliver quite some current. That is probably how my sample blew its current measuring resistors. They were rated at one Watt each, so it had managed quite something to break them. The replacements I fitted are 6x 2 Ohms at 2 Watt each. It was quite a snug fit.
The diode, I think, was simply damaged by brute hands trying to find the resistor problem. I did not look like it had been blown up electrically.
Next step was to order a replacement battery. It arrived but didn’t charge at all. Again service manual to the rescue: wonderful, the chinese manufacturer had miswired the plug. Well that was an easy fix and now I can go for hours on battery power. That will be great when doing work on the car.
As I didn’t get the original power adapter with the scopemeter I dug into a box and bodged one from a wall-wart and a battery plug. The Fluke adapter port is quite particular in that the outside is + and the inside is -, so do take care there, although plugging it in the wrong way does not damage the meter (or so I heard. Ahem.).
So, with some luck but mostly a great service manual this new buddy of mine has been given a new lease on life and I have regained lots of desk space 🙂