Printable View
I ask for a little information: a file .hex of the map, how is it obtained? I would to run a a2l a edc16c34 but with sw different than the a2l that I own, and asks me a blessed offset during loading. Are the hours that we are around and moving but I can't seem to skip out.
test with offset 800000
Quote:
Originally Written by sergiot
I add a zip with the a2l that I would like to use and the map for which I would
the bin file is correct and the maps are seen as shown in the a2l.
also hex seems right to you. but I will check later.
Ok, and how is it to me if I try to load: map 1.6 hdi 110cv my 2007, and to add l a2l certain maps, such as the driver's wish, I can't find it? I do not understand where mistakeQuote:
Originally Written by sergiot
but the problem which is????
not only the map, not find it, and others???
at the beginning you say that the hex file is not what you expected for the a2l.
at this point, it is normal that some of the maps are, but it is a case, and other not the find.
exactly, and what I dislike the most is that I can't find the most important maps...but maps only "secondary" that I'm not interested at the moment.Quote:
Originally Written by sergiot
the hex file that is there in the folder is just for the a2l that is always located inside the folder. my question is how to adapt the a2l to my files ori? there is the setting for the offset in load, since them we have, but how can I calculate? if I know that my ecu has sw xxx (a candidate hypothesis), while that of the a2l is yyy which method you use to make it compatible for my xxx? and then, there's a way to create a hex file from my files ori?Quote:
Originally Written by sergiot
I spontaneously arises the doubt, seeing my map ori, the reading is correct at this point. Missing too much info in the initial part. I had perhaps read it in the boot or on the bench? I've read through the kess and kline.
there is no way out.
the file a2l are compiled on the basis of the hex file to which they refer.
there is a method to change the a2l, to the extent of us operators in the aftermarket.
but a method to get there.
you open the right file with the a2l is right. find the maps you want, then you compare the different file looking for the same maps, that are there, but can be moved to address. often not very moved.
does not count for this discussion, the method or instrument used.
there are a lot of a2l around that are missing their maps main.Quote:
Originally Written by henry pontoons
if it was a problem of offset simply see the maps in the wrong location, not that it would disappear!
The simplest method is to open along with the windows of the file with a2l to your file with the function in memory "title" under the view menu. And them 2d by scrolling a little bit a and a little bit of the other align the maps that interest you
Quote:
Originally Written by Errecinque
Quote:
Originally Written by sergiot
another question: is it plausible that what the ecm calls turbo pressure (4 maps for this ecu) in reality by a2l are the 4 maps are very different and bp are very different from what it says ecm?
don't use ecm, so I don't have a lot of experience.
but read what is on the various forums, ecm, especially crack, can we trust a little day and the other way as well.
on the file a2l rather not discuss, those are made by the manufacturer of the file, and make the faith.
you just have to be careful for the correct translation in Italian.
Quote:
Originally Written by sergiot
chapter writing mod file: kessv2 automatically calculates the checksum for this ecu? otherwise winols is reliable in the correction cksm?
I on the edc16c34, I have never had problems of cks ecm calculates well. I would say that you can stay quietQuote:
Originally Written by henry pontoons
Quote:
Originally Written by Errecinque
Time a couple of days and I think I will be able to post a first preview of the mod so maybe you can tell me if I'm wrong and as a mistake