How difficult would it be to activate OEM alarm and do a LCM reflash for OEM LED tail light retrofit?
Easy! Just add the corresponding FA`s to your modules and that`s it.
My NCSdummy no longer works, ever since instaalling it on my IBM t42 it keep giving an error when I try to load the E60 chassis, basicly it`s saying it cannot load SWTFSW05.DAT and SWTPSW05.DAT.
BLooD30: Please always provide an NCS Dummy log (right click the log, click "Copy Log" from the menu and paste here). Also have a look in the "NCSEXPER\DATEN\E60\" folder and verify the "SWTFSW05.DAT" and "SWTPSW05.DAT" files are actually there. If not, your NCS Expert installation is corrupt.
[ ] 17:00:28 NCS Dummy 0.4.0.0 beta 2 launched.
[ ] 17:00:28 Successfully loaded 2236 translations from "Translations.csv".
[ ] 17:00:28 Selected path to NCS Expert DATEN folder "C:\NCSEXPER\DATEN\".
[ ] 17:00:28 Successfully loaded 17 supported chassis.
[ ] 17:00:37 Selected chassis "E60".
[E] 17:00:37 An error occurred while reading function keywords from "SWTFSW05.DAT": Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
[E] 17:00:37 An error occurred while reading parameter keywords from "SWTPSW05.DAT": Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
[ ] 17:00:37 Successfully loaded 385 modules.
Thats what i get, the two files are are defiantly in my E60 daten folder.
BLooD30: You must install Microsoft .NET Framework 3.5 Service Pack 1. That will fix the problem.
Hello Revtor,
I have registered in this forum especially because of your tool. I didnt used it (Im a beginner) but sounds very interesting. Correct me if Im wrong but my understanding of your tool is as follows:
The tool shows up what parameters can be set on the selected/ read-out module. It does not modify anything.
If this is correct my question is: Do you intend to make the tool more user friendly?
My suggestion would be to implement an interface which shows the parameters and the possible settings like in PA Soft (for example by using radio buttons), so that the user can select what he wants to code and generates an MAN-File file with NCS Dummy for NCS Expert.
Is this something what you would like to do?
no man file...nettodata
Yes, that's correct. NCS Dummy only interprets NCS Expert data and trace files.I have been thinking along these lines, but at the moment I have very little time to develop the application - so progress is going very slowly and I cannot make promises about features like that. I'm also not sure how well this would work for modules with large numbers of functions. PA Soft's BMW Scanner only shows interesting/useful functions. I don't know what you people find interesting functions and I have very little interest in implementing a list of useful functions, so NCS Dummy would show all functions. For some modules with hundreds and hundreds of functions (of which only a fraction is really useful), that would really clutter the output. Further there's the fact that many functions have parameter keywords like "wert_01", "wert_02", "wert_03",... which are completely meaningless. You can't use the current translation mechanism in NCS Dummy to give meaningful explanations as the meaning differs from function to function. I could add a translation mechanism that combines function and parameter keywords but it would be an immense job to fill those translations and definitely not something I would want to waste my time on...Do you intend to make the tool more user friendly? My suggestion would be to implement an interface which shows the parameters and the possible settings like in PA Soft (for example by using radio buttons), so that the user can select what he wants to code and generates an MAN-File file with NCS Dummy for NCS Expert.
Hey Revtor, I'm trying to load the "nettodat.trc" generated from my M3's cluster, and it's telling me "[E] 15:47:50 An error occurred while reading trace functions from "NETTODAT.TRC": Not a valid hexadecimal code."
I've attached the NETTODAT.TRC and the corresponding FSW_PSW. The module in question is KMB_E46M3.C24
Am I doing something wrong?
You are not doing anything wrong. This is a known bug in the current release of NCS Dummy. I was intending to provide quick updates for NCS Dummy 0.4.0.0, but due to lack of time this has been postponed - sorry. While developing the nettodata parser I did not have much sample "NETTODAT.TRC" files. The ones I had all used a single byte notation. It wasn't until later I realized there were different notations as well. It will be fixed in the next version.
To everyone reading the thread: I still welcome "NETTODAT.TRC" and "FSW_PSW.TRC" trace files. The more real-life data I have, the better I can test the application. You can mail them to . Please always include chassis and module or rename the files to "chassis-module-NETTODAT.TRC", for example "E46-KMB_E46M3.C24-NETTODAT.TRC". Thanks!
For the E46 I'm still looking for trace files of following modules: "BTM_E46.C01", "MIR.C01", "RA_CD43.C01", "SHD.C03", "SHD.C04", and "SM_E46.C01". Here's an overview of modules I'd like to get trace files of:
Type 1 (most interested):Type 2 (most interested):
- E38: ACC (C01..C02)
- E60: ACC_E65 (C06..C09), ACC2_E60 (C24..C28), LRR_60 (C50..C52)
- E65: ACC_E65 (C05..C09), ACC2_E60 (C24..C28)
- E89: ACC2_E90 (C44..C47)
Type 3:
- E53: DXC8_E53 (C01..C03)
- E60: AFS (C03..C04), AFS_60 (C05..C0B), ARS (C0B..C0F), ARS_70 (C11..C12), DSC8_RPA (C01..C04)
- E65: ARS (C09..C0F), ARS_70 (C11..C12), CIM (C03), CIM2 (C04)
- E70: AFS_70 (C04..C05), ARS_70 (C12..C13), EDCS_HL (C04), EDCS_HR (C04), EDCS_VL (C04), EDCS_VR (C04), ICM_71 (C04..C06), VDM_E70 (C02)
- E83: DXC8_E83 (C02)
- E89: AFS_90 (C04..C0A)
- R50: KMB_R50 (C04..C11)
- RR1: CIM (C03), CIM2 (C04)
Type 4:
- E38: SHD (C03..C04)
- E46: SHD (C03..C04)
- R50: SHD (C03..C04)
Type 5:
- E60: RLSS_E70 (C02)
- E70: JBBFE3R (C40), JBBFEII (C06..C0A), RLSS_E70 (C02)
- E89: JBBFE (C04..C07), JBBFE3R (C40), JBBFEII (C06..C0A)
- R56: SPEG (C04..C05)
If anyone can create "NETTODAT.TRC" and FSW_PSW.TRC" trace files for modules listed above, I would be most grateful. I don't have a single example of these types yet. I don't need all of them, but I do need at least one (and preferably a few) of each type. Please post the trace files here, or mail them to and don't forget to include chassis name and module name. Trace files of modules not listed above are welcome too, of course - more is better . Thanks!
- E38: SM_E38 (C02)
- E39: RA_CD43 (C01), SM_E38 (C02)
- E46: BTM_E46 (C01), MIR (C01), RA_CD43 (C01), SM_E46 (C01)
- E52: MIR (C01), RA_CD43 (C01)
- E53: RA_CD43 (C01), SM_E46 (C01), SM_E53 (C01)
- E83: SM_E46 (C01), SM_E53 (C01)
- E85: SM_E46 (C01)
I should have access to at least a few of those between my E46 and dad's E60, I'll see what I can find.... I hope the coding indices I have are the right ones.
I assume "cheating" by manually entering an FA and using the "CoapiGetNettoDataFromCbd" and "CoapiGetFswPswFromNettoData" functions isn't good enough for your purposes?
There is a fix already
http://storage.v12.su/data2txt12032011.rar
@revtor
Hello revtor,
I see that your address is. be
Are you Belgian? And do you speak french? (by mail not on the forum of course)
cmoimem: Sorry, English only.
stonesfan: Thanks a lot!
big thx russiane39 and revtor
keep on going!!
There is another quickfix for data2txt:
http://storage.v12.su/data2txt25032011.rar
Fixed saving of files like KMB_E85.C08 . It is not recommended for anyone, except those poor mans, who have errors with older data2txt.
This is example string, which pisses me off. I have absolutely no idea, what + could mean.
PARZUWEISUNG_DIR : {} 00000051 0001 055E {} (0F) ({+,'','',''}) 68
Revtor, maybe you have any idea ?
Bookmarks