gslender wrote:Ken, so what is the guidance here? Is ok to publish mods against the official release (in accordance with the license terms, provided freely to msextra, with no strings etc) or would this activity of adding a feature be severely frowned upon?
I appreciate that it is the msextra's team desire to limit further development and enhancement of ms2, but does that also mean that any community enhancement submitted will be restricted too?
dontz125 wrote:Hi, Ken.
I can appreciate the desire to 'nudge' people towards the MS3 platform if they want the latest and greatest in features, but I have to question the notion of a 'hard stop' to MS2 development (within the capacity and capability of the processor and memory, obviously). The MS2 processor IS still a main-line MS product; the MS2 daughter card (and associated kits) are still being produced and sold hand-over-fist, and the MicroSquirt and MicroSquirt Module line has no MS3 equivalent.
There are many people clamoring to buy the new MS3 processor and MS3x expansion board. Is it really necessary to declare an end to MS2 coding beyond tweaks and fixes?
dontz125 wrote:you weren't always the keeper of MS2/Extra.
I understand and (deeply) appreciate that this is your hobby, not your job, and I also understand that there are only so many hours in the day, and that your primary focus has to be the MS3.
That said, you have people who are willing to do the MS2 work for you - gslender and robs have been throwing out several ideas AND actually doing the spadework that goes along with it. racingmini_mtl is still a major contributor, even if his focus is more towards his own boards these days. You have been sufficiently impressed with gslender's coding that (as far as I can tell) you've allowed him to do the bulk of the coding for his tweaks that (unless I've lost track) you've incorporated into the current MS2 beta. Quite frankly, I would suggest that the idle mods you and he have worked on are far more than "tweaks", but rather a significant change and improvement to the functionality of the code.
Posting comments on a forum that could be taken as deprecating or pompous must be done with care, due to the lack of expression and posture; this next is said without sarcasm, and with respect for your efforts and accomplishments: you weren't always the keeper of MS2/Extra. If you are unable or unwilling to continue development and expansion efforts of the code, perhaps it is time to bring someone else on board to take over that duty.
I am a bit baffled by the notion of "copying our features" - at what point does basic functionality become a feature? Is coping with the idle lurch inherent with the AC switching on and off a feature, or basic function?
Is implementing an AFR protection a feature, or basic function?
Given the expense entailed in a lunched engine vs the simple aesthetics of a smooth idle (I have owned several cars that dipped at idle when the AC tripped), I would be inclined to say that the AFR system is far more important, and far more of a candidate for inclusion.
From a rider's perspective: I have read a number of people point out that the 'flat shift' function in MS2 doesn't work well with high-revving bikes;
I have also read that there is a plan to add a bike-style shift-cut to MS3.
Is this a feature, or a basic function?
Even I would say that it's a feature - but where does that leave all the bikers who have installed MicroSquirts (or WILL install - the uS is still a first-line B&G product!) who now want that 'feature' for their bikes? Since it's a feature, will permission for backporting to MS2 be refused?
dontz125 wrote:The point I'm trying to make, and one I would suggest is echoed by others in this thread and elsewhere, is that the MS2 is still a first-line device. The MicroSquirt and MicroSquirt Module are first-line variants of the MS2. Ceasing support of the firmware of a 'title' product is not good business. B&G have JUST released the V3 uS - for all its limitations (and I have a few comments on that), that product is most certainly not at the end of its life.
The MS2 is going to be around for a while, especially in the motorcycle field; the MS3 box is BIG, and rather few people on tightly-packed sport-bikes are going to be interested in strapping the ECU to the tank. There are still a few bike-specific aspects I'd like to see added that most of the car guys installing MS3s couldn't care less about. Would I be able to able to get together with (say) gslender and bash some ideas about, or am I dead in the water?
Ken - would it be reasonable to see a proposed mod that you can review to determine if the limited features are 1) not too taxing to maintain, and 2) keep the features low enough such that value for MS3 is maintained???
gslender wrote: An example....several people I spoke to before I got into Megasquirt recommended I buy one as it was mentioned as "OpenSource" and has lots of "community contributions". That advice was wrong. I'm now very aware it isn't "OpenSource",
Users browsing this forum: No registered users and 2 guests