|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Today's Posts | Search |
|
BMW 3-Series (E90 E92) Forum
>
Nettodat = Fsw_psw?
|
|
01-26-2013, 06:05 PM | #1 |
Lieutenant
32
Rep 447
Posts |
Nettodat = Fsw_psw?
Hi. Quick and potentially slightly stupid question.
I can code a module using the FSW_PSW file, --> or I can code the SAME module using its related NETTODAT. QUESTION: When I code a module using NETTODAT, is that effectively setting all the same switches as if I did the same settings in the FSW_PSW file? I'm thinking yes, but wanted to check. |
01-26-2013, 07:55 PM | #2 | |
Captain
72
Rep 838
Posts |
Quote:
|
|
Appreciate
0
|
01-26-2013, 08:15 PM | #3 |
Lieutenant
32
Rep 447
Posts |
Same here.
I'm thinking the NETTODAT is basically just a numeric representation ("compiled" version if you wish) of the human-readable FSW_PSW file... but wasn't 100% certain. Sitch is: I de-coded my car prior to service (over-cautious.. I know) and want to re-code all my modules, 1 at a time. One of them, NFRM (FRM2), has non-standard NETTODAT settings for the 4-click turn signal. So I was wondering... do I need to code the backed up NFRM *and* the NETTODAT... or just the NETTODAT because it does all of NFRM *plus* it fixed the non-standard hex bytes for the turn signals. Mmeh. What the heck, I'll just give it a try with NETTODAT only and see if all the changes stick! Simple enough. |
Appreciate
0
|
01-27-2013, 01:05 PM | #4 |
Lieutenant
32
Rep 447
Posts |
For reference, for anyone stumbling on this via a search.
I just recoded a handful of modules using their backed-up NETTODAT files instead of creating a .MAN file for each one. They all worked (one at a time) except ABG which wouldn't talk to its backed-up NETTODAT, so I coded it with the backed up FSW_PSW file normally. Coding from a backed-up NETTODAT is a little easier (especially if you have more than 1 to do) because I don't need to copy/rename each FSW_PSW file to .MAN and Change_Job to SG_Codieren and all that, just code directly one-step from NETTODAT (*Note: NCS seems to need old-school less-than-8-character long file names for NETTODAT.TRC. It didn't like it when I had names like NFRM-NETTODAT.TRC, but "NRFM.TRC" worked fine). Also - don't forget to change your selected ECU between coding! Fyi - seems like most modules CAN be coded directly from their NETTODAT (easier when backing up/restoring)... but not all. |
Appreciate
0
|
Bookmarks |
|
|