WinISD and Deltalite-II 2515

[abarson]

I'm trying to use WinISD to calculate port size for an old DIY cabinet, and having some difficulty.

I discovered that the Deltalite 2515 that shows up in the WinISD driver database is the first generation, and has totally different T-S parameters than the "-II" model I have, so I can't use that.

I then tried to enter all of the T-S parameters from the Eminence datasheet, but when I try to save the entry, it throws an error stating that almost all of the data I entered is wrong. Anyone know why this is, and what the solution is?

Aside from WinISD, I tried a few online port calculators: two came close to agreeing with each other, while two others provided radically different results. Is there one that's reliable?

[craig.p]

Originally Posted by abarson

I then tried to enter all of the T-S parameters from the Eminence datasheet, but when I try to save the entry, it throws an error stating that almost all of the data I entered is wrong. Anyone know why this is, and what the solution is?

Try this. Use the driver editor (<CTRL>D). Make sure auto-calculate is enabled. Then

1. Enter Mms
2. Enter BL
3. Enter Cms
4. Enter Re
5. Enter Sd
6. Enter Qms

The rest of the parameters should appear automatically.

Don't forget to enter your speaker dimensions (rightmost tab in the driver editor).

Disclaimer: I'm a relative WinISD newbie. If one of the board heavies comes in and says something different than I have, then he's right and I'm wrong.

[greenboy]

I think he's already called some of us who know the answers a bunch of Bashers, several times ; }

Funny how that works.

RTM, abarson, that's gonna matter. And look at my sig which you've probably already seen a number of times. Anything look a little like it might have something to do with WinISD there?

[abarson]

greenboy,
Thanks for the pointer. For all the times I've looked at the fEarful plans, for some reason I missed your compendium of drivers for WinISD. I can only blame having grown up in Bigfork on that!

I did notice that some of the parameters are in different units in the datasheet than in the application, which might explain why WinISD puked all over them when I entered them manually. Moving the decimal point three places does make a difference!