Discuss: Real time mapping DSM Link style?
Discuss: Real time mapping DSM Link style?
Now we have a read/write byte protocol, I was thinking about how to implement real time mapping.
One way is to implement the entire main fuel and timing maps in RAM, but I think that would be quite cumbersome.
What do we think of the way the DSM Link does it with the sliders at 1000-8000 RPM for fuel and timing? I quite like it, and it certainly fits better with the way I map personally. I'm more likely to have the patience to implement something to do this than I am something to relocate whole tables to RAM etc...
One way is to implement the entire main fuel and timing maps in RAM, but I think that would be quite cumbersome.
What do we think of the way the DSM Link does it with the sliders at 1000-8000 RPM for fuel and timing? I quite like it, and it certainly fits better with the way I map personally. I'm more likely to have the patience to implement something to do this than I am something to relocate whole tables to RAM etc...
I used DSMLink for years and it was an outstanding product, but I don't think you will get much discussion here because I think most Evo owner don't even know what DSMLink is.
The thing I really like about tuning in RAM was being able to adjust settings for different occasions, like going to the drap strip, etc. I could turn on NLTS, change the launch RPM, maybe timing and fuel all right there with the car running. Then, when the day was over, I could simply load the old setting right back in without ever having to shut the car off or flashing or anything like that.
Basically, it gave you ability to have a bunch of tunes saved where you could load then to RAM for different occasions. I know your particular question in this thread is a bit different, though. Sorry, I got a little of topic thinking back to DSMLink.
As far as your question, I don't really know. The slider method did make it much easier to tune and much faster to tune, but obviously it didn't give the granularity and fine detail. A lot of the reasons DSMLink did this was because the stock DSM ECU was in the highest load column at anything above 2.1 g/rev, so even on a mildly modded DSM you were really only tuning the highest load column anyway. So, the slider approach worked pretty well, while not making it complicated for the novice tuner.
New versions of DSMLink will actually have the entire maps available, like ECUFlash, and actually I think I would actually prefer this for live RAM tuning also. I think most people in this forum are used to the way that ECUFlash presents the entire maps for tuning and this would logically be the best approach to continue for tuning in RAM. I know it will be harder to implement, but I think it will be worth it in the long run.
Eric
The thing I really like about tuning in RAM was being able to adjust settings for different occasions, like going to the drap strip, etc. I could turn on NLTS, change the launch RPM, maybe timing and fuel all right there with the car running. Then, when the day was over, I could simply load the old setting right back in without ever having to shut the car off or flashing or anything like that.
Basically, it gave you ability to have a bunch of tunes saved where you could load then to RAM for different occasions. I know your particular question in this thread is a bit different, though. Sorry, I got a little of topic thinking back to DSMLink.
As far as your question, I don't really know. The slider method did make it much easier to tune and much faster to tune, but obviously it didn't give the granularity and fine detail. A lot of the reasons DSMLink did this was because the stock DSM ECU was in the highest load column at anything above 2.1 g/rev, so even on a mildly modded DSM you were really only tuning the highest load column anyway. So, the slider approach worked pretty well, while not making it complicated for the novice tuner.
New versions of DSMLink will actually have the entire maps available, like ECUFlash, and actually I think I would actually prefer this for live RAM tuning also. I think most people in this forum are used to the way that ECUFlash presents the entire maps for tuning and this would logically be the best approach to continue for tuning in RAM. I know it will be harder to implement, but I think it will be worth it in the long run.
Eric
Hi John,
I agree with Eric. I too used DSMLink for years and love it for what it is, but one of the main reasons I moved to ECUFlash was because of the ability to tune all the various load sites and not just the WOT condition.
Thank you for all your efforts on the "live tuning" front. You're doing the community a wonderful service.
I agree with Eric. I too used DSMLink for years and love it for what it is, but one of the main reasons I moved to ECUFlash was because of the ability to tune all the various load sites and not just the WOT condition.
Thank you for all your efforts on the "live tuning" front. You're doing the community a wonderful service.



