Problems with VR sensors and ms3/ms3x

[bmw5002]

james, could you enlighten me on what the bit 7/8 mean with the rc firmware? in the log i see bit 7 going high everytime i get the pw spike... read somewhere that its mapdot, but the mapdot line in the log is basically steady state at that time...

[bmw5002]

another strange issue just cropped up. the wideband input is reading .10 or 25.4, just flips between the two. i checked the pin on the connector for the ms and it is reading the proper voltage. is something off with the configuration or something? megalog is showing the same thing.

[muythaibxr]

Bits 7 and 8 are MAPdot accel/decel.

The log probably just isn't fast enough to catch the spikes.

Try increasing the MAPdot threshold.

Ken

[bmw5002]

Bits 7 and 8 are MAPdot accel/decel.

The log probably just isn't fast enough to catch the spikes.

Try increasing the MAPdot threshold.

Ken

So it would catch the pw spike but not the mapdot spike?
EDIT: I figured out how to rescale the mapdot and tpsdot range to better see the spikes

Also any ideas on the wideband input? Major dealbreaker right there. It was working fine the other day...

[jsmcortina]

another strange issue just cropped up. the wideband input is reading .10 or 25.4, just flips between the two. i checked the pin on the connector for the ms and it is reading the proper voltage. is something off with the configuration or something? megalog is showing the same thing.

If you enable an ego volts gauge does it match the input?
Did you re-calibrate your AFR table after loading the firmware?

James

[bmw5002]

another strange issue just cropped up. the wideband input is reading .10 or 25.4, just flips between the two. i checked the pin on the connector for the ms and it is reading the proper voltage. is something off with the configuration or something? megalog is showing the same thing.

If you enable an ego volts gauge does it match the input?
Did you re-calibrate your AFR table after loading the firmware?

James

im not sure how to get ego volts. i dont see that anywhere in the list when i right click a gauge to switch it. i just recalibrated the afr table and still same issue. but the afr input was working just fine as of yesterday. today, its all out of whack. i haven't changed anything since.

[bmw5002]

ook so i ironed out most of the injector pw spikes by tweaking the accel enrich tables.
the two remaining MAJOR issues are the sync loss and the wideband input.
can anyone tell me if the ms3 is supposed to shut down the engine completely after a sync loss? the issue has happened a few more times. while driving, a sync loss will occur and even coasting in gear and hitting the accelerator will not bring the engine back to life. it backfires every time i hit the accelerator. only cure is to turn off the ignition then restart. james suggested the connection to the sensor may be going out intermittently however i find it strange that restarting works every time. seems to me that an intermittent connection that happens to work again when i restart the car may just be random enough to reconnect itself when i am coasting to a stop in gear or maybe stay disconnected when i am trying the restart it. what i am saying is that it seems like a software error. while the sync loss may not necessarily be a software error, the subsequent power loss until restart may be. on a side note, this car ran 100% fine with never a hiccup on the stock ecu before the megasquirt was installed. no wiring involving the cam and crank sensors was modified during the megasquirt install. so it may be that the vr conditioning circuits in the megasquirt do not work as well with these sensors as the stock circuit does. or maybe the 6/7 code needs to be tweaked? im curious as to how many others are running this type of setup on the megasquirt with no sync loss. i saw one or two on msruns, however they were using ms2/extra with external vr conditioner circuits.

[jsmcortina]

You posted composite logs showing a completely missing crank signal. It isn't going to work like that and you need to fix it.

No signal -> no rpm -> not running

James

[bmw5002]

ok well there is still the issue with my wideband input now. i cant see any a/f data in my logs and ve analyze will not work. im supposed to be hooking the turbo up this weekend and i would really like the aid of those two things. i guess ill try loading the new firmware and see if it fixes it. does that input have any conditioning circuit? or does it go right to an adc pin on the cpu? hard to believe a hardware error would crop up like that... i still am unsure of how to see direct voltage from that input.

[bmw5002]

something got corrupted in my configuration. i flashed the new firmware, choosing not to keep any settings. opened ts and the gauge is reading correctly. after the difference report showed up, i sent my tune to the controller and power-cycled, and then the gauge is back to reading wrong again. any way i can see whats messed up in the config without having to copy all my settings over to a new tune file?

[muythaibxr]

What version of TS are you using? Can you send the latest msq you are using to reproduce the problem?

Ken

[bmw5002]

What version of TS are you using? Can you send the latest msq you are using to reproduce the problem?

Ken

v0.999.7

msq is attached. please help me out. many thanks in advance. i really need to use the wideband in the next few days.

[muythaibxr]

Try upgrading to the latest 0.998.

Ken

[bmw5002]

the update function keeps telling me that i have the latest version. ill try downloading it from the site.

[muythaibxr]

I meant 0.999.8. You have to manually download it.

Ken

[bmw5002]

I meant 0.999.8. You have to manually download it.

Ken

ah ok checked the beta section of the site and found it. ill report back soon.

[bmw5002]

still having the same issue with the new ts. clearly this is some kind of bug. guess i will have to transfer everything to a new tune file? can anyone else duplicate this?

[jsmcortina]

Duplicate what?

Please step us through what we need to do to replicate what you are seeing.

James

[jsmcortina]

EGO sensor type is set to "Disabled" - it won't work like that.

James

[bmw5002]

EGO sensor type is set to "Disabled" - it won't work like that.

James

doh! i feel like such a moron. i turned it off because i didnt want closed loop control and i guess thats when the gauge stopped working. i cant tell you how much i appreciate all the help ive been getting here. really sorry to bother you with stupid questions.

well that really brings the remaining problems with my install down to one - the sync loss. i put a new connector on the crank sensor, and still the same issues. i really don't feel like this is a wiring issue. ran just fine on the stock ecu. can anyone explain to me why when looking at the composite logger, i see around 18 crank pulses per 720*? if you see the subaru timing diagram attached, also just looking at the cam and crank wheel, the crank wheel has 6 teeth so i should see 12 pulses per 720*, no?

subaru_6_7_timing_chart.gif