03-22-2015, 08:04 PM | #89 | |
Lieutenant
163
Rep 578
Posts |
Quote:
|
|
Appreciate
0
|
03-22-2015, 09:40 PM | #90 |
Major
586
Rep 1,035
Posts |
Awesome! Congrats on getting it going... thats a good feeling
I was playing around with TokenMasters NCD/CAFD tool last night and tried out the "What-if" feature that shows what needs to be coded (or what ECUs are affected) when you enable certain options, and indeed it showed that REM and HU_NBT both have parameters that need to be updated if option 507 (PDC Rear) is enabled. I guess your success confirms that his app gives correct information Last edited by squidlyboy; 03-22-2015 at 09:55 PM.. |
Appreciate
1
RayonF304.50 |
03-22-2015, 09:54 PM | #91 |
Major
586
Rep 1,035
Posts |
Your accomplishment motivated me to through the "FA(VO) Step-By-Step (MWPos) 8-24-2013.pdf" procedure again getting ready to VO code for when all my parts arrive, post-installation, and i had this question that always stuck in the back in my mind when it came to coding...
Why is it when you do the Connect to the car, sometimes you use "F10" and sometimes you use "F20" for the vehicle target selector? It just weirds me out that something can go wrong if you pick the wrong one. In this case (VO-coding), you use F10, but last night when i was reading out the entire SVT tree to back up all my ECU (cafd/.ncd) files, the TokenMaster video showed that you needed to use F20. Anyone know why its F10 in some instances and F20 in others? |
Appreciate
0
|
03-22-2015, 10:00 PM | #92 | |
General
10927
Rep 42,967
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
__________________
2018 F06 Alpina B6 650ix GC; Space Grey; Vermillion Red Nappa Leather; Executive; B&O; Driving Assistant 2017 F15 X5 xDrive50i MSport; Glacier Silver Metallic; Black Dakota Leather; Executive; B&O; Driving Assistant; RSE |
|
Appreciate
0
|
03-22-2015, 10:21 PM | #93 |
Major
586
Rep 1,035
Posts |
I probably shoulda provided more details... sorry
I have an F30. In the intro coding docs, i was told to use F10 to connect. For the first ECU i coded (ASD), it worked, no problem. On the next ECU i tried to code (i forget which now, maybe FEM), i got an error saying it couldn't read it or something, and someone told me i needed to change it to f20 in order for it to work. I did that and it worked. I'm not sure why i needed to do that, but it worked. So... at that point, i'm not sure when i need to use F10 or F20. Last night, watching TM's video on "FDL Coding for BMW F30", it said to connect using F20. In this document i'm reading on VO coding, it says to pick F10. None of what i've read has ever said anything along the lines of, "if you have a F30, ALWAYS use this, if you have .... ALWAYS use that..." It seems like it will change for the same car, depending on what ECU you are coding or for different situations. I'm kinda at a loss at when to use what in a definitive way, because it seems like the rules change randomly... And as you know, there is no F30 option in the vehicle target selection dialog. So all this time using F10, i've been coding for a 5-series?? Last edited by squidlyboy; 03-22-2015 at 10:35 PM.. |
Appreciate
0
|
03-22-2015, 10:35 PM | #94 | |
General
10927
Rep 42,967
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
F001 psdzdata covers the F01/F02/F03/F04/F07 (5-Series GT is an F07 NOT an F10) F010 psdzdata covers the F06/F10/F11/F12/F13/F18 F020 psdzdata covers the F20/F21/F22/F23/F30/F31/F32/F33/F34/F35/F36/F45/F80/F82/F83 (There is no Z4 Fxx Chassis yet) F025 psdzdata covers the F15/F16/F25/F26/F48/F85/F86 F056 psdzdata covers the F54/F55 F56 (Mini Cooper and Clubman) I001 psdzdata covers the i3/i8
__________________
2018 F06 Alpina B6 650ix GC; Space Grey; Vermillion Red Nappa Leather; Executive; B&O; Driving Assistant 2017 F15 X5 xDrive50i MSport; Glacier Silver Metallic; Black Dakota Leather; Executive; B&O; Driving Assistant; RSE |
|
Appreciate
2
|
03-24-2015, 06:44 PM | #95 | |
New Member
2
Rep 18
Posts |
Quote:
|
|
Appreciate
0
|
03-24-2015, 07:38 PM | #96 |
Major
586
Rep 1,035
Posts |
|
Appreciate
0
|
03-24-2015, 08:21 PM | #97 |
Major
586
Rep 1,035
Posts |
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 |
Appreciate
0
|
03-26-2015, 11:36 AM | #99 | |
Major
1245
Rep 1,211
Posts |
Quote:
|
|
Appreciate
0
|
03-26-2015, 11:38 AM | #100 |
Major
1245
Rep 1,211
Posts |
|
Appreciate
0
|
03-26-2015, 12:29 PM | #101 |
Major
586
Rep 1,035
Posts |
|
Appreciate
0
|
03-26-2015, 01:31 PM | #102 |
Major
1245
Rep 1,211
Posts |
Still a work in progress. Just got the replacement Pulse Generators (that I had missed when ordering the parts before) in the mail yesterday, planning on putting them in this weekend which should let me code the DSC without any errors. I'm still not 100% sure if that will fix everything as I think there may be an issue with the Park Assist module I bought on eBay. But yes, I plan on writing up a DIY on it once I finish
|
Appreciate
0
|
04-04-2015, 04:38 PM | #103 | |
Major
586
Rep 1,035
Posts |
REM replacement notes
My Rear Electronic Module (REM) - Part #61359329700 - arrived this week, and since my retrofit cables have not come in yet, i figured i would go ahead and do the REM replacement first since its a necessary pre-requisite task. Thanks to everyone who did NOT bid on this on Ebay ... It was sitting there at $175 for the longest time, and i finally offerred the guy $125, which he accepted It had one missing mounting tab, but between one mounting tab and another mounting screw it was good enough to secure it in the battery compartment.
This particular REM is the one roxxor recommended as having all the necessary pins/connectors needed to power the PDC sensors and connect/run the data to the NBT head unit and stereo speakers. I was tempted to take apart the REM unit to see how its wired, but ahh.. was too lazy But i did take some pics of the install and wanted to share some of my install details in case anyone might find it useful during your own rear PDC retrofit. Btw... other than having to drill holes in the rear bumper, this part (replacing REM) of the overall rear PDC retrofit made me the most nervous, since its such a key part of the car and could screw up a lot if something went wrong. However, after seeing how easy it was to replace, most of those fears are gone. The whole install takes less than 15-20 minutes as there is not a lot to remove. This was one of the easiest things i've replaced on the car. However, coding WILL be required after replacing this part to get rid of an innocuous dash error and your rear windows not being able to open/close. Or you can do coding all at once after the PDC sensors are installed. More on the coding part later. Here is the removal/swap procedure:
Once you button everything back up, turn on the car to make sure everything looks the same/normal. The only thing that should show up on your dash is a warning to set the date/time on the car again and a Trunk Open warning on your dash. Don't be alarmed about the Trunk warning. You have a new REM that requires new coding to bring it up to snuff. From Rsnic: Quote:
Thanks again to roxxor for pioneering this Rear PDC Retrofit DIY thread, taking all the initial risks and paving the way for the rest of us! You did the hard work, and the rest of us are just filling in details, and enjoying the fruits of your labor EDIT: add coding info about the 'Trunk Open' warning on dash Last edited by squidlyboy; 04-18-2015 at 10:54 AM.. |
|
Appreciate
2
|
04-04-2015, 08:22 PM | #104 |
Private First Class
18
Rep 176
Posts |
Thanks for the info. I bought the REM that supersedes the 700. Hopefully it works. I took a picture for comparison and will post it when I can get the link working.
|
Appreciate
0
|
04-06-2015, 06:57 PM | #105 |
First Lieutenant
54
Rep 341
Posts |
|
Appreciate
0
|
04-06-2015, 11:06 PM | #106 | |
Major
586
Rep 1,035
Posts |
Quote:
Anyways, while i'm waiting, I just wanted to inquire about the above statement you made in your DIY procedure about pointing the connector sockets away from center of the bumper. Just curious why this is needed / why it matters? Thanks! |
|
Appreciate
0
|
04-11-2015, 04:23 PM | #107 | |
Major
586
Rep 1,035
Posts |
Quote:
I was originally debating going with a used 700 or a new 61359362394 (which is the one i think you guys bought) since the difference at the time was only about $40 difference. But when the guy dropped the 700 to $125, i couldn't pass it up. But before i pull the trigger on this brand new REM, just wanted to see if you guys encountered any compatibility issues? |
|
Appreciate
0
|
04-11-2015, 07:58 PM | #108 |
Private First Class
18
Rep 176
Posts |
I installed it to check and I have that same issue so your REM is probably ok. Maybe it has to do with coding and when everything is plugged up correctly it will work
|
Appreciate
0
|
04-11-2015, 08:20 PM | #109 | |
Private First Class
18
Rep 176
Posts |
Roxxor coming through in the clutch. I suspect we didn't do this.
Quote:
|
|
Appreciate
0
|
04-11-2015, 08:31 PM | #110 |
Major
586
Rep 1,035
Posts |
Hmm.. i'm a little confused.
I'm not sure how to generate a new CAFD for the REM without VO coding the car for the new option, which is the rear PCD sensors (option 507). However, I (we) haven't installed the PDC sensors yet... just the REM ... so it seems like its premature to do any coding yet. I'm guessing if you VO code right now for 507, you will get some kind of PDC sensor malfunction error since it won't be able to detect them. |
Appreciate
0
|
Post Reply |
Bookmarks |
|
|