Pages: [1] 2
Author Topic: Volvo S60R  (Read 9460 times)
Victory
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« on: January 27, 2010, 06:32:35 PM »

Hi all,

First post and from the subject, yes, I'm a Volvo owner.  More importantly I own one with an ME7.01 ECM.  Anything special I should be looking for as I begin tuning using the new tools here on this site?

I too feel like many of you, completely shut down by the tuning.  I'm used to tuning cars with vairous systems.  It's a first I've learned that I have to pay someone to tune it for me.  Tuning is not for everyone but it shouldn't be withheld from everyone.

Look forward to learning the new system.

Regards,

Scott
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +116/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #1 on: January 30, 2010, 01:04:17 PM »

Hi Scott,

The tools I am putting together to release to people have only been tested on the Audi ME7.1. But I am hoping to support all ME7.X assuming there aren't too many crazy differences.

I will try to talk to some of my professional tuning contacts and see if I can find out any information for you about Volvo S60R ME7.01 tuning.

I considered buying an S60R before I picked my S4. They are cool cars.
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
turboskipper
Jr. Member
**

Karma: +3/-0
Offline Offline

Posts: 40


« Reply #2 on: October 19, 2010, 09:06:34 AM »

Hi Scott,

The tools I am putting together to release to people have only been tested on the Audi ME7.1. But I am hoping to support all ME7.X assuming there aren't too many crazy differences.

I will try to talk to some of my professional tuning contacts and see if I can find out any information for you about Volvo S60R ME7.01 tuning.

I considered buying an S60R before I picked my S4. They are cool cars.

My boss has an S60R and would also like to play with the tuning. I tried reading the car with the nefmoto flashing tool and had no luck. We could probably help test if you expand support to all ME7.X Tony
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +116/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #3 on: October 19, 2010, 02:55:59 PM »

Can you send me a log file of the attempt to read?
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
turboskipper
Jr. Member
**

Karma: +3/-0
Offline Offline

Posts: 40


« Reply #4 on: October 29, 2010, 10:09:40 AM »

Here is a log with the new flashing software. Note that he suspects this car has an IPD calibration. I would think I should at lease be able to connect to the ECU though even with an IPD cal. Log with the engine running and with the engine not running but ignition on.

Quote
29/Oct/2010 01:05:29.233: LOG: Opened FTDI device.
29/Oct/2010 01:05:29.234: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
29/Oct/2010 01:05:29.235: LOG: FTDI ChipID DLL is loaded, checking chip ID...
29/Oct/2010 01:05:29.235: LOG: Unable to read FTDI device chip ID
29/Oct/2010 01:05:29.281: LOG: Starting send receive thread.
29/Oct/2010 01:05:29.283: LOG: Send receive thread now started.
29/Oct/2010 01:05:29.286: USER: Disconnected
29/Oct/2010 01:05:29.307: USER: Connection attempt number 1.
29/Oct/2010 01:05:29.312: USER: Connecting...
29/Oct/2010 01:05:29.616: USER: Connecting to address 0x01.
29/Oct/2010 01:05:31.947: LOG: Failed to read sync byte. Read 0 bytes.
29/Oct/2010 01:05:31.965: USER: Slow init failed.
29/Oct/2010 01:05:31.966: USER: Disconnected
29/Oct/2010 01:05:31.987: USER: Connection attempt number 2.
29/Oct/2010 01:05:31.991: USER: Connecting...
29/Oct/2010 01:05:32.294: USER: Connecting to address 0x01.
29/Oct/2010 01:05:34.625: LOG: Failed to read sync byte. Read 0 bytes.
29/Oct/2010 01:05:34.643: USER: Slow init failed.
29/Oct/2010 01:05:34.646: USER: Disconnected
29/Oct/2010 01:05:34.666: USER: Connection attempt number 3.
29/Oct/2010 01:05:34.672: USER: Connecting...
29/Oct/2010 01:05:34.976: USER: Connecting to address 0x01.
29/Oct/2010 01:05:37.305: LOG: Failed to read sync byte. Read 0 bytes.
29/Oct/2010 01:05:37.321: USER: Slow init failed.
29/Oct/2010 01:05:37.323: USER: Disconnected
29/Oct/2010 01:05:37.347: LOG: Closing FTDI device.
29/Oct/2010 01:05:37.354: LOG: Send receive thread now terminated.
29/Oct/2010 01:06:09.650: LOG: Opened FTDI device.
29/Oct/2010 01:06:09.651: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
29/Oct/2010 01:06:09.651: LOG: FTDI ChipID DLL is loaded, checking chip ID...
29/Oct/2010 01:06:09.652: LOG: Unable to read FTDI device chip ID
29/Oct/2010 01:06:09.700: LOG: Starting send receive thread.
29/Oct/2010 01:06:09.702: LOG: Send receive thread now started.
29/Oct/2010 01:06:09.705: USER: Disconnected
29/Oct/2010 01:06:09.726: USER: Connection attempt number 1.
29/Oct/2010 01:06:09.731: USER: Connecting...
29/Oct/2010 01:06:10.035: USER: Connecting to address 0x01.
29/Oct/2010 01:06:12.366: LOG: Failed to read sync byte. Read 0 bytes.
29/Oct/2010 01:06:12.382: USER: Slow init failed.
29/Oct/2010 01:06:12.384: USER: Disconnected
29/Oct/2010 01:06:12.405: USER: Connection attempt number 2.
29/Oct/2010 01:06:12.408: USER: Connecting...
29/Oct/2010 01:06:12.712: USER: Connecting to address 0x01.
29/Oct/2010 01:06:15.041: LOG: Failed to read sync byte. Read 0 bytes.
29/Oct/2010 01:06:15.060: USER: Slow init failed.
29/Oct/2010 01:06:15.062: USER: Disconnected
29/Oct/2010 01:06:15.083: USER: Connection attempt number 3.
29/Oct/2010 01:06:15.087: USER: Connecting...
29/Oct/2010 01:06:15.391: USER: Connecting to address 0x01.
29/Oct/2010 01:06:17.725: LOG: Failed to read sync byte. Read 0 bytes.
29/Oct/2010 01:06:17.743: USER: Slow init failed.
29/Oct/2010 01:06:17.745: USER: Disconnected
29/Oct/2010 01:06:17.766: LOG: Closing FTDI device.
29/Oct/2010 01:06:17.769: LOG: Send receive thread now terminated.
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +116/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #5 on: October 29, 2010, 12:36:36 PM »

Have you tried connecting using fast init?
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
turboskipper
Jr. Member
**

Karma: +3/-0
Offline Offline

Posts: 40


« Reply #6 on: October 29, 2010, 01:57:09 PM »

Have you tried connecting using fast init?

If I remember right I tried both but I'll try fast again just to make sure.
Logged
turboskipper
Jr. Member
**

Karma: +3/-0
Offline Offline

Posts: 40


« Reply #7 on: November 02, 2010, 11:56:09 AM »

Fast init with and without vehicle running.
Quote
02/Nov/2010 02:55:09.948: LOG: Opened FTDI device.
02/Nov/2010 02:55:09.949: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
02/Nov/2010 02:55:09.949: LOG: FTDI ChipID DLL is loaded, checking chip ID...
02/Nov/2010 02:55:09.950: LOG: Unable to read FTDI device chip ID
02/Nov/2010 02:55:09.998: LOG: Starting send receive thread.
02/Nov/2010 02:55:09.999: LOG: Send receive thread now started.
02/Nov/2010 02:55:10.002: USER: Disconnected
02/Nov/2010 02:55:10.021: USER: Connection attempt number 1.
02/Nov/2010 02:55:10.025: USER: Connecting...
02/Nov/2010 02:55:10.027: USER: Connecting to address 0x01.
02/Nov/2010 02:55:10.476: LOG: Sent message with service ID StartCommunication
02/Nov/2010 02:55:10.480: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 413ms
02/Nov/2010 02:55:10.482: USER: Fast init succeeded.
02/Nov/2010 02:55:10.533: LOG: Failed to send message 1 times, message send failed.
02/Nov/2010 02:55:10.534: USER: Disconnected
02/Nov/2010 02:55:10.557: USER: Connection attempt number 2.
02/Nov/2010 02:55:10.561: USER: Connecting...
02/Nov/2010 02:55:10.563: USER: Connecting to address 0x01.
02/Nov/2010 02:55:10.969: LOG: Sent message with service ID StartCommunication
02/Nov/2010 02:55:10.973: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
02/Nov/2010 02:55:10.976: USER: Fast init succeeded.
02/Nov/2010 02:55:11.025: LOG: Failed to send message 1 times, message send failed.
02/Nov/2010 02:55:11.026: USER: Disconnected
02/Nov/2010 02:55:11.049: USER: Connection attempt number 3.
02/Nov/2010 02:55:11.054: USER: Connecting...
02/Nov/2010 02:55:11.056: USER: Connecting to address 0x01.
02/Nov/2010 02:55:11.460: LOG: Sent message with service ID StartCommunication
02/Nov/2010 02:55:11.464: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
02/Nov/2010 02:55:11.466: USER: Fast init succeeded.
02/Nov/2010 02:55:11.517: LOG: Failed to send message 1 times, message send failed.
02/Nov/2010 02:55:11.518: USER: Disconnected
02/Nov/2010 02:55:11.540: LOG: Closing FTDI device.
02/Nov/2010 02:55:11.543: LOG: Send receive thread now terminated.
02/Nov/2010 02:55:30.559: LOG: Opened FTDI device.
02/Nov/2010 02:55:30.560: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
02/Nov/2010 02:55:30.560: LOG: FTDI ChipID DLL is loaded, checking chip ID...
02/Nov/2010 02:55:30.561: LOG: Unable to read FTDI device chip ID
02/Nov/2010 02:55:30.609: LOG: Starting send receive thread.
02/Nov/2010 02:55:30.610: LOG: Send receive thread now started.
02/Nov/2010 02:55:30.613: USER: Disconnected
02/Nov/2010 02:55:30.634: USER: Connection attempt number 1.
02/Nov/2010 02:55:30.638: USER: Connecting...
02/Nov/2010 02:55:30.640: USER: Connecting to address 0x01.
02/Nov/2010 02:55:31.046: LOG: Sent message with service ID StartCommunication
02/Nov/2010 02:55:31.050: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
02/Nov/2010 02:55:31.052: USER: Fast init succeeded.
02/Nov/2010 02:55:31.102: LOG: Failed to send message 1 times, message send failed.
02/Nov/2010 02:55:31.103: USER: Disconnected
02/Nov/2010 02:55:31.125: USER: Connection attempt number 2.
02/Nov/2010 02:55:31.129: USER: Connecting...
02/Nov/2010 02:55:31.131: USER: Connecting to address 0x01.
02/Nov/2010 02:55:31.537: LOG: Sent message with service ID StartCommunication
02/Nov/2010 02:55:31.541: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
02/Nov/2010 02:55:31.544: USER: Fast init succeeded.
02/Nov/2010 02:55:31.593: LOG: Failed to send message 1 times, message send failed.
02/Nov/2010 02:55:31.595: USER: Disconnected
02/Nov/2010 02:55:31.616: USER: Connection attempt number 3.
02/Nov/2010 02:55:31.620: USER: Connecting...
02/Nov/2010 02:55:31.622: USER: Connecting to address 0x01.
02/Nov/2010 02:55:32.029: LOG: Sent message with service ID StartCommunication
02/Nov/2010 02:55:32.033: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
02/Nov/2010 02:55:32.034: USER: Fast init succeeded.
02/Nov/2010 02:55:32.085: LOG: Failed to send message 1 times, message send failed.
02/Nov/2010 02:55:32.087: USER: Disconnected
02/Nov/2010 02:55:32.110: LOG: Closing FTDI device.
02/Nov/2010 02:55:32.113: LOG: Send receive thread now terminated.
02/Nov/2010 02:55:38.423: LOG: Closing NefMoto ME7 ECU Flasher BETA 1.6.0.0
02/Nov/2010 02:57:27.033: LOG: Opened NefMoto ME7 ECU Flasher BETA 1.6.0.0
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +116/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #8 on: November 02, 2010, 06:25:30 PM »

Thanks for the log. All I can think that would cause this, is the ECU not responding to address 0x01. All VAG cars have their ECUs at address 0x01, and then they have some funny protocol switching when using address 0x11. I'm guessing that the Volvo may not have the ECU at address 0x01.

If the connection address isn't the problem, then it is possible that my connection timings are incorrect, or that there is some other method that is necessary to wake up the ECU.

Are you able to use VAG-COM or any other OBD software to connect to the ECU? If you can, then VAG-COM displays the connection address in the top left corner.

Do you know if the car has the ECU connected to a CAN bus? I believe newer cars using the CAN bus need a different wake up method.
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
turboskipper
Jr. Member
**

Karma: +3/-0
Offline Offline

Posts: 40


« Reply #9 on: November 03, 2010, 08:00:58 AM »

Thanks for the log. All I can think that would cause this, is the ECU not responding to address 0x01. All VAG cars have their ECUs at address 0x01, and then they have some funny protocol switching when using address 0x11. I'm guessing that the Volvo may not have the ECU at address 0x01.

If the connection address isn't the problem, then it is possible that my connection timings are incorrect, or that there is some other method that is necessary to wake up the ECU.

Are you able to use VAG-COM or any other OBD software to connect to the ECU? If you can, then VAG-COM displays the connection address in the top left corner.

Do you know if the car has the ECU connected to a CAN bus? I believe newer cars using the CAN bus need a different wake up method.

I'll try with VAG-COM and see what I can come up with. Not sure about the CAN bus.
Logged
turboskipper
Jr. Member
**

Karma: +3/-0
Offline Offline

Posts: 40


« Reply #10 on: November 08, 2010, 06:41:55 AM »

Tried using VAG-COM and scanning all ECU addresses with no luck. Maybe it uses CAN? I was using a k-line cable.
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +116/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #11 on: November 08, 2010, 12:40:15 PM »

If it uses CAN you would need a Ross-Tech CAN cable to test.

My flashing software just using the K-line and does not support CAN.
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
turboskipper
Jr. Member
**

Karma: +3/-0
Offline Offline

Posts: 40


« Reply #12 on: November 08, 2010, 01:34:06 PM »

If it uses CAN you would need a Ross-Tech CAN cable to test.

My flashing software just using the K-line and does not support CAN.

Yes, I know. I don't have the CAN ross-tech cable and also know that your software does not support that. Too bad. IPD makes a flash loader for their calibrations. Would be interesting to get my hands on it and see what communication it uses.
Logged
fredrik_a
Full Member
***

Karma: +24/-0
Offline Offline

Posts: 220


« Reply #13 on: January 20, 2011, 04:15:30 AM »

For what it's worth... Take a look at http://www.nefariousmotorsports.com/forum/index.php?topic=340.0title=
 
Logged
Mladen
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 51


« Reply #14 on: January 21, 2019, 10:08:59 AM »

Old thread I know,

Did anyone ever get further with this?
Logged
Pages: [1] 2
  Print  
 
Jump to:  

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