[Solved] BSI DELPHI series EL HW D6 - TELECODING READING BSI peugeot 208 II corsa F

Hello.
Currently working on new Peugeot and Opel BSIs.
Previously, there were also BSI DELPHI but on a different HW D5 motherboard
descriptions here:
https://www.elektroda.pl/rtvforum/topic3640481.html

This time it is the same group of cars, but the BSI version of the HW D6.
now on the table I have:
EL3 HW D6 Corsa F
EL4 HW D6 peugeot 208 II

So far worked out:
1. Reading with an ordinary programmer (eg UPA etc.) from the pads on the motherboard.
2. Modification - adjustment of the mileage and calculation of the checksum.
3. execution of VIRGIN.
4. diagnostics on the table - i.e. pinout.
5. history reset
6. Telecoding without the need for online

An instruction will be published soon - if anyone is interested, they can ask.



And there is already a prototype needle plate for the BDM frame


Managed to master TELECODING without online.
Just be able to read and write eeprom. As you can see above - it is doable.
Of course, this is a batch change in the HEX editor.

With the right mesh, it can be done very quickly.
Unfortunately, there is no such data and must be created.

below is an example of several dozen cells that I have already described - the colored ones.
It does not describe all but those that will be useful to me.

- trailer module
- electric mirrors
- change of lamps to FULL LED
e.t.c





There is no one mesh for all BSIs
Only BSI dunks with the same numbers and versions - AND WHAT'S IMPORTANT !!
Having the same software edition (this can be checked in the Identification in the diagbox) will have the same position. Such BSIs are also replicable on the basis of the eeprom itself.

As for the configuration - changing cells alone is not enough - the areas of configuration (usually there are two) have their own separate checksums.
The checksum must be calculated correctly - then the individual codes work properly, if the CS is counted incorrectly in the coding, the preview in Diagbox is chapped and nothing works properly. Of course, the CS counting has also been worked out.
I think I will describe it soon.

And it worked
the first chapter is already everything about the BSI EL3 HWD6 and programming without online

all very interesting, I am from Argentina and my language is Spanish, but I hope not to bother translators.
if you need any dump just ask.

Currently, I do not have the full knowledge of the PIN CODE algorithm
below are examples of PIN in FL3 HWD5



To the administrator - I know that I wrote the same in two places, but I did it due to the different number of people watching the topic.

After a dozen or so tests in several BSI DELPHI, the case looks like this:
In the same BSI, whatever changes in the eeprom data - the immo code after entering e.g. 0001 is always the same coded.

If the code 0001 is entered in another BSI model, this PIN is coded differently:

So in different BSIs: EL3, EL4, FI, 3 FI5 ... code 0001 will be a different string.

It is easy to conclude that either there is another algorithm ... or there is some variable in the algorithm ..... (it's not vin - I checked).

Currently I am creating a small BSI DELPHI partial coding database for the most used functions - subject to modifications.

Electrically folding mirrors
Change of lights to FULL LED
changing the parking aid options. (parktronics)
hook module assembly

TELECODING CRC COUNTING

I have the following:

DELPHI EL3 HW D06 10.47 edition
DELPHI EL4 HW D06 10.89 edition
DELPHI FI5 HW D05 edition 09.79

Anything can be done, but I don't have that many bsi to upload.
I still have EL5 hw d5 and FI3 HW d5 to do
I haven't checked the edit yet.



I invite you to cooperate ... if someone has a free BSI that he would like to know - he can send it - the costs are a return package.

And one more thing in relation to the programming - why do I do it:

The whole topic of programming concerns the new BSI DELPHI.
Car models that entered production after 2016
308 t9 lift
3008 II
5008 II
208 II
c3 III
CORSA F
e.t.c

The case is that the listed cars are not listed at all in Diagbox after starting.
And after using alternative cars, there is an entry in many of the configuration tabs
- "unspecified value" and this fact alone blocks the possibility of encoding such a BSI even if such a possibility was enabled.

Diagox presents it as an error and exits the configuration, although we do not change anything in this line and we are interested in another. When creating diagbox, these versions (7) of the cars mentioned above did not have some of their systems as well, so the box will not encode them because it does not recognize them. And the manual method is the most because it does not refer to the Diagbox database.

In terms of diagnostics of new PSA OPEL and DS
There is currently a version of Diagbox 9.68
it works in offline mode - it does everything except telecoding the recharging (because there is no connection with the server)
This is the full version (not virtual or some kind of transplant)
I have been using it for a while and I am very pleased.
diagnostics of the 3008 II Corsy F 208 II or DS 7 crossback is not a problem.
communicates all history modules, real data preview and execution tests.
The version is assigned by hardware to the computer - it cannot be copied to another.
It is worth making a good backup or clone - in case of disk failure .....

Breadboards came in




I upload the project on HW6 -

Continued telecoding
In most cases, BSI configuration alone is not enough.
It is also necessary to code the multimedia system (radio navigation)
ie NAC or RCC decoding
camera 180
new themes
cruise control active
and other cool stuff

It is possible but not with DIAGBOX because it is online
You can browse and find a solution in French forums.
For my part, I tested the self-building of the interface based on the guidelines from this forum.
Everything flashes as it should.
I also wrote step-by-step instructions in Polish on how to make such an interface.
The software is free to download links in the manual.
I will try to supplement it with specific tested encodings and I will post it here in some time.
I am not the author, and the authors made it available for free and their intention was to make it free, at least as they describe it on the forum.
so here it will also be free with a small but - there will be points.
Why ?
For a simple reason - I share it, others should also, and to have points, you need to throw in something and it must be interesting for others to download.

If someone has such a problem after downloading - I will send it.

I am adding more configuration mappings. now I checked - they work so far.

DELPHI EL3 HW D06 10.47 edition
DELPHI EL4 HW D06 10.89 edition
DELPHI FI5 HW D05 edition 05.66
DELPHI FI5 HW D05 edition 09.79

I invite you to post edited descriptions under specific HW and editing

NAC RCC Configuration Works Great
You can rip the backup
parameters can be changed
menu functions
add functions etc ...
If you mix too much, you can always restore.




[img-3]

works even more, just mapping BSI configuration

And where did you find?

I wrote that it maps, that is, I do it's not found, only one BSI has fallen, the other has a problem with backlighting (something fell) but I ordered a new one, because I do not want to unsolder

Sorry ... I didn't understand ....

And it's not that even a regular launcher can be coded on foot after obd2?

oktawian89 wrote:

And it's not that even a regular launcher can be coded on foot after obd2?

Is that a question or answer?
Because if you answer, expand the topic.

In the thread I'm talking about car coding after 2017.
Until 2016 you can do it with "ordinary DIAGBOX".

you could log as long as you did not disable the dragon communication to uds and nothing else is needed

I only have diagbox 9.68 - I do not have a DRAGON

I have 9.23 from Rorry too, but you can't only write there

none of them can be coded
I do it manually
I read and write UPA directly from eeprom

diagbox 9.68 on VMware for free https://mhhauto.com/Thread-DIAGBOX-9-68-FREE

glapsson wrote:

So far worked out:
1. Reading with an ordinary programmer (eg UPA etc.) from the pads on the motherboard.
2. Modification - adjustment of the mileage and calculation of the checksum.
3. execution of VIRGIN.
4. diagnostics on the table - i.e. pinout.
5. history reset
6. Telecoding without the need for online

Hi.
Does VIRGIN mean the BSI status as new, to which you can enter DiagBoxem VIN as you need?

I have in my P308 T9 to activate TomTom Trafic after changing the radio from Smeg to Nac. In the current configuration, it cannot be done and I need a BSI with VIN as it was originally on the radio. And changing only the VIN number in the eeprom causes bushes to DB.

Virgin is a fairly broad concept ..... It depends on what data you clear

the same VIN and PIN already means that you can add BSI
but you also clean up stories and sometimes programming.
vinu in eprom without counting the checksum for vin can not be changed.
there will be bushes

I just care about VIN. On the table, I have a BSI connected with a radio under DB. If one is compatible with the other, TomTom Trafic should activate.

It could be done
just why this way .... better not to have a good wine at NAC

glapsson wrote:

It could be done
just why this way .... better not to have a good wine at NAC

When I activate TT, after the VIN on the radio returns to the one from my car, the activation should not go back. At least that's what I assume
NAC TT was not active in the donor, if it succeeds, it will continue to work for the next 3 years. I now have the status on the server: pending activation.

kruchy666 wrote:

I have in my P308 T9 to activate TomTom Trafic after changing the radio from Smeg to Nac. In the current configuration, it cannot be done and I need a BSI with VIN as it was originally on the radio. And changing only the VIN number in the eeprom causes bushes to DB.

if there is no BTA in the car that was in the donor's car, you do not need to change the VIN in BSi to activate traffic, it works long, just activation on the PSA server, you have to wait for over a week

Added after 2 [minutes]:

kruchy666 wrote:

I just care about VIN. On the table, I have a BSI connected with a radio under DB. If one is compatible with the other, TomTom Trafic should activate.

assemble Arduino v3 and canshield v2 described here https://www.forum-peugeot.com/Forum/threads/t...dage-et-calibration-dun-nac-rcc-cirocco-sans- diagbox-via-arduino.121767 / you will code NAC as you want and maybe change VIN to BSI if you have to

Added after 5 [minutes]:

kruchy666 wrote:

glapsson wrote:

It could be done
just why this way .... better not to have a good wine at NAC

When I activate TT, after the VIN on the radio returns to the one from my car, the activation should not go back. At least that's what I assume
NAC TT was not active in the donor, if it succeeds, it will continue to work for the next 3 years. I now have the status on the server: pending activation.

well, it should work without any problem because activation is not after VIN, only after UID, so as soon as it is active, you can change VIN freely.

NAC already configured by arduino.
Activation on the server has been waiting for almost a month and the status is still "In progress".
I have BTA installed and coded already. Is it working? I don't know, I haven't pressed SOS or assistance yet.
In addition, the car is not detected by MyPeugeot. Neither on the car's VIN, nor on the donor's VIN.
Perhaps there is too much discrepancy. The radio is from Citroen and it is a Wave3 which was not installed in the P308.
I think VLud in one post described that the radio on PSA servers is identified by the serial number of the radio, but it was also about activation only with a compatible VIN.

Exactly, but activation only when you wanted to run from BTA net (then VINs had to agree in devices)
as with a smartphone it was not necessary

I put the BTA in, but I did not connect the Can nowhere I only need traffic and speedcams

okay so I know that with the latest BSI soft from 208 (teletransmission to the latest online diagbox), which has LOCK in the eeprom, can be changed after OBD VIN with arduino with canshield ... tested

goes to run androidauto in rcc with this Arduino device if it is not available originally ???