rhw335i: Earlier this year I got a similar report of someone who ended up with a parameter in his trace file that did not exist in the coding index displayed by NCS Expert after reading. To be honest, I'm still clueless as to what may cause this but the error message displayed by NCS Dummy is correct: the parameter does not exist in the module description file!
There are two workarounds to process the trace file with NCS Dummy:
- Disable "Strict FSW/PSW (error on unresolved keywords) !" on the NCS Dummy "Options" tab. This will make NCS Dummy ignore non-existing keywords. I strongly recommend to enable this option again once you are ready with the trace file. If you export a trace manipulation file from NCS Dummy for coding with NCS Expert and NCS Expert trips over the non-existing parameter as well, untick the "RADIO_SDARS" checkbox in the graphical trace editor and export again.
- Open the trace file in a plain text editor and remove the "RADIO_SDARS" and "antdiag" lines. NCS Dummy should now no longer error on the file.
PS: Could you please mail the original "FSW_PSW.TRC" and "NETTODAT.TRC" trace files to? Thanks!
Update: Above workarounds would not work in this situation. As it turns out rhw335i's trace file belongs to module description file "CIC.C1A" instead of "CIC.C08" (see posts further down). After switching to this module rhw335i no longer had issues opening the trace file in NCS Dummy and recoding the car with the exported trace manipulation file. It's unclear why NCS Expert reported the wrong module, but NCS Dummy can determine the correct module with the "Filter Module by Trace File" feature (refer to chapter 3.6 in the NCS Dummy user manual).
Last edited by revtor; 05-21-2013 at 12:19 PM.
Revtor
I just noticed that my CIC FSW_PSW.TRC file in the work folder has “SPEEDLOCK_X_KMH_ MIN _COE“ and “SPEEDLOCK_X_KMH_ MAX_COE “ instead of “SPEEDLOCK_X_KMH_ MIN “ and “SPEEDLOCK_X_KMH_ MAX “ as referenced in the VIM instructions. Does that make a difference? Is DVD in Motion possible with a “CIC.C08” CIC? I also posted in the bmwcoding forum's post with the instructions for DVD in Motion.
Is ### a PM email address? I tried using it as an email address and comcast email would not accept it. Sorry if this is a dumb question.
Thanks,
Bill
Last edited by IcemanBHE; 05-12-2013 at 10:16 PM. Reason: Removed email
That doesn't matter, but is interesting nonetheless because that's in my opinion further proof that your coding index is not C08 but C10 or later...
The instructions should work for all CIC versions.Is DVD in Motion possible with a “CIC.C08” CIC?
Update: Email came through this time. Thanks!
Last edited by revtor; 05-13-2013 at 01:09 AM.
Update to rhw335i's issue:
Even though NCS Expert reported "CIC.C08" was used for reading the trace file, rhw335i's trace file was full of keywords that are not present in this module description file. Since NCS Expert cannot "invent" keywords, they had to come from elsewhere - from another module description file...
Using the "Filter Module by Trace File" feature in NCS Dummy the trace file turned out to be a perfect match for module description file "CIC.C1A". Using this module, rhw335i was able to load the trace file in NCS Dummy without errors, make changes to it, export the trace manipulation file and finally recode his car.
I'm clueless as to why NCS Expert reported the wrong module, but the SP-DATEN update rhw335i performed earlier may be involved. Anyway, if you encounter the same issue - a trace file that doesn't load in NCS Dummy using the module indicated by NCS Expert - just use the "Filter Module by Trace File" feature in NCS Dummy to determine the correct module description file for that trace file.
For more information about the "Filter Module by Trace File" feature, refer to chapter 3.6 in the NCS Dummy user manual.
So I'm hoping this isn't a question thats been asked a ton of times, but I have a 2007 e92 335i coupe I'm trying to use ncs dummy with. I've gotten ncs expert to work with my car to get the windows to auto up, but everything else I've coded hasn't worked properly. I decided I would give ncs dummy a go to try and figure it out there. When I load my trace file or man file, and filter modules by trace file, it tells me there are no modules found matching trace file. Any ideas/thoughts as to why this is happening? I have done quite a bit of searching on google and on bimmerforums site to find out why, but the only thing I can come up with is that the top of my trace file says "BAUREIHE E92" and none of the listed modules say anything about an e92 option. Only e90 like "ACC2_E90" or "AFS_90". Should I change my trace file to say "e90" instead of "e92"? I want to add my trace file so you can see if something went wrong somehow, but I'm unsure how to attach something. I just started getting into this over the past 4 or so days to no avail. I'm just trying to understand this better without bricking my car. Thanks a ton in advance!
minimac21234: My guess is that you did not create a proper trace file with NCS Expert.
NCS Expert uses the "FSW_PSW.TRC" file for other purposes as well, so most of the time the data in this file is not a valid trace file for your module(s). Please follow the instructions in chapter 6.1 ("Reading FSW_PSW.TRC and NETTODAT.TRC trace files") of the NCS Dummy user manual to create valid trace files in NCS Expert.
If you think you did everything right, mail the "FSW_PSW.TRC" and "NETTODAT.TRC" trace files toand specify what module they (should) belong to.
BMW e70 USA - translation cruise control from miles to kilometers on the dashboard (KOMBI) - ???
Hi, revtor! Thanks for a job
Would you be so kind to make program save FSW_PSW.MAN file to the current directory from ..\CFGDAT\coapi.ini which used by NCSexpert as configuration file. It would be much more convenient.
I'm starting NCS via self-made frontend which holds a database of clients with appropriate working directory for each client.
Here is a line from coapi.ini:
And that is a frontend http://e.mail.ru/cgi-bin/getattach?i...nnel=¬ype=1 - just place file in the same directory with NCSexper.exeCode:WORKING_DIR = ..\work\john.e36
Vink: Check your private messages for a test version that reads the working directory from "COAPI.INI". Let me know if it works for you.
Anyone have a mirror to ncsdummy? Revtor your site seems to be down
Update 3: The webserver is fixed and the download links should be working again. Hopefully for good this time.
Last edited by revtor; 07-14-2013 at 06:08 AM.
sorry I have the "new x1 (e84) 03/2013" and ediabias working on laptop. How do I read my drive modules with ncs expert and then manipulating them? I installed ncs expert and dummy ... thanks a lot
interkillers: All this is covered in the NCS Dummy user manual.
thank you the ncs dummy user manual is fantastic...
One question...for dvd in motion how do I know what 'my cic... i.e cic.c09 ecc...
X1 E84 2013
interkillers: Read a trace file from the CIC and NCS Expert will show the correct module afterwards. for detailed instructions, refer to chapter 6.1 of the NCS Dummy user manual.
Hey Revtor, I ran into a minor bug. When I maximize the screen on my laptop display (2880x1800 resolution), I get this error
Not a big deal; no negative effect by just hitting continue as far as I can tell, but just thought I'd let you know.
What is the code to enable the SMG shift lights on a 6MT car?
A new version has been released: NCS Dummy 0.6.0.1! Refer to the first post in this topic for the download link. What's new since the last release?
0.6.0.1 (2013-08-07)
- Fixed "MaxDropDownItems" crash at very high display resolutions.
- Fixed broken shortcut key CTRL+C to copy a single line from the log.
- Added the more familiar shortcut key F5 as an alternative to CTRL+ENTER to reload list dropdowns and path textboxes.
- Shortcut key F3 to find the next search item now also works when the focus is not on the graphical trace editor.
- Searching in the graphical trace editor now scrolls the entire function into view (if possible) instead of only the found item.
- Find window opens automatically after successfully filtering modules by keyword or order option.
- Small number of new and corrected translations.
This minor release addresses a recently reported bug that could crash NCS Dummy at very high display resolutions. Furthermore a few small user interface improvements were implemented.
Last edited by revtor; 08-07-2013 at 10:40 AM.
[ ] 10:46:26 NCS Dummy 0.6.0.1 launched.
[ ] 10:46:26 Loaded 14757 translations by revtor, IcemanBHE, joako, lolo, rdl, StefanL, rondo and LPCapital.
[ ] 10:46:26 Loaded NCS Expert DATEN folder "C:\NCSEXPER\DATEN\" with 14 chassis.
[ ] 10:46:27 Loaded chassis "E39" with 220 modules.
[ ] 10:46:35 Loaded module "GM3.C04" with 109 functions, 3 properties and 9 unoccupied blocks.
[E] 10:46:45 An error occurred while reading "C:\NCSEXPER\WORK\FSW_PSW.TRC": Unresolved function keyword "LASTBEREICHSKENNFELD". Make sure chassis and module match those of the trace file.
AM GETTING THIS ERROR MESSAGE AFTER HAVING CHOOSE MY CHASIS AND MODULE AND MY FSW/PSW TRACE FILE
WHAT SHOULD I DO ??
You need to select car/module to match your trace file.
Hi all,
just started with coding, found NCS Dummy, very helpful, thanks a lot!!!
Everything works fine, however, one question:
On a X5 I get an "1 erroneous parameter" message when loading KMBI_E38.C12 into NCS Dummy.
- how can I find which parameter is erroneous in the editor?
- is this critical? are the module-data wrong, or is it a problem of this module? I expect the module-data, as at this point NCS Dummy does not know anything about the car...
Have been searching for this in the manual and in the forum, didn't find anything...
Thanks in advance!
Alfredo
Bookmarks