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.
An actual Hydra update though. Talked with a tuner who does a lot of Hydra stuff, developed a basemap for it, etc. They are still being sold, but they don't have any sort of software dev guy working for them. So no real updates can be done. Apparently the firmware has a lot more features in it than are currently enabled, they just need software written around them.
So still a solid ECU, and good hardware, but nothing in the pipeline as far as big software updates.
Completely incorrect Joe - the picture was one from a google web search, actually, admittedly, I will take 5 minutes tomorrow to update to our own image... we use a completely different type of processor and architecture to MS, thats why it is 10x more accurate on ignition and 100x more accurate on fuelling.... (compared to MS2 anyway as I haven't yet had experience of MS3).
There are fundamental differences that separate our ECU from MS, from the PTM, to the comms protocol, to the actual HW architecture.... Ours was developed for a Le Mans engine - does MS even have GDI or DBW capabilities (Have a look under DBW on our ECU, spot the MS bits there - I dont expect so...) I suggest you get your facts correct before making libellous claims - which parts on our PCB did you notice the MS uses Joe? I admit we had a comm port, and a PCB, but injection drive, coil drive, VR, Op Amp based anolog input filtering, DSP windowed knock control, Flash data logging memory (as opposed to SD Card), the list goes on.... that's why the higher powers didn't care - the point was as incorrect then as it is now... Anyone with basic electronics engineering can confirm that, and anyone who takes a look at the open source comms protocol we released will see how ours was implemented by Alex, MEs Software engineer, who clearly knows what he is doing.... It would be HARDER to disguise our product this far from MS than it would be to start from scratch, and the fact that we had ALOT of funding to do so for the Le Mans engine development means that is what we did..... The first ever version even had 16x16 ignition tables and floating point resolution for all the fuel/ign tables etc.... not sure if MS3 even has that does it?
See I didnt even know they did it - thats how much we copied them...
Doesent look like a very safe system - secondary TPS and DBW sensor positioning etc in there?
Our V4 ECU could run MS2 FW, but was clearly labelled as such and we were only banned from selling when we fell out with a chap called Bill Shurvington, and we then stopped - Before that we used to buy MS1 V3.0s in from Jerry @ DIY... its an old story maybe 8 years ago - started ME221 dev approx 5 years ago, and before I met Alex I did a small, simple electronics ignition system called the NODIZ, using a PIC processor and 8 months of messing
Matt, go back to "developing" your "new" wideband.
And perhaps your online time would be better spent over on an FM-approved Miata forum, Miata.net.
There is a much better pool of FM221 customers over there. You're only going to dig a deeper hole for yourself here.
Matt, go back to "developing" your "new" wideband.
And perhaps your online time would be better spent over on an FM-approved Miata forum, Miata.net.
There is a much better pool of FM221 customers over there. You're only going to dig a deeper hole for yourself here.
the ignition and fueling accuracy as well as update speed are superior to MS3 - we will be doing back to back testing and having it independently verified very soon,
Originally Posted by Matt Thorne
Completely incorrect Joe - the picture was one from a google web search, actually, admittedly, I will take 5 minutes tomorrow to update to our own image... we use a completely different type of processor and architecture to MS, thats why it is 10x more accurate on ignition and 100x more accurate on fuelling.... (compared to MS2 anyway as I haven't yet had experience of MS3).
So its superior....to something you haven't tried?
Originally Posted by Matt Thorne
See I didnt even know they did it - thats how much we copied them...
Doesent look like a very safe system - secondary TPS and DBW sensor positioning etc in there?
Our V4 ECU could run MS2 FW, but was clearly labelled as such and we were only banned from selling when we fell out with a chap called Bill Shurvington, and we then stopped - Before that we used to buy MS1 V3.0s in from Jerry @ DIY... its an old story maybe 8 years ago - started ME221 dev approx 5 years ago, and before I met Alex I did a small, simple electronics ignition system called the NODIZ, using a PIC processor and 8 months of messing
I have tuned yesterday the car that Elior complained about, we all happen to be friends. Knowing first hand the issues they encountered from day one I can understand their frustration. I had a nightmare tuning this car yesterday.
1. There is an error when trying to log pulls, so I had to work with what I felt was ok.
2. The ignition table management is horrible. You can't increase or decrease marked cells by any increment. Only interpolate or manually adjusting each and every cell. When you try to copy a row anywhere, it copies that row to the entire rows underneath it.
3. Choosing a number for overboost is greyed out! Can't adjust it or enable it from what I have seen.
And this is just from what I have worked with, and that's not getting on about the menu layout.
I'm Alex, I own 50% of Motorsport Electronics and I feel like my company has been affected by how these discussions evolved and by past history that doesn't have ANYTHING to do with the company.
First of all, on the software, since my primary role here and why I got into the business was to design and create the firmware to run the ECUs and the software to configure them. From design to implementation, it's 100% original. Don't take my word for it, just look at the architecture of the processor, the communication protocol that has been released as open source and compare it to Megasquirt's. There's absolutely no connection there and it's very easy to prove.
As for Matt's dealings with Megasquirt, that's a completely different chapter! It was before Motorsport Electronics and he was accused of copying the software, which I've just proven above it to not have anything to do with. Anyone is more than welcome to put the two ECUs side-by-side and see that they are based on two different software solutions:
- 221 uses floating point for every data entity in the ECU, whereas MS uses (mostly) integers.
- Communication protocol is completely different
- Idle algorithm is completely different
- Fueling algorithm is completely different
- The flexible IO system is completely different
Yes, Matt's relationship with MS went south a couple of years before we started ME. That's been documented and discussed to death. How does that have anything to do with ME, a company that didn't even exist back then and was only started years after said events happened? How does that have anything to do with me, or the ME221? Just stop and consider that for a few seconds please.
And of course there were issues. We'd be lying if we said there weren't. But which product doesn't have them? We aren't afraid of exposing them, hence we have a dedicated public Facebook group for all the users and we consistently help out people on the forums with questions that are ME221-related. The product has also come A LONG way since Joe has last seen it, hence having both versions on sale now. I think the last couple of pages are a prime example of how not to debate on a forum, but I'd be more than happy to answer any actual questions on the subject of the ME221.
The M-tech V4 board was never licensed to run the MegaSquirt firmware, nor were the unauthorized copies of the V3.0. It is possible that the code team was not aware of the V4's existence, and therefor did not send a cease and desist letter, until after the falling out.
All I can say is that I got a unit for a customer before testing it myself - first mistake, after all I have been through with this unit I am not selling it any more.
Sorry it is just not ready - too many rough edges.
While the snafu with the Megasquirt piracy and all the history to go along with it may have nothing to do with your current company, ME, they do have everything to do with your partner in crime. Sadly, these things tend to follow people. For those that know the history, your engineer (or one of them anyway) ripped off technology from a different manufacturer and tried to claim it as his own. While that may have nothing to do with ME, it has everything to do with his character and we all know that you are the company that you keep...
I'm Alex, I own 50% of Motorsport Electronics and I feel like my company has been affected by how these discussions evolved and by past history that doesn't have ANYTHING to do with the company.
First of all, on the software, since my primary role here and why I got into the business was to design and create the firmware to run the ECUs and the software to configure them. From design to implementation, it's 100% original. Don't take my word for it, just look at the architecture of the processor, the communication protocol that has been released as open source and compare it to Megasquirt's. There's absolutely no connection there and it's very easy to prove.
As for Matt's dealings with Megasquirt, that's a completely different chapter! It was before Motorsport Electronics and he was accused of copying the software, which I've just proven above it to not have anything to do with. Anyone is more than welcome to put the two ECUs side-by-side and see that they are based on two different software solutions:
- 221 uses floating point for every data entity in the ECU, whereas MS uses (mostly) integers.
- Communication protocol is completely different
- Idle algorithm is completely different
- Fueling algorithm is completely different
- The flexible IO system is completely different
Yes, Matt's relationship with MS went south a couple of years before we started ME. That's been documented and discussed to death. How does that have anything to do with ME, a company that didn't even exist back then and was only started years after said events happened? How does that have anything to do with me, or the ME221? Just stop and consider that for a few seconds please.
And of course there were issues. We'd be lying if we said there weren't. But which product doesn't have them? We aren't afraid of exposing them, hence we have a dedicated public Facebook group for all the users and we consistently help out people on the forums with questions that are ME221-related. The product has also come A LONG way since Joe has last seen it, hence having both versions on sale now. I think the last couple of pages are a prime example of how not to debate on a forum, but I'd be more than happy to answer any actual questions on the subject of the ME221.
Cheers,
Alex
Hi Alex,
That's cool. I'm glad that you didn't just copy our source code, but why did you copy our manual?
Below, please find your manual from Nov 16, and then my manual that is more than 10 years old. You clearly plagiarized my manual. You even of a picture of my hand in your manual. Those are my words. THAT'S MY HAND.
ME221 manual, Nov 16:
MSPNP Gen1 Manual, from 10 years ago:
Also note, their order of operations.
__________________
Chief of Floor Sweeping, DIYAutoTune.com & AMP EFI
Crew Chief, Car Owner & Least Valuable Driver, HongNorrthRacing
03-21-2017, 02:44 PM
1
