[dpaul]

That’s not it. The OP has repeatedly mentioned that INPA works fine.

[elthox]

Originally Posted by dpaul

That’s not it. The OP has repeatedly mentioned that INPA works fine.

Inpa can work. But with NCS could be different. I`ve seen cases throwing Coapi error because of latency.

[dpaul]

Originally Posted by elthox

Inpa can work. But with NCS could be different. I`ve seen cases throwing Coapi error because of latency.

Never seen a situation where INPA would work properly with improper latency

[elthox]

Assuming daten files are ok with a proper version and car modules have no problem, i dont see any other reason except port settings.

[dpaul]

Originally Posted by elthox

Assuming daten files are ok with a proper version and car modules have no problem, i dont see any other reason except port settings.

Well, simple enough for the OP to check.

[herqt]

Originally Posted by elthox

Assuming daten files are ok with a proper version and car modules have no problem, i dont see any other reason except port settings.

I can screenshot the port settings theres even a video step by step how to install bimmergeeks tools, pdf files with installation instructions, i know ive done everything correct u can find my posts on other forums aswell. I know ive done everything correct double checked everything tryied to install uninstall using different options, its not the installation problem, i even tryied vmware with russian ncsexpert tools all included loading win xp windows machine with everything ready checked that latency of com port 1 is 1 drivers are up to date, theres nothing else left to check. The problem is somewhere else i even found threads in other forums about same problem that somehow their car vo/fa got deleted or somethingn that ncsexpert cant read fa/vo and they somehow restored it by fa.ssd we were talking about it before in this thread. My car modules working fine. But i vant code anything cuz of that vo/fa reading shit. Latency 1 is the first thing ive checked

[elthox]

What happens when you access cas and frm via INPA? Can you read them and their info?

[herqt]

Originally Posted by elthox

What happens when you access cas and frm via INPA? Can you read them and their info?

what exactly should i try to read from cas on impa? identification and stuff works idk what do u mean, try to eject cd from ccc throw inpa? works also.

[herqt]

So just tested my setup on e46 and ncsexpert works fine reads fa, can code, so my cars vo will be broken for sure...

[dpaul]

So did you try using an ssd file?

[herqt]

Originally Posted by dpaul

So did you try using an ssd file?

nope, scared to fuk up everything, ive no idea about the codes with $747 or some stuff how to make my cars fa. i know there goes #1206 -date of car, then should go color and then codes of the modules inside car. and vin decoder shows some random codes.

[dpaul]

Originally Posted by herqt

nope, scared to fuk up everything, ive no idea about the codes with $747 or some stuff how to make my cars fa. i know there goes #1206 -date of car, then should go color and then codes of the modules inside car. and vin decoder shows some random codes.

Seems you're at an impasse then.

The only thing I can say is that you can't permanently fuck anything up by coding. Your vehicle is going to start and run no matter what you do. The worst that can happen is some options won't work correctly.

I would start by writing the VO to the CAS using an ssd file and just seeing if you can read it back. Just to see if this method of restoring a VO actually works.

Whether the CAS has a readable VO after the ssd trick or not, nothing is going to change about the way the car works until you default code a module (i.e. have NCSexpert set parameters in that module based on the VO it obtains from the CAS). Since you can't change any coding now because NCSExpert can't obtain a VO, you have nothing to lose. And you still have the presumably untouched although currently unobtainable copy of the VO in the NFRM.

[herqt]

Originally Posted by dpaul

Seems you're at an impasse then.

The only thing I can say is that you can't permanently fuck anything up by coding. Your vehicle is going to start and run no matter what you do. The worst that can happen is some options won't work correctly.

I would start by writing the VO to the CAS using an ssd file and just seeing if you can read it back. Just to see if this method of restoring a VO actually works.

Whether the CAS has a readable VO after the ssd trick or not, nothing is going to change about the way the car works until you default code a module (i.e. have NCSexpert set parameters in that module based on the VO it obtains from the CAS). Since you can't change any coding now because NCSExpert can't obtain a VO, you have nothing to lose. And you still have the presumably untouched although currently unobtainable copy of the VO in the NFRM.

Will give it a try, btw tested istap yesterday, it also couldnt read VO.

[elthox]

What if....your central module aka JBE (referring to my e91) is somehow defective, and blocking communication? If you have experience with ista+, you would see the diagram how modules connect. Everything pass through JBE. I also experienced a similar event few years back with my e46. Kombi was defective and not allowing to read ZCS, even if it was functioning ok. After changing with a used part, everything was accessible.
If you have a chance of finding any used JBE module for testing, give it a try.
If theory is true, then try to flash your module and see what happen.
Merry Christmas!

[dpaul]

Originally Posted by elthox

What if....your central module aka JBE (referring to my e91) is somehow defective, and blocking communication? If you have experience with ista+, you would see the diagram how modules connect. Everything pass through JBE. I also experienced a similar event few years back with my e46. Kombi was defective and not allowing to read ZCS, even if it was functioning ok. After changing with a used part, everything was accessible.
If you have a chance of finding any used JBE module for testing, give it a try.
If theory is true, then try to flash your module and see what happen.
Merry Christmas!

Yes, bad JBE could give the symptoms described. Worth trying reflash of existing JBE with WinKFP or replacing JBE with known-good module.

[icon2015]

Also, worth checking if after you receive this error and you click OK, you can edit your FA. And if so if you see your FA full list. If yes, then one or more of those options don't collide with your database files, you will have to delete the ones that are in this situation, I haven't found a quick way to find them in these situations, I just delete the ones that I know the car doesn't need, and them add them one by one back to the FA until I find the culprit(can be more than one).

If your final step would be to make your FA by ssd file, you can get your important car options by using any online BMW VIN decoder, and then add them to your newly created ssd file.

Tip:
1. #MMYY referrers to manufacturing date, MM - month, YY - year(last 2 digits), which is also available by online BMW VIN decoder;
2. The last option of the FA will be the type of battery registered to your car, -AXXX is AGM type and -BXXX is normal type of battery, where XXX is the amount of energy charge in a battery by Ah, just look at your battery and take that info from there;
3. *PL33 option, the one described in the example of dpaul is the type of your chassis, also available by any online BMW VIN decoder;
4. &LCSW% is the cars upholstery, you can keep that as it is won't affect any coding.

[herqt]

Originally Posted by icon2015

Also, worth checking if after you receive this error and you click OK, you can edit your FA. And if so if you see your FA full list. If yes, then one or more of those options don't collide with your database files, you will have to delete the ones that are in this situation, I haven't found a quick way to find them in these situations, I just delete the ones that I know the car doesn't need, and them add them one by one back to the FA until I find the culprit(can be more than one).

If your final step would be to make your FA by ssd file, you can get your important car options by using any online BMW VIN decoder, and then add them to your newly created ssd file.

Tip:
1. #MMYY referrers to manufacturing date, MM - month, YY - year(last 2 digits), which is also available by online BMW VIN decoder;
2. The last option of the FA will be the type of battery registered to your car, -AXXX is AGM type and -BXXX is normal type of battery, where XXX is the amount of energy charge in a battery by Ah, just look at your battery and take that info from there;
3. *PL33 option, the one described in the example of dpaul is the type of your chassis, also available by any online BMW VIN decoder;
4. &LCSW% is the cars upholstery, you can keep that as it is won't affect any coding.

No i dont see fa list. Its like blank page
And yes i should try by fa.ssd Need some help to make it but well since i gave up on that idk when im going to try it again, my setup works on other cars tested on e39 e46 e61 even coded some stuff . i gave up on my car, one guy from this forum Joe@TopGearSolutions thanks to him, he tried to help me throw teamviewer, tested my and his own ncsexpert setups, same problem no solution.

[herqt]

Originally Posted by dpaul

OK, so have you tried using an ssd file?

There is not much to it if you have a stored copy of FA - you make a text file with the appropriate VO and a header and footer.

Here's one I've used so you can see the structure:

M E90_CODIERSCHL ALL
A 001 WBAPL33549A515442
E90_#0911&LCSW%0354$7SP$823$845$850$853$876$8SM$92 5*PL33-A090|0000000|0000000|0000000

Just replace VIN with yours and the string starting E90_ with whatever's in your FA.trc. If you don't have an FA.trc, fake up the option list to the best of your ability. Obviously, the file extension needs to be ".ssd" but the name can be anything. I used the last 7 characters of the VIN

Put the ssd file in your NCSExpert/Work directory
Load NCSexpert using Expert or Factory Coding mode, not Manipulate
Choose "Start" (F1)
Choose "Open File (F5)
Select your ssd file
Back (F6)
Process ECU (F4)
Select CAS
Choose "Change Job" (F2)
Select FA_Write
Select "Execute (F3)

Hey, made my own ssd file but its not working. I select my ssd file and i get error
Error in line of controlling file (*.ssd)
A 001 mycarfullvin2

As i know 2 is the checksum of my vin(ncsexpert shows it). Have no clue what i should replace on that .ssd file

ssd:

M E91_CODIERSCHL ALL
A 001 mycarsvin2
E91_#1206&ANAT%0475*VU91$520$548$851$1CA$249$320$3 86$428$494$534$541$609$612$620$633$6AA$801$863$879 $8SP-A090

tried with that 2 and w/o every time same error :/
Error in line of controlling file (*.ssd)
A 001 mycarfullvin

[dpaul]

Don't include the checksum digit

Edit: sorry, I see that you have tried it without

[herqt]

Originally Posted by dpaul

Don't include the checksum digit

ive tried, same error

[dpaul]

Originally Posted by herqt

ive tried, same error

Include |0000000|0000000|0000000

Edit: also maybe remove spaces in third line

Just a total guess on my part - really have no idea

[dpaul]

Here's a link to a Russian site with a good description of ssd file format

https://www.drive2.ru/l/456668136897251064/

It seems as if none of the suggestions I've made actually matter. But the Russian thinks a blank line at the end of the file might be important and has suggestions about line length. He also thinks having the checksum is important.



SSD file

A typical SSD file for cars with FA looks like this:

M E60_CODIERSCHL ALL
A 001 WBANU91000AB12345A E60_ # 0307 & LCBA% 0475 * NU91 $ 2KM $ 205 $ 248 $ 300 $ 302 $ 346 $ 4AT $ 415 $ 428 $ 441 $ 494 $ 502 $ 508 $ 522 $ 534 $ 548 $ 644 $ 690 $ 899 $ 899 $ 899 $ 899 $ 899 -NMUW

The file did not fit in width, in fact it consists of only two lines

In this case, an imitation of a car similar to Severyanka , but with a fake VIN number, is given. The VIN is recorded with the checksum (highlighted in bold) and the familiar picking code (FA) is indicated.

Each line in this file begins with a letter defining its type and then the corresponding data with a space. Let's start with the first one:

- In the line with the letter “M” (“M-line”, most likely from it. Modus or English Mode - operating mode) at the beginning is indicated the body index (E63) and the line “_CODIERSCHL” (together with the body index), and then an indication that we are working with all ("ALL") car blocks. Instead of “ALL” there may be the name of a specific block, but more on that later;

- The line with the letter “A” (“A-line”) contains data about the vehicle having an FA. Here is a three-digit serial number, VIN of the car with a checksum, and then its FA without spaces. A string can be no more than 2 KB in length (2048 bytes, in this case 2048 characters), plus FA can be divided by the “\” character (backslash, separated by a ******* into short lines of no more than 200 characters. Like this:

A 001 WBANU91000AB12345A E60_ \
# 0307 & LCBA% 0475 * NU91 $ 2KM $ 205 $ 248 $ 300 \
$ 302 $ 346 $ 4AT $ 415 $ 428 $ 441 $ 494 $ 502 $ 508 \
$ 522 $ 534 $ 548 $ 644 $ 694 $ 701 $ 8SD $ 890 $ 899 $ 899 $ 899 $
899 -NMUW

You can break it into as many lines as you like, anywhere in the line (preferably by "blocks" in the form of a whole option code) and for any length no more than 200 characters;

- You can add comments as separate lines, marking them with a semicolon at the beginning of the line:

; any comment

There are lines of another type, but about them a little later. In addition, there must be an empty line at the end of the SSD file (just press Enter). Otherwise, NCS Expert may throw an error reading the last line. Not always, but it happens.