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... |
*chuckles*
|
Originally Posted by codrus
(Post 1400262)
I'm pretty sure Ford and Honda were doing speed-density before megasquirt was...
--Ian |
|
MOAR POWAH.
They never did have a good explanation for not taking advantage of their 16x16 tables... guess it was too hard to develop 16 unique breakpoints. |
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.
|
Originally Posted by Matt Thorne
(Post 1400263)
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. |
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.... |
Originally Posted by Ben
(Post 1400271)
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. 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 |
Hmmm. I guess its not ripping someone off if a third party gives you the data...
Does copyright work like that? IANAL. |
Originally Posted by afm
(Post 1400265)
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 |
Originally Posted by aidandj
(Post 1400277)
Hmmm. I guess its not ripping someone off if a third party gives you the data...
Does copyright work like that? IANAL. --Ian |
Originally Posted by codrus
(Post 1400278)
If it's a from-scratch software implementation on a from-scratch hardware board of an algorithm that isn't protected by a patent, then it's "totally different" in every way that matters.
--Ian
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. |
|
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 |
:love:
|
HI KEITH!!!
|
So what's up?
|
I get a notification every time this thread is updated. Silly me clicked on it.
|
You know you love this thread :)
|
All times are GMT -4. The time now is 01:25 AM. |
© 2024 MH Sub I, LLC dba Internet Brands