
User
Guide
Rev: A, 02 03 2004,.sw3.10
Page 55
File Transfer
There are three types of files which can be transferred to/from an
NPC:
•
NPC System Software
•
NPC System Configuration
•
Luma-Net Device Programming
All file transfers to/from the NPC are done with an ftp client.
Code File and Configuration File
Two of the kinds of files you can transfer to and from the NPC are:
code files
(extension “cod”) and
configuration files
(extension
“dat”), using the FTP file transfer protocol.
The
code file
is the application code or software that makes the
NPC operate.
The
configuration file
contains the entire NPC. Retrieving the file
from an NPC allows you to backup configuration transfer the same
configuration to/from multiple NPC’s or send configuration to the
factory for analysis.
The NPC knows whether to send or receive a code or configuration
by the extension of the file. If a file is sent or requested with
a .cod
extension, the firmware code is sent or received. If a file is sent or
requested with
a .dat
, the configuration data is sent or received.
Luma-Net Files
The last kind of file you can transfer to/from your NPC is the Luma-
Net configuration files. These files contain all of the programming
data contained in a Luma-Net device. The determination of which
devices programming is retrieved is determined by the name of the
file requested. The filename follows the following format:
P[port #]L[device address].lda
For example, if a device connected to port #2, or the Luma-Net B
port, with address 18 from which you wanted to retrieve
configuration, you would enter the ftp command
get P2L18.lda