The FlashTool V1.27

[antus]

the dos version of antusprom can handle Tp4 and scanner pro at the same time via two com0com loopbacks, but that functionality isnt in the flashtool version yet due to the first attempt being unstable and needing a re-work.

[Holden202]

when the aldl passthrough is added to the flashtool that will allow tp4 and scanner pro to work together ... otherwise you still need to use the dos based antusprom

if antus can work out a plugin for TP5 there may be a light at the end of that tunnel too ... but that ain't going to happen for a while!

[mag]

Have loaded flashtool v1.15 & started emulation. received cal from ecu & initialised TP5, flashtool "READY" & "TP Found" boxes are both illuminated. TP5 logging not working, clicking "acquire data connect/disconnect" has no effect. TP5 logging is ok if I use dos version of antusprom. what have I missed.

[Holden202]

you have missed the part where we said logging doesn't work. only changing xdf data in TP5 will work with that connection.

If you want to log and change xdf data at the same time the dos antusprom is the only option.

[antus]

Note: To connect to an OSE v1.0.1 bin in a car with no BCM you must make sure "Options/Preferences/DisableBCM Chatter" is NOT selected.

[Dec_head]

Just checking to see if their was any further development with the logging tuning via usb aldl or tunerpro 5 integration.

[VL400]

No, nothing further has been done with this. Once TP5's plug-ins are working something will be written to use that. Will make it much easier to setup too.

[Tinker]

Hi,

I am using autoprom and successfully connected to ecm , read cal etc with no problems. But when trying to modify xdf in the flex output editor I get a unknown error when writing xdf . green status blocks seem to get 3/4 of the way ...



any ideas ?

[VL400]

Can you email me the XDF? If I can reproduce the error should be able to fix it.

[malser]

* Note - VS Ecotec and newer PCMs that have a 128k binary use a memory bank switching method.
The flash tool only supports reading and writing to bank 1, the first 64k. This means the 'Get Bin'
function does not get the entire binary.

I apologize in advance for my english. I have a question.
I know that my firmware is located in the 2 bank, 64k to the second (starting with address 8000 and end. 32k). Can I read them your program.