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

[Brainer]

Hi everyone:

I have a WT3 Woofer Tester which I used years ago on Windows 7.

I no longer have any PCs running Windows 7. My current PC runs Windows 10.

I tried to get the my WT3 to work with DATS software ver. 2.1.1 on Windows 10, but haven't had any success. Previously, I used a much older DATS software version when on Windows 7. Can you use DATS software ver. 2.x with an original WT3?

I tried following instructions written by John in a thread here on the froum for Windows 11, (even though I'm using Windows 10) but that didn't work. I'm still getting wild readings when I try to short the test leads.

There seems to be a lot of confusion on other audio forums on how to do this properly. Can John or someone set me straight on the proper way to do this?


Thanks

[tktran]

I have had success using the WT3 on Windows 10 with the current DAT V3 software.

Troubleshooting tips:
Try a different USB port
Check the alligator clips are still functioning (WT3 is over 10 years old now, terminals to alligator clips were not soldered in mine, just crimped)
I have used this troubleshooting guide; particularly the last page- set the input/output volumes correctly (mic record level 54 on WT3 hardware in Windows 10 running DATS)
Good luck!

[Brainer]

Okay, I was about ready to completely give up and the throw the thing in the garbage, when I decide to try DATS software 3.1.6.

Now, I'm I'm at least getting test lead measurement results that are not crazy, but I'm getting some erratic measurements of resistors.

From the DATS Help menu:

Impedance Analyzer Menu

When the software is first installed the default test lead impedance is 0.3 Ohms which is typical of the units.

I'm getting 0.2477 Ohms, so I think that's probably okay.





But when I measure a 997 Ohm test resistor, I get this graph:









The Re measurement on the right is accurate, but if you watch the demo video on Youtube, this graph be linear, all the way up to 20K.



Does anyone have any suggestions?

[tktran]

I've had this problem too, though I can't recall what I did to fix it be perfectly straight.

It's reported here too:

https://techtalk.parts-express.com/f...08#post1487608

even with a DATS V3 hardware on Windows 11. So it may be a bit finicky. But let's be honest, 10 year old hardware that's still working? That's a lifetime in our modern era of "planned obsolescence" hardware. (I'm looking at you Android hardware providers)

[Brainer]

Yes, that's the thread I referred to in my first post above. So, nothing new to me there.

As for obsolescence, I haven't seen anything that clearly proves the older unit can't work with Windows 10. In fact, plenty of people claim to have it working.

[tktran]

have you taken a measurement of anything; other than test leads and resistors?

So what’s the problem now?

[Brainer]

Yes, I did one test. I tested a Gershman 10" woofer that I have, and the results came out somewhat screwy (I'm pretty sure). For sure I know that the results are quite different than the last time I ran that test on the same woofer a few years ago. Age might have changed the results a little, but not by that much.


Dayton doesn't seem to care whether people get this working on current versions of Windows or not. When I read about people calling in to ask, it seems they're just told:
"Buy the new one". When I called in to ask, I was told the same thing. Not cool and not good for the planet.

[tktran]

I'm in the same boat. I'm confident a $129 DATS V3 will solve it. But I had this same problem before but then after some time the calibration was perfect and straight, and yes when I checked it again it wasn't straight like yours.

And the money isn't an issue, AND I'd like to support John's small business. But I'm totally into the Reduce Reuse Recycle thing that my kids are learning at school to mitigate climate change. I mean, I'd happily send $129 to him without him sending me another piece of hardware, but then he'll probably feel inclined to troubleshoot and help me figure it out, and we could be at it for hours and hours if not days.

The real issue is probably not DATS.

Windoze updates breaks a lot of things.
If you've ever done software updates, it breaks all kinds of random things- breaking features of GPUs; eg. audio out of HDMI no longer working, refresh rates no longer selectable. So you swear off AMD GPUs and vow never to buy them again. Your next computer has an nVIDIA GPU, but 12-18 months again after another Windoze update something else happens.

What about a subscription based Woofer Tester/DATS John? If the hardware isn't changing but you have to provide the software updates to counter Windoze' games...

[Brainer]

I'm in the same boat. I'm confident a $129 DATS V3 will solve it. But I had this same problem before but then after some time the calibration was perfect and straight, and yes when I checked it again it wasn't straight like yours.

And the money isn't an issue, AND I'd like to support John's small business. But I'm totally into the Reduce Reuse Recycle thing that my kids are learning at school to mitigate climate change. I mean, I'd happily send $129 to him without him sending me another piece of hardware, but then he'll probably feel inclined to troubleshoot and help me figure it out, and we could be at it for hours and hours if not days.

I don't know that I'd want to send another $129.00. But I'm tired of throwing things away and damaging the planet. There is no reason to make things obsolete that often. And I'd happily pay a little more for something that lasted longer or pay for updates (only if they were reasonably-priced). The constant obsolescence also assumes everyone can afford to constantly replace things.

You really think this might be caused by an update? Any guesses as to which modules might be the problem? Audio, I would assume?

[AEIOU]

I don't know that I'd want to send another $129.00. But I'm tired of throwing things away and damaging the planet. There is no reason to make things obsolete that often. And I'd happily pay a little more for something that lasted longer or pay for updates (only if they were reasonably-priced). The constant obsolescence also assumes everyone can afford to constantly replace things.

You really think this might be caused by an update? Any guesses as to which modules might be the problem? Audio, I would assume?

Or maybe scrounge up some older computer equipment and install Windows 7 ? You can still Download Windows 7, 32Bit ISO and 64Bit ISO.

[Chris Roemer]

In preface, let me say that I blame Win "updates" for 99.9% of all WT/DATS "incompatibility".

This thread (FINALLY) prompted me to try my WT3 (I also have DATS) on my 10 y.o. (HP) notebook.
It didn't work (TODAY), although I've used both WT3 AND DATS with various vers. of WT AND DATS softwares on my 2 "main" platforms (I THINK the softwares are mostly interchangeable - except MAYBE for the newest WT - the $170 one?).
They DO work on my (15 y.o. ?) Compaq desktop - running VISTA !
They've both also worked on the notebook, which started out as Win7, then went to 8 OR 9 (was there a 9?, don't remember - or care), finally Win10 (today). I think our (my wife's) NEW notebook (2 y.o.?) is running Win11? - but so far I've stayed off of it.

So, WT3 (pretty old now) hardware on a Win10 notebook, using "DATS v2.?" software (It's just what came up when I clicked the WT/DATS icon). The Z-plot LOOKed VERY noisey. Shorted leads - same deal. Set main audio to 0, 1, 50, 67, 99, and 100. ALL NOISEY (with a VERY high Zmax at low freqs. - like 1k to 10k ohms.

In control panel I navigated to USB Mic settings to fuss with it. The mic input was NOT set to "stereo" (per NORMAL - I THINK updates set this back to "1-ch" ALL THE T!ME). I set it to "2-ch 48000 Hz rate - DVD quality".

. . .

Problem SOLVED !

Now my leads (shorted) read around 0.2ohms. The noise was gone (blue line was FLAT). I could run a sweep (or T/S parms) on a driver - getting a "nominal" Z-plot. I have the mic input set to 67 (although that particular value is probably NOT critical - try 50).

I see this all the time (dang Win updates).

I hope you also have success.

[Brainer]

The plot I posted above was with software 3.1.6. It made no difference.


And I'm glad you appear to be having success, but the instructions specifically tell you to use stereo, 44.1KHz CD Quality, so that doesn't make a whole lot sense to me.


From The QuickStart Guide on Dayton's website:
https://www.daytonaudio.com/images/r...ck%20start.pdf

Switch to the “Advanced” tab and select “2 channel, 16 bit, 44100 Hz (CD Quality)” as seen below
(left).Now click Apply.Next, select the “Levels” tab and make sure the level is set to maximum as seen
below (right) and that it is not muted. DATS will not operate correctly with 1 channel input or at sampling
frequencies other than 44.1 kH

Chris: Just to be clear, you were using software version 2.x ??

[Chris Roemer]

Your post just asked whether WT3 COULD work on Win10 using DATS 2.1.1 software ...

All I'm sayin' is that for ME, my WT3 DOES run on Win10 using DATS 2.0.b2 (BTW). I've used newer softwares w/my WT3, and older w/my DATS, and I've never seen any incompatibility between MY hardware and software versions (I don't have the NEWest hardware though).

AFAIK, in order to sample to 20kHz, your rate must be at least 2X that, or > 40kHz. I'm pretty sure I'd get the same results at 44kHz. What I DO know is that Win updates (or SOMEthing) kicks my mic back from stereo to mono OFTEN. And at 1-ch, I get garbage.

[Brainer]

Ah, I'm back to having crazy, way off readings. It's very frustrating. I'm glad for you that you could get it to work. I wish I had some idea what factors affected this thing.

[Steve Lee]

^ have you checked the wire connections at the alligator clips like TKTRAN had an issue with?