VCM2 V86 Module Programming etc.
Register
Results 1 to 9 of 9
  1. #1
    DK Veteran
    Dunker's Avatar
    Join Date
    Oct 2009
    Location
    Yorkshire
    Posts
    1,086
    Thanks Thanks Given 
    195
    Thanks Thanks Received 
    590
    Thanked in
    274 Posts

    Default VCM2 V86 Module Programming etc.

    I've just got a VCM2 clone and installed V86 and the calibration files from V81. All patched ok. Module programming is unavailable at the moment but I have whats supposed to be the extending programming patch which I will try tomorrow. The IDS program tells me that there are no days left on the software licence but obviously the V86 patch takes care of this. The module programming patch needs applying and then apparently this needs repeating every 120 days.

    My question is this: If the software had been installed on the correct date (ie. within the first 120 days from when V86 came out - or there-abouts) would module programming have been enabled until this 120 day period ran out?

    Basically, if I set the date on my laptop to the correct date, then installed the software and V86 patch and then on every boot change the date on my laptop back to the install date, would I ever need the extended programming patch?

    The install disk only has a single file installer so there's nothing I can see there.

    Also the VCM2 I have is a 2 in 1 and has the JLR138 with it but as far as I am aware there isn't a module programming patch for this. Am I right in thinking this before I install the JLR138?
    Last edited by Dunker; 3rd July, 2014 at 10:31 PM.
    V Series TMS470 / EEPROM data - encryption / decryption, totally pwned.

    IEC 62056-21 - new discussion: sonsivri.to/forum/index.php?topic=60412.0


  2. The Following User Says Thank You to Dunker For This Useful Post:

    visavis88 (30th December, 2014)

  3. #2
    DK Veteran
    Dunker's Avatar
    Join Date
    Oct 2009
    Location
    Yorkshire
    Posts
    1,086
    Thanks Thanks Given 
    195
    Thanks Thanks Received 
    590
    Thanked in
    274 Posts

    Default

    If anyone does get one of these VCM-II and wants the module programming working from day 1 then I can confirm that installing from the right date does work. With a new install of V86 with the date set to mid February 2013, everything installs correctly and modules programming is enabled (and works - I flashed new firmware into a 2002 Focus PCM to test it).

    Does anyone know if V86 works under a virtual install of XP???
    V Series TMS470 / EEPROM data - encryption / decryption, totally pwned.

    IEC 62056-21 - new discussion: sonsivri.to/forum/index.php?topic=60412.0


  4. #3
    DK Veteran

    Join Date
    Nov 2011
    Location
    friend and friend
    Posts
    1,673
    Thanks Thanks Given 
    90
    Thanks Thanks Received 
    472
    Thanked in
    225 Posts

    Default

    if friend works perfect, no problem for intalacion tube.
    search the internet and how to get a video installation.
    works perfect.
    in the version you'll say it's demo, but is enabled to connect to the car and it works perfect, last week encode key ford focus 2009., and worked perfect.

  5. #4
    DK Veteran
    Dunker's Avatar
    Join Date
    Oct 2009
    Location
    Yorkshire
    Posts
    1,086
    Thanks Thanks Given 
    195
    Thanks Thanks Received 
    590
    Thanked in
    274 Posts

    Default

    If anyone's interested I've installed IDS and JLR on seperate Virtualbox (dynamic hard drive resizing) installs under Debian. I've tested IDS and it seems to work perfectly. The dates are frozen at the install date so module programming should work forever without any further patches. Obviously a previous session can't be restored without using backup to host shared folder but I'll have a look and see if the session save path can be altered to the shared linux folder I've set up under the install. Just need to try out JLR. Never seen a diagnostic system that is runs from a local webserver. Looks interesting though.

    If anyone gets a VCM2 with JLR don't follow the web video install guides totally. Skip the mongoose part and use the VCM2 driver on the install disk instead.
    Last edited by Dunker; 10th July, 2014 at 12:28 AM.
    V Series TMS470 / EEPROM data - encryption / decryption, totally pwned.

    IEC 62056-21 - new discussion: sonsivri.to/forum/index.php?topic=60412.0


  6. #5
    Top Poster

    Join Date
    Sep 2012
    Location
    South Africa
    Posts
    198
    Thanks Thanks Given 
    78
    Thanks Thanks Received 
    71
    Thanked in
    25 Posts

    Default

    I have another solution......

    Edit the registry file
    see "release date" - make that less than 120 days to current date

    regedit
    hkey_local_machine
    software
    Ford Motor Company
    IDS
    see file "ReleaseDate"

  7. The Following 2 Users Say Thank You to deondti For This Useful Post:

    Dunker (10th July, 2014), Talleresmalaga (19th January, 2019)

  8. #6
    DK Veteran
    Dunker's Avatar
    Join Date
    Oct 2009
    Location
    Yorkshire
    Posts
    1,086
    Thanks Thanks Given 
    195
    Thanks Thanks Received 
    590
    Thanked in
    274 Posts

    Default

    I was under the impression that it could go too far - ie. more than one check and that could then cause problems later - sort of lulls you into a false sense of security. Thanks for the info though. I'll clone an install and let the date roll on.

    The main reason I use virtualbox for things like this is I can have safe(r) internet access on the Linux box with the network pass-through disabled to the various windows installs and it only takes 10 seconds to boot into them. (20 at most for the very big ones).
    V Series TMS470 / EEPROM data - encryption / decryption, totally pwned.

    IEC 62056-21 - new discussion: sonsivri.to/forum/index.php?topic=60412.0


  9. #7
    Newbie
    Join Date
    Oct 2012
    Posts
    14
    Thanks Thanks Given 
    1
    Thanks Thanks Received 
    2
    Thanked in
    1 Post

    Default

    Quote Originally Posted by deondti View Post
    I have another solution......

    Edit the registry file
    see "release date" - make that less than 120 days to current date

    regedit
    hkey_local_machine
    software
    Ford Motor Company
    IDS
    see file "ReleaseDate"


    For those who have Windows 10 ,,,,,,,,,after searching for about 4 hours,,,,,,,the file is in a different location,
    \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Ford Motor Company\IDS

  10. The Following 2 Users Say Thank You to pdf999 For This Useful Post:

    Stelaras26 (22nd January, 2018), Talleresmalaga (19th January, 2019)

  11. #8
    DK Veteran
    Stelaras26's Avatar
    Join Date
    Nov 2017
    Location
    Skyrim
    Posts
    940
    Thanks Thanks Given 
    1,449
    Thanks Thanks Received 
    657
    Thanked in
    359 Posts

    Default

    Any who has this option disabled can use this.Tested win7 win xp.
    Attached Files Attached Files

  12. The Following 5 Users Say Thank You to Stelaras26 For This Useful Post:

    ascouser (24th June, 2022), eagleone-two (27th June, 2018), sergei5005 (24th October, 2018), Talleresmalaga (19th January, 2019), Zoltan 13 (10th December, 2018)

  13. #9
    Top Poster

    Join Date
    May 2017
    Location
    argentina
    Posts
    129
    Thanks Thanks Given 
    38
    Thanks Thanks Received 
    7
    Thanked in
    7 Posts

    Default

    ?? QUE ES ESTO?

 

 

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.