![]() ![]() ![]() Then when you connect to the ECU, a difference report will come up with the limited values on the left, ECU values on the right (Controller Settings). With it on, when the msq is loaded, if any array values are out of bounds the defined limits are enforced. Don't enforce your own "Safe" values to a tuned ECU.Ĭode: Select all validateArrayBounds = true ![]() Please remove the "Gauges and settings limit" thing now in a new 3.0.29 release, don't wait for whatever the next huge (V4.0.0?) release will be.Īlternatively, if you connect to an ECU for the first time with a project, RESPECT THE SETTINGS IN THE ECU and port them over in the "Settings and gauges limits". I'm sorry if this post feels like I'm angry-posting, but I'm really angry and feeling for the helpless customer (who has no good 3G/4G connection so that I can send him a new tune file to load). And it has happened so many times, it's just ridiculous. There is exactly 0 reason for this thing to happen. His VE table is capped to 255, and there is no way to get back! This is happening so many times it's not funny anymore.Ĭustomer leaves with a tuned N/A Honda that revs to 10800rpm and runs on nitromethanol (max VE ~340 in some cells).Ĭustomers wants to increase the rev limit on the drag strip, connects with his laptop for the first time with the ECU, and all his max RPM settings (including rev limiter, max RPM in tables, etc) are automatically set to 9000. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |