[rusEfi] 1999 Honda Civic stock D16Y8 #26

[maximus64]

Finally got my car started on rusEfi

First cold start video:
[video][/video]

Idle way too high and seen to be running on all 4 cylinders but doesn't sound good (you can tell in the video). I don't have a Wideband install on this car yet, any recommendation for a good wideband sensor are welcome. I'm using the 1 and 24 tooths wheel inside the stock distributor. The MAX9926 chip that came with Frankenso board doesn't work well with the 1 teeth wheel due to the 85ms watchdog, so I had to design my own VR conditioner board. Still need a lot of work. I will update with more details later, I need to go to bed 4 am now

Engine bay picture:


Specs:
Honda Civic 99 EJ - D16Y8 stock
Frankenso V0.4 board
Custom VR conditioner board
Coil on plug conversion

[AndreyB]

very nice first post

hope to make some progress on https://sourceforge.net/p/rusefi/tickets/319/ you've reported today or tomorrow

[stefanst]

Congrats #24!
And good night i guess
Please share the schematic of your signal conditioner if you have a minute.

[maximus64]

This is my VR conditioner circuit


Schematic:
https://www.dropbox.com/s/t23hil8vccm56mi/vr_circuit.pdf?dl=0

Kicad Project:
https://www.dropbox.com/sh/klta9apg37xmeyy/AADsa9HaYyMjfQZlnalKJxIya?dl=0

[kb1gtt]

Sweet first post. I usually make a wiki note, for first time posters. Have you come across this particular section yet? It's about VR design and includes a link to an app note that you might find interesting. http://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger#VR_lower_level_details.2C_formulas.2C_app_notes.2C_etc

Awesome post about the VR. I created a quick QUCS such that those of us who do not have the circuit can see what it does.

VR_circuit.png (56.63 KiB) Viewed 10506 times

QUCS schematic file found here.
https://cp.sync.com/dl/6a5ff5be0#u7d2xz84-nghw2b44-q233hu3z-ynmah2hc

[AndreyB]

Schematic:
https://www.dropbox.com/s/t23hil8vccm56mi/vr_circuit.pdf?dl=0

Kicad Project:
https://www.dropbox.com/sh/klta9apg37xmeyy/AADsa9HaYyMjfQZlnalKJxIya?dl=0

copy-paste of these files just to save them here

[kb1gtt]

Slightly updated version of the QUCS simulation below. Perhaps this looks kind of similar to what maximus64 sees in the real world. I corrected the polarity of the opamp, and used a file based voltage source to simulate a VR sensors voltage. I don't have the same op-amp, I used a AD825 because it was the closest I had in the component library. Hopefully the rest of the circuit reacts similar to the real world.

VR_circuit.png (54.36 KiB) Viewed 10499 times

https://cp.sync.com/dl/51f06f7d0#sja4r376-mtmdvjsa-nmdvm53c-u6ianr82

[maximus64]

The output doesn't look correct. I checked the AD825 and isn't compatible to LM393. The LM393 has open collector output.
LTSPICE doesn't have open collector comparator so I just rig up some transistors

[maximus64]

rusEfi console engine sniffer output:





I still haven't able to get rid of the stuttering yet.

[kb1gtt]

Here's the list from QUCS. Do any of these look to have the open collector you noted? They didn't seem to work the way I was hoping or expecting, so I doubt it and it's a small list.

[maximus64]

Here's the list from QUCS. Do any of these look to have the open collector you noted? They didn't seem to work the way I was hoping or expecting, so I doubt it and it's a small list.

I check each of them and most are just general purpose op-amp, but you could convert the output signal to open collector and play with it.
So far the VR board seem to work nicely. I haven't tried above 4000 RPM yet due to no tune.

[kb1gtt]

I've gotten the QUCS working with a PSice model provided by TI. However it appears that there is a bug in the windows version of QUCS. There is a preprocessing utility that I'm supposed to select which converts the PSpice model to a QUCS native model. This utility is called ps2sp, which fails. However when I select no preprocessor, it simulates very well. However the output is wrong. Here are my notes and where I'm currently at with the simulation, It still not working correctly.

OK, so QUCS R0.19-snapshot has a bug when trying to use SPICE imported devices. I got this QUCS model to work by first un-installing QUCS and installing it into "C:\Qucs" note this has no spaces, and the default includes "program files" which has a space. Once QUCS is installed with no spaces, then you need tinyperl and you'll need to specify that it's installed in "C:\Qucs\bin" Notice the default will try to install into a folder which won't work. It needs to be in the root bin folder.

Capture.PNG (3.96 KiB) Viewed 10482 times

Then I added a ".END" after the ".ENDS" in the PSpice file, and QUCS stopped complaining about things. Here's the files which attempt to use the PSpice model. I suspect that the linux versions would do this just fine. I think the issues I'm having are windows related. I've only found people complaining about it who were also windows people.
https://cp.sync.com/dl/4a63cdb70#rtbmyrt9-dnxg94q6-xnazzdxt-bx8y8t7a

[maximus64]

Just a small update. I had to move the crank trigger input to pin PA8 because the pin PA5 isn't 5v tolerant and now the issue is gone I also ordered an SLC-FREE WideBand controller (http://www.14point7.com/products/slc-free) and I'm also in the process of building an engine simulator heh

[maximus64]

I have good news and bad news, good news is that I made my own timing light and it works. The bad news is that the timing isn't consistent, it move when the RPM change 0-15 degrees advanced from where I set it at and then slowly settle at the setpoint, it also does the same when the RPM drop or increase. It seems to only advance the timing. I had checked the ignition setting on rusefi and it set to fixed timing 12 degrees advanced. I tried to record a video but it won't show up on the camera well.

Oh and I also notice that the tunerstudio timing gauge also jump around a bit when applying some throttle 14, 12.7, 12, ...

[kb1gtt]

Made your own timing light, sweet. Is that a design you can share? I've been tempted to do it with LED's but I was concerned that they don't make enough light. I think the traditional bulbs are the way to go, but those are harder to find and harder to work with. I'm wondering what you had tried.

[AndreyB]

Good news I think its about the default iat timing table which you had not reset, bad news you are not the first person to be confused by that.