03-06-2020, 02:37 AM
(03-06-2020, 01:25 AM)zyNoT Wrote:I seen this and 7.6 was the problem. Agree with zynot(03-04-2020, 08:55 AM)DewDewMax Wrote:Just because you get a successful message doesn't mean it was flashed right. Just because you don't get fault codes doesn't mean it flashed correctly. I've done extensive research on this so you can believe what you want, but if you flashed any BBZ that required 7.70.0.62 or above then your flash is bad and you don't even know it.(03-02-2020, 09:55 PM)MaraJin Wrote: just flashed 2 trucks with the feb-2019 official incal disks converted to the older compression for 7.6. - they went right in using 7.6 -- i am thinking you have something wrong if files are getting corrupt for you.I have also flashed NUMEROUS BDR's with 7.6 without any issues at all. Also with new 2019 converted to old format and 2018 converted as well with date changed.
The ONLY ECMs I would ever flash with 7.6 would be CM870 and CM871.
You guys seriously think you can use a 2013 software product to flash a cal requiring an ecfg made with CalbertNG in 2014 or newer? INSITE has no idea what those new parameters or new addresses are. If you're running a CM2250 BBZ, check your key off and key on count. You'll see it says 65535 because INSITE actually flashed a RLOC as that because the addresses were offset. But hey guys - do what you want. Just trying to save people future headache.