The two (cabinet impedance variations and crossover interactions) happen at different parts of the band, limiting the effect (in some cases more than others). Ideally you would but if for some reason you can't include the cabinet influence, don't let it stop you designing.
can anybody light me up about this? 😕 Should the effect of the cabinet on the impedance be taken into consideration?
always use the impedance measurement with the driver mounted in the cabinet.
started to learn using this application and it's very easy to draw schematic, plus using "fpgraph tracer" for having fun.
however i got this error while loading frd files, both from FPgraph output or from below link that i download
http://www.rjbaudio.com/Audiofiles/FRD files/ScanSpeak 9500.frd
when i open this frd file, i can understand it easily since everyday i'm dealing with database for analytics. header will be : Frequency SPL Degree
with this simple txt file, still wondering what's wrong with my import process
however i got this error while loading frd files, both from FPgraph output or from below link that i download
http://www.rjbaudio.com/Audiofiles/FRD files/ScanSpeak 9500.frd
when i open this frd file, i can understand it easily since everyday i'm dealing with database for analytics. header will be : Frequency SPL Degree
with this simple txt file, still wondering what's wrong with my import process
Attachments
XO design part is completed with values and curves are populated, when i close and reopen project .dxo file then error pop up.
opening project .dxo file in notepad, any clue on which value that related to the error "Floating point division by zero".
opening project .dxo file in notepad, any clue on which value that related to the error "Floating point division by zero".
Attachments
great, another trick 😀 solved now
I keep getting a "file load error!" when I try to input frd and zma files traced from FPGGraphTracer. Anyone know what this could be?
Could that program be using commas to mark decimal places (rather than a period/dot) in numbers? If so, XSim won't work with that.
I think I see two problems with that data. First, the frequencies (first column) need to be in ascending order, lowest frequencies first. Second, could that be a negative [-] sign in front of each frequency???
I was wondering if anyone would be willing to look at my first XSim XO before I start ordering parts.
- Home
- Design & Build
- Software Tools
- XSim free crossover designer