How to get started with Honda

Your chance to introduce yourself and your vehicle
Post Reply
TVA_VAE
Posts: 1
Joined: Sun Mar 29, 2020 4:13 pm

How to get started with Honda

Post by TVA_VAE »

Dear

We are into hardware and firmware, but I am not 100 percentage following how to start. We are looking to put this in Honda's (D14A4 and D16Y7). Civic and Del Sol.

How to get started?

Greetings
Thomas Van Aken
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: How to get started

Post by AndreyB »

See https://github.com/rusefi/rusefi/wiki/Hardware for the first two questions. I kind of think that your Honda has 2 or three VRs, I believe microRusEfi would NOT work for you so assembled Frankenso is your best shot in my opinion. Frankenso kit is a cheaper but riskier option.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
ZHoob2004
contributor
contributor
Posts: 153
Joined: Sun Apr 03, 2016 7:11 pm
Location: Tucson, AZ

Re: How to get started

Post by ZHoob2004 »

I'm probably one of the people to talk to when it comes to Hondas I suppose.

Both cars are obd1 I assume?

Frankenso will be plug and play with reconfiguring the internal jumper wires, but I was unable to get the 1-tooth cam sensor working (hardware limitation) so I was unable to run anything but simultaneous fuel and distributor ignition.

Currently I am running microrusefi on my b16 crx using an obd0->obd1 jumper harness that I rewired so I have a plug and play ECU. I am still running the simultaneous fuel and distributor ignition because MRE (microrusefi) only has one VR input, and I haven't yet connected an external conditioner to handle the cam signal.

I don't remember if either of those engines are VTEC engines or not, but that is another thing that is currently unsupported, both hardware and software.

In your case, it all depends on what you want. For PNP, frankenso is probably a good idea but I can't promise any progress on the cam sensor issue, and it's probably more hardware than you need. In the case of MRE, you could build a PNP adapter (the connectors are readily available) or you can cut and crimp directly into your harness.


Additionally, I don't have AC control yet because of a low number of low-side outputs on MRE. Frankenso would do fine in this regard, as it has 12


Final note: I don't really recommend the frankenso in kit form. I assembled the kit and it wasn't fun. Lots of small unique pieces on a board with a less than stellar layout (sorry). And a lot of confusion about what is really necessary.
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: How to get started

Post by AndreyB »

ZHoob2004 wrote:
Sun Mar 29, 2020 9:39 pm
I don't remember if either of those engines are VTEC engines or not, but that is another thing that is currently unsupported, both hardware and software.
I suspect that FSIO got VTEC software covered. Is it a high-current high-side control? I remember we have added a weird custom high-current high-side module for my short term Accord test mule but do not remember if it was VTEC or something else.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
ZHoob2004
contributor
contributor
Posts: 153
Joined: Sun Apr 03, 2016 7:11 pm
Location: Tucson, AZ

Re: How to get started with Honda

Post by ZHoob2004 »

AndreyB wrote:
Sun Mar 29, 2020 11:09 pm
I suspect that FSIO got VTEC software covered. Is it a high-current high-side control? I remember we have added a weird custom high-current high-side module for my short term Accord test mule but do not remember if it was VTEC or something else.

For your Accord I think it was probably for variable length intake manifold or something similar.

The issue with using fsio for VTEC is it's changing the VE of the engine, and as such requires either multiple VE tables, or a supplemental fuel table. Similar situation for ignition.

My comment regarding this is less about software and more about neither setup having onboard hardware to handle it, though I'm currently brainstorming a solution on that front for my car.
Post Reply