AMX Notes:

D:P:S

device numbers:

Master 0
1-255 AxLink Devices
301-3072 NetLinx Card Frames (discontinued)
5001 NetLinx Controller
5002 NetLinx Switcher Device
5003 - 10000 NetLinx ICSLan Devices (below):

EXB (ICSLan) Boxes 5101 - 5164

DXLink TX 5301 - 5364
DXLink RX 5401 - 5464
Legacy Devices 7000 - 8000
NetLinx IP Devices 8001 - 10000

10001 - 32000 NetLinx Peripheral Devices (below):

In room TP start @ 10001
schedualing TP start @ 10101
AMX Digital Signage @ 20001
(range is 32000)

start virtual devices at 33001 (range from 32001 - 33000 not typically used)

32001 - 32767 Dynamic Devices

32768 - 36864 Virtual Devices
36865 - 37864 Dynamic Virtual Devices
37865 - 40999 NetLinx Module Virtual Devices
41001 - 42000 Duet Module Virtual Devices

an IP addressed device will have a device number of 0

Port numbers:

port 1 = master
port 2 not used

Axlink devices port 1 always

legacy systems (3001 - 3072) reference sheet on website
controllers [5001 devices] (range only for NX and DVX-X200)
Serial 1 - 10
IR 11 - 20
Relays 21
I/O 22

Switcher Devices [5002 devices]

video 1 enova
audio 2 dgx 100
send command section of hardware ref manuel

EXB-REL8 and EXB-I/O8 use port 1

5301 -5464 DXLink have 8 ports

modero TP - (example) max of 100 ports don't use high numbers

DEFINE_DEVICE
dvTP_Conf102Audio = 10001:4:S
dvTP_Conf102Lights = 10001:5:S

greater then 32000 us 1

System Numbers:

each master needs a unique system number (valid range is 1 - 65535)

examples:

dvConf102Master = 0:1:102; // Master

dvConf102Keypad = 85:1:102; // AxLink Keypad

dvConf102DVD = 5001:2:102; // DVD RS-232 port #2

dvConf102BluRay = 5001:11:102; // BluRay IR port #1

dvConf102Proj = 5401:1:102; // Projector DX-RX RS-232

dvConf102TP_Nav = 10001:1:102; // Room Touch Panel

system 0 means this system

DEFINE_DEVICE
dvMaster = 0:1:0

the code could be written in the master with system 0 and then loaded to each
extended master
the master assigned system # can never be 0

style guide:

www.amx.com
products - development tools - netlin studio
right side has the style guide also in the resources in training

single line note = // xxx

multi line note = (* xxx *)

Events

event handlers:
* DATA_EVENT
* BUTTON_EVENT
* CHANNEL_EVENT
* LEVEL_EVENT
* TIMELINE_EVENT

button events:
push = on
release = off
hold = stay on until released

Device channel pair

DEVCHAN
[dpTP,1]

TP - channel codes can be anything between 1 -4000

set_pulse_time 12 = 1.2 seconds

set_pulse_time 5 = every time pulse time is changed

push:
{
to[xxxx]; //this turns on output channel for as long as button is pushed
}

push:
{
min_to[xxxx]; //this turns on output for push only for pulse time or released
which ever is longer
}

info highlight keyword then press F1

Mutually exclusive = if one is true the other is false or on and off

([dvRelays,SCREEN_UP],[dvRelays,SCREEN_DOWN],[dvRelays,SCREEN_STOP])

if consecutive you can use a range

([dvRelays,SCREEN_UP]..[dvRelays,SCREEN_STOP])

and combine

([dvRelays,SCREEN_UP]..[dvRelays,SCREEN_STOP],[dvRelays,SCREEN_PRESET])

total_off turns off mutually exclusive set

Feedback:

momentary feedback = fake feedback (no traffic) on confirmation of transmission or

reception

pseudo feedback = button received by master but not the actual status of device
(typical with IR)

true feedback = gives actual status of device but might not be possible with all
devices (serial or IP) or native netlinx devices
in the feedback channel

tech note 993 (read) about feedback