Axcess to NetLinx Conversions
Table of Contents
Axcess to NetLinx Conversions
Devices in NetLinx are now Device:Port:System variables instead of Integer variables. This means you can no longer assign a DEVICE identifier to an integer variable such as:
CURR_DEV = PUSH_DEVICE
NetLinx does allow you to accomplish the same thing using event operators. From within a BUTTON_EVENT, you would use the following:
CURR_CHAN = BUTTON.INPUT.CHANNEL
(Gives you the current push channel as an integer.)
CURR_DEV = BUTTON.INPUT.DEVICE.NUMBER
(Gives you the current push device as an integer.)
You can also use:
CURR_DEVICE = dvVCR.NUMBER
(from anywhere in your code)
NetLinx includes many new KEYWORDS; such as DEV, SWITCH, CASE, CHAR, FOR, LONG, and many others. It is important that you don't use these KEYWORDS as user defined identifiers. The compiler will catch these errors and allow you to fix them. A list of these are in the help section of NetLinx Studio.
In NetLinx, WHILE loops no longer timeout after a half second. Relying on the WHILE timeout was never recommended, but now it can lock you into an endless loop. WHILE loops now behave just like MEDIUM_WHILE loops.
DEFINE_COMBINE statements require the use of a Virtual Device. Virtual Devices are declared in the DEFINE_DEVICE section and have a value between 32768 and 36863. The Virtual Device must be the first device in the DEFINE_COMBINE list. The master treats the Virtual Device just like any other device, except the Virtual Device can never go offline. This resolves some problems associated with the first device in the DEFINE_COMBINE list falling offline.
•NetLinx has a more robust, and more strict compiler. Errors that were overlooked in Axcess, will be caught in NetLinx. This means that older Axcess code that compiled error free, may not compile in NetLinx. This does not mean that the language changed, only that certain errors did not surface under the Axcess Compiler.
•Once you have downloaded your program to the NetLinx Master, you must reboot the Master. The Master must be rebooted for any changes to the Master to take effect; including program downloads, system number changes, and Network IP address changes.
Table of Contents