Content → Rocrail Server → Configuration

• General | Trace | Service | Automatic | Controller | R2Rnet | SVG | Finder | Command Mapping | Presets
• Mobile Databank

The idea behind the LocoDB/CarDB/TrainDB is to be able to access all locomotives/cars/trains on all computers with access to the same NAS/Cloud storage.
Even with an offline Rocview it will be able to access the locomotives and check their properties.

Without read and write access of the RocrailDB this concept will not work.

Notes:

• Instead of "RocrailDB", can also use a different name for the database directory that is compatible with your operating system.
• Rocrail does not create the database directory automatically. It must be created initially by the user in the NAS/cloud storage.

The Database path points to a directory which can be read and write by all users running Rocrail.
Every loco has its own directory named by its ID. Blanks are replaced with underscores; Blanks in IDs are discouraged and not supported.

<code>
RocrailDB
├── CarDB
│   ├── EssoTank
│   │   ├── backup
│   │   │   └── 20251017162241462-EssoTank.xml
│   │   ├── EssoTank.xml
│   │   └── M4524.png
│   ├── Frico
│   │   ├── backup
│   │   ├── Frico.xml
│   │   └── M4524.png
│   .
│   .
│
├── LocoDB
│   ├── BR01097
│   │   ├── backup
│   │   │   ├── 20251016161334845-BR01097.xml
│   │   │   ├── 20251016161340115-BR01097.xml
│   │   │   └── 20251017075932411-BR01097.xml
│   │   ├── BR01097.png
│   │   ├── BR01097.xml
│   │   └── DB01.png
│   ├── BR120119-3
│   │   ├── BR120119-3.xml
│   │   └── m33535.png
│   .
│   .
│   .
│   └── V1002215
│       ├── DB100.png
│       ├── m3072.png
│       └── V1002215.xml
│
└── TrainDB
    └── Freight_train
        ├── backup
        |   └── 20251017162241462-Freight_train.xml
        └── Freight_train.xml

The directory of a train (in TrainDB), a locomotive (in LocoDB), or a car (in CarDB) can be selected in the file manager.
The object will then be displayed in the specific index dialog.

The specific index dialogs then are displayed with all trains, locomotives or cars.

The group field can be used as filter.

The "Workspace" and "Scale name" is used as selection in the LocoDB in case of automatically loading.

For selecting a locomotive from the LocoDB the "Workspace" and/or "Scale" field should contain a value which match the Plan properties.

The Workspace field accepts a CSV list of multiple names.
The group field can be used as extra filter.
Example:

"layoutA,layoutB,layoutC"

With the "Locomotive database" option the export of the selected locomotives will be in the LocoDB.
The export will overwrite existing files.

Locomotives will be automatically loaded from the LocoDB if following is all true:

1. No local locomotives are defined.
2. The Locomotives database path exists and is accessible.
3. The Plan properties contains a selection by Workspace and/or Scale-Name.
4. Locomotives in the LocoDB matches the Plan properties criterium.