ME221 and FM221 rip off DRAMA....NOW WITH 60% less RIP Hydra?
#101
The manual was written by myself - The pic and 10 words or so of text were taken from sources on the web for that connector - I added to it to label the correct wire colours and also what to do with the other 5 pin versions - apologies, I will tomorrow change the picture to one taken in house - and to be honest its one of those things when compiling the manual that I just never got round to updating.... The picture was obtained from a google search though, not looking through your manuals, it may of linked back there however. In fact I think it was actually posted originally by an ME221 user on a forum - edit found it...Iat Sensor Reading Me221 - Forced Induction & N/A Power Mods - MX5Nutz Forum
As to what I may or may not of copied with rights or not to do so, the story is very long and old, and in short I created the V4 based ECU based on the V2.5, and was given permission by that very same person whom had a lincense to do so, who I believe was called Lance, but I really don't remember - its old news, very old news, and I soon realised MS with its 16bit power and architecture just could never do what an ECU I wanted to do could (i.e remappable IO/tables etc) this was actually documented by me in a video when we first starteded to explore the methodology of the ME22 as a retailable system after we finished the ME442 race ECU here:
Suffice it to say this 'modifyiability' isnt open to the public MEITE software - we need an easier way of letting users 'flow chart; the process chains visually, but it can be glanced at by the way the tables are named and pointers etc work inside the ECU...
As to what I may or may not of copied with rights or not to do so, the story is very long and old, and in short I created the V4 based ECU based on the V2.5, and was given permission by that very same person whom had a lincense to do so, who I believe was called Lance, but I really don't remember - its old news, very old news, and I soon realised MS with its 16bit power and architecture just could never do what an ECU I wanted to do could (i.e remappable IO/tables etc) this was actually documented by me in a video when we first starteded to explore the methodology of the ME22 as a retailable system after we finished the ME442 race ECU here:
Suffice it to say this 'modifyiability' isnt open to the public MEITE software - we need an easier way of letting users 'flow chart; the process chains visually, but it can be glanced at by the way the tables are named and pointers etc work inside the ECU...
#103
I totally get that, and I am not even remotely trying to claim anyone involved with MS invented speed-density. It's just a little ridiculous to claim that the fueling algorithm is totally different when basically all standalones offer the same algorithms (which is a good thing).
#106
SADFab Destructive Testing Engineer
iTrader: (5)
Join Date: Apr 2014
Location: Beaverton, USA
Posts: 18,642
Total Cats: 1,866
Looking at how the table is built it looks like it interpolates past the end of the table. So you need both rows the same at the end, or else you have no idea what is happening.
#107
Supporting Vendor
iTrader: (33)
Join Date: Jul 2006
Location: atlanta-ish
Posts: 12,659
Total Cats: 134
The manual was written by myself - The pic and 10 words or so of text were taken from sources on the web for that connector - I added to it to label the correct wire colours and also what to do with the other 5 pin versions - apologies, I will tomorrow change the picture to one taken in house - and to be honest its one of those things when compiling the manual that I just never got round to updating.... The picture was obtained from a google search though, not looking through your manuals, it may of linked back there however. In fact I think it was actually posted originally by an ME221 user on a forum - edit found it...Iat Sensor Reading Me221 - Forced Induction & N/A Power Mods - MX5Nutz Forum
Do you really expect me to believe that you didn't "quite innocently" rip us off in other places? If you'll do it where it's obvious, you'll do it where it's not.
#108
Thats an ignition map - and we found it to work very well on the dyno - you can see we improved upon it.... We were actually supplied these numbers by G19 Engineering in the UK for our initial maps.... take it up with them we were not to know the source, nor did we care... its a table we later got RIGHT on our rolling road here, hence the actual data differs.... Hopefully our VE tables dont look like VE tables, or our engine CC doesent match as well.... come on guys, this is just getting a little silly now...
Joe don't comment on mapping buddy, we saw your skills in action when we were in Colarado with you....
Joe don't comment on mapping buddy, we saw your skills in action when we were in Colarado with you....
#109
So first it was accidental use of a photo. And then it was the picture and "10 words or so", but clearly you copied and pasted the entire text from my manual into yours. Dude, you have a track record of ripping us off, and here you are, ripping us off again.
Do you really expect me to believe that you didn't "quite innocently" rip us off in other places? If you'll do it where it's obvious, you'll do it where it's not.
Do you really expect me to believe that you didn't "quite innocently" rip us off in other places? If you'll do it where it's obvious, you'll do it where it's not.
And MS has a track record of ripping off small business and tightening the noose which is EXACTLY what they did to me 10 years ago. I apprently 'reipped off' MS before there was even licensing, and once I was informed I offered to pay licensing, then I decided to try my own way when MS said no, and I stopped selling it, and started work on the NODIZ I had the same agro from megajolt fans about that, however, megajolt needs EDIS, NODIZ has the drivers built in, so completely different in terms of complexity (though some didnt understand that comupting trigger patterns and telling an EDIS when to fire are leagues apart) etc, but still, the same old crap from the same old people...
I have had enough of defending myself to a competitor - you have a nice little piece of historical leverage you can use over and over again, even if the timelines and processes are innacurate - its so long ago I don't even have the emails from it anymore.
I don't want to waste anymore time on this - both myself and Alex wish you all well, and we will continue to work on our ECU - now all of the UK tuners are using it, and rightly saying how much easier it is to tune than MS, how much more repeatable, reliable etc it is, that is worth more of a win for me, the product, and the company, than any comment on a forum every will be...
Best wishes,
Matt
#111
I totally get that, and I am not even remotely trying to claim anyone involved with MS invented speed-density. It's just a little ridiculous to claim that the fueling algorithm is totally different when basically all standalones offer the same algorithms (which is a good thing).
--Ian
#112
--Ian
#113
Originally Posted by afm
It's just a little ridiculous to claim that the fueling algorithm is totally different when basically all standalones offer the same algorithms (which is a good thing).
I don't know where you're going with this.
#115
Currently Active Users Viewing This Thread: 41 (13 members and 28 guests)
18psi*, yossi126, Savington, EO2K+, afm, codrus, aidandj*, Lincoln Logs, ManiacLachy, Reverant, SchmoozerJoe, Keith@FM, eddyc49
18psi*, yossi126, Savington, EO2K+, afm, codrus, aidandj*, Lincoln Logs, ManiacLachy, Reverant, SchmoozerJoe, Keith@FM, eddyc49