LONMARK Product Conformance Review and Checklist

Transcription

1 LONMARK Product Conformance Review and Checklist November 2001 Introduction This Guide outlines the steps to follow to demonstrate conformance with the LONMARK Interoperability Guidelines and obtain a license to use the LONMARK logo on a product. There are five major steps to the LONMARK Conformance process: 1. Design and in-house testing of product according to the LONMARK Interoperability Guidelines 2. LONMARK Conformance Review application and documentation submittal 3. LONMARK Conformance Review 4. Conformance confirmation and license agreement. 5. Conformance maintenance Whom to Contact if you have Questions Any questions you have concerning the contents of this Guide, or interpretations of the LONMARK Interoperability Guidelines, should be directed to: LONMARK Technical Office Tel: Fax: tech@lonmark.org Step 1 Design and In-House Testing of Product The LONMARK Interoperability Guidelines provide direction on how to use the LonWorks protocol to design interoperable LONWORKS products. The Guidelines outline specific selections to make at each of the seven layers of the LonWorks protocol. Some of these selections are made within the LonBuilder or NodeBuilder software, others through statements in the Neuron C application code, and others refer to specific hardware that should be used. You should follow the Interoperability Guidelines exactly for products that are to carry the LONMARK logo. A checklist is provided for recording that all the Interoperability Guidelines have been followed. Please include this completed checklist with your application. Once you have completed design and testing of your product you are ready to submit your application for the LONMARK Conformance Review. LONMARK Interoperability Association Page 1 of 16 Part Number Rev L

2 Step 2 LONMARK Application & Documentation Submittal The LONMARK Conformance Review has been designed with the goal of minimizing the amount of effort and paperwork required. The actual product does not need to be submitted. The list below outlines the information that is required to begin the review of your product. To submit products for the LONMARK Conformance Review you must be an up-to-date LONMARK Partner or Sponsor member of the LONMARK Interoperability Association. If you have not already enrolled as a LONMARK Partner or Sponsor you must include your completed LONMARK membership application with your submittal for the LONMARK Conformance Review. The Conformance Review of your first LONMARK product is included with your initial enrollment as a LONMARK Partner or Sponsor. A Standard Program Identifier (SPID) uniquely identifies each LONMARK product. A Standard Program ID must be selected for each product prior to submitting for LONMARK conformance review. The SPID is stored in memory on the product and its format is described in detail in the LONMARK Application Layer Interoperability Guidelines. Instructions for selecting a SPID are provided on the LONMARK web site ( in the Design Guidelines area of the Products section. If you have any questions please contact the LONMARK Association Principal Engineer (mailto:tech@lonmark.org). Required LONMARK application material: Paperwork: Software: LONMARK Membership Application - include if not already enrolled as a LONMARK member LONMARK Conformance Review Application - indicate product(s) to be reviewed Interoperability Checklist - submit a separate checklist for each product Product Documentation - submit documentation of the LONWORKS interface Signed LONMARK Logo License Agreement - complete Exhibit C indicating product(s) to be reviewed Product External Interface file (XIF), Device Resource Files (TYP, FMT, FPT, and at least one language file) if required. Please refer to the Guidelines to determine if the Device Resource Files are required. Page 2 of 16 LONMARK Interoperability Association

3 Step 3 LONMARK Conformance Review The review process is as follows: a) After receipt of your application and payment, the review of your product can begin. Reviews are conducted on a first-in-first-out basis. b) The review process is interactive. As errors are encountered during the process, the reviewer will contact you to make changes, and again review the newly submitted materials. This process continues until your node passes the review. Providing the corrected materials are submitted within sixty (60) days, starting from when you receive feedback, no additional fees are required at the time of resubmission. Once the review of your product, is complete you will receive an (or fax) review summary, followed by an official letter on completion via postal mail. LONMARK Interoperability Association Page 3 of 16

4 Step 4 Conformance Confirmation & the LONMARK License Agreement Once you receive your LONMARK Conformance Confirmation you will be eligible to incorporate the LONMARK logo on the product, packaging and related promotional material. The LONMARK Logo is a registered trademark of Echelon Corporation in the United States and other countries. The ability to use the Logo is governed by a license agreement as follows:. The LONMARK License Agreement The LONMARK License Agreement details the legal restrictions on the use of the LONMARK logo. The completed agreement will be returned to you upon successful completion of the LONMARK Conformance Review. The LONMARK License is valid for two years from the effective date. After two years, both the LONMARK Interoperability Association and your company may elect to re-license the LONMARK logo. Transferability of LONMARK License Agreement If the right to manufacture or provide a LONMARK product, product line, or service is transferred from a manufacturer to a different corporate entity, the right to use the LONMARK logo is assignable by the manufacturer with the prior express approval of the LONMARK Interoperability Association. The association approval is subject to the following restrictions: The LONMARK product should be functionally unchanged by the transfer. Any change to the functionality requires re-testing. The buyer should have a LONWORKS OEM License Agreement on file with Echelon Corporation. The buyer should submit a modification to the LONMARK License Agreement to reflect the new product ownership. Discontinuance You may wish to discontinue the use and support of the LONMARK logo on a particular product or family of products some time in the future. You should notify the LONMARK Interoperability Association in writing prior to the planned discontinuance of use. This notification should clearly identify all products involved, the effective date, and the reasons for the planned discontinuance. The association will confirm the discontinuance with you prior to the effective date. On the effective date of discontinuance, you should cease to use, display, advertise and promote the LONMARK logo relative to the products involved. Page 4 of 16 LONMARK Interoperability Association

5 Step 5 Maintaining Conformance Existing LONMARK Products Once a product has successfully passed the LONMARK Conformance Review it can carry the LONMARK logo. If you need to make any revisions or modifications to the function of the product that affect its network behavior then you have in essence created a "new" product. This "new" product should be tested following the normal procedure to ensure it is compliant with the LONMARK Interoperability Guidelines. If changes to a product have NOT created a "new" product, for instance only the packaging or name has changed, then you may apply for a modification of an existing License Agreement. Modification of Existing License Record To request modification of an existing License Record, you should submit a new LONMARK License Agreement with a cover letter that addresses the changes. When the LONMARK Interoperability Association receives the modified License Agreement, the LONMARK Secretary will review it for accuracy, and upon approval, a revised License Record will be issued. Customer Reports As a LONMARK member, we value your help in letting us know of any problems experienced between any of your licensed products and any other product bearing the LONMARK logo. Your feedback will help us continue to improve the conformance review and refine the design guidelines. Step 6 What if the technical guidelines do not meet your needs? The LONMARK Interoperability Guidelines are designed to apply across a broad range of industries. The guidelines are generic, rather than specific to a given industry or application and can be readily adapted to address industryspecific needs. However, some manufacturers may have particular needs not addressed by the guidelines. For example your application may require new transceiver types or functional profiles that are not already defined. The guidelines exist to serve the interests of manufacturers and end-users and thus, if a problem is encountered, it should be brought to the immediate attention of the LONMARK Principal Engineer. Working groups will be convened as necessary to address any technical issues. LONMARK Interoperability Association Page 5 of 16

6 LONMARK Conformance Review Application November 2001 Applicant Name: Primary Contact: Title: Company: Address: City, State (Province): ZIP (Postal Code), Country: Telephone: Fax: Products to be Reviewed The following products are submitted for the LONMARK Conformance Review Product Name Standard Program Identifier (SPID) LONMARK Interoperability Association Page 6 of 16

7 Testing Fees The following testing fees apply: First Product US$ products (US$2,000 per product) 5-9 products (US$1,500 per product) 10 + products (US$1,000 per product) US$ US$ US$ Please enclose payment for any applicable testing fee with this application (Make check or Purchase Order payable to the LONMARK Interoperability Association). Billing address for invoices: Name: Title: Company: Street: City, State (Province): ZIP (Postal Code), Country: Telephone: Fax: Please mail the completed application, together with payment of the appropriate testing fee in U.S. dollars, to: Secretary/Treasurer LONMARK Interoperability Association 550 Meridian Avenue San Jose, CA USA Tel: Fax: secretary@lonmark.org , LONMARK Interoperability Association. Echelon, LON, LONWORKS, LonBuilder, NodeBuilder, LonTalk, Neuron, LONMARK, and the LONMARK logo are trademarks of Echelon Corporation registered in the United States and other countries. Part Number Rev M LONMARK Interoperability Association Page 7 of 16

8 LONMARK Interoperability Guidelines Checklist November 2001 Applicant Name: Product Name: Standard Program ID: (hex) 8 : Manufacturer ID: (hex) (dec) Device Class: (hex) (dec) Device Subclass: (hex) (dec) Model Number: (hex) (dec) Communication Media: (hex) (dec) Standard Transceiver Name: Neuron Chip Clock Rate: MHz Standard LONMARK Objects Supported (dec ): User-Defined LONMARK Objects Supported (dec ): External Interface File (XIF) Name: Associated Device Resource Files (TYP, FMT, FPT, language files): Passive Configuration Tool Description: Other Agency Approvals (UL, cul, CE, TÜV, etc.): LONMARK Interoperability Association Page 8 of 16

9 Indicate that all guidelines were complied by marking a check in the boxes provided, or N/A if the guideline is not applicable to your implementation. Do not leave blank. Application Layer (Layer 7) The following guidelines are from the LONMARK Application Layer Interoperability Guidelines V3.2 manual (LYR732.PDF, E). or N/A Application-Layer Guideline 2-1: The LONMARK interoperable file transfer protocol must be used for communicating files of data. Data must be sent in 32-byte packets (not including protocol overhead) with a window size of 6 packets. Application-Layer Guideline 2-2: Message Code 0x3E is reserved for the exclusive use of LONMARK Interoperable file transfer protocol. The LONMARK Interoperable file transfer protocol is used for the transfer of the Configuration Template file and the Configuration Parameter Value file as well as any user-defined files. Application-Layer Guideline 2-3: Message Code 0x4E is reserved for the transfer of the ANSI/ASHRAE BACnet NPDU frames. Application-Layer Guideline 2-4: Message Code 0x4F is reserved for future use. Application-Layer Guideline 3-1: LONMARK objects must be used as the building blocks for designing the application-layer interface. Application-Layer Guideline 3-2: If a LONMARK object is implemented then, as a minimum, the node must implement all the object's mandatory network variables. Application-Layer Guideline 3-3: Any LONMARK Guidelines-compliant node that supports more than one LONMARK Object must include a Node Object to allow monitoring and control of the objects within the node. Single-object nodes also require a Node Object if the node implements alarms, self-test, range checking, fault detection, file transfer, or other functions belonging to the Node Object; or if the application program must continue to operate when the object is disabled. Application-Layer Guideline 4-1: A given configuration property can be implemented as either a config class network variable or as a configuration parameter. Application-Layer Guideline 4-2: User-defined configuration properties, which must be modified for successful commissioning of the device, must either be defined with resource files and user documentation or a passive tool must be provided. The documentation and resource files, if any, must be supplied at the time the node is certified. The passive tool, if any, must be available at the time the node is certified. Application-Layer Guideline 4-3: If a passive tool is required for successful commissioning of a device, the tool shall conform to the definition of a passive tool in Chapter 1 of the document, and shall be available to anyone owning the device on equivalent business terms, and such availability shall be demonstrably free of any discriminatory terms and conditions. Application-Layer Guideline 4-4: If no passive tool is required for the successful commissioning of a device, any and all configuration information required to be modified to successfully commission the device shall be implemented and exposed via LONMARK configuration properties and user documentation. LONMARK Interoperability Association Page 9 of 16

10 Application-Layer Guideline 4-5: Host-based nodes that support configuration parameters shall use the Configuration Parameter Template file and the Configuration Parameter Value file. Other applications may also optionally use this method, or may use a derivative form of this method called direct memory read/write configuration parameters as long as the configuration parameters may be read and written with the standard read/write memory messages in the LONWORKS protocol. Application-Layer Guideline 4-6: File type 0 (zero) must not be used. Application-Layer Guideline 4-7: File type 2 must be used for the SCPT file template. Application-Layer Guideline 4-8: The first file index defined on the node must be the Configuration Parameter Template File (file type 2) and the second file index defined on the node must be the Configuration Parameter Value File (file type 1). Application-Layer Guideline 4-9: If the optional constant Configuration Parameter Value file is defined on a node, it must be the third file defined (file index 2), and it must be of file type 1. Application-Layer Guideline 4-10: The transfer of the Configuration Parameter Template file and the Configuration Parameter Value file must be accomplished using message code 0x3E. Application-Layer Guideline 4-11: File type 0 through file type 127 and file type 256 through file type 32,767 are reserved for LONMARK usage. File types 128 through file type 255 and file type 32,768 through 65,535 are available for user-defined file types. Application-Layer Guideline 5-1: The node documentation string format specified in Chapter 5 of the LONMARK Interoperability Guidelines must be used to encode instances of objects to their object types. Application-Layer Guideline 5-2: The node documentation string must be stored in the node's memory. Application-Layer Guideline 5-3: Standard Program Identifiers (SPIDs) must be used. Application-Layer Guideline 5-4: A node's application program that wishes to communicate its physical location or ID assignment to a network management tool may write this information into the location ID field of its configuration structure when the node is reset. This information must be either a 15-bit unsigned integer, or a 0-6 -character ASCII string. If the physical ID is a simple integer in the range , the first byte (location[0]) contains the upper byte of this integer in binary, with the most significant bit set to one. The second byte (location[1]) contains the lower byte of the physical ID. If the most significant bit of the first byte is zero, the location field will be interpreted as a string of ASCII characters of from 0 to 6 bytes in length. If the string is shorter than 6 characters, it must be null-terminated. Application-Layer Guideline 5-5: User defined network variable interfaces within objects that are intended to be a part of the object's interoperable interface shall have a user functional profile template resource file (*.FPT) created for the device. Application-Layer Guideline 5-6: Network variable self-documentation strings as specified in Chapter 5 of the LONMARK Interoperability Guidelines must be used to map network variables to the objects declared on the node. Application-Layer Guideline 5-7: The network variable documentation string must be stored in the node's memory. Page 10 of 16 LONMARK Interoperability Association

11 Application-Layer Guideline 5-8: If the application is hosted on a processor other than the Neuron Chip then the network variable documentation strings must be provided as a response to the Query SNVT command issued by a network management tool. Application-Layer Guideline 5-9: Either a passive tool must be available at certification time or all user defined network variable types that are part of the application' s interoperable interface must have definitions contained in a resource file that is supplied along with the other materials required for node certification. These files shall define the user types and enum values (*.TYP), formatting information for rendering the user types (*.FMT), and string resource files for at least one language (*.<language extension>). Application-Layer Guideline 6-1: If network variable selection is performed on the host, then the host application must manage a network variable configuration table, and respond correctly to the Update and Query NV Config messages using the data structure defined in the Neuron Chip Data Book. Application-Layer Guideline 6-2: Host-based nodes must preserve network variable configuration table contents across hardware resets and power cycles. Application-Layer Guideline 6-3: The host must determine whether authentication is required for a network variable, based on the authentication bit in the corresponding network variable configuration table entry on the host. If a network variable is configured to be authenticated, then the host application must reject an unauthenticated update or poll to that network variable. Application-Layer Guideline 6-4: The host application must respond to Network Variable Fetch and Network Variable Poll request messages with the appropriate data from the requested network variable. If the application is in the Off-line mode when a Network Variable Poll is received, the response must contain no data. Otherwise, the response must contain the correct number of bytes of data as specified by the network variable type. Application-Layer Guideline 6-5: The host application must deliver the nionline and nioffline commands to the network interface when the Mode On-line and Mode Off-line messages are received. Application-Layer Guideline 6-6: The host application must ensure that the Standard Program ID (SPID) is present in the network interface. Application-Layer Guideline 6-7: The host application must implement the LONMARK self - documentation requirements. It must respond to the Query SNVT request message with the same data that a Neuron Chip -based node would respond with. The appropriate data structures are defined in the Neuron Chip Data Book. Application-Layer Guideline 6-8: If a developer chooses to incorporate the optional feature of dynamic Network Variables, the implementation shall conform to the three requirements listed in Chapter 6 of the LONMARK Application Layer Interoperability Guidelines. Application-Layer Guideline 7-1: Wherever possible the maximum number of 15 address table entries should be supported on a node to avoid binder failure. As a minimum nodes must support a number of address table entries equal to the number of non-configuration network variables plus the number of bind-able message tags, or 15, whichever is less. Application-Layer Guideline 7-2: A node must support a reasonable number of network variable aliases to avoid network variable connection constraints. LONMARK Interoperability Association Page 11 of 16

12 Application-Layer Guideline 7-3: All LONMARK Guidelines-compliant nodes must support 2 domains to facilitate integration into subsystems, and subsystems into systems. Application-Layer Guideline 7-4: It must be possible to configure a self-installed node with a network management tool and have that node's address be set to any legal LonTalk protocol address. Application-Layer Guideline 7-5: Self-installed nodes shall not modify their Channel ID field. Application-Layer Guideline 7-6: Nodes must be manufactured with a 0 (zero) Channel ID. Application-Layer Guideline 7-7: A node's application program must not be dependent upon its network configuration. Application-Layer Guideline 7-8: All nodes must provide internal or external access to the service pin. Application-Layer Guideline 7-9: A sub-system must include one or more sub-system gateways to allow connection to an interoperable system. Application-Layer Guideline 7-10: A sub-system gateway external interface node must meet all the Interoperability Guidelines. Application-Layer Guideline 7-11: Under no conditions shall a LONMARK gateway pass commands from a command-based system directly into a LONWORKS network. Instead, these commands shall be mapped to LONMARK objects. Application-Layer Guideline 7-12: Nodes intended for installation on shared media (see Shared Media Considerations in Chapter 7 of the Interoperability Guidelines) must provide some means for locally causing the node to go unconfigured, for example by invoking the Neuron C go_unconfigured() function. Application-Layer Guideline 7-13: Nodes intended for installation on shared media (see Shared Media Considerations in Chapter 7 of the Interoperability Guidelines) must support the wink function and must provide a wink that does not create a potentially dangerous or costly situation if invoked at any arbitrary time in the operational life of the node. Layers 2-6 The following guidelines are from the LONMARK Layers 1-6 Interoperability Guidelines V3.0 manual (LYR1630.PDF, E). or N/A To be interoperable, all of the nodes on a channel must be configured with the same channel parameters and the parameters must be for one of the standard transceiver types. Minimum acceptable clock rate is indicated in table 3-1. An oscillator with an accuracy of 0.02% or better must be used. The default number of priority slots must be configured as shown in table 3.1. Application nodes must not use priority slot 1; it is reserved for use by network management tools. Network input buffers must be at least 66 bytes. Page 12 of 16 LONMARK Interoperability Association

13 Network output buffers must be sized to accommodate the longest packet that the node can send. Priority network output buffers are necessary if the product can send priority messages or network variables. The receive transaction buffer pool must be sized to the LonBuilder minimum default or greater. The formula for the default is given in table 6-1 of the Neuron C Programmer's Guide. Neither Acknowledged nor Request/Response service is permitted for packets requiring a network output buffer greater than 66 bytes. Physical Layer (Layer 1) The following guidelines are from the LONMARK Layers 1-6 Interoperability Guidelines V3.0 manual (LYR1630.PDF, E). or N/A Specified transceiver schematics must be followed exactly. TP/XF78 and TP/XF1250 physical channels PCB trace lengths between the TPT/XF module P2 header and the twisted pair stub connector should be kept less than 5 cm for the TPT/XF-78 module and less than 2 cm for the TPT/XF-1250 module. The total differential trace capacitance between CP0 and CP1 lines connecting the TPT/XF module and the Neuron Chip must be 3 pf. The performance specifications listed in table 2.2 assume the use of UL Level IV, 22 AWG (0.65 mm) twisted pair cable. Use the specified termination circuit to terminate TP/XF-1250 and TP/XF-78 physical channels. TP-RS physical channel Use the specified termination circuit or a TP/XF terminator to terminate the TP-RS channel. The TP-RS nodes must comply with the grounding requirements of the EIA RS-485 Standard detailed in the EIA RS-485 Specification Section A.3 entitled Optional Grounding Arrangements. PL-10(L-N) and PL-10(L-E) physical channels When connecting the input (line side) of a switching power supply directly to the coupling circuit of a PLT-10A -based device, the guidelines for preventing the switching supply from attenuating the communications signal as outlined in the PLT-10A User's Guide must be followed. When connecting the input (line side) of a switching power supply directly to the coupling circuit of a PLT-10A -based device, the guidelines for preventing the switching supply from conducting excessive noise onto the communications channel as outlined in the PLT-10A User's Guide must be followed. LONMARK Interoperability Association Page 13 of 16

14 PL-20(L-N) and PL-20(L-E) physical channels When connecting the input (line side) of a switching power supply directly to the coupling circuit of a PLT-20 -based device, the guidelines for preventing the switching supply from attenuating the communications signal as outlined in the PLT-20 User's Guide must be followed. When connecting the input (line side) of a switching power supply directly to the coupling circuit of a PLT-20 -based device, the guidelines for preventing the switching supply from conducting excessive noise onto the communications channel as outlined in the PLT-20 User's Guide must be followed. PL-30(L-N) physical channels When connecting the input (line side) of a switching power supply directly to the coupling circuit of a PLT-30 -based device, the guidelines for preventing the switching supply from attenuating the communications signal as outlined in the PLT-30 User's Guide must be followed. When connecting the input (line side) of a switching power supply directly to the coupling circuit of a PLT-30 -based device, the guidelines for preventing the switching supply from conducting excessive noise onto the communications channel as outlined in the PLT-30 User's Guide must be followed. TP/FT-10 physical channel All nodes on a TP/FT-10 channel shall operate normally while meeting the EMC standards detailed in Table 2.9 of the LONMARK Layers 1-6 Interoperability Guidelines. The TP/FT-10 channel performance is characterized for the cables listed in Table One of the listed cables must be used for the network wiring. Cables shall meet specifications outlined in Appendix A. If the cable has a shield, the shield shall be connected to link power source ground via a 470kΩ, ¼ -Watt, 10%, metal film resistor to prevent static charge build up. No more than one physical-layer repeater shall be in a path between two nodes on a network. Physical-layer repeaters shall not be interconnected in such a way as to create a loop. A singly terminated free topology network shall have a single termination provided by the link-power source. This termination shall be approximately 53Ω. The link-power source and termination may be located at any point in the network. A doubly terminated bus topology network shall have two terminators. One terminator shall be provided by the link-power source. This termination shall be approximately 105?. The second termination shall be as shown in Figure 2.8. One terminator shall be placed at each end of the bus. A Link-Power Unit Load (LPUL) is defined to be 285mW DC drawn from the network. A node may consume multiple Link-Power Unit Loads. A maximum of 128 LPULs is allowed on the network. A link-powered node shall meet the requirements of Table A TP/FT-10 node shall sustain no hard failure, and shall start up successfully when plugged into a powered network. Page 14 of 16 LONMARK Interoperability Association

15 The transmitter shall employ differential Manchester encoding of data and clock information with a raised cosine waveform as illustrated in figures 2.10 and The polarity of the transmitted waveforms may be inverted depending on the state of the preceding bit; at the start of transmission, polarity is arbitrary. The transmitter peak amplitude (Vp) into a network termination of approximately 53Ω (as defined earlier in the cable termination section) connected directly at the transceiver output shall be between and V over all manufacturing variations and operating conditions. At the end of packet transmission, the waveform shall remain transitionless for at least 3 bit-periods after the final clock transition (excepting the final data transition, if present). The net voltage remaining on the transmission line after 8 bit-times from the last clock transition shall be more than that created by transmitting a pulse of either polarity at peak amplitude for one-half of a bit-time. The delay from the Neuron Chip transmit enable output to the start of transmission on the network shall not exceed bit-times. The voltage spectrum into a network termination of approximately 53Ω (as defined earlier in the cable termination section) connected directly at the transceiver output shall meet the maximum specification of figure 2.12 over all manufacturing variation and operating conditions. The data pattern to be used for evaluating the voltage spectrum shall be generated by the CRC polynomial X 8 + X 6 + X 5 + X A node shall meet the minimum impedance specified in figure In link-powered nodes, a notch in the impedance specified by figure 2.13 is permitted to allow use of fixed-frequency switching regulators. This notch shall be less than 3kΩ in depth, less than 0.25f in width and above 1.6f, where f=78.125khz. During packet transmission, the transmitter impedance shall be a minimum of 2000Ω from 0.1f to 2f. The receiver shall ensure reception of data by the Neuron Chip under all conditions allowed by the TP/FT-10 system and all node specifications. LONMARK Interoperability Association Page 15 of 16

16 Checklist completed by: Signature: Name (Print): Title: Company: Date: Please mail the completed application and checklist to: Secretary/Treasurer LONMARK Interoperability Association 550 Meridian Avenue San Jose, CA USA Tel: Fax: , LONMARK Interoperability Association. Echelon, LON, LONWORKS, LonBuilder, LonTalk, Neuron, LONMARK, and the LONMARK logo are trademarks of Echelon Corporation registered in the United States and other countries. ASHRAE and BACnet are registered trademarks of the American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. Part Number Rev M Page 16 of 16 LONMARK Interoperability Association