Problem, I appear to be getting data errors when editing the same file mixing between TP & TC??
I'm using Arap 6E bin and in TP the 6Ev011 bin def. and in Cats using their 6E def.
I can see that the TP def. has greater data bit address, when editing the same file with Tunercat will this cause data errors...this sounds only too possible?
Can someone with experience confirm what is sounding like a bad practice.

 

What are you changing? I can look at it...........Maybe the scaling is diffrent at the locations you are changing.........

/N.

 

I don't follow what you mean by "TP def. has greater data bit address"

Can you please explain what you mean and give an example of the error you're seeing?

 

By def. I mean the Bin definition file, I'll sort this out in my brain one day.
In TunerPro its either *.ecu or *.xdf. TunerPro seems to provide a greater range of defined data address points as does the equivalent TunerCat bin definition and I'm concerned that editing interchange between the two using the same bin file may produce errors.
To be more clear....I burned a eprom and notice strange behavior with the 700R4 TCC lock and when I removed the chip from the ECU and tried to read the bin again and the bin would not even load using TunerCat, TunerPro would load the file but showed mucho wrong data values with Hex column showing FF & FFF (like a bad burn). Funny because there was no red lamp and the burn did verify at the time. I'm unsure what caused this to happen which promoted this thread.
I also had the checksum disable by the AA input.
After the run the car was leaking some oil on the floor so I was worried?

 

I'm using both TC and Tunerpro without any problems.

You must have the correct value at $08 to be able to read the *.bin using TC otherwise you will get a error message, its a "safety" check so that you are using the correct *.tdf file.