[rusEfi] Mitsubishi 4G63 and 4G92 (#6)

[AndreyB]

Trigger is http://www.msextra.com/doc/ms1extra/MS_Extra_Ignition_Hardware_Manual.htm#4g63

[AndreyB]

Trigger is http://www.msextra.com/doc/ms1extra/MS_Extra_Ignition_Hardware_Manual.htm#4g63

That looks pretty close to my Ford Aspire trigger shape - maybe even the same - see http://rusefi.com/forum/viewtopic.php?f=3&t=375#p3882

You have that logic analyzer/oscilloscope, right? can you record both sensor signals while the car is idling? I want to see if the angles are the same.

[AndreyB]

I did not have a chance to test it yet, but latest version now does not write to flash if engine is running - if engine is running the settings are applied but they are only saved into flash once you turn the engine off. Feel free to try this if you want, or I will test this hopefully on Sunday.

[Tambralinga]

I will set the ts for the crank and cam 4/1 hall sensor
How is the test signals cam / crank?

[AndreyB]

This works differently. You are not 4/1 skipped tooth, you are 4+1. You cannot totally customize it via ts, I need to code it. For me to code it I need u to record oscilloscope signal.

You can also try using aspire setting sinse it's also 4+1 (not 4/1)

[AndreyB]

This works differently. You are not 4/1 skipped tooth, you are 4+1. You cannot totally customize it via ts, I need to code it. For me to code it I need u to record oscilloscope signal.

You can also try using aspire setting sinse it's also 4+1 (not 4/1)

[Tambralinga]

ok

JP52, JP53 use it to connect to w212, w211?
How to use JP52,JP53?

[Tambralinga]

Hi Andrey,
I have test CRANK, CAM sensors form my car.
Form Hantek 6022BE Oscilloscope.
CH1 = CKP, Yellow line.
CH2 = CAM, Green line.

CKP Input at INP-11
CAM Input at INP-12
Sensor 4+1

In this images. Speed on 1300 rpm.







Thanks.

[kb1gtt]

It appears there is an issue with the CAM sensing signal. The graphic in the bottom of the screen seems to indicate the scope was set to DC mode, but the signal that's captured seems to indicate the probe was capacitor coupling / AC mode. Can you check your GND strap? I've made broken my GND straps before, perhaps this is the issue here. Please check continuity with a multi meter to verify the GND stap is correct. The signal seen on that pin should be much larger and should be much more square, very similar to the CKP signal.

CKP seems a bit lower than expected as well. I would expect the CKP to be more like 5V to 0V. Was this done with a 10X probe or a 1X probe? I see the software notes 1X probe, but was the actual probe 10X? That can account for why the signal appears to be lower than expected. Does the probe have a 1X vs 10X switch? Several probes have a switch that allows you to change the probe scaling.

Can we get three different pictures? One picture that shows the rising edge of the CKP signal. Please fill the screen with only the transition from low to high. Then do the same but from high to low. I'm looking for these pictures to see if we would have better results capturing the raising or falling edge. For the third picture, please show much more of the full rotation. Something that hopefully shows the CKP and CAM and how they interact with each other. I'm expecting one pulse per rotation from CAM, but you are seeing much more than that. Can you take a p

Can you safely disassemble the CAS and take a picture of the internal wheel?

[Tambralinga]

for mitsubishi

[kb1gtt]

Looks like that matches the MS page, so I expect 4 pulses for Crank, and I'm not sure what to expect for a pulse for CAM. The only issue I see is that exponential decay instead of the square wave like the top signal. I think the bottom signal should look something like the red in this marked up picture.

[rus084]

may be the signal passes through capacitor and hence it turns out that?

[Tambralinga]

input signal cam and crank no response with TS (RPM)
Input INP11 and INP12

[AndreyB]

Do you have channels #11 & #12 connected to pins PC6 and PA5?

ok
JP52, JP53 use it to connect to w212, w211?
How to use JP52,JP53?

See http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#Step_2a:_Hall_sensor_input

[Tambralinga]

Looks like that matches the MS page, so I expect 4 pulses for Crank, and I'm not sure what to expect for a pulse for CAM. The only issue I see is that exponential decay instead of the square wave like the top signal. I think the bottom signal should look something like the red in this marked up picture.

Thanks, kb1gtt.

I'm wrong some GND. And I should be update like this.



But the graph doesn't square.
Mr.X

[Tambralinga]

Do you have channels #11 & #12 connected to pins PC6 and PA5?

ok
JP52, JP53 use it to connect to w212, w211?
How to use JP52,JP53?

See http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#Step_2a:_Hall_sensor_input

Hi rusEFI,

I am followed the Jumper. But it have no signal form RPM in Tuning Studio.

Mr.X

[AndreyB]

I am followed the Jumper. But it have no signal

Can you please post a picture of your whole Frankenstein as it is now?

Can you take stm32 off FRK and check the signal on the green and yellow wire when you are cranking the engine?

[Tambralinga]

I am followed the Jumper. But it have no signal

Can you please post a picture of your whole Frankenstein as it is now?

Can you take stm32 off FRK and check the signal on the green and yellow wire when you are cranking the engine?

It have no the LED lighting.
Mr.X

[AndreyB]

This is getting more interesting every day. First of all, that's not the final Frankenstein 0.1 revision - the op-amp part of the board looks different, is this some release candidate? But this should not be a problem.

The red wire on W211 obstructs my view - do you have R311 & R321 pull-down resistors? What are the values?
What values did you use for R310 and R320 pull-up resistors?

I am confused because http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#Step_2a:_Hall_sensor_input says one thing and https://docs.google.com/spreadsheet/ccc?key=0Arl1FeMZcfisdHQyRzhvSE1WOTd1NC1YYm8xZlB2Z3c says something else

Anyway, the cam sensors are simple, try them on a bench: while you spin the shaft, the output should be probably GND sometimes and floating (not connected) sometimes. Can you double-check your sensor output with the sensor on the bench?

Once you verified sensor output (it is either GND/floating or maybe it should be something else?), you should be able to reproduce it on the table with FRK board without discovery. I think floating (disconnected) channel #11 / #12 input should be 5v output on W211/W212 and GND channel #11/#12 should be zero volts output on W211/W212. Can you please verify this and report your results?

Once again, thank you for your patience with us

[Tambralinga]

Hi ...
I was test firmware latest version update on 29 Jul, 2014.
The results like this...
- FRK can not connect to Tuning Studio, Have no any signal form FRK, Discovery.
- Port PC15 Spark1 doesn't working. We was test the FRK in test mode it OK, just working.
- Port PE4 Spartk2 just working fine.
As the test we remove resister (Pull up) R320 and R310.

Thx.
Mr.X

[AndreyB]

Anyway, the cam sensors are simple, try them on a bench: while you spin the shaft, the output should be probably GND sometimes and floating (not connected) sometimes. Can you double-check your sensor output with the sensor on the bench?

We did some troubleshooting over Skype, the sensor is switching between GND and floating as expected

Once you verified sensor output (it is either GND/floating or maybe it should be something else?), you should be able to reproduce it on the table with FRK board without discovery. I think floating (disconnected) channel #11 / #12 input should be 5v output on W211/W212 and GND channel #11/#12 should be zero volts output on W211/W212. Can you please verify this and report your results?

test #1: GND input channels 11 and 12, tell me what you read on W211 and W212
result:
out put both 0.01 volt to W211 and W212

test #2: float input channels 11 and 12, tell me what you read on W211 and W212
need to return these pull-ups

[AndreyB]

- FRK can not connect to Tuning Studio, Have no any signal form FRK, Discovery.

per skype troubleshooting: works in GND<>PB1 mode, does not work otherwise

[Tambralinga]

- FRK can not connect to Tuning Studio, Have no any signal form FRK, Discovery.

per skype troubleshooting: works in GND<>PB1 mode, does not work otherwise

Thanks to Andrey.
You can see output in this video.

[video][/video]

Mr.X

[AndreyB]

I know that some pins, for example PE0 and PE1, and blinking LED but not clicking an injector well - that's because discovery has some stuff connected to these pins (MEMS?) and some of the current is lost there. But that's PE0 and PE1, not the pins you are having issues with.

Hold on, I want to add something into the dev console to be sure.

[AndreyB]

By the way you need to reset rusEfi in order for new output pinout to be applied. If you are just changing it in TS, not much is happening right away. I guess this should be made more obvious somehow.

[Tambralinga]

Hi Andrey,

I have some questions for configured port for SPARK_1 (Firmware Release on 29 Jul, 2014)
I was test on Tuning Studio, Default configured as PC7=HIGH DRIVER 6. It dosen't work.
Please in attached.


But in the reference document like ...


Close to PC15 = OUT 2 > SPARK_1.

Now, In the TS. I have changed to PC15 followed the document, It working.
In the right way, Do we have to change it to PC15 or not ?
Or I'm wrong in "HIGH DRIVER".

Thanks,
Mr.X

[Tambralinga]

Hi Andrey,

The RPM result form FRK comparison with Defi .
I have tested of RPM to Mitsubishi 4G92 and connect to TS and Defi.
Please see result in the video.

[video][/video]

That is normal case or something wrong.
Thanks.
Mr.X

[AndreyB]

[video][/video]

Let's double-check what do we see on this video?

1) is this the real car or simulator? Because I am not sure what we are looking at!
2) TS shows something like ~900rpm? and What is Defi? Some kind of a dash? What does this dash show? The dash shows 1200?

I guess if you would zoom out and show the big picture the context would be more clear. Right now I am not sure what I am looking at.

[AndreyB]

If we are looking at the real car and if we have trigger decoding issues, then I need you to attach a log file of your dev console run - not TS.

Turn TS off, turn dev console on. I would expect you see something like


in digital sniffer and something like


in analog sniffer.

Once you have it, please attach your log file. Your log fine is in the 'out' folder where your console is. File names are something like MAIN_rfi_report_2014-08-01 20_04.csv - I would need the last fine.

With this log file, I would be able to confirm your trigger signal shape so that 1200rpm would be 1200, not 900.

[AndreyB]

I've improved trigger signal error detection, current version - 20140802 - would blink the orange LED if the trigger sensors are not providing the expected signals.