the framework suzuki gsr 600 2007

[legendaryslave]

controls well , gives you only the gsxr
and puts the strings 80 and 90 from the change
nn goes well on the gsr 600 2007
right?

you're right, this bike is not there and' excuse ? was an oversight then

[linus146]

sorry you legendary
but, as written in the previous message, actually the version 181 puts me on the list this bike
I just have to try to process the file because what I posted nn corresponds to the indications of the tacho
also if this is a little unpleasant and you have to edit the file manually

[linus146]

the reading was made in the 8-bit and nn 16
8-bit the result of the string 60's and this
ff ff ff 7b fb ff ff ff 7b fb ff ff 7b fb ff ff ff

virtually ff 7b fb has to be changed in ff 97 fe

[legendaryslave]

the reading was made in the 8-bit and nn 16
8-bit the result of the string 60's and this
ff ff ff 7b fb ff ff ff 7b fb ff ff 7b fb ff ff ff

virtually ff 7b fb has to be changed in ff 97 fe

then you have solved the 8-bit read ?

[linus146]

I have basically used incorrectly an old version of the tacho( where nn there was the gsr 600) while also having the new one ( which I then used to make the correct file)

and also reading nn I corresponded because it was 16-bit
with the 8-bit I solved ( + tacho version 181 )

thank you for the collaboration

[ecutuningpro]

hello it is the km is the string ff 7b fb

[linus146]

hello ********* pro
to me you're asking me or are you saying?

[ecutuningpro]

hello, I was saying-

[linus146]

in fact......................................this is the procedure of the tacho

Car type: Suzuki GSR 600 - 93c56 - 2006 year
The mileage is stored in the next lines:
0060: xx xx FF FF EF xx FF FF EF xx FF FF EF xx xx xx
where the next bytes:
FF FF EF - is a mileage
this, however, our reading

ff ff ff 7b fb ff ff ff 7b fb ff ff 7b fb ff ff ff-----should therefore be amended ff 7b fb