diyAudio

diyAudio (http://www.diyaudio.com/forums/)
-   Software Tools (http://www.diyaudio.com/forums/software-tools/)
-   -   Weird after crossover frequency estimation (http://www.diyaudio.com/forums/software-tools/226513-weird-after-crossover-frequency-estimation.html)

Mario Pankov 27th December 2012 04:47 PM

Weird after crossover frequency estimation
 
Hello,

Farfield measurement, 1m distance from woofer, used JustMLS. Looks fine when into the optimiser ( upper graph ) but once a simple 2nd order electrical crossover is attached, there`s a weird spike at 4.5Khz. Measured with the crossover, the woofer exibits no such spike. What is the reason LSPCad to interpret the posterior response like it is shown? It makes a simple crossover construction a nightmare and can`t get rid of it, what am I doing wrong?
Also, once all steps have been taken ( following the manual ) the Start button for the automatic optimisator does not do anything. Any ideas why?
http://img19.imageshack.us/img19/9153/graphszg.jpg

Uploaded with ImageShack.us

sreten 27th December 2012 06:26 PM

Hi, I'd guess a silly number entered as the driver's inductance, rgds, sreten.

Mario Pankov 27th December 2012 07:52 PM

Hi Sreten,

This is done through LSPCad 6.2, no option to enter T/S there, at least I couldn`t find one :) As far as I can tell, it only required frequency response/phase + impedance plot. No issues with tweeter simulation.

DrBoar 1st January 2013 08:39 AM

Is there any kind of smoothing in the graphs? If so there could be a one of numercal value in response or impedance plot that is an order of magnitude larger or smaller than all other. Such an outlier could throw of the calculations without showing up if there is smoothing.

So if you look at the textfile of numerical data how does it look around 4800 Hz?

Mario Pankov 2nd January 2013 10:36 PM

Went back to using Holm impulse and completed ( almost ) the project already :) I looked at this and I think it is some crossover high Q peak combined with the frequency bump of the driver which does not happen in reality ( when measured ). No idea why simulated this way, have checked the values multiple times one by one.


All times are GMT. The time now is 10:46 AM.


vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2014 DragonByte Technologies Ltd.
Copyright 1999-2014 diyAudio


Content Relevant URLs by vBSEO 3.3.2