Jump to content
SAU Community

Recommended Posts

Just purchased the car (knowing I'd have some audio issues), and first thing I do with every car is upgrade the sound system as it's never that fantastic from factory.

I'm looking to do sub, amp and speaker upgrade. Now I don't have the Bose system in mine. So,

1) Does the main head unit have the inputs I can use for the sub and amp wiring (kept there for the Bose system) ?

2) What size speakers are they? 

 

Please don't say "don't bother, too hard, won't work, deal with it - you got an import..."etc etc etc as I have done a complicated setup on a Falcon before where all factory connections had to be bypassed, and if that's what I have to do again, then I will. By that, I mean I installed a separate head unit so it worked entirely independently of the car's inbuilt system.

 

 

Head unit is abit too much work as the headunit runs most of the car's electronics, you can check out Tesla style headunit swap that some people are doing now.

I currently run Hertz HSK165 for fronts, HSK163 for rears with Audison Lrx 4.1k and 2x Hertz HX300D with Audison Lrx 1.1k. They all go through Audison Bit Ten processor. 

Exactly what Colin said. The headunit is far too deeply integrated into the car's electronics, rendering some elements of the vehicle useless (albeit still driveable).

The method that Colin and I have opted for is to augment the headunit with a quality DSP, amp and speaker setup.

I wrote a thread several years ago which vaguely documents the things I did to make that happen. Bear in mind that since the last post, I changed the front speakers from the Boston Acoustics SPZ60 to Morel Hybrid series because in the end, I discovered that in the final days of their existence, the SPZ series proved to be shit quality compared to their previous ProSeries models. That, and support for them was suffering.

Once this friggin' work project is done, perhaps I'll then have time to complete the next phase in the project, involving a mini computer to interface to the touchscreen (video and control) and provide GPS functionality, as well as the music. Only problem is that it'll still be composite video feeding to it, since I can't be bothered taking the next step of hacking a Sony serialiser IC out of some bok-choi device to get what I want.

Edited by The Max
  • 10 months later...

audio installers here susggest 
ALPINE ILX-W650E 7INCH ANDROID AUTO/APPLE CARPLAY

and shifting the factory screen to the glovebox or deleting it 

i have a magnet phone holder that is designed to mount into the cd slot 

IMG-20200418-WA0014_1__08770.1587176151.jpg

Edited by Daspien

Does that integrate with the CANBUS in any way to show you air con status in the very least?

I see it also has dual camera interfaces. Did your installer integrate your reverse and side mirror cameras into it?

Edited by The Max

Found the manual for it. No CAN bus interface. Rules it out for me. I like to know what I've dialled in for climate control. :) To be fair, the data codes pertaining to that would likely vary between manufacturers and even models within the same manufacturer if they were to change any particular component in their system. It'd be a bastard to account for all of them.

Interfacing with our cameras will likely require some work because if I remember correctly, the cameras are natively composite video but then pass through a serialiser in the boot first before they get integrated into the selection of video signals in the infotainment system. In which case, you'll likely have to extend some coax cable from the two cameras to the back of that Alpine.

Got to give them credit where it's due though, it supports FLAC file formats. That's a major plus given the uptake on supporting that format is still pretty crappy. I like it overall and the touchscreen on these would be much friendlier to operate than our OEM resistive panels, which require either big buttons or needle fingers! Not to mention their capability of supporting swipe gestures, which our resistive screens don't do well at all.

Do you know if we need to keep the CD player stacker to keep the aircon/OEM screen to work? I was thinking of removing the analogue clock/CD player and volume controls bit + card reader would provide enough space for a 7"Alpine in there. 

Yes. Don't forget as well that the hazards button in the upper panel interconnects with that main button cluster as well, so you would need to do some creative rewiring and relocating of the OEM headunit if you want to retain the basic functionality.

Edited by The Max

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
×
×
  • Create New...