Pages: [1]
Author Topic: Losing my Mind  (Read 8264 times)
Cadensdad14
Full Member
***

Karma: +8/-1
Offline Offline

Posts: 134


« on: July 08, 2015, 08:06:34 PM »

So im trying to get started in this.  Ive been over the tutorials and looked at other people who have had similar issues and im hoping someone can help point me towards where im going wrong.  I have a B5 A4 1.8t running a ch box.

I purchased this cable
http://www.ebay.com/itm/261875978025?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

I downloaded nefmoto, tunerpro, winols demo, and the D2XX driver pack.  I also got the mprog and ftdi ft_prog programs.  I downloaded the most current version of VCDS off of their website along with the drivers for it. 

so heres whats going on
When i use the version of VCDS that came with the cable, release 409.1, i am able to configure to com1 and use VCDS with my car.  I set up VCDS for COM1 and set it to force dumb mode.  When i run the test I get the results:

Port Status: OK
Interface: Found!
Type: Serial Pass-Through
Opti/Iso: No
Ross-Tech Design: No

When I open NefMoto I get no devices to select in the top right corner.

When I use the FTDI utility FT_Prog i am unable to find any devices when I scan and Parse.

When I open VCDS Release 14.10 and run a test on COM1 it returns:

Port Status: OK
Interface: Not Found

Could Someone tell me what Im doing wrong?  Did i purchase a cable with the wrong chipset?  Am i missing a step in recoding a driver to be a ross-tech hex?  My head feels like its going to explode.
Logged
tjwasiak
Sr. Member
****

Karma: +26/-0
Offline Offline

Posts: 420


« Reply #1 on: July 08, 2015, 08:08:04 PM »

It seems it is not FTDI based...
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #2 on: July 08, 2015, 09:12:12 PM »

You must use that cable with VCDS lite.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Cadensdad14
Full Member
***

Karma: +8/-1
Offline Offline

Posts: 134


« Reply #3 on: July 09, 2015, 03:31:42 AM »

You must use that cable with VCDS lite.

VCDS is not that important to me right now.  Can I use it to pull my .bin?
Logged
automan001
Full Member
***

Karma: +47/-0
Offline Offline

Posts: 153


« Reply #4 on: July 09, 2015, 04:37:22 AM »

VCDS is not that important to me right now.  Can I use it to pull my .bin?
It's possible. But you will probably need different software for this cable. I read and write bins with such cable in bootmode using ChipLoader software (from Chipsoft, you can find "cured" version).
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #5 on: July 09, 2015, 08:44:50 AM »

Go to your device manager, under PORTS. Properties, then DRIVER. Post a screenshot.

Sounds like your cable may be CH based.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #6 on: July 09, 2015, 11:14:41 AM »

VCDS is not that important to me right now.  Can I use it to pull my .bin?

If you bought a CH based cable you're in trouble.
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
Cadensdad14
Full Member
***

Karma: +8/-1
Offline Offline

Posts: 134


« Reply #7 on: July 12, 2015, 07:09:25 PM »

Its ch340 based.  Didn't pay enough attention.  Im going with the galetto.  My fault
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.019 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)