[Shazsta]

Yea I think it's best just to wait for all the parts to come in then do it.

[roxxor]

The problem I believe is that if you install the new module without coding it, it in essence doesn't know what options you have, which might be why you are getting that error. You could always create the CAFD then VO code it without the PDC, then go back and recode it after the parts come in.

[squidlyboy]

Originally Posted by roxxor

The problem I believe is that if you install the new module without coding it, it in essence doesn't know what options you have, which might be why you are getting that error. You could always create the CAFD then VO code it without the PDC, then go back and recode it after the parts come in.

Please ignore my PM to you earlier... i didn't see you had responded.

So i take it you never encountered this issue then? I guess if you installed everything at once and did your VO coding immediately after, it just took care of itself.

Back to the coding though .... I always thought that the new CAFD file gets created automatically when you VO code the new rear PDC option. I guess i don't know how to create a new CAFD file for this new REM by itself, so to speak. How do you go about that?

[RSnic]

SquidlyBoy & Shazsta,

Thanks to advice from Shawn Sheridan, when I replaced the REM in my car, I injected CAFD into the REM ECU; to do so, after connecting to car with E-Sys

• Click on READ FA/VO
• Right Click on FA/VO and ACTIVATE FA/VO
• Click on READ SVT(VCM)
• Left Click on ECU (not the associated CAFD)
• Cleck on DETECT CAF FROM SWE
• Select CAFD matching car's I-Level
• Select OK

That will bring the REM into line with the rest of the car; then you can VO Code it

[Shazsta]

Cool, thanks!

[squidlyboy]

Originally Posted by RSnic

SquidlyBoy & Shazsta,

Thanks to advice from Shawn Sheridan, when I replaced the REM in my car, I injected CAFD into the REM ECU; to do so, after connecting to car with E-Sys

• Click on READ FA/VO
• Right Click on FA/VO and ACTIVATE FA/VO
• Click on READ SVT(VCM)
• Left Click on ECU (not the associated CAFD)
• Cleck on DETECT CAF FROM SWE
• Select CAFD matching car's I-Level
• Select OK

That will bring the REM into line with the rest of the car; then you can VO Code it

Woohoo that worked! Error gone - I owe you a beer brutha! Dayum... I almost returned the REM

[squidlyboy]

This is just for my information, but when you do a Detect CAF from SWE, how does it know to create the new CAF file for the new 700 REM and not my old 702 REM?

Because when you do a Read SVT, you are reading the ECU's based on your generic VO (vehicle Order) and at no time does it actually probe the hardware ECU in the car and say, "ah this is a 700 and not a 702 so lets create the CAF for a 700"

When does E-Sys probe the car and detect that there is an actual 700 there and not the default 702 that came originally with my factory VO?

[Chris@codemybimmer]

Originally Posted by squidlyboy

Man.. i'm getting impatient waiting for all my parts to arrive Everybody's done with their retrofit already or finishing up their coding... dang.

I only just got my metric step drill bits in and my Vata-Pro sensors (Ebay) today. I was hoping the default white paint that they used on the sensors would match Alphine White, but alas, its way brighter, so it would really stick out. Good thing i ordered some Alpine White touch up paint/cc. I'm not good with painting where the goal is a thin even layer... esp when the touch up paint tube is like a bottle of white-out with that little useless brush. I already read what roxxor and steelerfan did - any other tips you guys have for getting a good even coat would be appreciated.

I decided to drill a practice hole this afternoon while i'm waiting. One good thing i found out is that an 18mm drill step bit creates the PERFECT sized hole. I lucked out too. The drill bit i used had the 18mm step as the last one on the drill bit, so i didn't really have to think about it - I just drilled straight to the end and pushed it through. I practiced on a peg board and i was pretty amazed how perfect and snug the sensor was against the hole BOOM

How close is the white color of your PDC to alpine white?
i just installed everything and it looks like the Sensors i got off Ebay were duds and i got to get new ones.

[squidlyboy]

Originally Posted by 1lyfe

How close is the white color of your PDC to alpine white?
i just installed everything and it looks like the Sensors i got off Ebay were duds and i got to get new ones.

The white on the sensors are noticeably brighter white than AW (#300), so i'm going to have to paint them with some BMW touch up paint.

In what way were they duds... just the color you mean? Or are they functionally not working?

[Chris@codemybimmer]

Originally Posted by squidlyboy

The white on the sensors are noticeably brighter white than AW (#300), so i'm going to have to paint them with some BMW touch up paint.

In what way were they duds... just the color you mean? Or are they functionally not working?

Im not 100% sure if its the sensor problem but it updates extremely slow.
as in when it wont sense anything unless its been for 2 - 3 seconds
example:
go into reverse
PDC shows up on screen.
someone walks past my car (not running) it wont pick anything up at all.
but if you walk up to the car and stay they for about 2 seconds it will show up on the screen.

[Chris@codemybimmer]

But it could also be because i got my body shop to paint the PDC while they were painitng my bumper so it matches color

[squidlyboy]

Originally Posted by 1lyfe

Im not 100% sure if its the sensor problem but it updates extremely slow.
as in when it wont sense anything unless its been for 2 - 3 seconds
example:
go into reverse
PDC shows up on screen.
someone walks past my car (not running) it wont pick anything up at all.
but if you walk up to the car and stay they for about 2 seconds it will show up on the screen.

oh man I hope these weren't the VataPro ones, which are the ones i got ...

[Chris@codemybimmer]

Originally Posted by squidlyboy

oh man I hope these weren't the VataPro ones, which are the ones i got ...

looking at my purchase history is was vatapro...
but the black ones...if that makes a difference =/
I bought the black ones cause they went on sale for 12$ per piece
Maybe the paint over the black has something to do with it. ill try sanding the paint off and see if its any better

[squidlyboy]

Originally Posted by 1lyfe

looking at my purchase history is was vatapro...
but the black ones...if that makes a difference =/
I bought the black ones cause they went on sale for 12$ per piece
Maybe the paint over the black has something to do with it. ill try sanding the paint off and see if its any better

You scored a great deal... i'm wondering if sanding/repainting them affects the performance. Roxxor didn't think so for the ones he got although he went OEM

Originally Posted by 1lyfe

Im not 100% sure if its the sensor problem but it updates extremely slow.
as in when it wont sense anything unless its been for 2 - 3 seconds
example:
go into reverse
PDC shows up on screen.
someone walks past my car (not running) it wont pick anything up at all.
but if you walk up to the car and stay they for about 2 seconds it will show up on the screen.

I'm just curious for those of you who purchased BMW OEM PDC sensors or had PDC installed as a factory option, what kind of delay/lag do you see with your PDC sensors?

[Chris@codemybimmer]

Originally Posted by squidlyboy

I'm just curious for those of you who purchased BMW OEM PDC sensors or had PDC installed as a factory option, what kind of delay/lag do you see with your PDC sensors?

my friends f30 has zero delay
you can run past the pdc and it will still pick it up

[squidlyboy]

Originally Posted by 1lyfe

my friends f30 has zero delay
you can run past the pdc and it will still pick it up

Dayum - see this is the kind of thing you definitely WANT to pay OEM prices for. PDC (ultrasonic) sensors are definitely not a commodity part.. yet

[RSnic]

Originally Posted by squidlyboy

This is just for my information, but when you do a Detect CAF from SWE, how does it know to create the new CAF file for the new 700 REM and not my old 702 REM?

Because when you do a Read SVT, you are reading the ECU's based on your generic VO (vehicle Order) and at no time does it actually probe the hardware ECU in the car and say, "ah this is a 700 and not a 702 so lets create the CAF for a 700"

When does E-Sys probe the car and detect that there is an actual 700 there and not the default 702 that came originally with my factory VO?

SquidlyBoy,

By Injecting CAFD, you get a twofor, so to speak. First,the CAFD now fits within the I-Step of the car; secondly, the codes in the selected module will be set to those in CAFD you selected from your computer and it reads the ECUs heading data, I believe, to figure out what hardware version of the module it is. When you read SVT, believe the CAF file used is the one that has the coding settings currently in that ECU module.

Hope that helps

[RSnic]

Originally Posted by squidlyboy

Dayum - see this is the kind of thing you definitely WANT to pay OEM prices for. PDC (ultrasonic) sensors are definitely not a commodity part.. yet

Might be a bad batch or something; I have black (originally) and have not had a problem.

Also, it just might be how much paint is on the face -- have been told that the paint has to fairly thin or it "desensitizes" the sensor, BUT, that maybe folklore???

[f30GTR]

Crap, I was just getting ready to paint mine today. I guess I'll do one coat then.

[roxxor]

Originally Posted by squidlyboy

Please ignore my PM to you earlier... i didn't see you had responded.

So i take it you never encountered this issue then? I guess if you installed everything at once and did your VO coding immediately after, it just took care of itself.

Back to the coding though .... I always thought that the new CAFD file gets created automatically when you VO code the new rear PDC option. I guess i don't know how to create a new CAFD file for this new REM by itself, so to speak. How do you go about that?

HA! Same back to you, I just responded to the PM before reading the updates on the thread, so you can disregard my PM as well lol.

[squidlyboy]

Originally Posted by RSnic

Might be a bad batch or something; I have black (originally) and have not had a problem.

Also, it just might be how much paint is on the face -- have been told that the paint has to fairly thin or it "desensitizes" the sensor, BUT, that maybe folklore???

Maybe i'll install them as is (no painting)... for now, just to get a data point to see if it makes any difference at all. If the lag still exists, and the color difference really bothers me, i could potentially try to paint them in place.

[RSnic]

Originally Posted by squidlyboy

Maybe i'll install them as is (no painting)... for now, just to get a data point to see if it makes any difference at all. If the lag still exists, and the color difference really bothers me, i could potentially try to paint them in place.

SquidlyBoy,

Sounds great; if the lag goes away, then the "folk lore" may be right -- in which case, a light coat of paint may still be OK.