hello all - Mitsubishi #31

kb1gtt · Post by **kb1gtt** » Wed Jan 25, 2017 11:18 am

Typically no you do not need to install those diodes.

Those are offered for people who need a slower decay time, which so far I think one application needed the flyback diode topology for alternator control. The low side drivers have an over voltage protection which has a faster and more accurate decay time than.

matt · Post by **matt** » Wed Jan 25, 2017 1:03 pm

one more thing. for my crank/cam input is going to op am with 5v pull up. am i righ?
apologies for my poor memory. not remember where i read about this.

Post by **AndreyB** » Wed Jan 25, 2017 1:36 pm

op-amp with 5v pull-up is a great option for Hall-type sensors. Channels #9 and #11 have all the holes needed to route digital outputs into pins PC6 and PA5. I do not have a great picture for this, once you make your board it would become the official example

triggerinfo command in the console is your way of testing. you would be grounding the signal wire and every time you ground it triggerinfo would go up.

matt · Post by **matt** » Wed Jan 25, 2017 2:01 pm

great!! your words make me much eager.
i am not fully concerntrate at console yet. last time i tried and got wrong configure, and i leave it until now.

matt · Post by **matt** » Wed Jan 25, 2017 4:08 pm

accidently lost 0.01uf caps should be at c300, c310,c320.
can i use 0.1uf since i have few extra of this caps?

matt · Post by **matt** » Fri Jan 27, 2017 1:58 pm

ok. notice some issue today. i plug stm board to shield with 12v power supply, and blue led at stm not blink. blue led blink only if i plug in mini usb and it can connected to tunerstudio.

Post by **AndreyB** » Fri Jan 27, 2017 2:09 pm

Google "rusefi overcurrent", update st link firmware to resolve

matt · Post by **matt** » Fri Jan 27, 2017 2:50 pm

russian wrote:It's not the first time that user clive1 from st forum is saving me - this guy knows everything stm32!

And it worked! With latest STM32 ST-LINK Utility v3.9.0.exe I've updated discovery firmware (not rusEfi firmware) and the issue is resolved!

With a little caveat: newer boards take an extra second to start. Still an open question how to put old firmware into the new board.

it this mean use older STM32 ST-LINK Utility? i tried v2.3.0.exe seems not working.

matt · Post by **matt** » Fri Jan 27, 2017 2:52 pm

ahhh.. not read properly your post. i try 3.9.0.exe.

matt · Post by **matt** » Fri Jan 27, 2017 3:12 pm

done!!

thanks russian.

kb1gtt · Post by **kb1gtt** » Sat Jan 28, 2017 12:17 am

I almost forget to reply.

mattsabun wrote:accidently lost 0.01uf caps should be at c300, c310,c320.
can i use 0.1uf since i have few extra of this caps?

These caps are semi important. They make a low pass filter, and by changing the caps to a larger size, you lower the knee of the filter, which means you will remove the higher frequency content of the analog signal. Les high frequency data means a slower response time to changes in the analog signal. This is commonly an OK thing, but if you are using that channel for something like alternator control, TPS or MAP, then you may not like the results. I did put this filter knee a bit high, and we recently dropped the knee for several of these circuits.

Basically, it's probably fine, but it might be a bit slow to respond.

matt · Post by **matt** » Sat Jan 28, 2017 11:22 am

hmm.. i ordered few 0.01 uf, the correct value for those capacitors.
one more thing, from what i understand vr sensor produced ac signal, and hall sensor produced dc signal. am i right?

Post by **AndreyB** » Sat Jan 28, 2017 12:10 pm

mattsabun wrote:i understand vr sensor produced ac signal, and hall sensor produced dc signal. am i right?

Probably no but you maybe mean the right thing but wrong terms?

VR signal is more "analog" as a curve and Hall is more on/off "digital" signal, but that's probably not AC or DC.

matt · Post by **matt** » Sat Jan 28, 2017 12:56 pm

so, if it possible if hall signal route via vr conditioner board?
j just want to know to improve my understanding.

Post by **AndreyB** » Sat Jan 28, 2017 12:58 pm

yes

http://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger
http://rusefi.com/wiki/index.php?title=Manual:Hardware:Frankenso:Hall_input
http://rusefi.com/wiki/index.php?title=Manual:Hardware:Frankenso:VR_input

matt · Post by **matt** » Wed Feb 01, 2017 1:40 pm

i can't find where is PC6 and PA5 pin which i need to cam and crank signal. it is need to be solder to directly to it's pin?

i notice if i jumper at jp211 and jp212, cam/crank signal will be at PC5 and PA7 which it none selectable at tunerstudio.

Post by **AndreyB** » Wed Feb 01, 2017 2:11 pm

Pc6 is right next to pc5, i bet the pa5 is close to pa7

I would expect existing jumpers to go to pc6 and pa5.

Do you want to clean this board?

matt · Post by **matt** » Wed Feb 01, 2017 2:28 pm

i mean PA5 and PC6 i can find it"s pin. just searching around if got specific hole that connect to those pin.

Post by **AndreyB** » Wed Feb 01, 2017 2:32 pm

Pc6 is a pin on the 25x2 header which connects to brain board. There is a trace going to pc6 - please trace this on board or schematics to the hole which is one sidr of the jumper. That hole is what you add your wire to. The wire would run from adc outputs 9 and 11 which also has holes provisioned. I can make a picture on Saturday.

matt · Post by **matt** » Wed Feb 01, 2017 2:50 pm

ok, got it. pc6 and pa5 goes to jp04 and jp05.

matt · Post by **matt** » Thu Feb 02, 2017 12:07 am

ok. got rpm sync. i wired cam angle (cam+crank) sensor to inp 9 and 11. tunerstudio is set to 4g63 trigger. cas is rotate by finger so max rpm i got around 198-230. but while i playing around with IO pin for injector, tunerstudio show fatal error.

any good running msq for 4g63/miata?

Post by **AndreyB** » Thu Feb 02, 2017 12:10 am

can you please post a nice picture of these jumper wires on the board? want to use as reference picture for this setup.

set engine_type 47 or set engine_type 41 set 1.8 and 1.6 defaults

Post by **AndreyB** » Thu Feb 02, 2017 12:32 am

mattsabun wrote:but while i playing around with IO pin for injector, tunerstudio show fatal error.

did you connect console? what was the error?

matt · Post by **matt** » Thu Feb 02, 2017 12:40 am

where to set engine_type 47 or set engine_type 41? did you mean in Tunerstudio?

i can get a picture once i arrive home, maybe 1 or 2 hour later.

Post by **AndreyB** » Thu Feb 02, 2017 12:41 am

No, these are commands in rusEfi console. You start console, you type command and press the button to send the command

matt · Post by **matt** » Thu Feb 02, 2017 12:46 am

ahh.. i do not use the console. i just wired mitsubishi cam angle sensor directly to rusefi board.
and cas are rotate by finger, i just to test whether got rpm sync or not.

Post by **AndreyB** » Thu Feb 02, 2017 1:29 am

rusefi_console.exe is really helpful while starting engine for the first few times, less needed later.

matt · Post by **matt** » Thu Feb 02, 2017 1:49 am

picture attach.

Post by **AndreyB** » Thu Feb 02, 2017 1:54 am

Thank you! This is now http://rusefi.com/images/Frankenso/frankenso_op_amp_hall_input.jpg

matt · Post by **matt** » Thu Feb 02, 2017 2:57 pm

all 4 led for injector blink in sequence, so i assume circuit for injector channel is ok.
next thing is ignition channel. i can't see any led blink. what is actual setting in tunerstudio?
i am using toyota yaris coil on plug. from my poor memory (4 years ago while playing with ms2), i set inverted-dwell 2.5ms and result a burn coil.

rusefi.com

[rusEfi] hello all - Mitsubishi #31

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.

Re: hello all.