DashHawk development is dead...

opt_ms3

Member
:
Mazdaspeed3
According to the MSD Tech Forums, It turns out that MSD has pulled the plug on that guy Ken Mosher and his DashHawk development team. (chair) The final release is 2.5. MSD is apparently coming out with a new and better product in the next 6-8 months.

This is kind of disappointing since those of us who have a DashHawk were pretty used to the constant software and firmware updates and bug fixes. I'm not saying that my DashHawk is now useless, because it works very well. It just sucks that they made the business decision that further development of the DashHawk was not necessary with the niche community of computer and car geeks.

That guy Ken at MSD did a great job with the DashHawk. I know that when I first plugged in my DashHawk to my MS3 with an old version of firmware, it didn't work very good at all. Went to the website, downloaded the new software/firmware, flashed the DashHawk, plugged it back in to the Mazda, and it read my Wideband sensor. That was sweet. I'm glad I purchased the DashHawk when I did, but some of you who are thinking about buying it, you should probably hold out and wait for MSD's new product. Whenever that does come out...
 
I heard this too, its a shame- its a good product. I would say 95% of MS3 owners have one.

I agree it's a shame, but disagree that 95% of MS3 owners have one. I don't even think 95% of the MS3 owners on this website have one.
 
this news is about 2-3 weeks old. i'm disappointed as well. i've only had my dh for about 2 months and so far, it's been very helpful
 
Seems pretty compitent in its current form, so while the news is kind of sad, it's really not a big deal (at least for me, personally).
 
well it sucks because the final release (2.5) is buggy (warning colors staying on once they hit the warning point, for one) and no one has popped in the Tech forum saying they are addressing the issue.
 
well it sucks because the final release (2.5) is buggy (warning colors staying on once they hit the warning point, for one) and no one has popped in the Tech forum saying they are addressing the issue.

Are you sure that you haven't set the warning to flash above and beyond the threshold?

For instance, I have my RPMs currently set to flash at 5300 and above, not just 5300.
 
i don't have one personally but why dont alot of you guys email him. maybe it'll encourage him to keep developing on his terms and possibility open source it.
 
thats not good but from reading the thread it sounds like another software company is suposed to pick up the reaghns were they left off. it sounds like msd outsorced there development and now the found someone else to either do a better jop or lower price diffrent ideas or fond someone in india or china to do it.
 
well it sucks because the final release (2.5) is buggy (warning colors staying on once they hit the warning point, for one) and no one has popped in the Tech forum saying they are addressing the issue.

yeh did that to me i jus went back to the beta
 
Is it possible that the open source community could take over new development? I wonder if the DashHawk team would allow it. I actually plan on getting a DashHawk within the next month or two.
 
I'd wait for the new generation of DashHawk comes out...the current customer support for the DashHawk blows!!!

I frankly think the DashHawk has been left hanging. They said they have no interest in wasting money on this obsolete unit.

I just want them to come out with something exactly like the Dashhawk, but with a slightly bigger, wider screen... (2thumbs)
 
Is it possible that the open source community could take over new development? I wonder if the DashHawk team would allow it. I actually plan on getting a DashHawk within the next month or two.

That would be awesome if MSD actually released the source code, and if there were actually enough freelance programmers willing to tackle the code in their spare time. Unfortunately, I am not a programmer/developer whatsoever, I'm more on the technical side of things, but I would continue the bug-testing that was working so well before MSD pulled the plug.
 
open source ftmfw.................please ken @ msd, help us out by giving the code to us........we'll do the rest........
 
Back