Viability of a Megasquirt application for FI on the renesis
#176
Originally Posted by rkostolni
Wow, Nov/Dec time huh? What is it that is going to take so long? Any way us forum members can help speed that along? Maybe donations to help pay for parts, or researching wiring diagrams, just name it if it can help get this along. I am dying to get this emanage out of control!
#177
Go Texas Longhorns!
We certainly appreciate the offers for help, the biggest issue is not so much money, but getting the MS software to read the stock ignition wheel. We are going to rig a standard 36-2 wheel up to the front of my pully and install a seperate ignition sensor to test the ignition side of things, but right now even if that works, I don't have more than my one wheel that I got form Speedsource.
We want this to be as plug and play as possible, to where all you need is the unit, a wiring harness and new coil packs. having to deal with the extra trigger sensor and trigger wheel is a complication we are trying to avoid.
Getting help to write the code would be nice, but its not as simple as just inserting lines of code here and there, you really need to understand the software. If you can help with the code (which is in assembly language) at www.msefi.com that would be great. You can see there is code there for 36-1, 36-2 and a neon trigger wheel aready in the MSnS code.
The time issue is just that, we need to some once we get everything together to test and work the kinks out. Believe me, we want this done as quickly as possible, but this is my daily driver and we have to work out our work schedules.
If anyone has any spare coil packs from a 2nd gen RX7 that would help, as well as a crank angle sensor from any Mazda car(RG, I think any of them will work right?). we would be appreciative. We will certainly take small monetary donations, but thats not required, I'm going to do this anyways for the experience.
I hope we can bring what we have working to Sevenstock in October.
We want this to be as plug and play as possible, to where all you need is the unit, a wiring harness and new coil packs. having to deal with the extra trigger sensor and trigger wheel is a complication we are trying to avoid.
Getting help to write the code would be nice, but its not as simple as just inserting lines of code here and there, you really need to understand the software. If you can help with the code (which is in assembly language) at www.msefi.com that would be great. You can see there is code there for 36-1, 36-2 and a neon trigger wheel aready in the MSnS code.
The time issue is just that, we need to some once we get everything together to test and work the kinks out. Believe me, we want this done as quickly as possible, but this is my daily driver and we have to work out our work schedules.
If anyone has any spare coil packs from a 2nd gen RX7 that would help, as well as a crank angle sensor from any Mazda car(RG, I think any of them will work right?). we would be appreciative. We will certainly take small monetary donations, but thats not required, I'm going to do this anyways for the experience.
I hope we can bring what we have working to Sevenstock in October.
#178
Originally Posted by brillo
We certainly appreciate the offers for help, the biggest issue is not so much money, but getting the MS software to read the stock ignition wheel. We are going to rig a standard 36-2 wheel up to the front of my pully and install a seperate ignition sensor to test the ignition side of things, but right now even if that works, I don't have more than my one wheel that I got form Speedsource.
We want this to be as plug and play as possible, to where all you need is the unit, a wiring harness and new coil packs. having to deal with the extra trigger sensor and trigger wheel is a complication we are trying to avoid.
Getting help to write the code would be nice, but its not as simple as just inserting lines of code here and there, you really need to understand the software. If you can help with the code (which is in assembly language) at www.msefi.com that would be great. You can see there is code there for 36-1, 36-2 and a neon trigger wheel aready in the MSnS code.
The time issue is just that, we need to some once we get everything together to test and work the kinks out. Believe me, we want this done as quickly as possible, but this is my daily driver and we have to work out our work schedules.
If anyone has any spare coil packs from a 2nd gen RX7 that would help, as well as a crank angle sensor from any Mazda car(RG, I think any of them will work right?). we would be appreciative. We will certainly take small monetary donations, but thats not required, I'm going to do this anyways for the experience.
I hope we can bring what we have working to Sevenstock in October.
We want this to be as plug and play as possible, to where all you need is the unit, a wiring harness and new coil packs. having to deal with the extra trigger sensor and trigger wheel is a complication we are trying to avoid.
Getting help to write the code would be nice, but its not as simple as just inserting lines of code here and there, you really need to understand the software. If you can help with the code (which is in assembly language) at www.msefi.com that would be great. You can see there is code there for 36-1, 36-2 and a neon trigger wheel aready in the MSnS code.
The time issue is just that, we need to some once we get everything together to test and work the kinks out. Believe me, we want this done as quickly as possible, but this is my daily driver and we have to work out our work schedules.
If anyone has any spare coil packs from a 2nd gen RX7 that would help, as well as a crank angle sensor from any Mazda car(RG, I think any of them will work right?). we would be appreciative. We will certainly take small monetary donations, but thats not required, I'm going to do this anyways for the experience.
I hope we can bring what we have working to Sevenstock in October.
Assuming that to get the timing to work is an issue of interface code for the ignition wheel, what else do you need once that's in place?
#179
Go Texas Longhorns!
We are installing the additional wheel b/c the car's ECU needs to have the stock wheel for it to be happy and not start shutting off things like the power steering (this is per speedsouce racing), and the MS can't read the stock wheel, therefore, we are using the new one to drive the ignition.
Ideally, we could write into the MS code a way to read the stock 36-2-2-2 wheel. Why Mazda decided to change from the former 36-2 wheel on the 3rd gen I have no idea. If we had the same wheel as the 3rd gen, we wouldn't have this problem.
Ideally, we could write into the MS code a way to read the stock 36-2-2-2 wheel. Why Mazda decided to change from the former 36-2 wheel on the 3rd gen I have no idea. If we had the same wheel as the 3rd gen, we wouldn't have this problem.
#180
Understood. So the MS app timing wheel interface needs to be ported to the 36-2-2-2 wheel.
Once you have that ported, do you also need to interface to the VDI & aux ports? Also, is there some way to mod the MS app so that it doesn't fry the stock coils?
Once you have that ported, do you also need to interface to the VDI & aux ports? Also, is there some way to mod the MS app so that it doesn't fry the stock coils?
#181
Go Texas Longhorns!
Originally Posted by Sapphonica
Understood. So the MS app timing wheel interface needs to be ported to the 36-2-2-2 wheel.
Once you have that ported, do you also need to interface to the VDI & aux ports? Also, is there some way to mod the MS app so that it doesn't fry the stock coils?
Once you have that ported, do you also need to interface to the VDI & aux ports? Also, is there some way to mod the MS app so that it doesn't fry the stock coils?
The coils are another issue, I don't think there is a way to run the MS in non-wasted spark mode. RG knows more about this one than me.
#183
Registered
The only reason we are going to use the additional 36-2 wheel is because the code is currently not capable of reading the 36-2-2-2 wheel. We can't just substitute the new wheel for the old one as then the factory ecu can't read it. This is why we need an additonal wheel and sensor. This is only temporary until we can find a way to get the new code written. Basically we are doing this to so we can work on getting a full tune in the car to show different results of different tuning. We are using this to bypass the waiting so we can keep making progress. Once the new code gets written and is known to work, then we'll just wire it up normally and remove the new wheel. The ultimate goal is plug and play.
The MS can only run rotary ignition in wasted spark at this time. This is because it was designed around the RX-7 ignition systems and both the 2nd and 3rd gen RX-7's use wasted spark mode. I fear that by firing the stock RX-8 leading coils twice as often will kill them. If the code can be changed to allow then to work independently of each other, that would be perfect. However that also means there needs to be a new output integrated into the MS ecu itself. For the total cost of this sytem, new coils still don't add up to a whole lot of money.
The next step at this time is to get it tuned in well as fuel only to see what kind of potential there is with this amount of control. You never know. There might be more than we think there is hidden in this motor. As we get this step down, the next will be to integrate our temporary ignition setup onto the car and then make sure it works.
The MS can only run rotary ignition in wasted spark at this time. This is because it was designed around the RX-7 ignition systems and both the 2nd and 3rd gen RX-7's use wasted spark mode. I fear that by firing the stock RX-8 leading coils twice as often will kill them. If the code can be changed to allow then to work independently of each other, that would be perfect. However that also means there needs to be a new output integrated into the MS ecu itself. For the total cost of this sytem, new coils still don't add up to a whole lot of money.
The next step at this time is to get it tuned in well as fuel only to see what kind of potential there is with this amount of control. You never know. There might be more than we think there is hidden in this motor. As we get this step down, the next will be to integrate our temporary ignition setup onto the car and then make sure it works.
#184
Registered
iTrader: (5)
Geeezz Fred your avatar is making me ill. That's alot of mass to be rocking. Now I have a moving avatar myself, thanks to BaronVonBigmeat.
Just to hyjack your thread where I know I've got your attention, I need a mock up engine to fab these brackets. Can I use an older engine or is the 8 engine different as far as the mounting points go. I need the bosses for the idler pulley and the engine lifting strap to be the same. I don't know about the other points yet. I know the manifolding will be different but I'll live with that as long as the alt is the same.
Any thoughts??
Just to hyjack your thread where I know I've got your attention, I need a mock up engine to fab these brackets. Can I use an older engine or is the 8 engine different as far as the mounting points go. I need the bosses for the idler pulley and the engine lifting strap to be the same. I don't know about the other points yet. I know the manifolding will be different but I'll live with that as long as the alt is the same.
Any thoughts??
#185
Registered
As far as I know, the mounting points for everything "should" be the same. I am not entirely sure though. Dave "guitarjunkie" should know. If you are actually attaching to the housings themselves, you will probably be fine. If you are attaching to the front cover, water pump assembly, etc, you may have problems.
#188
Administrator
is it possible to only share control of the ignition with the megasquirt or any other ems solution. i wonder if there is any system that could control it but still allow the stock pcm to react by retarding timing due to input from the knock censor?
#189
Originally Posted by zoom44
is it possible to only share control of the ignition with the megasquirt or any other ems solution. i wonder if there is any system that could control it but still allow the stock pcm to react by retarding timing due to input from the knock censor?
#190
Go Texas Longhorns!
I might help things for those interesting to log onto the MS forums in the MegasquirtnSpark section
Here: http://www.msefi.com/viewforum.php?f...7c594650b483f7
and voice your interest in getting the code written to read the RX8 trigger wheel pattern of 36-2-2-2. I don't want to bombard them to death, but there are quite a few rotary folks over there and I think if they really see the interest someone can step up and help alter the code. Please show/share your support for our project in the MS forums as well
Here: http://www.msefi.com/viewforum.php?f...7c594650b483f7
and voice your interest in getting the code written to read the RX8 trigger wheel pattern of 36-2-2-2. I don't want to bombard them to death, but there are quite a few rotary folks over there and I think if they really see the interest someone can step up and help alter the code. Please show/share your support for our project in the MS forums as well
#191
i have some experience with robotics and a motorola hc11 cpu... hmm this is pretty similar .. i was reading the megasquirt manual and ran across this line...
Many OEM and popular aftermarket EFI systems use older processor technology (like the MC68HC11 or Z80) which operate at 1 or 2 Mhz internal bus speed
interesting...
Many OEM and popular aftermarket EFI systems use older processor technology (like the MC68HC11 or Z80) which operate at 1 or 2 Mhz internal bus speed
interesting...
#192
Registered
Since the factory ecu will no longer have control of fuel or spark when all is said and done, it will also have no way of controlling a knock sensor. Fortunately I know which wire to tap into on the harness. The MS has the ability to control knock. This is easy. For a nonturbo car that is properly tuned, you won't need it.
#194
Registered
For anyone that is interested in a possible MS application for the RX-8, please create a name and password on the Megasquirt forum www.msefi.com and add your name and wish for this to become a reality. I have basically started a plea for help from those guys since they have alot of guys very familiar with writing code for MS. If I can get the backing from many others, I hope one of them will write the code for us. The thread that I started over there is:
http://www.msefi.com/viewtopic.php?t=10809
The more support I get the better. This also means the faster I can get everything else worked out and a functional plug and play harness available to everyone. At the very least I can get a complete diy on how to do it.
http://www.msefi.com/viewtopic.php?t=10809
The more support I get the better. This also means the faster I can get everything else worked out and a functional plug and play harness available to everyone. At the very least I can get a complete diy on how to do it.
#196
Posted at MS guys. Also, since I am in Katy, if you guys need anything let me know. I wouldn't mind popping by for a visit sometime just to see you guys working on it. Beers all around. GF is an ex bartender, we can set up a lil bar and set her to being busy! haha Best of luck with this endeavor.
#198
Originally Posted by olddragger
Megasquirt II is due to be released very very soon. Much more power. Would that make things any easier?
Olddragger
Olddragger
The processor is from the Motorola HCS12 family. It has plenty of excess capability and is a 16 bit machine allowing as much timing resolution as anyone can practically use. Since it is in the Motorola family the MegaSquirt embedded code will port over quite easily, however the MegaSquirt-II code has been converted to the C programming language since there is a free GNU cross-compiler for this CPU. This will make it much easier for others to customize the algorithms to meet their needs.
#200
Go Texas Longhorns!
Currently, all the "rotary specific" code is written for MS I only. I'm sur they will port it over at some point but right now, MS II won't really help us.