Hey guys, hopefully someone can help me.
I recently bought an Infinity Kappa 8"
Kappa 800W | More performance. More flexibility.
Using the manual's T/S, I've plugged them into WinISD. When attempting to model the woofer, I get the error "Invalid floating point operation."
I've never seen this error before in the many woofers I've modeled. I tried downloading WinISD Pro Alpha and and get the same error.
I've tried to put in as few (or as many) T/S parameters into WinISD, allowing it to calculate parameters that may vary/differ from the manufacturer, but still get this error.
QES: .460
QMS: 4.0
QTS: (Calculated) .413
FS: 34.5
Xmax: 9.25
Does anyone have any clue what I might be doing wrong? Is this just a one-off woofer with odd T/S parameters?
I'm interested in getting a modeled response so I can see where I should be hitting mechanical limits, etc.
I recently bought an Infinity Kappa 8"
Kappa 800W | More performance. More flexibility.
Using the manual's T/S, I've plugged them into WinISD. When attempting to model the woofer, I get the error "Invalid floating point operation."
I've never seen this error before in the many woofers I've modeled. I tried downloading WinISD Pro Alpha and and get the same error.
I've tried to put in as few (or as many) T/S parameters into WinISD, allowing it to calculate parameters that may vary/differ from the manufacturer, but still get this error.
QES: .460
QMS: 4.0
QTS: (Calculated) .413
FS: 34.5
Xmax: 9.25
Does anyone have any clue what I might be doing wrong? Is this just a one-off woofer with odd T/S parameters?
I'm interested in getting a modeled response so I can see where I should be hitting mechanical limits, etc.
Interesting driver. I'm not sure why WinISD is throwing that error, but using Hornresp to model that driver in the recommended 1 cu.ft. box tuned to 40 Hz results in a fairly large peak at Fb, which might sound pretty decent for car audio use.
The specs though suggest that you can probably get some pretty good results using TWO of those drivers in a tandem-driver TL with slightly larger net volume.
The specs though suggest that you can probably get some pretty good results using TWO of those drivers in a tandem-driver TL with slightly larger net volume.
Been too long ago to remember for sure, but it's a very precise ['picky'] program, so IIRC/IME just input the basics when published specs seem bogus with Vas, Qts being the ones usually causing the error.