Skip to content

Radio & Navigation fault code in CAN Gateway

Featured Replies

Hi,

I've done a few searches for this but not found an answer yet, so here goes!!

I've removed the MFD 2 from my octy 2 vRS & replaced it with a Columbus :D. Very pleased!

vrStu helped me code it in, and it seems to work ok.

I get the fault code come up for the missing second aerial, which I know about, however in the Can Gateway I keep getting the following:

2 Faults Found:

1300 - Control Module for Navigation with CD-Rom (J401)

004 - No signal/Communication - intermittent

Freeze Frame:

Fault Status:00100100

Fault Priority: 2

Fault Frequency: 7

Reset Counter 134

Mileage 56373 km

Time Indication: 0

Date: 2000.00.00

Time 15:06:50

01304 - Radio

004 - No Signal/Communication - Intermittent

Freeze Frame:

Fault Status:00100100

Fault Priority: 2

Fault Frequency: 7

Reset Counter: 134

Mileage: 56373

Time Indication: 0

Date: 2000:00:00

Time: 15:06:50

I'm guessing here that it is recognising that the old MFD2 is no longer there, but how do I stop it from continuing to report this as a fault? Is there a way of telling the CAN gateway that the Controler is no loner there or deleting it?

Cheers!

Bruce

Check your connections for the phone, make sure that is not causing a break in the CAN communications. You'll need to take the radio out to check this but it's possible that a wire has been trapped/pulled when you did the swap over.

You get it twice because the Radio & Nav on the Columbus are the same controller.

Shouldn't be connected to the removal of the MFD2.

  • Author

Cheers Stu, that makes sense. I'll check it out. Would this affect how things work as I can't say Ive noticed any problems?

I get the same Bruce and I also did the swap from MFD2 to Columbus.

Hopefully a very nice man will take a look in the very near future. ;)

  • Author

Thanks guys, just checked the back of the set, couldn't see anything which was trapped or loose, but It seemed to go in much easier this time! Will have a "pootle round" in a bit & check it again!

Let me know if you find out what caused it on yours

The only other thing that I can think of is the Gateway support for the Columbus, obviously the Columbus is quite new and I know Ross-Tech had to make some changes to VAG-COM/VCDS to allow communication with the Columbus.

does this mean a mfd2 is up for grabs

does this mean a mfd2 is up for grabs

I think you missed the boat on both counts there.

  • Author

Hmmm. Yeah, that could also be true. I'm booked in for a 40K service on Saturday, so I will ask the master tech if it needs updating.

Will plug in Vag com later when I've done a few miles & see if it crops up again.

oh well

Hmmm. Yeah, that could also be true. I'm booked in for a 40K service on Saturday, so I will ask the master tech if it needs updating.

Will plug in Vag com later when I've done a few miles & see if it crops up again.

What year is your car Bruce?

  • Author
does this mean a mfd2 is up for grabs

Sorry, it went in a matter of hours!

  • Author
What year is your car Bruce?

'06 registered on a 55 plate that Jan, so I reckon it is an early one

'06 registered on a 55 plate that Jan, so I reckon it is an early one

Hmm - Could tie in with the gateway theory then. There is lots of talk about early VW's needing CAN adaptors just to get the units working.

All PQ35 (i.e. Golf 5 and Octavia 2) based models use the same sort of CAN databus. The difference you are supposedly referring to is TP1.6 (like it is being used in the PQ34 (i.e. Golf 4 and Octavia 1) versus TP2.0 in the PQ35 (TP stands for Transport Protocol). There is no need for any sort of adapter in this case.

However, to finally answer the original question we've seen these codes a couple of times now and as far as we can tell this is a common issue with the RNS510/Columbus. Under certain circumstances the unit seems to timeout on requests/messages from the Gateway which then creates this fault code. It is possible that newer gateway software versions have a higher threshold regarding this timeout but at the end you can just ignore those communication codes unless you actually have functional issues which you can track down...

Thanks for clearing that up Sebastian

  • Author

Just spoke to our dealer, latest software updates came in last week, so have asked to have it checked out as the last update it had was 2 years ago when it had the standard Stream HU!

Only downside, have had to put it off until 31st as they are now overbooked.

As i've now got the car on Saturday, I might get the modding done that i've been planning:thumbup:

Software update for what (i.e. which control module)? :)

  • Author
Software update for what (i.e. which control module)? :)

Not sure, it sounded like a "service pack" kind of thing as he said it contained the "latest updates and all previous ones in one". Anyway it hasn't been plugged into VAS for a long while, so it will be interesting to see what happens!

Might be worth saving a full autoscan so that you can see what has been updated.

  • Author

Yeah, I saved one with the faults on it from today, so should be interesting to what if any changes they make.

Mine is due at the dealers next Tuesday so I will ask if there are any updates that can be applied to an '06 car.

I am guessing if VAS is plugged in it will see the Columbus and do the necessary.

Just as long as it doesn't update the ECU.;)

Just as long as it doesn't update the ECU.;)

Yeah that might be a little troublesome eh ;)

If you don't want a reflash you have to inform the dealer, if not and the update fails due to a remap you gotta pay for the new ECU yourself. ;)

Bit of a long story to tell here Sebastian. ;)

Lets see what Tuesday brings.

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.