XSim free crossover designer

Here is an example of how well Xsim can do in predicting the response of one of my speakers vs the actual measurement using a production crossover PCB (orange is actual measurement and blue is prediction by Xsim):
1703090325079.jpeg

The predicted Step Response matches perfectly also - but here is just the measured Step Response - a very nice behavior close to the ideal right triangle shape:
1703090412980.jpeg
 
Hi guys 🙂 I recently discovered Xsim from reading here, many thanks to the creator of it! so am now playing with it.

I have this 3rd order crossover project just as an experiment. I constructed the FRD and ZMA as text files from manufacturer graphs, so I realise they are a bit theoretical at this point too. Component values started out at Butterworth then drifted with adjustments in capacitors. I was just wondering if you cast your eye over it, and feed back your observations, so I can learn my way around 'steering' it, and what needs steering to get what effect.
I am still learning around what makes a good graph vs a bad one, what statistics are the vitals, and which are the less dramatic.
Cheers!
upload pic.jpg
 
Look for a base sensitivity (level). Your response rises towards 1kHz but it would ordinarily want to stay where the lower midrange is. Make it fall slightly towards the top.

However the outside of your box will probably raise the upper midrange and treble even beyond this. The inside of your box will also raise some of the lower frequencies.
 
  • Like
Reactions: Inducted
Thanks, that's interesting - so if I were to target more like bringing the overall level more around the 80 to 85bB line?
Is that dip under 4ohm on the system impedance any cause for caution? small impedances make something inside me say 'don't short circuit stuff!'
 
I constructed the FRD and ZMA as text files from manufacturer graphs, so I realise they are a bit theoretical at this point too.
Did you include the phase responses of the SPL and impedance responses of the drivers? That would likely have been done using a minimum-phase transformation, but some manufacturers include the phase data with their impedance curves.

It would be handy to know which drivers you are using, so please provide some further details.
 
Well, first problem is, you also need phase measurements. Second is that phase info doesn't meaningfully average, except when all curves are very close, at which point, best to just pick the one closest to the middle.

What I've done is to model each actual driver with multiple drivers measured at all the different places, and just drag them in and out of the circuit to look at the results from different places. XSim will let you have driver or othe parts just sitting unconnected, they get ignored in the sim.
 
You could of course average magnitudes, but angles? What's the average for an extreme case like 80dBSPL@0deg and 80dBSPL@180deg?
Combine them as vectors, you get -infinity @ undefined degrees. Average dBSPL.and deg separately you get 80dB@90deg. But 180deg is the same as -180deg, so is the average phase also 80dB@-90deg? Which?, can't be both.

Or try
80dBSPL@181deg and 80dBSPL@-179deg: Average the dBSPL and degrees separately, you get 80dBSPL@1deg, which is nonsense, it should stay around 181deg. The periodicity of phase makes averaging strange.
 
  • Like
Reactions: DSP_Geek
The issue with averaging complex quantities is only a problem if you're trying to arrive at a typical type curve using a bunch of good (but made under different conditions) curves. If you have a bunch of curves that SHOULD be identical but arent, because of noise, though, then averaging the complex curves (average the real parts and average the imaginary parts) is an advantage because averaged noise should go toward zero.