PRG Mbox Remote Manual 3.9 - Manual (Page 106)

100 MBOX ® REMOTE USER MANUAL
Note: The csv import/export tool is intended for the creation of large or complex pixel mapping configurations from
automatically generated data. Beyond a certain point it can be quicker to create a script to convert some other data
into position and patch information, and save that in a csv format rather than attempting to place and patch the same
fixtures individually using Mbox Remote.
The import functionality requires that the csv file be formatted properly for handling by Mbox Remote. If the formatting
is not correct, Mbox Remote will not be able to read the file, or errors may occur when the file is being read.
Guidelines:
+ The csv file may only hold data for one context. If data is created for more than one context, the data should be
saved as multiple csv files, one for each context.
+ The csv file requires that data be organized into lines of text, with each line representing either organizational data
or one fixture’s data.
+ The first line of the file, known as the "header," holds the names (in order, separated by commas) of the properties
listed (in corresponding order) in the fixture data in the following lines. The import window notes what the header
should include and shows the correct order, spelling, and formatting. For example:
+ Property names must follow the standards dictated and must be spelled and capitalized correctly. These are:
- fix_reference (required) - This must match exactly the name of a fixture profile in the .pmap configuration for the
fixture to work. If the reference name is not already in the configuration, the fixture will be ignored. In other
words, it is critical to import/create profiles BEFORE doing a csv import.
- fix_univ
- fix_addr
- fix_xpos
- fix_ypos
If a wrong name is detected during the import process, Mbox Remote will display an error such as the one below:
\
+ The lines following the header are known as the "body." These lines hold the fixture data corresponding to the
property names in the header, in the order specified.
+ The fixture data lines should be of the correct data format only, no punctuation (other than decimal points where
appropriate), symbols, etc.
- fix_reference - text (includes characters A-Z, 0-9, some punctuation (+ - _ ( ) [ ] etc.), but no commas.)
- fix_univ - integer (0-63999)
- fix_addr - integer (1-512)
- fix_xpos - integer or float
- fix_ypos - integer or float