The MegaSquirt Project has experienced explosive growth other the years, with hundreds of new MS installations occurring every week - a phenomenal success! MegaSquirt has been successfully used in all aspects of Internal Combustion engine applications including R&D, Industry, Race, and Research. The MS project has transformed itself from a simple R&D project into a full-featured mature engine control system. To reflect this the support structure has also changed to meet the needs of MegaSquirt Users.
Moving forward, the R&D forums for MegaSquirt project are in a read-only mode - no new forum posts are accepted.
However the forums will remain available for view, they still contain a wealth of information on how MegaSquirt works, how it is installed and used. Feel free to search the forums for information, facts, and overview.While the R&D forum traffic has slowed in recent years, this is not at all a reflection of Megasquirt users, which continue to grow year after year. What has changed is that the method of MegaSquirt support today has rapidly moved to Facebook, this is where the vast majority of interaction is happening now. For those not on Facebook the msextra forums is another place for product support. Finally, for product selection assistance, all of the MegaSquirt vendors are there to help you select a system, along with all of the required pieces to make it complete.
Forum for discussing how to install MicroSquirt(TM), choose and troubleshoot sensors, wiring, and communications for MicroSquirt (TM) and MicroSquirt Module(TM).
Forum rules
Read the manual to see if your question is answered there before posting. If you have questions about MS1/Extra or MS2/Extra or other non-B&G code configuration or tuning, please post them at http://www.msextra.com The full forum rules are here: Forum Rules, be sure to read them all regularly.
I am a member of the FSAE team for Temple University and the engine we are using is from a 2007 Yamaha Phazer. We first tried to use the stock map sensors but they did not seem to work. We then went to autozone and purchased a duralast map sensor from a 2005 Cobalt SS which uses a gm 2 bar sensor so we figured they would be the same. Now when we got back and plugged in the values(which we found online) to calibrate it, we get map readings for around 70-80 Kpa. It definitely runs a lot better with this map sensor when compared to the stock ones, but the it idles very high and keeps on reving higher. I was just wondering if we did something wrong with the calibration or do you think this duralast map sensor wont work because its not a true gm 2 bar map sensor?
What we plan on doing now is buying a gm 3 bar from online, but just wanted to hear some peoples input before going ahead and doing this. Thanks
The MAP sensor shouldn't make that much difference, and I would think the stock one was a 1bar type, as the engine isn't turbocharged. AFAIK, fitting a 2bar one isn't detrimental, but I don't know whether the sensitivity is different without trolling spec sheets.
70-80 kPa doesn't seem too high for a high revving modern twin cylinder. I am running around 70 kPa at 900-1000 rpm (idle) on a 1990s YZF1000 engine, but your advance settings will affect this. Single cylinder bikes have spiky MAP transitions, and your twin will be no different, but you say it is better with this 2 bar sensor, and keeps on revving higher...is that just at idle? Is this as the bike warms up? If your ignition or fuel values vary with the MAP fluctuations at idle or your WUE is not set up you might see this. Also, is there some sort of mechanical warm up enrichment on the throttle body?
I think it is likely to be a settings issue, so why don't you datalog the behaviour and post a .msq, that way we can see what is happening.
Sorry I wasn't that clear when explaining it, but the map sensor reads around 80kpa with out the engine running when we enter the correct values in from online. When we started it, it would only idle with the computer unplugged, and it seemed to be idling around 3k. We then tried messing the with map values so it would read 100Kpa when it wasn't running, and this caused the engine to sky rocket up to 5k when we started it. The map values were almost down to 30kpa when it reached 5k before we shut it down.
slobra96 wrote:Sorry I wasn't that clear when explaining it, but the map sensor reads around 80kpa with out the engine running
OK, that could happen if you were at high altitude, but have you got the map sensor wired correctly. Obviously you have some calibration values for the MAP sensor, OEM or otherwise and you have put these in your table. 30 kPa does seem a little low for a motorcycle engine idling, you would get this on a closed throttle on overrun, but I wouldn't expect to see this on a normal intake.
24c - he says he's getting 80kPa with the engine OFF. If this is the Temple University in Philadelphia (39 fasl), it SHOULD be reading a lot closer to 100kPa.
Either you have some significant calibration issues, or your Vcc to the sensor is way off.
Thanks for that dontz125, I realised second post he said engine NOT running, but had no idea where Temple University is, being a Brit, so I was just being polite with the high altitude. I reckon it's a settings or wiring issue too.
It's worth noting that the MAP sensor reading wrong (or any other sensor problems really) will not cause excessive rpm. All those sort of problems will reduce the rpm. The only thing that can cause excess rpm is a vacuum leak (i.e. too much air entering the engine).
This can be a missing/misaligned gasket, a missing vacuum fitting, an IAC stuck open, a throttle stop mis-adjusted, etc., but somehow the engine is getting too much air. So fix that first before doing anything else.
Thanks guys, were gonna try calibrating it ourselves tomorrow and try it again. I will update you guys tomorrow, thanks for all your help. And yea Temple University is in Philadelphia, PA hahah.
We calibrated the map today our selves and it works like a charm. We also figured out why it was reving up so high, and it was because of the IAC being open all the way. Thanks for all your help, Ill let you know what other problems we run into.