VVDI PROG - Page 180
Register
Page 180 of 290 FirstFirst ... 80130170175176177178179180181182183184185190230280 ... LastLast
Results 2,686 to 2,700 of 4343

Thread: VVDI PROG

  1. #2686
    DK Veteran

    Join Date
    Apr 2015
    Posts
    954
    Thanks Thanks Given 
    83
    Thanks Thanks Received 
    2,369
    Thanked in
    578 Posts

    Default

    Quote Originally Posted by obeids View Post
    Hi there

    Is there a missing diagram on the VVDI prog?
    I have done many W209 / W203 ignition which have mark on PCB ( 209 ZGW ). I find 2 types of diagram on VVDI prog. However the chip selection is wrong. 90% of those that I have done had 3L40k / 4L40K / 5L40k. The pin connections are the same but chip ID differs. Currently only show 1L59W and some other one. If you select those that are in Menu under IMMO -> BENZ then it doesn't read or reads corrupt.
    GO to MCU and select the matching Mask for 4L40K and it will read using the same diagram of W209 9S12 ST12.
    So please add this mask in the option when select that Immo.
    Thanks alot
    Thanks for your feedback, still finding EIS and try to find the caused reason.

  2. #2687
    DK Veteran
    Basti13's Avatar
    Join Date
    Oct 2009
    Location
    UK
    Posts
    375
    Thanks Thanks Given 
    103
    Thanks Thanks Received 
    73
    Thanked in
    32 Posts

    Default

    Quote Originally Posted by p1et View Post
    Post picture. We can't see anything.
    Now you can see .
    NO PASS

  3. #2688
    Top Poster +
    HIC's Avatar
    Join Date
    Apr 2010
    Posts
    248
    Thanks Thanks Given 
    31
    Thanks Thanks Received 
    74
    Thanked in
    63 Posts

    Default

    Hi everybody
    I am a new buyer for VVDi prog;i recieve my package yesterday;all is OK.
    I m going to try it in the evening.
    Best regards
    H.E

  4. #2689
    DK Veteran
    CarCity's Avatar
    Join Date
    Nov 2016
    Location
    Inside my clothes
    Posts
    2,354
    Thanks Thanks Given 
    566
    Thanks Thanks Received 
    2,122
    Thanked in
    1,266 Posts

    Default

    Hi all Friends

    I need to read FRM3R E70 VDM D-Flash
    But VVDI-Prog not detect automatically D-FLASH and EEE memory size ?
    what process I should try ?
    Thank for your advance
    I surprise those who do not want to use the Thanks and Reputation buttons but ask for the password of the files.

  5. #2690
    DK Veteran
    sniegavirs's Avatar
    Join Date
    Mar 2017
    Location
    Latvia
    Posts
    573
    Thanks Thanks Given 
    426
    Thanks Thanks Received 
    321
    Thanked in
    184 Posts

    Default

    Quote Originally Posted by CarCity View Post
    Hi all Friends

    I need to read FRM3R E70 VDM D-Flash
    But VVDI-Prog not detect automatically D-FLASH and EEE memory size ?
    what process I should try ?
    Thank for your advance
    What is the MCU?
    One i was reading a while ago is D-FLASH 32KB and EEE 4KB
    Last edited by sniegavirs; 13th November, 2018 at 01:25 PM.

  6. The Following User Says Thank You to sniegavirs For This Useful Post:

    CarCity (13th November, 2018)

  7. #2691
    DK Veteran
    CarCity's Avatar
    Join Date
    Nov 2016
    Location
    Inside my clothes
    Posts
    2,354
    Thanks Thanks Given 
    566
    Thanks Thanks Received 
    2,122
    Thanked in
    1,266 Posts

    Default

    Quote Originally Posted by sniegavirs View Post
    What is the MCU?
    One i was reading a while ago is D-FLASH 32KB and EEE 4KB
    MCU : MC9S12XEQ384
    I read that :
    Corrupt D-Flash file detected! Results probably incorrect!
    VIN: WBAFG8100DL28****
    Production date: 12.12.2012
    Programming date: ff.ff.ffff
    HW-NR: 9206234 (Hardware part number)
    SW-NR: ffffffffffff (Updated part number)
    ZB-NR: ffffffffffff (Original part number)
    S: 9287252 (Original part number)

    and now need to repair this :
    Attached Files Attached Files
    I surprise those who do not want to use the Thanks and Reputation buttons but ask for the password of the files.

  8. #2692
    DK Veteran
    sniegavirs's Avatar
    Join Date
    Mar 2017
    Location
    Latvia
    Posts
    573
    Thanks Thanks Given 
    426
    Thanks Thanks Received 
    321
    Thanked in
    184 Posts

    Default

    Quote Originally Posted by CarCity View Post
    MCU : MC9S12XEQ384
    I read that :
    Corrupt D-Flash file detected! Results probably incorrect!
    VIN: WBAFG8100DL28****
    Production date: 12.12.2012
    Programming date: ff.ff.ffff
    HW-NR: 9206234 (Hardware part number)
    SW-NR: ffffffffffff (Updated part number)
    ZB-NR: ffffffffffff (Original part number)
    S: 9287252 (Original part number)

    and now need to repair this :
    As far as i understand for this MCU it is possbile to have D-FLASH and EEE in partitions.
    But if for example: if D-Flash is 32KB then EEE is 0KB or if EEE is 4KB then D-FLASH is 0KB and of course full P-Flash. Correct me if i am wrong..
    And for this MCU being used in BMW FRM modules it is P-Flash with EEE 4KB and no D-Flash(0KB) In VVDI Prog menu you can select under 8-OTHER->BMW->FRM-E-SERIES-XEQ384 and there is only EEE and P-FLASH options to read.

    You should read EEE as 4KB and forget about D-Flash. If your EEE is corrupted i might not be able to help but i have files from 2012 E71 FRM XEQ384 EEE 4KB and P-FLASH.
    Last edited by sniegavirs; 13th November, 2018 at 01:54 PM.

  9. The Following User Says Thank You to sniegavirs For This Useful Post:

    CarCity (13th November, 2018)

  10. #2693
    DK Veteran
    CarCity's Avatar
    Join Date
    Nov 2016
    Location
    Inside my clothes
    Posts
    2,354
    Thanks Thanks Given 
    566
    Thanks Thanks Received 
    2,122
    Thanked in
    1,266 Posts

    Default

    Quote Originally Posted by sniegavirs View Post
    As far as i understand for this MCU it is possbile to have D-FLASH and EEE in partitions.
    But if for example: if D-Flash is 32KB then EEE is 0KB or if EEE is 4KB then D-FLASH is 0KB and of course full P-Flash. Correct me if i am wrong..
    And for this MCU being used in BMW FRM modules it is P-Flash with EEE 4KB and no D-Flash(0KB) In VVDI Prog menu you can select under 8-OTHER->BMW->FRM-E-SERIES-XEQ384 and there is only EEE and P-FLASH options to read.

    You should read EEE as 4KB and forget about D-Flash. If your EEE is corrupted i might not be able to help but i have files from 2012 E71 FRM XEQ384 EEE 4KB and P-FLASH.
    Thank you so much
    Can you give me that files ?
    I surprise those who do not want to use the Thanks and Reputation buttons but ask for the password of the files.

  11. #2694
    DK Veteran
    sniegavirs's Avatar
    Join Date
    Mar 2017
    Location
    Latvia
    Posts
    573
    Thanks Thanks Given 
    426
    Thanks Thanks Received 
    321
    Thanked in
    184 Posts

    Default

    Quote Originally Posted by CarCity View Post
    Thank you so much
    Can you give me that files ?
    One is from my own read FRM but i don't have inf about HW and SW numbers but it is from 2012 E71.
    Other file is from my FRM file collection that i got somwhere..

    Good luck mate!

    P.S. Please ignore that D-FLASH file in one of the rar's
    Attached Files Attached Files

  12. The Following 2 Users Say Thank You to sniegavirs For This Useful Post:

    CarCity (13th November, 2018), serikpay (1st July, 2023)

  13. #2695
    Member

    Join Date
    Oct 2017
    Location
    Hungary, Budapest
    Posts
    90
    Thanks Thanks Given 
    15
    Thanks Thanks Received 
    49
    Thanked in
    14 Posts

    Default

    MCU Reflash Cable V3

    Hi guys, I would like to read/write an ST10F269 with my VVDI Prog, but bit confused now.

    Connection Diagram got an "Important!!!" tab, which titled as : MCU Reflash Cable V2 modified to V3, which about to modify cabling and remove resistors.

    ST10F269 tab says use MCU Reflash Cable V2

    Originally I have MCU Reflash Cable V3, but the cabling and other parts also looks same as the unmodified V2 which needs some costumisation by the Important tab.
    So my question is that, should I modify my factory V3 cable as V2 > V3 or can use it "as factory" V3 and just solder to MCU ?

    Sorry if hard to understand

  14. #2696
    Member

    Join Date
    Jul 2008
    Location
    romania
    Posts
    44
    Thanks Thanks Given 
    278
    Thanks Thanks Received 
    5
    Thanked in
    5 Posts

    Default

    u can use v3

  15. The Following User Says Thank You to mickye_dj For This Useful Post:

    kaleval (14th November, 2018)

  16. #2697
    DK Veteran
    lion0304's Avatar
    Join Date
    Oct 2014
    Posts
    3,679
    Thanks Thanks Given 
    1,750
    Thanks Thanks Received 
    3,315
    Thanked in
    1,938 Posts

    Default Hyundai I30 KEFICO 39122-2B122 Pinout

    ECU with gear box integred MCU ST10F275



    **** Revised complet pinout ***
    Attached Images Attached Images
    Last edited by lion0304; 16th November, 2018 at 09:47 AM.
    Be polite. No Thanks + Rep, no HELP!!! Slava Ukcraine. Dead Putler civilians's killers!!!

  17. The Following 6 Users Say Thank You to lion0304 For This Useful Post:

    alclot (19th November, 2018), damih (16th November, 2018), Perryking (15th November, 2018), PremierD (16th November, 2018), sqlkarol (16th November, 2018), taxo1965 (18th November, 2018)

  18. #2698
    Top Poster

    Join Date
    Oct 2009
    Location
    Poland
    Posts
    140
    Thanks Thanks Given 
    25
    Thanks Thanks Received 
    36
    Thanked in
    20 Posts

    Default

    Quote Originally Posted by Samic View Post
    did you connect 1KΩ resistor between DUOUT and VCC? if not pls do. if so, but still not work. please setting software voltage to 4.2V then try again.
    yes, have connected 1kohm resistor, tryed with vcc from 3,5V to 4,5V and still have message "chip not connect"

  19. #2699
    Top Poster

    Join Date
    Oct 2009
    Location
    Poland
    Posts
    140
    Thanks Thanks Given 
    25
    Thanks Thanks Received 
    36
    Thanked in
    20 Posts

    Default

    Quote Originally Posted by CarCity View Post
    MCU : MC9S12XEQ384
    I read that :
    Corrupt D-Flash file detected! Results probably incorrect!
    VIN: WBAFG8100DL28****
    Production date: 12.12.2012
    Programming date: ff.ff.ffff
    HW-NR: 9206234 (Hardware part number)
    SW-NR: ffffffffffff (Updated part number)
    ZB-NR: ffffffffffff (Original part number)
    S: 9287252 (Original part number)

    and now need to repair this :
    Here repaired EEE
    Attached Files Attached Files

  20. The Following User Says Thank You to gif_kuba For This Useful Post:

    CarCity (17th November, 2018)

  21. #2700
    Junior Member

    Join Date
    Feb 2011
    Location
    PL
    Posts
    25
    Thanks Thanks Given 
    81
    Thanks Thanks Received 
    49
    Thanked in
    18 Posts

    Default

    VVDIPROG


    Chrysler Occupant Classification Module connection
    MC9S12DG128_Secured
    3L40K

    Chrysler OCM 56043195AT mcu 3L40K vvdiprog.jpgChrysler ocm.jpg

  22. The Following 4 Users Say Thank You to sqlkarol For This Useful Post:

    lalaina74 (17th November, 2018), lion0304 (17th November, 2018), Perryking (19th November, 2018), PocketHero (17th November, 2018)

 

 

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.