Gampy wrote:I am having one heck of a bad time with my AllPro, yet my SparkFun is working the best I've ever seen, 21 minutes for 1m, Zero retries most of the time.
My AllPro is flaky when I connect it directly to the PCM on my work bench. However, when I connect it via a Y-cable that has a second OBD2 device attached (usually a ScanTool SX or LX), the AllPro is reliable. Something about having a second device on the VPW bus makes a big difference. I thought I was the only one who had this problem, but maybe not?
It has always been reliable in my car, where there are several other devices on the bus.
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!
DavidBraley wrote:I wish Pete and Tazzi would get there piece of kit out into the world! Can you hear me yelling Pete and Tazzi!!!
What is this SparkFun gizmo you speak of! Those people are just down the road from me. It's where I by some of my Arduino's, Raspberry Pi's, and other such electronics fun.
Yea, me too ... But I learned along time ago to allow the cream to rise to the top in it's own good time.
As for the SparkFun, I got it a long time ago as a gift: OBD-II UART, and the USB - Serial port addon on board FTDI Basic Breakout - 5V.
I also got a OBD-II to DB9 Cable with a switch, but they don't list one with a switch now.
Unfortunately the USB-Serial is FTDI ...
[edit]
I should also mention it's not 4x capable.
Hi all,
For those that are interested, the Sparkfun board Gampy listed uses the same STN series chip that the OBDLink SX uses.
Gampy, why the comment about the FTDI USB interface?
I have a genuine one that I was using for OBD1 PCMs.
FTDI has the ONLY USB interface that is natively supported in the Android OS.
joukoy wrote:Now tested with my other PCM (Service: 12586242)
First, Full OS + CAL write with LS Droid (Because I don't have xdf for original OS), then some modifications to tune and calibration write with PCM Hammer.
No problems
joukoy,
That doesn't sound right, ServiceNo: 12586242 covers HardwareNo: 12583660, and is Amd Flash I believe. (according to my info)
Yet, the log clearly states Intel Flash.
[08.01.41.207] Flash chip: Intel 28F800B, 1mb
Could you please confirm.
(Not that it really matters I guess, maybe just to me)
When I bought this PCM + engine + trans combo, seller told me it is 12586242. There is no sticker left, so I am not sure.
Is there other way than label to check it?
joukoy wrote:When I bought this PCM + engine + trans combo, seller told me it is 12586242. There is no sticker left, so I am not sure.
Is there other way than label to check it?
Unfortunately not, the Service number is only on the label, not within. (at least that I know of)
I would refrain from using that service number, it could get confusing ... The important numbers for you to remember are the hardware number and OsID.
MudDuck514 wrote:Gampy, why the comment about the FTDI USB interface?
Because of their drivers that silently brick clones ...
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!
MudDuck514 wrote:Gampy, I understand and agree. Guess I was lucky that the one I bought from Amazon uses a Genuine FTDI chip and never had any problems.
And just to make myself clear, I would respect them if they screamed clone and didn't load ... but to harm the naive and innocent.
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!
All the pcmhacking interfaces use ftdi chips, because the drivers are high quality. It does suck that they bricked clones, but every genuine pcmhacking interface shipped has had genuine chips, and they work well.
I would recommend you do use the service number. The hardware numbers change with a pcm clone, and are less well known. I think if you read the OSID, you can see what service number that shipped on and that will probably mean the most to others on forums.
antus wrote:All the pcmhacking interfaces use ftdi chips, because the drivers are high quality. It does suck that they bricked clones, but every genuine pcmhacking interface shipped has had genuine chips, and they work well.
I would recommend you do use the service number. The hardware numbers change with a pcm clone, and are less well known. I think if you read the OSID, you can see what service number that shipped on and that will probably mean the most to others on forums.
Not knocking their quality, they are the best!
The service number @joukoy has is wrong for the Pcm he has, that is why I recommended he not use that service number ... Normally I would not recommend that.
As for OsID to Service number, How??
That I want to know. Any way to get the Service Number back.
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!
Do you have a device that works with PcmHammer other then the AllPro??
I am having one heck of a bad time with my AllPro, yet my SparkFun is working the best I've ever seen, 21 minutes for 1m, Zero retries most of the time.
I wish Pete and Tazzi would get there piece of kit out into the world! Can you hear me yelling Pete and Tazzi!!!
