Lab.gruppen NLB 60E Description
Third party integration
Hide thumbs
Also See for NLB 60E:
- Supplementary manual (1 page) ,
- Specifications (2 pages) ,
- Operation manual (35 pages)
Related Manuals for Lab.gruppen NLB 60E
Summary of Contents for Lab.gruppen NLB 60E
- Page 1 File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc’ Modified: Jan 16, 2009 Page 2 of 21 NLB 60E Third Party Integration Protocol Description (Revision 2) Date: January 16, 2009 Revision: 2A...
-
Page 2: Table Of Contents
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 3 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc Index PROTOCOL OVERVIEW..................5 CONNECTION MANAGEMENT................6 .................... 6 ESSAGE SEQUENCING ADDRESSING ......................7 .................... - Page 3 Device Control Lab.gruppen application for control and monitoring of a NomadLink network. General Purpose Input, ports on the back of NLB 60E that can trigger certain actions on the NomadLink network NLB 60E Network bridge between an Ethernet and NomadLink network Subnet Denotes a NLB 60E and its connected amplifiers.
-
Page 4: Protocol Overview
File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 1 Protocol overview The described protocol in this document is both an extension and a revision of the previous 3 party protocol for the NLB 60E. The following is a short summary of controllable and monitorable parameters. • Mute/Un-mute... -
Page 5: Connection Management
From a clients view, a message session adheres to the following sequence. After establishing a connection it is possible to send one or multiple messages to the NLB 60E. The messages will be handled sequentially in the order they are sent and responses will be sent back accordingly. -
Page 6: Addressing
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 7 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 3 Addressing 3.1 Addressing a bridge The bridge is addressed using its IP-number. For fixed installations relying on static IP addresses it is highly recommended that bridges have fixed IP addresses instead of using DHCP. -
Page 7: Example Communication
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 8 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 4.1 Example communication For example, to mute the subnet the following string is sent (note that it ends with a newline character!): Subnet.Mute = 1 The reply would then be (also ending with a newline character):... -
Page 8: Message Reference
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 9 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 5 Message reference 5.1 Error replies If an error occurs the bridge responds with ‘ERROR! [Message]’ where the message part is a more detailed description of the error. -
Page 9: Subnet Mute
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 10 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 5.2.2 Subnet Mute Sets / gets subnet mute control (mutes or un-mutes all devices in the subnet) Address Value Subnet.Mute... -
Page 10: Subnet Status
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 11 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 5.2.4 Subnet Status Gets full status for entire subnet. Address Value Subnet.Status Reply (values from top to bottom) [XX] –... -
Page 11: Subnet Serial At Position
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 12 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 5.2.5 Subnet Serial at Position Gets serial number for an amplifier at the position given by the ‘value’ field. Address Value Subnet.SerialAtPosX... -
Page 12: Mute
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 13 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 5.3.2 Mute Set / get mute control for an individual channel Address Value [VDN].MuteX 0 –... -
Page 13: Mute Status
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 14 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 5.3.3 Mute Status Get mute status for individual channels for one device Address Value [VDN].MuteStatus Reply [Mute status] –... -
Page 14: Status
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 15 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 5.3.4 Status Gets overall status and metering information for a device. Address Value [VDN].Status Reply (values from top to bottom) 0 –... -
Page 15: Virtual Device Name Management
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 16 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 5.4 Virtual Device Name Management 5.4.1 Subnet VDN Sets / gets a VDN entry i.e. virtual device name and associated serial number. This command is only supplied as an alternative way for administration of the VDN table. -
Page 16: Virtual Device Name Manager - Operations Manual
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 17 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 6 Virtual Device Name Manager – Operations manual 6.1 The VDN Manager application The VDN application is a stand-alone program that is not part of the DeviceControl software package. -
Page 17: Adding Devices To The Virtual Device Name Table
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 18 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 6.3 Adding devices to the virtual device name table 6.3.1 Adding devices that are present on the NomadLink network 1. - Page 18 Document type: Last modified: Page: Technical Documentation 09-01-16 Page 19 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 3. Edit the virtual device name by selecting the cell and typing the desired name. The name must: a) only include characters A-Z, a-z, 0-9, @ and - b) not start with the name "Subnet".
-
Page 19: Adding Devices That Are Not Present On The Nomadlink Network
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 20 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 6.3.2 Adding devices that are not present on the NomadLink network 1. Click on the row marked by a star to add a new entry to the virtual device name table. The Position column will state “Missing”... -
Page 20: Replacing A Device In The System
Document type: Last modified: Page: Technical Documentation 09-01-16 Page 21 of 21 Based on template: ‘Technical Documentation.dot’ File: ‘NLB-60E communication protocol - Revision 2 DRFT 2A.doc 6.4 Replacing a device in the system 6.4.1 Replacing with a device that is already present on the NomadLink network 1.