Device config files

Config files are the backups nobody can find when the DSP dies at eight on a Friday. This tab keeps them with the project, linked to the unit they belong to, so the next person on site does not have to rebuild from memory.

Uploading

Open a project and go to Config files. Drag files onto the table or the empty area, or press Upload config files to browse. You can select several at once and each upload is shown with its own progress row.

The tab accepts the file types devices actually export: XML, JSON, TXT, CFG, CONF, INI, YAML, YML, CSV, DAT, BIN, PLIST, REG and BAK. The limit is 50 MB per file, and anything larger is rejected with a message on the upload row. If file storage has not been configured for your installation, an orange banner appears and uploading is disabled.

Linking a file to a device

A backup belongs to a specific unit. Click the Device cell on a row, or choose Link device from the row menu, and pick from the list. The options come from what has been installed on the project and what is on the plans, so a file can point at the exact amplifier with its serial number and location, or at a product when the file applies to every unit of that model.

The name of the linked product is stored alongside the link. If that catalog item is later deleted, the row still tells you what the file was for, marked as deleted rather than going blank.

Notes

Click the Note cell or choose Add note to write a line about the file: which device it configures, whether it is a pre config or a post commissioning backup, what firmware it came off. Press Enter to save, Shift and Enter for a new line. Notes are searchable.

Finding a file

The search box matches on file name and on note text. When there is more than one file type in the project, a row of extension buttons appears so you can show only the XML files, only the JSON files, and so on. Reset clears both.

Opening and downloading

Clicking the file name opens it in a new tab, which is handy for reading an XML or JSON export without downloading it. The row menu also offers Open in new tab and Download.

Deleting

Delete asks for confirmation and then removes the file permanently. There is no recycle bin and no undo, so be sure before you confirm.

Limits

There is no versioning. Uploading a newer backup of the same device adds a second file rather than replacing the first, so use the file name or the note to say which is current. Nothing is parsed or validated: the app stores and serves the file, it does not read it, compare it or push it back to a device. Files are stored per project, so a device that moves to another project needs its configs uploaded there as well.