When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Yeah, while pretty cool for sure, the stuff you're talking about would only really be relevant for a proper race team/racer, or someone super nerdy doing some really out of the box things......like you
MS could probably support fuel pressure failsafe and whatnot
clearly no UAT went into developing that application.
If you've never had the pleasure of AEMPro, or Hydra 2.5/2.6, or god forbid WARI, then sure, but they make ELConsole/InfinityTuner look downright usable
...would only really be relevant for a proper race team/racer, or someone super nerdy doing some really out of the box things......like you
I bet that a lot of OEMs do it. It is true that most people want plug and play. But I bet if Miata + Infinity was well documented, more people would do it.
One thing I actually need to get done is to get the VVT trigger pattern added. Currently one of the limitations of Infinity is that it offers little configuration for trigger patterns. And its a bit retarded. https://enginelab.net/documentation/...escription_EAL
I bet that a lot of OEMs do it. It is true that most people want plug and play. But I bet if Miata + Infinity was well documented, more people would do it.
One thing I actually need to get done is to get the VVT trigger pattern added. Currently one of the limitations of Infinity is that it offers little configuration for trigger patterns. And its a bit retarded. https://enginelab.net/documentation/...escription_EAL
MS is like that. Thats now my only complaint of the squirt now that you can buy the pro with real connectors on it. That you cant just define the ******* triggers like an adult, you need daddy DIYat to hold your hand.
MS is like that. Thats now my only complaint of the squirt now that you can buy the pro with real connectors on it. That you cant just define the ******* triggers like an adult, you need daddy DIYat to hold your hand.
On the contrary, if you really are an adult, with the MS you can code your own engine decoder because you have the source, like I have done for many different engines.
If you've never had the pleasure of AEMPro, or Hydra 2.5/2.6, or god forbid WARI, then sure, but they make ELConsole/InfinityTuner look downright usable
I've played in Hyrda. My favorite part was scrolling to tune the fuel map. runner up was having to turn off the car to load changes to a tune.
On the contrary, if you really are an adult, with the MS you can code your own engine decoder because you have the source, like I have done for many different engines.
I looked at the MS code, it's complete spaghetti code. Of course you can change it, but I'd rather not deal with it.
On the contrary, if you really are an adult, with the MS you can code your own engine decoder because you have the source, like I have done for many different engines.
I've been down this path with EL/AEM stuff before. EL is a blank slate. When you buy their ECU, you get a box and nothing else. And actually, all the ECU's are manufactured by AEM - EL doesn't manufacture their hardware. They just resell what AEM makes.
The firmware doesn't do anything - it's the models that actually make it function like an engine management system or whatever else you want to develop it as. It's great that you've unlocked "the secret" that all the boxes are the same but unless you develop your own models, you can't make use of any extra I/O. So you're going to lose all the functionality of the Infinity system and everything that makes it awesome. You better be pretty bad *** at system controls development if you think you're going to make your own controls models.
AEM has done a pretty good job of locking things down. Like you've found, their wizard is just an in-between for the user and things working in the background. The wizard is actually AEM-specific and it's not a function of EL but it's what streamlines setting up and running the models. If you create new models, you won't be able to use the AEM wizard but if you're able to make your own models, I guess you can probably also make your own wizard but that's a lot of work. If you ask me, you've delving into something that 98% of average EMS users don't and won't care about. The 2% of guys like us that can and do make their own controls stuff might be interested in this, but a $3000 development box is a tough pill to swallow for cheap *** Miata guys. What is it that you think you're gaining doing all this? The EL documentation is to support model development and has nothing to do with actually running an engine. AEM built all the models that actually make the EL system an engine management system and their documentation is written so that end users can use it as an EMS, not develop models. AEM doesn't sell a dev box - that's EL business. So you're basically taking all the engineering work that AEM put into the system and throwing it out the window. Sounds like a great place to start.
To be honest, you're not really uncovering anything new. The EL site has been up forever and so has their documentation. All anyone has had to do is find it and read it.
I've watched engines kill themselves over a bug in the Infinity, which to my knowledge, is still unresolved. There's another bug that causes the ECU to lockup, and because the ECU also has battery power on it, you need to disconnect the battery for it to recover. A significant feature of the ECU only works if you connect it to a hardcoded input. Another significant feature (much needed in the drag racing scene) would randomly completely shutdown one or two cylinders on a 5+ cylinder engine, and had gone unresolved for 4 years.
What bug has been killing engines? I think they had some problems with power sequencing in some cases a while back but I use Infinity a lot and haven't had any issues at all. I'm also interested in this other unresolved bug that shuts down cylinders on engines with 5 or more cylinders. My 1000+hp 2JZ doesn't have that problem.
Also, the AEM support stuff are pretty pathetic. I was once called in to solve a non-starting car (it was on a freshly installed AEM EMS-4). The car would not get initial sync on a 60-2 trigger wheel. It would calculate RPM every now and then but it would not get a constant sync. For giggles, I brought a Universal MS3 in, connected power, ground and signal. It would also not sync. I watched the composite log, and measure 59 teeth instead of 58. I counted at least two more times, 59 every time. So I entered 60-1 in the TS settings, and sure enough, it synced perfectly. The AEM tuner emailed AEM, and - you better believe this - this is their answer (to the best of my memory as it was couple of years ago):
This can't be a 60-1 wheel because we have never seen one before. There is probably some other error, and the MS ECU is only able to sync up with a 60-1 setting because there are too many teeth and the MS has a slow processor, so entering more teeth somehow compensates for that.
No solution was given or any idea as to why the EMS-4 is not syncing. The customer ended up removing a tooth as the EMS-4 doesn't have configurable generic missing tooth wheel settings.
I agree with AEM - there's no such thing as a 60-1 wheel. You had a 60-2 wheel but you had the polarity of the crank sensor wrong so it wasn't detecting the missing teeth correctly which isn't an uncommon problem. So you got lucky and were able to make a BS "60-1" trigger in MS. If you had the sensor polarity right, it would have worked fine. Instead, you had to basically lie and tell the MS it was a 60-1 in order to get your incorrectly setup 60-2 to work. How is that AEM's fault?
I think that the hardware is the best of any other ECU, but I am not happy with AEM approach of locking the model down, hardcoding inputs/outputs, restricting to Bosch 4.2 LSU and generally sandbagging the whole thing. I see a lot of potential in the hardware and I want to take advantage of it.
Everything you said is correct. I am starting from scratch. I do have to write a complete model from nothing. Luckly I am fairly competent with software (it's my profession) and I am good at figuring out things. I think people will follow down this path once I lay the ground work. The model will be difficult but it is possible to get... inspiration from the AEM models. I don't want to copy too many things because it is their property after all. Worst case scenario I will fail at making my own model and will run AEM models/firmware.
The $3000 number that is thrown around is moot. The hardware is same, so its ~2300 for Infinty 7 or ~1250 for Infinity 5. The approach I'm taking should be applicable to both. At 1250 Infinity 5 is pretty competitive, especially if you think about what's possible.
Why I chose this route
I love the hardware, but not the software
I have a lot of ideas for things I want to do. Like DBW based traction control. PWM fuel pump control. Knock detection that works better than Megasquirt. Maybe something with turbo speed and VVT.
I like to play with new things. This car has long passed any logic and reason and is now firmly in the "look what I can do" realm.
What I want to accomplish
Pave the way for AEM/EngineLab on Miata platform
Write some helpful tools for EL Console
Learn how the EFI, O2 sensor, knock sensing, DBW and traction control actually work
12-08-2016, 01:53 PM
0
