id a bin file?

[Holden202T]

i used winhex to copy the first bit of the file (which was emtpy) and pasted it infront of the file, basically extended it by 1000.

[Silver308]

Gday,
Trying to get my head around a problem and have a couple questions.
Im trying to identify a bin pulled (used Gq-4x) from a mates VN 355,which has an 808 ecu. When id'd comes up with File unknown, and a whole heap of stuff like:
Detected MD5 11a7a710248bef1c6e36dde5a3f5534a IN AREA 0x6000 - 0x7FFF

When opening in TP is it a case of trying a few XDF's untill one yields results?
Some VN v8 xdfs show a heap of blank tables, but when opened up with ose12 xdf, the tables/figures are looking a little weird, (VE tables are maxed out accross whole range, fuel air ratios up at 25 odd etc)

Also, have since found out after looking at the tables, that the car is also running a unichip unit (fell out from under the dash when putting the ecu back in), from my understanding they modify signal after the ecu, sending it to the engine, would the ecu be self learning throwing the numbers out trying to compensate from the Unichip?

The car drives fine, but is running lean and can definitly feel it holding back when giving it a boot full. As far as we can tell is still running factory 19lb injectors (which are to small) checked bosch number on them, unless they have been reflowed.

[antus]

Its a 16kb file, not a 32kb file, so your file does not line up. I removed the first 16kb (which was all 0xFF) and now the1s ID tool picks it as a 5D VN/V8, and it should line up with the 5D xdf. The program ID byte has been set to AA so i can assume it is modified.

[Silver308]

Thanks Antus, that makes more sense now.