Getting WT3 and Dats 2.1.1 to work on Windows 10 (Calling John Murphy. John?)

[Brian Steele]

So, curiousity got the better of me, and I ran an impedance test using DATS, then ran it again in REW, first calibrating using a 100 Ohm value for Rsense, then a 10KOhm value for Rsense. The results were essentially identical, LOL.

[Brian Steele]

I use 100 Ohm as the value for the Sense resistor in REW and the results look fine. I've tested it with a number of 2% resistors I have in stock and the measurements were dead on or very close to the published specs of each resistor. Funnily enough the results I was getting with REW were better than what I was getting with the DATS software - until I realised that I had to configure the DATS software to use the "G" rather than "H" version of the DATS V3 hardware.

[dcibel]

Zoom in on the photo in the document, looks an awful lot like “103” printed on R1 mentioned. Of course, if it’s 100 ohm you instead, should be clearly obvious in any measurement you make that the impedance measured is very wrong. Easy to figure out for yourself and change accordingly.

[Brian Steele]

The 10 kOhm mentioned in that PDF as the value for the DATS V3 "sense" resistor (the resistor in series with the voltage source and the device being tested) seems rather high. My calculations put it around 100 Ohms, which is what I use for my preference settings in REW. I'd actually be surprised if it's as high as 10kOhm, because that would result in the DUT (which is usually a driver with nominal 4~8 ohm impedance) being driven by a VERY low voltage. And if Rsense was that high, the DATS ability to provide voltage would be pretty much load-invarient, and the author mentioned in the PDF that he has trouble with clipping if the output level is set above -4dBFS.

As Rsense is in series with the DUT and the voltage source, it's pretty easy to measure its actual value

1. Measure the open circuit voltage from the DATS (run an impedance sweep and use a multimeter that can record max voltage). Call this voltage Vmax
2. Connect the DATS terminals to a known resistor R and run the sweep again). Call this Voltage Vr.
3. Calculate Vsense = Vmax-Vr
4. Calculate Rsense= (Vsense/Vr)*R

Repeat for several values of R if possible.

Of course this value for Rsense might be off slightly because "R" will also include the lead resistance, but you can minimize the impact of the lead resistance by using a known resistor with value closer to 100 Ohms for the test above. And then just round off the result (because I'm pretty sure that the DATS is not using a 99.7 Ohm resistor as Rsense, LOL).

[dcibel]

This instruction can be used on any OS that DATS functions on really:

https://www.diyaudio.com/community/threads/running-datsv3-natively-on-macos-using-rew.381943/

[Brian Steele]

FWIW, it should be possible to configure REW to use the DATS and WT3 hardware to perform impedance measurements, just in case you can't get the DATS/WT3 software to work.

[tktran]

whoops. Windoze did it again.
you played with my DATs, screwed by the update
You think that’s you’re smart
changing settings to 48K
and single channel record!

The WT3, DATS, and DATS V2 are not compatible with the DATS V3 software.
The newest version of the DATS V2 software, version 2.1.2, is available for download on the product page: DATS V2 product page
You can find the download in the "Manuals & Resources" section.

I hope this helps.

after mucking around (unplug, replug, reboot, try different USB port)

I went back to this thread and this is what was
needed!

thanks.

i hope this helps others.

[andy_c]

Brainer,
Did you ever try changing the hardware setting to WT3? Based on the original screen shot you posted I'm pretty sure that's all that was wrong.
This was likely a complication that resulted from using DATS V2 software with WT3 hardware. That combination requires a change at the Preferences dialog to let the DATS V2 hardware know it is being used with WT3 hardware. But perhaps the WT3 hardware unit was dying. In the later hardware I added diode protection to prevent the units from being damaged by voltage spikes returning from the driver when the cone is displaced.

I have the DATS 1 hardware and previously was unable to get it to work with the V2 software. It worked okay with the V1 software. Then i saw your post 23 and tried out the option specified there for using the older hardware with the V2 software. It worked like a champ and I've been using the V2 software ever since.

[John L. Murphy]

Yeah, I wish. I reflowed the joints today. Nothing changed at all.


And, as for whatever version of DATS software I should use, that didn't make any difference either. I tried the original version that came with the WT3, ver. 2.x and V3. No difference.
So today, the thing went into the garbage.

Thanks anyways.

Brainer,
Did you ever try changing the hardware setting to WT3? Based on the original screen shot you posted I'm pretty sure that's all that was wrong.
This was likely a complication that resulted from using DATS V2 software with WT3 hardware. That combination requires a change at the Preferences dialog to let the DATS V2 hardware know it is being used with WT3 hardware. But perhaps the WT3 hardware unit was dying. In the later hardware I added diode protection to prevent the units from being damaged by voltage spikes returning from the driver when the cone is displaced.

Regards,
John

[aarond]

Just to follow up somewhat... my WT3 seems to be pretty finicky but, luckily, I can get it to do what I need running Windows 10 and the DATS software. My latest frustration seems to be that it doesn't like to sit long before providing reuslts that look like a bunch of uncalibrated noise. Fortunately the diffence between a valid plot and a garbage one is obvious so I'm not worried about mistaking bad data for good.

The solution is to disconnect the USB and close the DATS then restart DATS. For extra measure I make sure the leads are open when connecting and then let it sit for a minute or two after starting everything. A quick calibration will show if it's working properly.
Part of my journey to getting this far was that I didn't know what the calibration curves are supposed to look like in order to verify correct operation.

My leads calibration does show some odd noise starting at 8k. I'm not sure if this is normal but that is well outside of the range I need to gather specs in so I fine with it.

My results so far have been repeatable to well within reasonable tolerances.

[tktran]

I dunno. It worked for me. I get completely straight lines. And it looks like it worked for this other fellow too:

https://techtalk.parts-express.com/f...07#post1490407



The only other thing I can think of is changing the record volume to 54 (weird number)

Microsoft Word - DATS V2 Quick Start 26Mar17.docx (trueaudio.com)​

[Steve Lee]

Sometimes you get the best light from a burning bridge.

[Brainer]

Yeah, I wish. I reflowed the joints today. Nothing changed at all.


And, as for whatever version of DATS software I should use, that didn't make any difference either. I tried the original version that came with the WT3, ver. 2.x and V3. No difference.
So today, the thing went into the garbage.

Thanks anyways.

[tktran]

Great tech support John and PE.

That should resolve all your issues Brainer.

[[email protected]]

The WT3, DATS, and DATS V2 are not compatible with the DATS V3 software.
The newest version of the DATS V2 software, version 2.1.2, is available for download on the product page: DATS V2 product page
You can find the download in the "Manuals & Resources" section.

I hope this helps.