rusefi.com

Then i guess, revision C is the currently -latest and gratest-. What do you suggest, should i go with revision C or revision B? I'm putting my thoughts bellow if anyone wishes to comment. The thing is that B uses the MAX9926/24 that is great for a VAG with a 60-2 crank wheel, as long as you add a re...

Is revision D ready to use or only B is tested (for a 4 cylinder engine)?

I noticed that in revision D you migrated to the new discrete-VR module, isn't it still under development?

You are right, i stand corrected!
they have indeed different pinout in this package (a big screw-up from ST if i may add since they advertise full pin compatibility from their M4 to M7 series)
Oh well, no rest for the wicked... new PCB incoming...

Hardware-wise, both MCUs ara pin compatible,
what is your reasoning? unsuported functionality in M7 series?

Will the 0.4.5 (2L) PCB work with the F7 MCU?

I'm saving the configuration to flash (through TS)

Going to try the neon trigger pattern later today

Something very strange is happening here......

I'm getting verified readings from logic analyzer and oscilloscope that crank cycle time is 9.7 - 9.8ms @ 6000 RPMs but both the console and TS are reporting exactly 6000 RPM.

Hmmmm, time to bring in JimStim and an Arduino as extrernal Stimulators

there is a discussion at http://www.eevblog.com/forum/testgear/hantek-ht4032l-logic-analyser/15/ about this but it's almost 3 years old It looks like they moded the crap out of it :o i have a DSO-2150 oscilloscope from Hantek for i dont really remember how many years , for the money back then, it wa...

How do i disable self stimulation?

Update #1 Notice 1) the fact that there is no sync loss, so, every other pulse "steals" 0.2ms by the previous [or next] pulse, or maybe gives 0.2ms to previous or next pulse [assumption: coil#3 period of 4.7ms is correct] Notice 2) it is always 0.2ms, no matter what rpm, if console or TS i...

All right, i managed to get my hands on a Logic Analyzer and scopping at 200KHz revealed some good info. The RPM was set at a very high of 12k (the problem persists even on 1k rpm and scoping that high makes it possible to have a lot of samples with smaller memory amount), set on 4-cyl wasted spark,...

I was thinking (for a long time now but always postponed it) to buy one of these http://www.hantek.com/en/ProductDetail_16_14.html Anyway, the console, is it a true logic analyzer or it's just pulling the data from the firmware/RAM and display them graphicaly? **update I had an Arduino mega lying ar...

OK new launch retard is using: engine->engineState.step1LimiterActive No more "L33t H4X0r" board configuration manipulation :D changes available @ git Disregard the other float variables i've added, they are for future racing function and launch control enrichment in the future. Now about ...

True, we'll have to add a new variable to dynamic Engine State in order to be within your design constrains, but, in order to have non-static ignition retard and some kind of fuel enrichment not just for launch control but for other functions aswell like knock retard & enrich, traction control r...

1 - Since engine_configuration_generates_structures.h and rusefi.ini are generated by rusefi_config.txt they should be in sync allready, one problem tho is that i don't know how to add the new submenu to rusefi.ini though rusefi_config.txt. so, I manualy edited rusefi.ini to add "Racing Feature...

Launch RPM Window: RPM range (window) prior to RPM Step1 Limit point (Launch RPM) that retards ignition to Step1 Ignition Value [usefull for turbo spool-up. a Later ignition point will produce more heat and exhaust gas pressure to exhaust manifold (=more energy for the turbocharger) helping it to s...

Here's the new patch. Minimal changes as you have predicted

well, it looks like you've already done the job.... :oops: Anyway now that we have a launch control it's time to increase accuracy at high revs(>16K) :D FYI right now it's doing fine up to 20K but there's an issue where "randomly" (if there's such a thing!) every other ignition falling edg...

Sorry, i've been away for the last 3 days.
I'll get right in to it asap

Here the first patch, it contains the launch control code.

No worriez, you can't be in front of the computer screen all the time

I was meaning to ask you about code commiting, i'll link Eclipse tommorow and fork the project for the major/crazy changes and look into svn patches [I never used that before ] for the bug squashing.

Bug squashed :) The problem was that during hard limit we where returning from the triggercallback without doing anything. That had the effect that if the signal was up in the previous ignition event it never came down (return) and while rpm was greater than rpmHardLimit it kept beeing high since we...

Nest step is getting this on a real vehicle, would you be interested to test it in real life? But first I need to fix https://sourceforge.net/p/rusefi/tickets/225/ - that's unless you can suggest a fix. I myself is now focused at https://sourceforge.net/p/rusefi/tickets/226/ I'm onto 225 myself, ju...

yep hopefully it is the same bug, however the time on coil 1 is varying by at least 720 degrees on this one then we still have the bug of timing variation every other pulse of coil 1 http://rusefi.com/forum/viewtopic.php?f=5&t=929 i'm going after it as soon as i finish with launch control *edit,...

Excellent... i will create the ticket.
btw, if you fix this we get a working launch control aswell....

It's not always 100ms this is just the higher number i have seen [worst case :)] This looks like a bug in the scheduling,it manifests only on COIL#1 and it also affects rpm Hard Limit try to set rpm limit at 7000 and set console RPM at 7001 , there's a chance each time the rpm signal goes from 7000-...

rebuild flash struct with extra variables -> done TS .ini -> done we now have exposed cluchUp and CluchDown channel selection, Launch RPM and Launch Ignition advance setting, use of fuel cut/spark cut/both exposed to TS the code works good on a basic level, however, a bug appeared on the rpm transit...

integration completed.... up to the point where i screwed up the struct offsets (bound to be happen at 4:30 in the morning!!!). Now i'm getting a nice console error message "EngineState: FATAL error: Unknown hw channel 1073741824" :D oh well, at least i got the code ready plus the .ini for...

I scoped the output of STM32F4 board in a variety of rpms and noticed that on coil #1 every other pulse the falling edge offsets by 0.4ms the trigger is set as 12-3 and bellow i have some screenshots. Have you noticed anythng similar? As you see the dwell is varying by 0.2ms every other pulse for co...

I received my discovery board yesterday and went ahead to implement the launch control I had to hardcode the Launch Control pin state read since for some mysterius reason defining the pin at engine_configuration.cpp Completely ignored me : [code]boardConfiguration->clutchUpPin = GPIOE_13; boardConfi...