rusefi.com

All adapter files are actually public https://github.com/rusefi/proteus-M73tu-adapter/ including schematics PDF at https://github.com/rusefi/proteus-M73tu-adapter/tree/main/proteusM73tu/gerber

You has trigger sync error during cranking - gap settings were fine but somehow it has missed a tooth

error code CUSTOM_PRIMARY_NOT_ENOUGH_TEETH = 9003
Not sure if that could be wiring/hardware/sensor issue. Another area to improve starting would be adjusting starting tune.

SubaruLT wrote: ↑

Sun Sep 17, 2023 8:30 pm

Can't say exactly. But how I noticed output and input pins are labeled according board. Easter to identify.

that's totally doing using existing toolset, I really hope the authors are not wasting time on manual rename.

Next step White accent sister vehicle in PR

https://rusefi.com/online/view.php?msq=1539

I've repaired the UI https://github.com/rusefi/rusefi/commit/86662f53021ea65d81d8641fcffa598f789a2353
and changed the default gaps https://github.com/rusefi/rusefi/commit/c0f84776922546353d8242fa34979320e0330e9b

please update firmware and try again

https://rusefi.com/online/view.php?log=1287 Great stuff it has all the needed data! on the left of https://github.com/rusefi/rusefi/wiki/Images/triggers/trigger_TT_36_2_2_2.png expected gap ratio sequence is rendered but the log show slightly different numbers, let's use "trigger gap override&...

SubaruLT wrote: ↑

Sat Sep 16, 2023 7:20 pm

I use Core 8 ECU with specific FW

Since you mention that please provide more details on some Core 8 - what changes are beneficial above rusefi firmware?

Something funny happens - for a few days already STM32F407VGT6 costs LESS than APM32F407VGT6 at JLC. Well, only at low quality - Geehy gets a hair cheaper at qty 30.

https://jlcpcb.com/partdetail/Stmicroelectronics-STM32F407VGT6/C12345
https://jlcpcb.com/partdetail/Geehy-APM32F407VGT6/C2990873

Please upload normal not trigger log taken at high data rate.

Still doing silly things - this time submerging ECU in water, using special grey proteus case.

EZ230 is very specific application so we can hard-code known TDC position 36/2/2/2 is used not only on Subaru but also Daihatsu and rotary RX-8 I am not sure of TDC is same for all applications. One thing we can do is we can at least note official Subaru TDC position for specific engine once you kno...

went 200v, attempted count 50 series and magic smoke was released pretty quickly

150v
ambient 25C
igbt 33C
resistor 50C

this has survived count 500 multiple times

moved 1N4007 to be parallel with TVS diode - that gives me lowest Vpp

I have no idea what is the problem we are trying to solve. No need in logs in your vehicle starts and runs.

Please post a log file see https://github.com/rusefi/rusefi/wiki/HOWTO-upload-log

in your opinion what is wrong this the following image? Note that it only shows VR rises not actual shape of the metal.

Smoczy wrote: ↑

Thu Sep 14, 2023 8:28 pm

I haven't made the layout yet, but when I do, I will try to make tests and present them here. Unless someone does it first?

yes please yes!!!

thank you for sweet content

Went up to 230v. IGBT has only lasted a few funded pulses

AndreyB wrote: ↑

Sat Sep 09, 2023 3:11 am

Just ordered 1.5KE400CA TVS Diode to be continued.

Well, something has changed but there is still the spike.

why don't you use a custom-chip instead, rather than discrete circuitry? Reasons change over the time for sure. Main focus is still universal crank/cam decoding, i.e. from 60/2 on the crank to only couple of teeth on cam. At some point we needed 100% assembly specifically at JLCPCB while JLCPCB was...

Please let me know if anyone has done it, and let me know your comments and observations what problem does this solve on top of existing https://github.com/mck1117/vr-interface? The open problem I am aware of would be a single-wire VR/Hall hybrid solution https://github.com/andreika-git/hellen-one/...

Would https://github.com/rusefi/rusefi/wiki/GDI4 work?

How is it going? I assume that one wideband would be enough for first month but eventually would be nice to monitor second side just as a safety precaution?

At the moment fuel correction only games one sensor in the account.

we now have an open source ECU compatible with that pinout https://github.com/rusefi/hellen-112-17

one day someone should improve https://github.com/rusefi/rusefi/issues/5561

Nope, custom 12/0 would not work here. You should use "Honda K 12+1" which has special FOUR_STROKE_TWELVE_TIMES_CRANK_SENSOR logic in the firmware.

Yes, these magic numbers are the range of randomly designated sync tooth on the cam.

Now please update to fresh snapshot and let's use proper configuration specifically for 2JZ

Smoczy wrote: ↑

Sun Sep 10, 2023 11:47 am

Maybe someone want to try

Exciting to see kicad and simulation can you please publish kicad and simulation raw files?

Any chance you could comment key ideas of this schematics right on the kicad page?

2JZ 3/0 cam wheel is a unique one and it looks like while we have all the needed code, we never got it to properly run and never documented the magic way it's configured while we are figuring it out. At the moment your log shows that engine phase was not detected - note the magic field names I am lo...

Please try and post tune with logs afterwards, that's the only way community would gain the answer. Trigger flexibility is one of the bulletproof areas of rusEFI