[Solved] Laskomex cd-2500 Change of the installer code by means of ISD-02A

Hello.
I recently purchased an ISD-02 interface.
When configuring CD-2502 I cannot find the option to change or read the installer code via the interface.
In the manual I read, among others:
The administrator password can be changed in the [Parameters - grouped by functionality] tab.
And in the description of the tabs -:
Parameters - grouped by functionality -
Parameters available in the control panel in the P-1, P-2 and P-6 procedures (change of the installer code), as well as the control panel identification parameters (serial number, control panel data type identifier, object identifier) grouped into function blocks.

I sent an email to Laskomex a few days ago, but no one replies.

I am sending the link to the intercom documentation. To change the installer code see section 8.6.
Additionally, if you just don't know the installer code, read point 8.
If an installer code has not been defined previously, the serial number is used as the code. Best regards.
http://www.laskomex.pl/dokumentacja/archiwum/cd2502.pdf

Thank you for your answer. I know the procedure for changing the code "from your finger" very well, but I asked about changing / reading the code from the ISD-02 level.

in the attachment there is a screenshot with the tab where it should be as in P-6, i.e. change of the installer code.

Generally, I do not deal with intercoms, but I have this model at home and that's why I know something about it There is no such option after scrolling the ribbon at the top?

I must have already rewound everything, unfolded what was to be rewound
I can change the serial number - there is no such possibility with my finger.
Based on the serial number, user codes are generated (I also read that somewhere). Installer code if default is the same as serial number.
I have tried this option. By changing the serial number, the installer code does not change to the default along with the serial number.
So still nothing.


For posterity:
After talking to the Laskomex service, the nice gentleman admitted that there was a mistake in the manual.
The installer code on EC2502 cannot be changed via the ISD-02 interface.

Hi,
Recently faced this problem and found a solution.
The ISD-02 program does not display the installer code, which does not mean that it is not in the EEPROM memory dump.
I have no idea if the memory addresses are the same for all control units, so I recommend that you verify the data with the ISD-02 program.

Follow the steps below to extract the installer code.

Start ISD-02 and load the memory dump.
For example, I used the screenshot attached to the program (2502_U68_Laskomex.bin).
Go to the "Lock codes / Premises options" tab. In the picture installer code recovery from EEPROM _1.jpg you can see the codes of the code lock assigned to the premises.

For the first two codes we convert to the hexadecimal system:
0285 = 011Dh
3737 = 0E99h

We search for the sequence 01 1D 0E 99 in the memory. On the picture installer code recovery from EEPROM _2.jpg marked in green and purple. Each lock code is written in two hexadecimal bytes.
The installer code is in front of the code for the first apartment, in this example at the address 200h, it takes two bytes.
After converting from hexadecimal to decimal system, we get the installer code (marked in red):
2117h = 8471

Respect for the research.
I took the easy way and bought a service password resetter
I don't remember who sold it, I can't find it now.
It works so that I plug it into the EC connector, wait a while and I have reset the default password without losing the saved data.
I change to mine and I have access.

They need to earn. The serial number used as the default installer code is stored in memory at 0h in two bytes. Such a device reliably copies memory cells from the address 0h to 200h (2 bytes)

martin-76 wrote:

Respect for the research.
I took the easy way and bought a service password resetter
I don't remember who sold it, I can't find it now.

We
It's called LX-DKxx - where xx is the model version. "02" restores factory default; "03" sets to "1234" [just in case someone has the original stickers broken]. The cost is about PLN 100 net.

karbon wrote:

Recently faced this problem and found a solution.
The ISD-02 program does not display the installer code, which does not mean that it is not in the EEPROM memory dump.
I have no idea if the memory addresses are the same for all control units, so I recommend that you verify the data with the ISD-02 program.

... and everything he wrote in this post @Carbon - this obviously does not like the warranty and it is a very delicate process, I generally do not recommend digging into memory.
You can easily break the program - so when doing such things, your fingers are away from the keyboard and do not click pointlessly on the screen. It's best to work with a saved file ...

Ah - and also one small observation - if you do this, e.g. to check what code the previous installer set - then technically speaking, you are violating the private secret of the person who may e.g. have the same code (this is not recommended, any passwords and pins should ALWAYS be different (completely different) in different places, but ...) in other housing estates which you have not managed to "take over" or which he still looks after.
Yes, I know that it is only ~ 10,000 combinations (checking 30 combinations a day, starting from 0000, you can manually find out the right one within a year - my friend broke his code to enter and hit it on the third day) that These are not the starting codes of the atomic head, nor that there are no sensitive personal data (names, peselas, etc.) in such intercom.
But technically, the person whose code you read this could sue you, and in law it is quite legitimate ... just sayin '.

martin-76 wrote:

For posterity:
After talking to the Laskomex service, the nice gentleman admitted that there was a mistake in the manual.
The installer code on EC2502 cannot be changed via the ISD-02 interface.

And yes - it is true, it is very possible that this "nice gentleman" was me.
This is essentially written in the manual and it is a mistake - it is not possible to suspect that the administrator code has been changed using the ISD-02 program (that is, "in" the program itself, as proved by @Carbon ). It was possible at first, but at the request of the installers themselves, this had just been removed (and at the request of the company's lawyers).
And it stayed in the manual because ... ... because it stayed.

And, since we are already on the topic of ISD, I will also mention that if the control unit is old enough that it does not have a 10-pin ISD socket yet, it is not possible to simply attach the ISD interface to the memory.
Then you have to say goodbye to the settings and do "RESET-INIT" or call / write to us and we will send plans to make a kind of "adapter" to connect to the memory through the processor port - but reading the memory from such an old device may not be possible anyway - and you need to create such an adapter, which also requires some work.
We provide the plans for free, but the adapter itself must be done "on your own"

It seems to me that this adapter plan is shown in the ISD-02 program
My activities took place in my housing estate where we no longer have a guarantee for an intercom and something had to be done, and I have an EEPROM reader ...

karbon wrote:

It seems to me that this adapter plan is shown in the ISD-02 program

I mean ... let me put it this way - it's not a great art to reverse engineer and work out any technological solution - especially when you have it in your hand.
The stubborn one from such an old EEPROM cartridge can be desoldered (it is surface mounted in a different place than now) and by appropriately adding "pins" from the wire, it can be "converted" for use in the socket of new boards or in MLX (such a "flash drive" for reading memory , comes with ISD). You can - it will work.
You only need to have time, conditions, skills and knowledge for this - and most often it is art for the sake of art, because it will be cheaper and faster, for example, to do "RESET-INIT" (this is what we call "reset to factory settings") or use LX-DK .
ISD and LX-DK especially make sense when you have a whole lot of objects and cassettes.

And these plans for the "adapter" show which pins to connect with which plugs in ISD, the program will not tell you, and I do not recommend it "at random", because you can wash the memory or ISD redirecting the voltage to the wrong place (I have a whole drawer of such fried plates from ISD). I can't share it here, because we spend it only on a clear, confirmed request of a given person, so that we can pursue them or something if necessary

Such MLX was once useful to me to copy "PINs and RFIDs" from 24C64 from the murdered EC2502 after lightning.
As for the installer code, we (installers) do "take over" of the installation at the request and with the consent of the administration / housing community / cooperative, if, for example, the contact with the current installer has ceased.
It would never occur to me and I don't have enough time to run around neighborhoods and break codes
I think that the topic of resetting the installer code has been described exhaustively by karbon and Serwis_LX, for which thank you and if nobody has anything else to add, the thread can be closed.

Serwis_LX wrote:

one small observation - if you do this, e.g. to check what code the previous installer has set - then technically speaking, you are violating the private secret of that person who may e.g. have the same code (not recommended, any passwords and pins ALWAYS should be different (completely different) in different places, but ...) in other housing estates that you have not managed to "take over" or which he still looks after.

You see, as a representative of the manufacturer, you look from a slightly different angle than us, installers, and above all, service technicians of such systems. We have a lot of situations where the Administrator, on behalf of the Community, orders us to take care of the existing (video) intercom system, completely unknown to us. Most often it is a change of the manager who "enters the game" with his proven companies or simply dissatisfaction with the service of the previous service company. Administrator / Community, so that we can "smoothly" and seamlessly "enter" the new system, triumphantly gives us individual codes, that is code tables, and believes that for us, service technicians, this is enough. After all, there are so many numbers that it should definitely be enough for us. And here is the zonk, because we know very well that individual codes, we are able to get them without any problems. The biggest problem is when trying to program, because we need the installer code for this. And here we start, because we MUST combine ISDs and other miracles, because we have to "bite" it somehow - the community is waiting for our help. We would not even think of what you are writing about, i.e. some hostile "acquisitions" of systems from other companies. I guess you watch too many crime movies ? And the very term that it may be "you violate the private secret of this person" is a confusion with confusion, because I would like to remind you that the system is owned by the one who paid for it, i.e. the Community / Cooperative etc., and not the person who installed it. And it is the Community (owner) that orders us to do some activities on the system. For the sake of clarity, I am talking about the situation after the warranty period, because then and in principle only then can such situations occur.

Somewhat similar situations were discussed in this thread: https://www.elektroda.pl/rtvforum/topic3573807.html

greetings

@Ircys We know it perfectly well.
Unfortunately, to paraphrase one of the stand-ups of the genius Jim Jeffries - "there will always be those few ... * souls * that will spoil everyone's fun and you have to adapt to them".

We cannot be sure that someone does not want to plant pigs on someone else, and uses our limited ability to find out if the person is lying.

I answer (because we also provide teleports on the website) at least one such telephone every day.
Unfortunately, I cannot list such things.
We can accept the switchboard sent and change its code to the one that the new installer wants, but we cannot provide the changed code.

That paragraph simply states what it is legally correct - that's right - the owner is the community or somebody else, but the service and maintenance is in the interests of the installer / contractor and we are required to protect his interests as well.
The installer also has to protect himself in some way, against such moves of the owners of the equipment - because it cannot be that they have a contract, the owner will say that he will take someone else to this failure, because [any reason], the other one will reset everything, rearrange, maybe something gets screwed up and goes to hell and then the owner suddenly remembers that it was the initial installer who was their service technician and now he will be left with a mess, without access and the owner will push and be dissatisfied - and who will ultimately be to blame for the whole situation? Let us remember that we are using the perspective from behind the desk, pardon us - such common "concrete" without any idea about these matters and with great conviction about the enlightened mission of their great Byzantium made of large slabs. And we had such cases on the line.

It is sad, it is unpleasant and difficult, but unfortunately true. Often it is pointless or exaggerated by orders of magnitude (after all, what "secret" "data" is in such an intercom?) - but our lawyers and contracts categorically and under the threat of exile to Siberia prohibit us from providing such information and distributing regulations how to "hack" such a password.

The only possibility - if the owner of the device, a given community, approaches us with an official letter on letterhead and with signatures that they confirm the need for access by a given installer and ask for access - then there is another conversation.