Hello,

I have a 2019 GLC 63 S, front camera lens was damaged by a rock on the road.

i purchased a new camera at the dealer installed and no display, black screen and camera image with red circle with line through it.

fault code first came up as wrong scn coding I believe, (this was a while ago, I reinstalled the cracked camera and life got busy so pushed it off till now)

in the mean time I have purchased an autel maxisys ultra s2, tried to back up and restore camera module hoping it would write the original SCN coding to the new camera but it did not.

tried to remove internals from original camera and install into new housing but I noticed the photo eyes on the boards are different so I’m assuming the lens is different and therefore camera calibration fails every time. Same part number seems like it’s just a newer design.

new camera installed now shows fault for General Electric fault for front camera on every diagnostic tool I own including xentry offline, not sure why the fault is different from the SCN fault I was getting before but it was like this before I did the module reprogramming with the S2, I’m assuming this fault is still for the SCN coding not done on the new camera

I am wondering if anyone would be able to guide me through the coding procedure with DTS Monaco 8.16 which I have installed on my laptop, I have never used DTS Monaco and I have a hard time wrapping my head around CBF/SMR-D files and how to retrieve them, etc. I would like to learn how to use the program more than I want to just let the dealer do it or pay someone to do it remote.

in my head if I can just copy the programming from the original camera and write it to the new camera this should work no?

let me know if there’s any further questions, I can obviously pay for your time.

 

send a message to forum sponsor @BenzNinja for his professional expertise to code your new camera for you.

 

I believe you are right and if you read the old camera variant codes you should be able to write them to the new camera.
If you have the full software with Xentry and all it's not to hard to do with a little help. And the files are easy to come by so that's no problem. I will try to help you if I can.

Do you have Xentry?
Sorry I just saw you have Xentry in your post.

I'm on night shift this week so I'll post some pictures but it'll be after 5 central time.

Let's start with this. Open Xentry and after it loads up and does it's vehicle I'd. Go to the left side where the icon looks like a bunch of computers like in the photo. This is the can bus section. Click on the + symbol in the can bus one at a time until you find the can bus for your camera and click on the box for the module. You will see a pop up like on the right side in the picture. This will tell you what file you need to load too communicate with the module in DTS Monaco. The in in the example picture I posted is module DRVU_NG.

You probably have the correct filter on your computer just open windows file explorer and click the drive your software is on and at the top right search for *.cbf and you should get a list of files. Find the one that matches your module you read from the can bus and copy that file to the desktop to keep it simple.
When you get that info take a screen shot press the windows key and the print screen key and it will put a screen shot in the pictures folder then in a screenshot folder it just created. Will will be taking screenshots to translate the text from German to English if we need to. After the screenshot in Xentry clear any codes once and you can close Xentry.

Also what vehicle connection do you have? Because I don't think Cbf files work with openport and DTS Monaco.


Example pic from Google

.

I'll post pictures from DTS Monaco later when I get back to work.

 

Thank you! I appreciate the help big time!

im currently working out of town right now but I will be back on Friday this week, wanted to get a jump on what do when I’m back.

The Monaco 8.16 I got online is currently configured for VCX SE which I have and says it does DoIP (haven tried this) , I also have a Texa multihub j2534 pass thru device and has DoIP as well but I would have to figure out how to configure Monaco for this.

And a launch passthru tool but I’ve heard mixed reviews. I usually reach for the Texa or VCX anyways.

I can post screenshots when I get back.

 

Sounds good and it's good your not impatient or in a hurry cuz there's is always lag in a forum.
Sounds good just updated when you can.

 

@RobertR728 Here is where im at so far

 

Okay so we now know what file we need to access the N148 module which is the camera and the file needed is SVS205. This can be a SMR-D or CBF type file. They are probably on your install drive that Xentry is on already. In file explorer at the top right in the search box type *.smr-d and *.cbf to find those folders. I like to copy the complete smr-d and cbf files into a desktop or the root folder so they are easy to get to. Don't worry if you don't see them ill send you the file if needed. Those files well need in a bit for DTS Monico or Vediamo. The folder will be something like this C:\Program Files (x86)\Mercedes-Benz\Xentry\MB_PKW\Caesar\cbf or C:\Program Files (x86)\Mercedes-Benz\Xentry\MB_PKW\Caesar\SMRX.

Okay so back to Xentry for a min before we get to far copy the module HW/SW info from Xentry for both cameras. In Xentry jut find the module were looking for N148 and double click it to get its info page hit print and print to PDF and put those files on the desktop too. Do this step for both cameras but start with the old camera and you can get the new camera info after we read the old one you will put in the new camera then well read and save the new camera.

Another issue i see are some can buss errors. So in Xentry back to the can buss page. Lets click on each red + to see what module or modules have buss errors and maybe clean those up if possible. Lets see what they are first since its not advisable to flash a module that is throwing codes. Im also curious what codes the new camera might throw and if those clear. If not will they clear if when you have the old camera hooked up.

Once all that is done and we know you've found your files we can move on to DTS Monico. I think its a little more user friendly than Vediamo.

Also I am in simulation mode cuz I don't have that camera so mine might look a bit different but will be very close. I think ill work on some screen shots for the next post

 

Once have the file and know what the can buss problems are well save the original coding from the old camera.

PICS
1 DTS start page choose temporary workspace
2 bottom right of pop up window you choose your file type. This one is SVS205.smr-d
3 Load the diagnostic can for the module file you used. We choose smr-d
4 Quick start tab check all the boxes and hit start. Should return all green with no errors
5 Quick start tab at the bottom where it says FNAS report save that file
6 Variant coding tab connect
7 Variant coding tab be sure all 3 boxes say all domains
8 Variant coding tab save the variant file
9 Complete vehicle coding tab click read then start. It should return all green no errors. The picture shows a fail reading because I'm in simulation mode
10 Complete vehicle tab click save

What we have just done is save all the coding from the old camera. Well repeat all these steps with the new camera too but after we look at the can buss errors

So far we have changed nothing and only did reads

 

Fault code here is about calibration. This is old fault code and now you have General Electric Fault?

 

Hello trigital
Good I'm glad someone with more knowledge than me chimed in. Yes were trying see why the code changed after he took apart the new camera. He works so his response time is delayed.

 

@trigital yes, old fault code with new camera plugged in i believe used to be wrong SCN variant or something along the lines of that, i could also be wrong about this, it has been months since i first tried to swap the cameras, mightve even been a different car, i work on quite a few MB vehicles in my spare time so stuff like this all kind of blends together lol

now with new camera in, it is general electrical fault (this happened before i tried coding/programming with Autel or splitting the cameras apart, i have another new aftermarket camera and a spare used camera in my shop, they all throw general electrical fault code on my personal car, the spare used camera i know for sure works with the car it came from, lens is just pitted.

calibration fault is from me putting the guts of my original camera into a brand new housing, photo eye is different on the new cameras so im guessing the lens is different thus not allowing me to complete calibration, (fails every time, picture is also a bit more fish eyed now than it used to be, assuming all this obviously)

@RobertR728
can faults are unrelated, i have an aftermarket carplay module in my car that causes that issue,

other faults are for oil pump solenoid (no cel, so i wont worry about this, benefit in my eyes as it defaults to higher pressure)

also have a couple faults for an aftermarket steering wheel (no heat feedback from wheel to SCM, and lane assist malfunction as no vibration motor is installed in the aftermarket wheel, waiting for an encoder module to come in to solve the wheel faults)

i tried to open up SVM205.cbf in temp workspace with my VCX SE plugged into the car yesterday however it said it failed to connect to interface so i think you're right about not working with CBF files.

looking for SMR-D file now and will try that, ill grab xentry screen shots with both cameras here in a bit

 

Take into account that SVS205 means Surrounding Viewing System aka 360... So you diagnosed the module responsable for all cameras. General Electric Fault mens anything but not coding.

 

@trigital i understand the module svs205 is responsible for all the cameras, i am confused about programming further than that ie: for each camera, could it be that the SCN coding on the SVS205 module in my car is too old to work with these new updated cameras? and that these cameras are not actually programmed to the car?

i thought i read about a forum a while ago where the camera had to be coded and was throwing mismatched scn coding mismatch fault, now reading it again OP was able to attain a new CBF file and coded to to car to fix problem.

 

The Xentry is pragmatically translated from German language.

German language is an explicative language.

Each word has mainly just one meaning.

For example, "calibration" is about.... calibration, nor coding, nor hardware testing.

Or, General Electric Fault is always about wires, connectors, defective camera.

If you can return to the Missing Calibration fault code, I can teach you how to translate further ( simple ) test routines with Xentry..


Autel, Launch or any Generic tools are based on generic tests or routines and sometimes is OK. But is far from being "exact" as MB has as a policy.

 

@RobertR728 i talked to the guy i got monaco from, he said only smr-d with VCX.

i found the SVS205.smrd in a similar path to the one you mentioned. copied to my desktop.


i talked to a buddy who is a tech for MB dealer here in Canada, he said most of the time they just have to do camera calibration after new camera is in, sometimes they have to update camera module.

with that information i have another question.
is there any way to find the latest SCN coding for SVS205? and then flash that via Monaco? maybe this will fix my issue?

 

Yes you can pretty easily find the current software but flashing that without having your variants saved could make it useless.

In DTS you can load that file you have and do all the steps I mentioned above as you are only reading and communicating with the module not writing to it.
If you're unable to read the module without errors then you won't be able to write to those areas that have errors either. That basically bricks the module so it's not recoverable.

So feel free to load that file up and click and change any settings you want to or just look.
Add long as you don't hit write or hit do coding it won't write and a simple reset it's back to how it was.

 

If your current issue is Electric Fault, I would continue diagnosis.
Xentry is a diagnosis system, not just a Fault code reader. It can help you step by step you only have to press "Continue" before reading the notes.
Coding a defective item is almost impossible.