Megasquirt Ecu
08-13-2005, 12:42 PM
#31
Senior Member
Join Date: May 2002
Location: California
Posts: 22,465
[quote name='mazdaspeed7' date='Jan 6 2005, 06:01 PM']I know. I think its almost something that needs to be designed into the EMS to deal with it.
Even the decel fuel cut wasnt helping on the MS, b/c its time based. And on top of that, any tuning that would make the car smoother in that low rpm range would cause a big stumble on WOT shifts.
[/quote]
as an aside, the stock ecus do a staged fuel cut, sometimes its only cutting 1 rotor on decel.
Even the decel fuel cut wasnt helping on the MS, b/c its time based. And on top of that, any tuning that would make the car smoother in that low rpm range would cause a big stumble on WOT shifts.
[snapback]571021[/snapback]
[/quote]
as an aside, the stock ecus do a staged fuel cut, sometimes its only cutting 1 rotor on decel.
08-13-2005, 04:42 PM
#32
Senior Member
Join Date: Oct 2003
Location: Canada
Posts: 3,502
[quote name='RETed' date='Aug 13 2005, 03:46 AM']Is there anyone that's contributing to the open-source development of the MS for 13B applications on here???
-Ted
http://fc3spro.com/
[/quote]
If anyone wants copies of fuel maps for different N/A setups, all they have to do is PM me..
That's all I have to offer though, www.msefi.com has plenty of people with alot more to offer, and who are actively making code for applications beyond what I need. The parameters and settings for what I use are more than sufficient, I just need to learn how to use it better... :P
-Ted
http://fc3spro.com/
[snapback]748130[/snapback]
[/quote]
If anyone wants copies of fuel maps for different N/A setups, all they have to do is PM me..
That's all I have to offer though, www.msefi.com has plenty of people with alot more to offer, and who are actively making code for applications beyond what I need. The parameters and settings for what I use are more than sufficient, I just need to learn how to use it better... :P
08-13-2005, 04:44 PM
#33
Senior Member
Join Date: Oct 2003
Location: Canada
Posts: 3,502
And yes the people at www.msefi.com have 13B specific stuff..
There are a handful of people here with maps or code that is really damn useful from anything like a stock port 13B with a dizzy to a big street port motor with Ford EDIS modules for ingition control.. All been done. And all taken care of with the MS box.
There are a handful of people here with maps or code that is really damn useful from anything like a stock port 13B with a dizzy to a big street port motor with Ford EDIS modules for ingition control.. All been done. And all taken care of with the MS box.
08-22-2005, 09:48 PM
#35
Junior Member
Join Date: Dec 2004
Posts: 5
I'm starting a MS project for my car. While the stock FC ECU does work, it has some problems I've not been able to solve. For one, no matter what I've done, the freakin hesiation is there, been through every thread and fix. Got a little worse when I went to Rtek 1.7. Go look over in the FD forums and you'll see they have similar problems.
Second problem is the 1500-3000 rpm range can run a bit rough only in the 25-40mph range--must be load/AFM related. Yea I could probably get an SAFC and smooth things out a little, but for a little more I'll have a full standalone system.
I want to learn more about electronics and am excited about the project. I like the open source side of the project and would like to support it somehow in the future. These forums are a great way to work together and share information. Funny how I see many of the same names here as on the msefi and rx7club.
You guys need to remember Ted is doing this for a business so he needs a company that will back products and get things fixed in a timely fashion. He has my full respect. I don't think he's really bashing MS, just pointing out some truthful points.
Oh and Ted, I'd rather have Linux take over the world instead of Microsoft--at least the world would then have something to say about future development. And one FYI about Linux, NASA is putting Linux on nearly all of the shuttle flight design and mission control workstations--that tells you something about Linux.
Go Megasquirt!!!
Second problem is the 1500-3000 rpm range can run a bit rough only in the 25-40mph range--must be load/AFM related. Yea I could probably get an SAFC and smooth things out a little, but for a little more I'll have a full standalone system.
I want to learn more about electronics and am excited about the project. I like the open source side of the project and would like to support it somehow in the future. These forums are a great way to work together and share information. Funny how I see many of the same names here as on the msefi and rx7club.
You guys need to remember Ted is doing this for a business so he needs a company that will back products and get things fixed in a timely fashion. He has my full respect. I don't think he's really bashing MS, just pointing out some truthful points.
Oh and Ted, I'd rather have Linux take over the world instead of Microsoft--at least the world would then have something to say about future development. And one FYI about Linux, NASA is putting Linux on nearly all of the shuttle flight design and mission control workstations--that tells you something about Linux.
Go Megasquirt!!!
08-28-2005, 05:00 PM
#36
Senior Member
Join Date: Dec 2003
Posts: 162
[quote name='RETed' date='Aug 12 2005, 11:46 PM']As of this moment, the MS is not in the same category as the Microtech / Haltech / Autronic.
I dunno why people like to compare them like apples-to-apples. :P
What we need is someone to start offering MS kits for the RX-7's and see what the pricing comes out to be???
Some eBay seller is selling them for other cars, and they are asking $500 for it!
I think the price is going to push closer to $1,000 once you get everything squared away...
Right now, it's all talk.
I understand your point about having it open-source and the capabilites are limitless, but the fact of the matter is...there is no such thing, especially with electronics.
You might think you can add a bazillion things to it, but there comes a point where the uP gets too loaded to handle all that processing...unless you go faster uP, which means more money.
I'm NOT knocking the MS - get that straight.
I'm just waiting on the sidelines to see if MS can develop into something what all of you guys are bragging about.
There are very few people that are doing the "grunt work in the trenches"; I've done that kinda stuff before, and it's tedious and boring.
Is there anyone that's contributing to the open-source development of the MS for 13B applications on here???
-Ted
http://fc3spro.com/
[/quote]
Well, starting from the top, a list of specific limitations would be interesting. With the 12by12 tables that MS offers, along with user adjustable table vertices I can't personally see that being a limitation. Happy to see proof that a fixed 16by 16 table would be better or that a larger table isn't just a big pain in the rear to tune.
As to your point about processing limitations. Yes there are limits, however the roadmap for MS includes CANbus support, with tests currently ongoing. This will allow processing and IO to be distributed. Won't give you the sheer grunt of the latest MOTEC units, but that was tried with the EFI332 years ago and was just found too difficult for the average user to handle. So Coil per plug, sequential injection, flybywire throttle control, native use of wideband sensing (note native use, not just basic PID autotune) and a few others are on the cards in the next 12 months, just not ABS/ESP and their ilk. But that's in the future. Right now there are MIPs and memory to burn with the and people working on porting the 8bit rotary specific code onto the 16bit processor. It'll do everything that 90% of users want with the current board and CPU.
As to offering RX7 specific kits, I'm not sure that is needed right now. Sure someone can offer loom services for a particular generation, but MS is not about taking on APeXI at its own game.
As for 'just talk' MS is running on a number of 12As and 13Bs of all flavours. There is a community forming where people can exchange ideas, test out new concepts and move the whole game forwards. Enthusiasts, all doing it for fun and to help each other out.
So come on. Give me a feature list that you would want in an ECU to put in one of your cars and we can put a gap analysis in place. In 12 months time we can do it again. I'm sure you can manage objective once a year?
I dunno why people like to compare them like apples-to-apples. :P
What we need is someone to start offering MS kits for the RX-7's and see what the pricing comes out to be???
Some eBay seller is selling them for other cars, and they are asking $500 for it!
I think the price is going to push closer to $1,000 once you get everything squared away...
Right now, it's all talk.
I understand your point about having it open-source and the capabilites are limitless, but the fact of the matter is...there is no such thing, especially with electronics.
You might think you can add a bazillion things to it, but there comes a point where the uP gets too loaded to handle all that processing...unless you go faster uP, which means more money.
I'm NOT knocking the MS - get that straight.
I'm just waiting on the sidelines to see if MS can develop into something what all of you guys are bragging about.
There are very few people that are doing the "grunt work in the trenches"; I've done that kinda stuff before, and it's tedious and boring.
Is there anyone that's contributing to the open-source development of the MS for 13B applications on here???
-Ted
http://fc3spro.com/
[snapback]748130[/snapback]
[/quote]
Well, starting from the top, a list of specific limitations would be interesting. With the 12by12 tables that MS offers, along with user adjustable table vertices I can't personally see that being a limitation. Happy to see proof that a fixed 16by 16 table would be better or that a larger table isn't just a big pain in the rear to tune.
As to your point about processing limitations. Yes there are limits, however the roadmap for MS includes CANbus support, with tests currently ongoing. This will allow processing and IO to be distributed. Won't give you the sheer grunt of the latest MOTEC units, but that was tried with the EFI332 years ago and was just found too difficult for the average user to handle. So Coil per plug, sequential injection, flybywire throttle control, native use of wideband sensing (note native use, not just basic PID autotune) and a few others are on the cards in the next 12 months, just not ABS/ESP and their ilk. But that's in the future. Right now there are MIPs and memory to burn with the and people working on porting the 8bit rotary specific code onto the 16bit processor. It'll do everything that 90% of users want with the current board and CPU.
As to offering RX7 specific kits, I'm not sure that is needed right now. Sure someone can offer loom services for a particular generation, but MS is not about taking on APeXI at its own game.
As for 'just talk' MS is running on a number of 12As and 13Bs of all flavours. There is a community forming where people can exchange ideas, test out new concepts and move the whole game forwards. Enthusiasts, all doing it for fun and to help each other out.
So come on. Give me a feature list that you would want in an ECU to put in one of your cars and we can put a gap analysis in place. In 12 months time we can do it again. I'm sure you can manage objective once a year?
Thread
Thread Starter
Forum
Replies
Last Post
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)