What enhancments does A-tap V2 cable have over V1

[Keith@HPTuners]

Anyone know the actual capability differences from a programming standpoint?

I know the packet protocol is a little different with a different header.. but what else?

What can the V2 cable do that the V1 won't?

I'll e-mail autotap and see what they say but I figured I'd post here as well.

[Keith@HPTuners]

Also, did a little more digging..

JPatrick of autotap stated that the only difference between the LDVXXXP1 and the autotap V2 device is the model # they report

which is also interesting.. as the VIA device is $149.95

Autotap has 2 cables that you can chose from, both are V2 I assume:

OBDII Generic Parameters KAT1WG $199.95
OBDII Generic & GM's Enhanced Parameters KAT1WEPT $289.95

Right now.. I'm just confusing myself.

[RoboGeek]

are the cables actually different? enhanced parameters would be a function of software I would think..

The more I try to find out about cables and what they can do.. the more I get confused or filled with misinformation. I swear most of those people had the cables designed for them and they just do the software...

[Keith@HPTuners]

Check out the links page with some of the new interface links I put up.. Lots of good stuff on there. Some are straight through, some use the ELM device, and then there is the B&B devices... that kinda sums it up..

in the end, it's still confusing.

I e-mailed autotap, I hope they respond here.

[Keith@HPTuners]

I e-mailed orders@B&B by mistake and didn't really get the answer I was looking for..

My one concern is about packet length... I guess I'll find out in a few days when I start to play though.

[beerman]

In B&B's LDV doc http://www.vehicleinterface.com/asse...xxP1-1103m.pdf it says on page 3 Firmware4 Revision History
Version 1.XX Not Applicable Old 15-byte fixed lenght
hope that helps

[Keith@HPTuners]

Ahh cool. I had that document on my desktop already.. Nice find.

[ls1tools]

Hi All,
Sorry I've been away so long.
EFILive uses both the AT V1 cable and the AT V2 cable so I have programmed against both APIs. They are *very* different APIs.

Just off of the top of my head...

The V1 API is fixed length 15 byte packets.
The V2 API uses a variable length message made up of a variable length header block and a variable length detail block.
The format is like this:
<start of frame=$01><Header length byte><header data bytes><detail length byte><detail data bytes><checksum>

The V1 is fixed at 19200 baud, the V2 has a programmable baud rate up to 115200 baud. On some data logging operations this gives up to 30% faster throughput.

The V2 has some "smarts" built in - it autodetects the OBDII protocol of the vehicle and reports it back to the PC based application.

The V2 has a checksum byte the V1 does not.

The V2 reports back error messages the V1 does not.

Paul

[Keith@HPTuners]

Thanks again Paul, you have provided a plethora of information on this forum.

[RoboGeek]

That answered alot of questions I had..
Thank Paul!

[The_Highlander]

Can it be used to reprogram??? LMK

THanks

[Guest]

Hi All,
Sorry I've been away so long.
EFILive uses both the AT V1 cable and the AT V2 cable so I have programmed against both APIs. They are *very* different APIs.

Just off of the top of my head...

The V1 API is fixed length 15 byte packets.
The V2 API uses a variable length message made up of a variable length header block and a variable length detail block.
The format is like this:
<start of frame=$01><Header length byte><header data bytes><detail length byte><detail data bytes><checksum>

The V1 is fixed at 19200 baud, the V2 has a programmable baud rate up to 115200 baud. On some data logging operations this gives up to 30% faster throughput.

The V2 has some "smarts" built in - it autodetects the OBDII protocol of the vehicle and reports it back to the PC based application.

The V2 has a checksum byte the V1 does not.

The V2 reports back error messages the V1 does not.

Paul

What's the maximum packet size on the V2? same as the LDV?

[ls1tools]

The API allows for up to 256 bytes, but it is physically limited to 32 bytes.

I do not believe it can be used for reprogramming.
But just because I don't think it can doesn't mean it cannot.
I don't fully understand *ALL* the requirements for reprogramming so I can't say for sure.

Paul

[Keith@HPTuners]

Check out the very large Flash Protocol thread for a little snippet on my latest findings regarding flash programming requirements. I'm not going to hijack this thread. There is a lot of good reading there.