Tech2Win Device Compatability w OBDXPro
-
- Posts: 397
- Joined: Wed Jul 05, 2017 8:30 am
- cars: 2001 Pontiac Grand AM SE
LD9 2.4l I4, 4T40E
2005 Chevrolet Venture
LA1 3400 V6, 4T65E - Location: North TX, USA
Tech2Win Device Compatability w OBDXPro
Hi all,
While I know that there are many interfaces that support the Tech2Win App, has anyone had any success using it with the new OBDXPro VT interface?
I would REALLY prefer to only have to but that interface for the present as I don't need Can Bus capability at present.
Thanks,
Mike
While I know that there are many interfaces that support the Tech2Win App, has anyone had any success using it with the new OBDXPro VT interface?
I would REALLY prefer to only have to but that interface for the present as I don't need Can Bus capability at present.
Thanks,
Mike
Re: Tech2Win Device Compatability w OBDXPro
I'm trying right now with multiple interfaces. Give me a few minutes.
Re: Tech2Win Device Compatability w OBDXPro
I have not yet developed the DPU API required to interface with T2Win.
Without the API, T2win cannot communicate with the tool.
Without the API, T2win cannot communicate with the tool.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
-
- Posts: 397
- Joined: Wed Jul 05, 2017 8:30 am
- cars: 2001 Pontiac Grand AM SE
LD9 2.4l I4, 4T40E
2005 Chevrolet Venture
LA1 3400 V6, 4T65E - Location: North TX, USA
Re: Tech2Win Device Compatability w OBDXPro
Hi all,
Tazzi,
Any plans for the API in the near future?
Or should I see about getting a J2534 tool such as the VXDiag Nano!
Thanks,
Mike
Tazzi,
Any plans for the API in the near future?
Or should I see about getting a J2534 tool such as the VXDiag Nano!
Thanks,
Mike
Re: Tech2Win Device Compatability w OBDXPro
With the dozen+ projects I got all on the go, the API isnt on the list right now.MudDuck514 wrote:Hi all,
Tazzi,
Any plans for the API in the near future?
Or should I see about getting a J2534 tool such as the VXDiag Nano!
Thanks,
Mike
It will be in the future but not at this second.
Just make sure to double check that the VXDiag can actually be used for T2win. I dont think I ever have used it for that as it never appears in the supported scantool list even though they say supported.
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Re: Tech2Win Device Compatability w OBDXPro
Hi all,
Wow, that was quite the adventure. I hadn't tried the Tech2Win so this was a perfect excuse. I couldn't get any of my interfaces(AVT852, OBDLink SX, OBDX Pro VT) to work with the Tech2Win in WinXP or Win7. Basically the Tech2Win never sees them after the first screen asking you if you are connecting with MDI or D-PDU API, second screen should show a serial number of what you are trying to connect with. Choosing the com port in the config of the Tech2Win software and assigning new "buttons" had no affect. I finally found drivers that would work in XP for the OBDX Pro VT but that didn't make a difference other than my XP laptop could see it installed. Tazzi just pointed out that the OBDX Pro VT won't work till he does some more stuff.
The VXDiag does show up with a serial number and works fine on my winXP laptop as well as my Win7 laptop. Shows it as a CANdi module
Wow, that was quite the adventure. I hadn't tried the Tech2Win so this was a perfect excuse. I couldn't get any of my interfaces(AVT852, OBDLink SX, OBDX Pro VT) to work with the Tech2Win in WinXP or Win7. Basically the Tech2Win never sees them after the first screen asking you if you are connecting with MDI or D-PDU API, second screen should show a serial number of what you are trying to connect with. Choosing the com port in the config of the Tech2Win software and assigning new "buttons" had no affect. I finally found drivers that would work in XP for the OBDX Pro VT but that didn't make a difference other than my XP laptop could see it installed. Tazzi just pointed out that the OBDX Pro VT won't work till he does some more stuff.
The VXDiag does show up with a serial number and works fine on my winXP laptop as well as my Win7 laptop. Shows it as a CANdi module
Re: Tech2Win Device Compatability w OBDXPro
what about GDS2? is that any different in seeing the interface?
-
- Posts: 397
- Joined: Wed Jul 05, 2017 8:30 am
- cars: 2001 Pontiac Grand AM SE
LD9 2.4l I4, 4T40E
2005 Chevrolet Venture
LA1 3400 V6, 4T65E - Location: North TX, USA
Re: Tech2Win Device Compatability w OBDXPro
Hi all;
In-Tech,
Thanks for the info.
Do you (and anyone else) care to share where you got your Nano from?
I would like you avoid getting ripped off buying a poor imitation - don't mind a clone as long as it works!
Again, thanks to all that answered.
Mike
In-Tech,
Thanks for the info.
Do you (and anyone else) care to share where you got your Nano from?
I would like you avoid getting ripped off buying a poor imitation - don't mind a clone as long as it works!
Again, thanks to all that answered.
Mike
Re: Tech2Win Device Compatability w OBDXPro
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
-
- Posts: 159
- Joined: Fri Aug 25, 2017 5:28 pm
- cars: liberty gen 5
- Location: Adelaide
Re: Tech2Win Device Compatability w OBDXPro
I've got a genuine Ford VCM2 that works pretty good and Abrites AVDI works too....... but MDI is the most stable by far. Just get a good clone and you'll have no probs with T2W and GDS2.
Even though they show up the other 2 are hit and miss with what they connect to.
Even though they show up the other 2 are hit and miss with what they connect to.