NYC Coding // thought on iCarly

[jsoto]

Got my PA soft in. Had to mess with drivers a-bit but it finally initialized. Cannot read IKE or EWS. No biggie. Pop the case open thinking it's the infamous pin 7/8 fix.

So how picky was the driver install for yours. Just wondering. I did a rollback and went with the driver on the package. newer ftdi drivers would product hardware not ready on virtual win xp instance

[mr_robot]

Which PA Soft cable did you get? Mine didn't need jumping the 7&8 terminals.


Sent from my iPhone using Tapatalk Pro

[jsoto]

No clue. Just ebayed it. the sticker looked the same on all the listings...
Unless it's due to me running a virtual *pc* instance that is not native....

[wpoll]

Originally Posted by jsoto

No clue. Just ebayed it. the sticker looked the same on all the listings...
Unless it's due to me running a virtual *pc* instance that is not native....

I run my PA Soft 1.4 (BMW Scanner) on a Mac via VMware Fusion - no issues. Well, aside from the USB 2.0 cable not working in a USB 3.0 port, which I get around with a USB 2.0 hub.

[jsoto]

Well, the included USB cable - whenever I plugged it in, 1 time out of 5, it would not even connect/device be seen. Just grabbed a USB cord from a device I had nearby and everytime I connected it to the OBD adapter, it recognized it. Eh, so baby steps.

Maybe it's not pin 7/8 and it's driver. Dunno. I had like 3 FtDI driver packages....each would not see hardware. Use the one with the package, and it finally got past Hardware Ready. However, it initial scan, it's coming up with cannot read ike or ews. I dunno if it's still driver related at this point..

Don't believe everything u read on the internet. Ha. Some say soldering 1/2 7/8 did not do squat. Others say it did the trick. It's like rolling the dice, and if one don't work, use the next google answer

[wpoll]

Originally Posted by jsoto

Well, the included USB cable - whenever I plugged it in, 1 time out of 5, it would not even connect/device be seen. Just grabbed a USB cord from a device I had nearby and everytime I connected it to the OBD adapter, it recognized it. Eh, so baby steps.

Maybe it's not pin 7/8 and it's driver. Dunno. I had like 3 FtDI driver packages....each would not see hardware. Use the one with the package, and it finally got past Hardware Ready. However, it initial scan, it's coming up with cannot read ike or ews. I dunno if it's still driver related at this point..

I had similar issues at first - and like you I tried cables, drivers etc. and finally figured out it was the USB 2.0 cable in a USB 3.0 port. FYI, this is supposed to work but it doesn't always and my goto fix for this issue has always been to connect via a cheap self powered USB 2.0 hub.

In my case, instant fix - PA Soft has been flawless ever since.....