Forum » Practical Harness Construction - Club Level » RB 25 Neo transplant into a 280z with Link Fury

RB 25 Neo transplant into a 280z with Link Fury

Practical Harness Construction - Club Level

Discussion and questions related to the course Practical Harness Construction - Club Level


Page 1
Author
131 Views

Hi All,

Was wondering who else on this forum has done this before ? Loads of questions and researching ahead ! Does anyone have a list of which of the OEM engine and emission controls , I should retain and disregard ?

cheers

Tony

Gooday Tech crew,

Was hoping you could clarify wrt OBD2 port connection and wether I should include it into my custom ECU harness to assist with future diagnostic testing ? I doing a RB25Neo transplant into a 75 280z and I imagine my 280z is unlikely to have a OBDII port because if it’s age ?

Should I consider adding this to my harness so that I could use OBD2 port for diagnostics or if I want to transmit to a tablet using an OBD to Bluetooth or WiFi device ?

My thinking was to use CAN1 via Comm port on my Link Fury ECU to achieve this and use CAN2 on ECU B port(CAN H/L) for my GaugeART multifunction gauge ?

Does my thought process make sense or do you have a better solution ?

Cheers

Tony

If you really do want an OBD2 port then it will be best to keep it on a separate CAN port than the Gaugeart gauge. The main rule with CAN bus is all devices on the bus must communicate at the same baud rate. I believe the gaugeart is hard coded for 1Mbit/s. Although some OBD2 devices can work at 1Mbit, most commonly they only support 250 or 500Kbit so you really want to keep them on separate buses to ensure they are not going to clash.

Having said that, OBD2 on an aftermarket ECU is really only any use for a basic display, OBD is too slow for logging or anything else of use and a laptop is better for actual diagnostics. It is even borderline too slow for a dash in many cases.

Thanks for your input Adam , yes I believe it far better to use the PC LINK diagnostics, it was more just building into the harness for what if’s vs configuring later .

Is there any other comm ports or harness addons recommendations I should consider for my build apart from the norm discussed in the club course ?

TIA

Tony

Gooday Tech Crew,

I have a question regarding FD3S wiring on the practical club wiring course , with regards to Engine coolant sensors , I noticed you have a single pin sensor on the the body harness and 2 pin sensor for the ECU . Will I’ll be able to run a single EC sensor for both the gauge and ECU ?

Gooday Tech Crew,

I have a question regarding FD3S wiring on the practical club wiring course , with regards to Engine coolant sensors , I noticed you have a single pin sensor on the the body harness and 2 pin sensor for the ECU . Will I’ll be able to run a single EC sensor for both the gauge and ECU ?

Hi Tony, the two sensors you refer to are the gauge sender (single terminal) and the engine coolant temp sensor (2 pin). Unfortunately if you want to retain the factory gauge cluster then you do need to incorporate both sensors. If you plan to use an aftermarket digital dash then the gauge sender isn't necessary since all the data for the dash will be sent via the ECU.

Thks for the reply Andre, all understood and for correcting me on the using the correct terminology . I will go the route of a gauge sender for my Speedhut gauge and ECT sensor for the ECU!

I’m assuming the same rule applies for oil pressure and temp indications?

cheers

Tony