Vcds ordered and should be with me shortly.

Do any of you kind briskodians have any advice for a complete novice on where to start. Is there an idiots guide etc? I have had a quick look through the ross-tech site and a few of their u tube videos. I think I need to do the following ( but please correct me if not right):

1. install latest version of software

2. Register on ross-tech for updates

3. Run auto scan on both cars and save text files as a precaution.

Any input apreciated.

Sent from my GT-P5110 using Tapatalk HD

TBH you have got the basics covered

The only thing I would add is read up on any changes you wish to make before changing them, also note where your saved logs go to… otherwise you maybe looking for them for a whilst

As you make changes, particularly using the long coding helper, make a note of what you have changed so if something doesn't work or does something unusual you can go back easily. Secondly run a scan after making changes to ensure you have not generated any new fault codes. Sometimes it will accept new coding (rather than rejecting the change) but then generate an error.

You don't have to register with Ross Tech unless you want support from them.

The cable will validate itself with the software: that will enable it to work.

I didn't contact Ross Tech for about a year after getting mine and then only because I required some coding help that was beyond me. (They were very good by the way)

Start with something 'easy' and low risk to get into it a bit. Try activating both fog lights, for example. Lots of others on this forum.

Have you purchased VCDS yet?

Have you purchased VCDS yet?

Yes

Only suggestion i'd have is before you make any changes, double save any scan logs and make sure you can open them before you make a change and when using the long coding helper i'd suggest taking a screenshot of it again saving it and making sure you can open it or write it down and double check it before you make any changes.

Remember save, save and save again before making any changes and if you REALLY aren't sure don't make the change, log onto Rosstech's wiki or ask on here.

As you make changes, particularly using the long coding helper, make a note of what you have changed so if something doesn't work or does something unusual you can go back easily. Secondly run a scan after making changes to ensure you have not generated any new fault codes. Sometimes it will accept new coding (rather than rejecting the change) but then generate an error.

I forgot to include the second scan, although I tend to just scan the controller I have made the changes to… unless I have done several code changes across several controllers, then I will do a full scan.

Its all the terminology im gona get mixed up with 'controllers' and 'coding' etc.