Import Equipment List

LightDesigner provides the ability to import stations and processors, and also allows a user to define and create space hierarchical data for a project.

Features of the equipment list must include processors and their assignments, primary spaces and any sub-spaces that are included (spaces can be detailed with X, Y geometry and dimension data), as well as any stations included in the project including their type, processor, and space assignments.

Where LightDesigner is concerned, an equipment list in spreadsheet form, OpenDocument Spreadsheet (*.ods) format, can be imported into a configuration using the "Import Equipment List" feature found in the "Project" menu. Alternatively, when creating a new project, you could import the equipment list in the Processor Properties and Data Import section of the New Project Wizard or New Server Project Wizard.

Equipment List Spreadsheet Formatting

The equipment list spreadsheet must be formatted in a specific way for a successful import.

Tip: The easiest way to create a valid equipment list for importing, is to begin from one. Try exporting an equipment list from an existing LightDesigner configuration first, then edit the data to match your new project needs.

Reference the sample equipment list below that was previously exported from a LightDesigner configuration:

A valid and importable spreadsheet requires the following sections of data:

PROCESSOR
- must specify the processor name
- the processor "NUMBER" (up to 20 processors are allowed per project)
- the "HOST RACK" that the processor is installed (specify either DRd or ERn)
- the address "SOURCE" (either "Manual" or "Automatic")
- the "IP ADDRESS" (if Manual is the source, you must provide a valid IP address)
- the "SUBNET MASK" (if Manual is the source, you must provide a valid Subnet Mask, 255.255.0.0 is default)
- the "GATEWAY" address (if Manual is the source, you must provide a valid Gateway address)

SPACE
- must specify the space name (this could be a Primary space or a sub-space, but if a sub-space you must also specify the exact "PARENT SPACE" name as it appears as its own "SPACE" entry. This is how the space hierarchy is created for the import. See the example above.
- must specify the "PARENT SPACE" name (if the project is broken down into spaces and sub-spaces)
- specifying the geographic (X, Y) location and dimension of each space is optional. When the geography is specified, at import, LightDesigner will not allow two or more spaces to overlap.
STATION
- must specify the station name (this would import as the station "Name" in the Property Editor).
- must specify the station "TYPE" (the station type is the stations short name as found in LightDesigner, the root name of the station as it is indicated in the Station Library minus the model number and gang information, e.g. 1-Button Stn or 1-Fader Stn, or Touchscreen.
- must specify a "PROCESSOR" to associate the station (the processor name must match a processor name from the "PROCESSOR" section)
- must specify a "SPACE" to associate the station (the space name must match a space name from the "SPACE" section)
- must specify if the station is a "PORTABLE" station or not. (this column is a simple "Yes" or "No" entry)
- the remaining columns of data are dependent on the "PORTABLE" setting or the "Type" of station specified (if a Touchscreen is specified you may also specify the "LCD THEME" to use, etc.)

Note: Even if the project does not include stations, the column headers must be present in the spreadsheet.

Importing Conflicts

The import process could result in a conflict that requires disposition before the import process will complete.

Import Equipment Errors Dialog

Importing an equipment list that includes invalid objects will result in an error dialog that explains the errors as well as provides an option for you to cancel the import or proceed importing omitting the objects that have errors.

Click [OK] to proceed with the import process, omitting the invalid objects, or click [Cancel] to abort the import.

Import Equipment Conflicts

Importing a spreadsheet into an existing configuration could cause a data conflict to occur, and LightDesigner to display a conflict dialog. There are multiple reasons a conflict can occur, with a main reason being a duplicate object of the same name; importing a file twice will not create the objects in duplicate. Instead you are provided with a conflict dialog for disposition of which version of the same object you would like to maintain.

You must specify a disposition of replace, merge, or ignore per conflict or a set an action that will affect all conflicts in a category or space at once.

After the import is completed successfully, there may still be errors incurred by the import. Check the Error Browser for a list of any incomplete assignments that may affect the configuration.