total newbie to nefmoto needing help with writing out a fault

Pages: [1]

« previous next »

Author

Topic: total newbie to nefmoto needing help with writing out a fault (Read 7253 times)

das_skold

Newbie

Karma: +0/-0
Offline

Offline

Posts: 8

	total newbie to nefmoto needing help with writing out a fault « on: March 18, 2014, 07:28:41 AM »

Hey guys thanks for the help first off. Im a total newbie to nefmoto, i have rewriten japanese ecms which is way simpler. I also am a vw tech and i currently have a high mileage vehicle with fault p0441 and it will cost me an arm and a leg to repair, I only uses the car for an a-b point driver, so i want to write out the fault. I have been trying to find a basic how to on pulling the .bin and editing it but im having issue. vehicle is a 2001 passat

thanks guys


	Logged

ddillenger

Hero Member

Karma: +639/-21
Offline

Offline

Posts: 5640

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #1 on: March 18, 2014, 07:51:32 AM »

Rule number 1.

Always post your file when requesting help.

Rule number 2.

Always post logs when requesting help (doesn't apply here, but just in case you stay a while).


	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

das_skold

Newbie

Karma: +0/-0
Offline

Offline

Posts: 8

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #2 on: March 18, 2014, 09:12:46 AM »

this was all i couuld get outof the ecm when using nefmoto and a vagcom cable.

Read 5 ECU info entries:
0x92, System Supplier ECU Hardware Number: 0261207435,
0x94, System Supplier ECU Software Number: 1037394890,
0x91, Vehicle Manufacturer ECU Hardware Number: 0x0D, 8E0909018 , 0xFF,
0x9B, Calibration Date: 4B0906018CM , 0010, 0x030040A7, 0x80000002, 0x559E, 1.8L R4/5VT , G01 ,
0x9C, Calibration Equiment Software Number: 0x00010101,


	Logged

ddillenger

Hero Member

Karma: +639/-21
Offline

Offline

Posts: 5640

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #3 on: March 18, 2014, 10:48:52 AM »

You need to go to the flashing tab and read your file.

Select a memory layout (in the Nefarious Motorsports folder, then memory layouts). Use 29F800BB

Then, select FULL READ FLASH.


	Logged

das_skold

Newbie

Karma: +0/-0
Offline

Offline

Posts: 8

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #4 on: March 19, 2014, 09:11:08 AM »

Quote from: ddillenger on March 18, 2014, 10:48:52 AM

You need to go to the flashing tab and read your file.

Select a memory layout (in the Nefarious Motorsports folder, then memory layouts). Use 29F800BB

Then, select FULL READ FLASH.

now im getting the following error no matter what i do i tried with every memory load out and with none.

now im getting the foloowing when trying to connect with a ross tech cable.

19/Mar/2014 11:39:33.838: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:39:37.868: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:39:41.870: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:39:44.871: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
19/Mar/2014 11:39:44.872: USER: Disconnected
19/Mar/2014 11:39:44.891: USER: Connecting...
19/Mar/2014 11:39:44.908: USER: Starting bootstrap loader upload.
19/Mar/2014 11:39:45.910: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:39:49.912: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:39:53.914: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:39:56.915: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
19/Mar/2014 11:39:56.916: USER: Disconnected
19/Mar/2014 11:39:56.925: USER: Connecting...
19/Mar/2014 11:39:56.943: USER: Starting bootstrap loader upload.
19/Mar/2014 11:39:57.945: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:40:01.950: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:40:04.955: USER: Sent bootstrap init zero byte.
19/Mar/2014 11:40:06.956: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
19/Mar/2014 11:40:06.957: USER: Disconnected
19/Mar/2014 11:40:06.994: LOG: Closing FTDI device.
19/Mar/2014 11:40:06.995: LOG: Send receive thread now terminated.
19/Mar/2014 11:40:23.165: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
19/Mar/2014 11:40:23.191: LOG: Opened FTDI device.
19/Mar/2014 11:40:23.193: LOG: FTDI device info - Description: Ross-Tech HEX-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA24 Device Flags: 0x0
19/Mar/2014 11:40:23.194: LOG: FTDI ChipID DLL is loaded, checking chip ID...
19/Mar/2014 11:40:23.196: LOG: FTDI device chip ID: 0x451D2ED9
19/Mar/2014 11:40:24.222: USER: Failed to read test echo from FTDI device.
19/Mar/2014 11:40:57.689: LOG: Closing FTDI device.
19/Mar/2014 11:40:57.717: LOG: Opened FTDI device.
19/Mar/2014 11:40:57.720: LOG: FTDI device info - Description: Ross-Tech HEX-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA24 Device Flags: 0x0
19/Mar/2014 11:40:57.720: LOG: FTDI ChipID DLL is loaded, checking chip ID...
19/Mar/2014 11:40:57.723: LOG: FTDI device chip ID: 0x451D2ED9
19/Mar/2014 11:40:58.747: USER: Failed to read test echo from FTDI device.
19/Mar/2014 11:41:04.291: LOG: Closing FTDI device.
19/Mar/2014 11:41:04.303: LOG: Could not open FTDI device
19/Mar/2014 11:41:04.304: USER: Could not open FTDI device.
19/Mar/2014 11:43:42.372: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
19/Mar/2014 11:43:42.373: LOG: Closing FTDI device.
19/Mar/2014 11:43:42.395: LOG: Could not open FTDI device
19/Mar/2014 11:43:42.397: USER: Could not open FTDI device.
19/Mar/2014 11:43:50.652: LOG: Closing FTDI device.
19/Mar/2014 11:43:50.663: LOG: Opened FTDI device.


	Logged

ddillenger

Hero Member

Karma: +639/-21
Offline

Offline

Posts: 5640

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #5 on: March 19, 2014, 09:14:38 AM »

Have you unchecked the "boot in intelligent mode" box in the VCDS options menu, then tested, and saved?

Why are you trying bootmode in nefmoto software?


	Logged

das_skold

Newbie

Karma: +0/-0
Offline

Offline

Posts: 8

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #6 on: March 19, 2014, 11:42:36 AM »

I was trying boot mode to see if anything would work. I uninstalled vcds and still nothing now it says ftdi error. i have uninstalled all ftdi drivers, and reinstalled them and i can not get them to set to the ross tech cable. it windows will only let me uses rosstech drivers.

Quote from: ddillenger on March 19, 2014, 09:14:38 AM

Have you unchecked the "boot in intelligent mode" box in the VCDS options menu, then tested, and saved?

Why are you trying bootmode in nefmoto software?


	Logged

ddillenger

Hero Member

Karma: +639/-21
Offline

Offline

Posts: 5640

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #7 on: March 19, 2014, 12:37:28 PM »

Is it a real VCDS cable? You have a lot of reading to do.

Download teamviewer, PM me your ID and password later this evening, I will get someone to take a look.


	Logged

das_skold

Newbie

Karma: +0/-0
Offline

Offline

Posts: 8

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #8 on: March 20, 2014, 08:20:03 AM »

its a real ross tech cable i also have a ebay cable, and i get this error again, the cable worked fine the other day and i updated vag com while i was working on a car in the shop and since then my ross tech cable will not work . so i uninstalled vag com/

ebay cable error:

20/Mar/2014 08:30:21.242: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 08:30:21.445: LOG: Cannot load license file, file does not exist: C:\Users\Das\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
20/Mar/2014 08:30:21.507: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 08:30:31.682: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 08:36:56.802: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 08:36:57.379: LOG: Cannot load license file, file does not exist: C:\Users\Das\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
20/Mar/2014 08:36:57.457: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 11:12:18.063: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 11:12:18.642: LOG: Cannot load license file, file does not exist: C:\Users\Das\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
20/Mar/2014 11:12:18.710: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 11:12:23.211: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
20/Mar/2014 11:12:23.275: LOG: Opened FTDI device.
20/Mar/2014 11:12:23.276: LOG: FTDI device info - Description: USB <-> Serial Serial Number: Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
20/Mar/2014 11:12:23.322: LOG: FTDI ChipID DLL is loaded, checking chip ID...
20/Mar/2014 11:12:23.327: LOG: FTDI device chip ID: 0xF3D0E7D5
20/Mar/2014 11:12:24.384: USER: Failed to read test echo from FTDI device.
20/Mar/2014 11:12:36.514: LOG: Closing FTDI device.
20/Mar/2014 11:12:36.544: LOG: Could not open FTDI device
20/Mar/2014 11:12:36.545: USER: Could not open FTDI device.
20/Mar/2014 11:12:48.720: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
20/Mar/2014 11:12:48.721: LOG: Closing FTDI device.
20/Mar/2014 11:12:48.748: LOG: Opened FTDI device.
20/Mar/2014 11:12:48.755: LOG: FTDI device info - Description: USB <-> Serial Serial Number: Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
20/Mar/2014 11:12:48.756: LOG: FTDI ChipID DLL is loaded, checking chip ID...
20/Mar/2014 11:12:48.759: LOG: FTDI device chip ID: 0xF3D0E7D5
20/Mar/2014 11:12:49.782: USER: Failed to read test echo from FTDI device.
20/Mar/2014 11:12:55.755: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 11:14:52.609: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 11:14:55.776: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 11:14:56.353: LOG: Cannot load license file, file does not exist: C:\Users\Das\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
20/Mar/2014 11:14:56.415: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
20/Mar/2014 11:15:00.134: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
20/Mar/2014 11:15:00.184: LOG: Opened FTDI device.
20/Mar/2014 11:15:00.186: LOG: FTDI device info - Description: USB <-> Serial Serial Number: Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
20/Mar/2014 11:15:00.186: LOG: FTDI ChipID DLL is loaded, checking chip ID...
20/Mar/2014 11:15:00.191: LOG: FTDI device chip ID: 0xF3D0E7D5
20/Mar/2014 11:15:01.247: USER: Failed to read test echo from FTDI device.


	Logged

stuklr

Full Member

Karma: +2/-0
Offline

Offline

Posts: 146

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #9 on: March 20, 2014, 09:11:13 AM »

I will give you some simple steps.

Open Vagcom

Go to settings and uncheck "boot in intelligent mode"

Save settings and close vagcom

Open nefmoto and try to connect now.


	Logged

Snow Trooper

Hero Member

Karma: +89/-24
Offline

Offline

Posts: 689

	Re: total newbie to nefmoto needing help with writing out a fault « Reply #10 on: March 22, 2014, 08:40:13 AM »

You are a tech at a vw dealer? I ask cause I was also and this should be really basic for you. If dd can't get you sorted pm me and I can give you alternate ways to pull and write your file.


	Logged

cartoons?
6A 61 72 65 64 40 76 6C 6D 73 70 65 63

Pages: [1]

« previous next »

Jump to:

Navigation

Personal Tools

May 04, 2024, 03:21:23 AM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Navigation

Personal Tools

Search