Page 1 of 6

frankenstein 0.11 on nissan sr20ve neo vvl #34

Posted: Tue Mar 14, 2017 4:13 am
by matt
FB_IMG_1489463542090.jpg
FB_IMG_1489463542090.jpg (19.28 KiB) Viewed 19019 times
consider this is 2nd project, my chasis is kia carens 1.8 swap with nissan engine.
at first it was with cvt transmission, but it cause many problem with standart ecu.
neo vvl not working if not install with full engine and dashboard wiring harness.

i change to manual transmission and ecu was swap with ms2 with 4g63 cam angle sensor.
for now i prefer it running with standard 360 slot cam angle sensor.
i can provide trigger pattern in this weekend.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 14, 2017 10:24 pm
by AndreyB
matt wrote:with 4g63 cam angle sensor.
Do you have pictures of both sensors, complete units? If these are interchangeable I wonder if one can use Nissan sensor on a Miata?

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Wed Mar 15, 2017 5:38 am
by matt
IMG_20170315_132409.jpg
IMG_20170315_132409.jpg (1.6 MiB) Viewed 18985 times
Left is 4g63 (vr4), right is nissan 360 slot. Still need to modified the plate, if not it not touch the camshaft.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Wed Mar 15, 2017 3:01 pm
by matt
here is 360 slot look like.
2017-03-15_22_57_05rpm_0_maf_NaN.png
2017-03-15_22_57_05rpm_0_maf_NaN.png (8.3 KiB) Viewed 18972 times

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Thu Mar 16, 2017 10:19 pm
by AndreyB
I guess let's begin without the 360 channel, I believe sync works based of the 4 slot?

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Fri Mar 17, 2017 7:09 am
by matt
sorry, i don't know any about trigger calculation.
so i need to log with only 4 slot?
i can provide this 4 slot in evening or tomorrow.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Fri Mar 17, 2017 3:31 pm
by AndreyB
matt wrote: so i need to log with only 4 slot?
Yes, please log only 4 slots as first step. Please select 'custom skipped wheel" total=4 skipped=0 while doing that.

What year/donor is your sr20ve? Want to name this trigger properly.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sat Mar 18, 2017 8:31 am
by matt
4 slot
2017-03-18_16_24_35rpm_0_maf_NaN.png
2017-03-18_16_24_35rpm_0_maf_NaN.png (32.44 KiB) Viewed 18920 times

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sat Mar 18, 2017 8:43 am
by matt
i'am also logging for a 360 slot. in case if you need that.
custom tooth wheel is set to 36.
2017-03-18_16_39_45rpm_0_maf_NaN.png
2017-03-18_16_39_45rpm_0_maf_NaN.png (20.47 KiB) Viewed 18919 times

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sat Mar 18, 2017 8:53 am
by matt
russian wrote:
What year/donor is your sr20ve? Want to name this trigger properly.
not sure, but i believe it come from primera p11 year 1995-2002.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 2:08 am
by AndreyB
matt wrote:4 slot
20170318 should now sync on Nissan Primara trigger.

We will deal with the 360 slot 2nd channel a bit later, you can start your car with 4 slots.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 8:02 am
by puff
will this 360-slot thing allow to track efficiency of each cylinder and measure instantaneous acceleration? just wondering how the whole thing looks like - the trigger and the sensor... at 6000 rpm it means a pulse each 2.7~µs - probably, not an easy task for a microcontroller?

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 1:26 pm
by AndreyB
puff wrote:at 6000 rpm it means a pulse each 2.7~µs - probably, not an easy task for a microcontroller?
360 on cam is only 3 times more work compared with a 60/2 on crank. We will see :)

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 1:31 pm
by matt
in TS it should be nissan trigger or custom tooth wheel? i test both is sync. i'am gonna to re-wired my cas now. hopefully it will start tonight.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 1:36 pm
by AndreyB
Nissan trigger, make sure you are using latest firmware.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 1:46 pm
by matt
yes. iam using snapshot_20170318_2151_rusefi

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 2:44 pm
by matt
and YESSS!! its start..

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 3:15 pm
by matt
and it start only once, not for 2nd time.. i try with custom tooth wheel rpm show correct, but with nissan looks like not stable and sometime remain 0 rpm. gonna work on it tomorrow.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Sun Mar 19, 2017 3:48 pm
by AndreyB
Do not even try 4/0 custom wheel - it would not work right for sure.

Do you have any console log files? There could be useful info there.

Next time try enable trigger_details & writeconfig commands in console or "print sync details to console" option in TS. This would produce some helpful messages with synchronization progress details.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Mon Mar 20, 2017 2:58 am
by matt
just curious, is this trigger event?
trigger event.png
trigger event.png (179.16 KiB) Viewed 18849 times

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Mon Mar 20, 2017 3:16 am
by AndreyB
matt wrote:out of curiosity, is this trigger event?
trigger event.png
this whole line is what you see in engine sniffer in console, raw data for it.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 1:30 am
by matt
i'am not so understand on issue #314 'faster cranking with battery-backed RAM'.
meaning on my stm32 disc got battery or i must put a battery at the back of my frankenso rev0.2?

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 1:34 am
by AndreyB
matt wrote:i'am not so understand on issue #314 'faster cranking with battery-backed RAM'.
meaning on my stm32 disc got battery or i must put a battery at the back of my frankenso rev0.2?
https://github.com/rusefi/rusefi/issues/314 is an improvement idea which was not implemented yet. some battery for stm32 does not matter where it would be - but that's just an idea at this point.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 3:17 am
by matt
today progress.

with nissan trigger setup in TS, no rpm sync.
with custom tooth setup it start for a 5 second, and engine stop if throtle if press.

i can start engine with standard ecu and log a trigger in console if its needed.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 3:19 am
by AndreyB
Next time try enable trigger_details & writeconfig commands in console or "print sync details to console" option in TS. This would produce some helpful messages with synchronization progress details.

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 4:08 am
by matt
russian wrote:Next time try enable trigger_details & writeconfig commands in console or "print sync details to console" option in TS. This would produce some helpful messages with synchronization progress details.

can i do this while cranking?

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 10:33 am
by matt
4 slot with enable trigger_details & writeconfig commands.
4slot2017-03-21_18_19_05rpm_0_maf_NaN.png
4slot2017-03-21_18_19_05rpm_0_maf_NaN.png (18.77 KiB) Viewed 18811 times

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 10:37 am
by matt
i'am also logging for 360 slot if this is needed.
360slot2017-03-21_18_28_40rpm_0_maf_NaN.png
360slot2017-03-21_18_28_40rpm_0_maf_NaN.png (11.17 KiB) Viewed 18809 times

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 11:56 am
by AndreyB
I've widened the expected cap a little bit. It was from 8.70 to 14.50 and it is supposed to sync on 9.69, 9.62 etc.

We do not need 360 slot data so far. I wonder if it starts on 4/0 because your trigger offset is 180, 360 or 540 off? Did you get a timing gun?
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 403: gap=38.76/0.02/9.61 @ 1 while expected 8.70/14.50 and NaN/100000.00 error=1
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 403: gap=0.02/38.76/0.02 @ 2 while expected 8.70/14.50 and NaN/100000.00 error=1
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 403: gap=38.74/0.02/38.76 @ 3 while expected 8.70/14.50 and NaN/100000.00 error=1
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 403: gap=0.02/38.74/0.02 @ 4 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 403: gap=37.72/0.02/38.74 @ 5 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 403: gap=0.09/37.72/0.02 @ 6 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 404: gap=9.69/0.09/37.72 @ 7 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 404: gap=0.02/9.69/0.09 @ 0 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 404: gap=38.73/0.02/9.69 @ 1 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 404: gap=0.02/38.73/0.02 @ 2 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 404: gap=38.60/0.02/38.73 @ 3 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:48 SGT 2017<EOT>: postMessage EngineState: 404: gap=0.02/38.60/0.02 @ 4 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 404: gap=37.89/0.02/38.60 @ 5 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 404: gap=0.09/37.89/0.02 @ 6 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 404: gap=9.62/0.09/37.89 @ 7 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 404: gap=0.02/9.62/0.09 @ 0 while expected 8.70/14.50 and NaN/100000.00 error=0
...
...
...
...
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 404: gap=38.86/0.02/9.62 @ 1 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 404: gap=0.02/38.86/0.02 @ 2 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=38.84/0.02/38.86 @ 3 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=0.02/38.84/0.02 @ 4 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=37.81/0.02/38.84 @ 5 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=0.09/37.81/0.02 @ 6 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=9.60/0.09/37.81 @ 7 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=0.02/9.60/0.09 @ 0 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=38.75/0.02/9.60 @ 1 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=0.02/38.75/0.02 @ 2 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=38.88/0.02/38.75 @ 3 while expected 8.70/14.50 and NaN/100000.00 error=0
Tue Mar 21 18:17:49 SGT 2017<EOT>: postMessage EngineState: 405: gap=0.02/38.88/0.02 @ 4 while expected 8.70/14.50 and NaN/100000.00 error=0

Re: frankenstein 0.11 on nissan sr20ve neo vvl

Posted: Tue Mar 21, 2017 12:26 pm
by matt
it start with 4/0 at 0 degree offset, but just a few second and engine not stable.
with nissan trigger no rpm sync at all.

p/s: no timing gun yet