DavidBraley wrote:I see in the PCM Hammer log above that the recognized device is a OBDX Pro VT. Where can someone get one of these? Or is this the device that Pete is developing with another guy? [/url]
Yes it's that device, and "another guy" is who posted that log.
Ops! No disrespect Tazzi! I had no idea you are the other half of this thing. I speak for many when I say we are super excited about this interface. Looking forward to when it's available! I'm also happy to pay up front if it helps to bring this thing to market. I'm going to need two!
-David
I'm a machinist... because engineers need heroes too.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
Gampy wrote:I'm not up on the C# side of things, where can I adjust the Timeout for the Allpro??
Right now, the values from Device.GetVpwTimeoutMilliseconds() are used for all devices, so that's the place to experiment.
I think it was overly optimistic to assume that the same values would work for all of them, though. In a future release I'll make that virtual so that each device type can have its own timeout values. Might also add the ability to override timeout values in the .config file as well, so people can easily experiment and fine-tune.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
NSFW wrote:Right now, the values from Device.GetVpwTimeoutMilliseconds() are used for all devices, so that's the place to experiment.
I think it was overly optimistic to assume that the same values would work for all of them, though. In a future release I'll make that virtual so that each device type can have its own timeout values. Might also add the ability to override timeout values in the .config file as well, so people can easily experiment and fine-tune.
Awesome, thank you.
For giggles I just disabled 4x on the AllPro and albeit slow it completed first time Zero retries!
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!
Did a full read with PCM Hammer 009 on the MX+. It seemed to go faster and it definitely looked different in the debug log. Here are the log tabs from the full read.
Available tools:
VCX Nano GM wifi (VXDIAG NANO-PLUS-V1.2 2020.10) (STM32F407 VTG6 ARM brand processor)
VAS 6154 Clone (VW6154-V1.0 1850) Looks like the VCX Nano but not as complicated.
Mongoose ISO/CAN
VAGcom HEX+CAN (HC8198369 Rev. B)
Maxidas DS708
Available tools:
VCX Nano GM wifi (VXDIAG NANO-PLUS-V1.2 2020.10) (STM32F407 VTG6 ARM brand processor)
VAS 6154 Clone (VW6154-V1.0 1850) Looks like the VCX Nano but not as complicated.
Mongoose ISO/CAN
VAGcom HEX+CAN (HC8198369 Rev. B)
Maxidas DS708
I'm satisifed now so I'm going to release a new build.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
Did another read on my actual truck. Worked. I should mention, i have had to put both pcms in recovery mode to do a full read with my j2534. I had a diablo trinity tune on this one but I unmarried it and reverted back to stock.
