Jump to content
SAU Community

Recommended Posts

i got an apexi avcr boost controller (second hand) and it didnt come with a loom so going to make one up

so just wondering if anyone can help me out by telling me which wires go where

i know the:

red-ignition power

purple-RPM.injector signal

green-ground

black-ground

gray-throttle signal

white-speed signal

as per the apexi wiring pdf on the net but i need to know which wires go to the

boost control valve (pink and black wires) and the pressure sensor (pink, white and black wires)

thats the:

yellow wire

pink wire

blue wire

brown wire

orange wire

pics below

11102010580.jpg

11102010581.jpg

so if anyone can help me out and let me know which one goes where that be great

cheers

ow and if ive posted in the wrong spot could mods please move thanks

Link to comment
https://www.sau.com.au/forums/topic/340014-apexi-avcr-wiring-help/
Share on other sites

i think you have answered your own question in a way,

your showing the pics of the boost sensor- pink, white, and black so connect these to the matching at the master, then boost control solenoid dark pink and black, connect these to there matching at the master, (the black is a common ground so ground all these to the same earth,

you need to find an ecu pinout for your engine, then at the ecu connect each wire to the relevent matching wire at the ecu,

all the spare wires i wouldnt touch just tape them up unless the pdf says otherwise,

yeah i dont know which ones go where though...

i just need to see if anyone knows which colour

goes to which one cause i dont want to stuff it

up lol so if anyone has one that they can look at

and see what plugs go where and the colours

they match up with that be great.

as for the ecu positions i have that already i got

it off the pdf

yeah what dose the filter do? do you know where to get one?

i know it wont be hard to match the wires but i need to know which one goes where lol

as you can see in the pic i got the unit and pressure sensor and boost control valve

so just need to join everything up

12102010584.jpg

Edited by Aaron BNR32 GTS-T

i dont get it...

run the

red-ignition power

purple-RPM.injector signal

green-ground

black-ground

gray-throttle signal

white-speed signal as stated in your 1st post. and join these at the ecu to correct wires

then the boost sensor mounts in your engine bay, run a boost and vacuum line from the inlet manifold to it, then join the pink black and white wires back into the AVCR master screen thats mounted on your dash, solder and insulate

,

mount the boost solenoid near the turbo but away from excessive heat, run a boost line to the turbo actuator and signal line from the turbo intercooler pipe or similar, run the dark pink and black wires back to the master avcr screen and join solder and insulate.

i dont get it...

run the

red-ignition power

purple-RPM.injector signal

green-ground

black-ground

gray-throttle signal

white-speed signal as stated in your 1st post. and join these at the ecu to correct wires

then the boost sensor mounts in your engine bay, run a boost and vacuum line from the inlet manifold to it, then join the pink black and white wires back into the AVCR master screen thats mounted on your dash, solder and insulate,

mount the boost solenoid near the turbo but away from excessive heat, run a boost line to the turbo actuator and signal line from the turbo intercooler pipe or similar, run the dark pink and black wires back to the master avcr screen and join solder and insulate.

no offence but i didnt think i could make it any clearer.

have a look at the pics in your 1st post,

boost solenoid

dark pink----------to-------> dark pink on the avcr master

black----------to------------>black on the avcr master

boost sensor

pink-----------to---------->pink on avcr master

white---------to----------->white on avcr master

black---------to---------->black on the avcr master

they wont work cause they receve the signal from the engine ecu with the wires i already know and process the infomation in the avcr unit and then send the info to the pressure sensor and control valve to open the wastegate via the colourd wires i dont know hence me needing to know

http://www.apexi-usa.com/content/pdf6115.pdf

ok couple of minutes on google for you

The colours on the harness side are correct to the avcr.

Pressure Sensor Pink goes to AVCR Pink

Pressure Sensor Black goes to AVCR Red

Solenoid Valve Red goes AVCR Yellow

Solenoid Valve Black goes AVCR Brown

Solenoid Valve White goes AVCR Blue

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...