Reusing identification medium in other projects/databases - AXM Classic
Using the same identification medium in different projects/databases
You are not only able to use the same identification medium within a project (see Reuse identification medium in the same project).
You also have the option of using the same identification medium not only in different locking systems, but also in different databases:
- Use in different AXM projects (projects have their own database)
- Use in an AXM and an LSM locking system
- Synchronise the identification medium in your project (see Synchronise a card/transponder (including importing physical access list)).
- Synchronise the same identification medium in another project or in another database.
- Identification medium is used in several locking systems which are separate from one another.
Recognition by the serial number
Although they are in different projects, both identification media have the same entry in the field in the window.
A look at the programmed transponder tells you that it really is the same transponder:
(It's required that the transponder's enclosure is the same as delivered from the factory.)
Recognition by the programmed data sets
You can also identify use in other databases by the programmed data sets:
- open.
- Click on the
button. - The window will open.
- Synchronise the transponder (see Synchronise a card/transponder (including importing physical access list)).
- Expand the area.
- Depending on which locking system you are in, you will see a second locking system in the programmed data sets. However, you will only see the locking system ID unlike when you reuse it in the same project (see Reuse identification medium in the same project). The locking system ID is also stored in the identification medium and is therefore known. However, the locking system’s name is saved in another database and therefore cannot be displayed.