17 Silverado
Register
Results 1 to 10 of 10

Thread: 17 Silverado

  1. #1
    DK Veteran
    nickolasd's Avatar
    Join Date
    Nov 2015
    Posts
    496
    Thanks Thanks Given 
    151
    Thanks Thanks Received 
    229
    Thanked in
    133 Posts

    Default 17 Chevy Silverado

    17 silverado with prod date 09/16

    D70f3525 mcu in a dash
    run hours 1224 need 612
    idle hours 312 need 160
    Attached Files Attached Files
    Last edited by nickolasd; 17th October, 2018 at 08:36 PM.

  2. #2
    DK Veteran
    mecjp's Avatar
    Join Date
    Oct 2013
    Location
    other world
    Posts
    393
    Thanks Thanks Given 
    217
    Thanks Thanks Received 
    155
    Thanked in
    86 Posts

    Default

    good job, can you share soldering point in cluster?
    sharing is the key of success

  3. #3
    DK Veteran
    nickolasd's Avatar
    Join Date
    Nov 2015
    Posts
    496
    Thanks Thanks Given 
    151
    Thanks Thanks Received 
    229
    Thanked in
    133 Posts

    Default

    heres is connection.
    with vvdiprog using mcu reflash cable
    use 1kOm resistor between RTXD and VCC


    green wire FLMD1 goes to pin 118 on mcu, somewhat difficult to solder that wire, pins are very small.
    red wire - VCC pin 113 on mcu
    yellow wire - RESET pin 114
    green - FLMD1 pin 118
    orange - RTXD pin 138
    black - GROUND pin 31
    blue FLMD0 pin 104
    Attached Images Attached Images
    Last edited by nickolasd; 16th October, 2018 at 03:15 AM.

  4. The Following 5 Users Say Thank You to nickolasd For This Useful Post:

    Berubeg (16th October, 2018), buga37 (4th September, 2022), cklair (16th October, 2018), mecjp (16th October, 2018), tech020 (28th June, 2021)

  5. #4
    DK Veteran
    nickolasd's Avatar
    Join Date
    Nov 2015
    Posts
    496
    Thanks Thanks Given 
    151
    Thanks Thanks Received 
    229
    Thanked in
    133 Posts

    Default

    BCM solved

    only dash left

  6. #5
    DK Veteran
    nickolasd's Avatar
    Join Date
    Nov 2015
    Posts
    496
    Thanks Thanks Given 
    151
    Thanks Thanks Received 
    229
    Thanked in
    133 Posts

    Default

    Heres 2 dash Dflash files with about 30min difference between them. DFlash changes a lot. Pflash stays the same.
    who is got some ideas about calculations?
    Attached Files Attached Files

  7. #6
    DK Veteran
    mecjp's Avatar
    Join Date
    Oct 2013
    Location
    other world
    Posts
    393
    Thanks Thanks Given 
    217
    Thanks Thanks Received 
    155
    Thanked in
    86 Posts

    Default

    I have compare first file and second file but first read seem bad reading can you share another more one to be sure
    too much FFFF ??!!
    Attached Images Attached Images
    • File Type: jpg 1.jpg (531.4 KB, 47 views)
    • File Type: jpg 2.jpg (481.8 KB, 35 views)
    • File Type: jpg 3.jpg (540.2 KB, 34 views)
    • File Type: jpg 4.jpg (522.6 KB, 28 views)
    • File Type: jpg 5.jpg (483.6 KB, 27 views)
    sharing is the key of success

  8. #7
    DK Veteran
    nickolasd's Avatar
    Join Date
    Nov 2015
    Posts
    496
    Thanks Thanks Given 
    151
    Thanks Thanks Received 
    229
    Thanked in
    133 Posts

    Default

    read is good, it was verified both times and also pflash came out exactly the same both times. my understanding that data moves around every time cpu shuts down and restarts, same thing you can see on a bmw ECUs like msv80, location of data will be different every time.

  9. #8
    DK Veteran
    mecjp's Avatar
    Join Date
    Oct 2013
    Location
    other world
    Posts
    393
    Thanks Thanks Given 
    217
    Thanks Thanks Received 
    155
    Thanked in
    86 Posts

    Default

    I know smelecom and jprog and now dp4 do the job but manually, and i don't know where's hours located in this mcu, it's a mystery at this time, but someone know how correct it? let us know if you found it mate
    Last edited by mecjp; 18th October, 2018 at 10:53 PM.
    sharing is the key of success

  10. #9
    Member
    Join Date
    Apr 2017
    Location
    PA - USA
    Posts
    46
    Thanks Thanks Given 
    7
    Thanks Thanks Received 
    20
    Thanked in
    13 Posts

    Default

    What do you think the chances are of being able to CLONE a customers inoperable cluster to a replacement cluster of the same part number using this method? Read via vvdiprog and transferring the file. It SHOULD transfer the security protocol number, vin#, hours, etc, correct? Or am I missing something?

  11. #10
    Top Poster

    Join Date
    Sep 2018
    Location
    USA
    Posts
    171
    Thanks Thanks Given 
    251
    Thanks Thanks Received 
    27
    Thanked in
    22 Posts

    Default

    Quote Originally Posted by dgunke View Post
    What do you think the chances are of being able to CLONE a customers inoperable cluster to a replacement cluster of the same part number using this method? Read via vvdiprog and transferring the file. It SHOULD transfer the security protocol number, vin#, hours, etc, correct? Or am I missing something?
    I know this is an old thread but I’ve had a couple of speedometer clusters CLONED by seeing them to “ODO PRO”.just google it.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.