Working with System Files
67
NetLinx Studio - Instruction Manual
Device Mapping
The Device Mapping dialog (see FIG. 128 on page 68) allows you to map files to System devices for file transfers. To
access this dialog, select a System (in the Workspace tab of the Workspace Bar) and select Project > Device Mapping.
Alternatively, use the Device Mapping command in the Source File, User Interface, and IR File context menus, or use the
toolbar button.
Also, every time you select a file (to send or receive) via the Select Files For File Transfer dialog (Other tab), the
program prompts you to enter (or verify) its device mapping information, in the Enter Device Mapping Information
dialog. Use this dialog to define the Device:Port:System (D:P:S) address assignment for a target device as described in
the Creating Device Mapping Assignments section on page 68.
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. The Axcess language allows physical device numbers in the range 0-255. The
NetLinx language allows numbers in the range 0-32767. Device 0 refers to the master; numbers above 32767 are
reserved for internal use.
NetLinx requires a Device:Port:System (D:P:S) specification where Axcess expected only a device number. The D:P:S
triplet can be expressed as series of constants, as variables separated by colons, or as a DEV structure, to explicitly
represent a device number, port, and system.
Here's the syntax:
DEVICE:PORT:SYSTEM
where:
Device: 16-bit integer representing the device number
Port: 16-bit integer representing the port number (in the range 1 through the number of ports on the device)
System: 16-bit integer representing the system number (0 = this system) that the device belongs to.
For example, 128:1:0 represents the first port on device 128 on this system.
DEV structure example:
STRUCTURE DEV
{
INTEGER Number // device number
INTEGER Port // port on device
INTEGER System // system device belongs to
}
In Axcess, Master Source Code files are always mapped to the Master Controller
(device = 0), and cannot be mapped to any other device. This does not apply to
NetLinx Master Source Code files.
To Next Page
Loading...
Need help?
General
