Creating A New Rpm Loader Project File; Editing A Rpmloader Project; Device Mapping; Device:port:system (D:p:s) - AMX RPMLoader Operation/Reference Manual

Using RPMLoader

Creating a New RPM Loader Project File

RPMLoader (RPMX) Project Files can be created in RPMLoader, to provide a method of using RPMLoader to
transfer files that were not necessarily generated as part of a RPM Project: when a new RPMLoader Project is
created, you can add and/or import local files as desired and transfer them via RPMLoader.
To create a new RPMLoader Project:
1.
Select File > New to open the New Project dialog (FIG. 36):
FIG. 36 New Project dialog
2.
Enter a descriptive Project Name and Master Name in the text fields provided (128 characters max).
3.
Click OK to close the dialog and save your changes.

Editing a RPMLoader Project

1.
Select Options > Project Information to open the Edit Project Information dialog (FIG. 37):
FIG. 37 Edit Project Information dialog
2.
Edit the Project Name and Master Name fields as desired.
3.
Click OK to close the dialog and save your changes.

Device Mapping

In order to transfer the system files to the correct devices, each file must have correct Device Mapping
information. NetLinx requires a Device:Port:System (D:P:S) specification for each file.



Device:Port:System (D:P:S)

A Device is any hardware component that can be connected to the NetLinx bus. Each Device must be assigned
a unique number to locate that Device on the bus.


NetLinx requires a Device:Port:System (D:P:S) specification. This D:P:S triplet can be expressed as series of
constants, variables separated by colons, or as a DEV structure, to explicitly represent a device number, port
and system.
The syntax:
DEVICE:PORT:SYSTEM
where:
18
If you are working with an RPMX project file (generated by the RPM web application), then the
device mapping is already established for each file that is indicated in the RPMX file, and is
displayed in the Mapping column of the File Transfer Status Window.
However, If you have added one or more local files to the transfer, or if you have created your own
RPM file in RPMLoader, then it will be necessary to define device mapping information for each
file indicated in File Transfer Status Window.
The NetLinx language allows numbers in the range 0-32767.
Device 0 refers to the master; numbers above 32767 are reserved for internal use.
RPMLoader