LonWorks Integration Guide CARRIER CORPORATION ©2010 A member of the United Technologies Corporation family · Stock symbol UTX · Catalog No.
Table of Contents Overview ....................................................................................................................................................................... 1 Before-you-begin checklist .......................................................................................................................................... 2 Assumptions .......................................................................................................................................
Overview LonWorks Integration with the i-Vu Link You can integrate LonWorks devices into an i-Vu CCN system with a i-Vu Link acting as a master device. Carrier i-Vu Link i-Vu Link LonWorks port S2 Module driver drv_ivulink_lon_.
Before-you-begin checklist Before-you-begin checklist Assumptions You know how to create custom equipment in ApplicationBuilder. You know how to install, wire, set up, and download memory to the i-Vu Link. The LonWorks network/devices have been commissioned by the third-party representative using LonMaker. Items to be installed at the job site Item Notes i-Vu Link LonWorks module driver drv_ivulink_lon latest version>.driver.
Before-you-begin checklist Other items needed for the integration Item Notes LonWorks Integration Tool Install from the Tools CD. Network variable information (.xif file) for each type of LonWorks device. For example, VAV Controller or Fan Coil Controller. Get from: Device address information (domain, index, subnet, and node address) Manual for each type of LonWorks device LonWorks • • • the third-party representative www.lonmark.com the LonWorks device. See Appendix B.
The integration process The integration process Follow the steps in this document to integrate one or more third party LonWorks devices into an i-Vu CCN system using an i-Vu Link. To install and network the i-Vu Link, see the i-Vu Link Installation and Start-up Guide. 1 Create custom equipment in ApplicationBuilder 1 Start ApplicationBuilder.
The integration process Point type Used for Link Integration Point to CCN Point Reading an analog or binary value from the third party device and then writing that value to the CCN network In: Link Integration Link CCN Passive Point to Integration Point Exposing an analog or binary value to the CCN network so that it can be written to the third party network In: Link Integration Read Integration Point Reading an analog or binary value from the third party device In: Read Integration, Link Integratio
The integration process 10 Click Next. 11 Equipment Name - type a new equipment name if desired. 12 Save Location - browse to a location where you would like to save the new custom equipment. Click Save. To format a LonWorks address All Lonworks addresses should be assigned to "lonworks://" only when setting up address strings in ApplicationBuilder. The LonWorks Integration Tool is used to define these addresses.
The integration process Method 2: Copy table point in i-Vu CCN 1 Launch i-Vu CCN. 2 Select the desired equipment in the navigation tree. 3 Expand the tables underneath that equipment. 4 Find the specific table and point that you want to read or write. 5 Click Copy in the table interface. 6 Inside of ApplicationBiuilder, hit CTRL-V to copy the CCN address from the table to the "ccn://" address field. Method 3: Map to point in i-Vu CCN 1 Launch i-Vu CCN.
The integration process 3 Assign and download custom equipment in i-Vu CCN 1 Open i-Vu CCN. 2 In the navigation tree, right-click the area where you want to place the custom equipment. Select Add Equipment from the drop-down menu. 3 Make the following entries: Field Notes Display Name Type an equipment name (i.e. ABB Drive).
The integration process 4 Click Save. 5 Browse to a location on your PC to save the file. (The file will have a .erl extension.) 6 Start the LonWorks Integration Tool (Lonworks_Integration_Tool.jar). 7 Click 8 Follow the wizard's instructions to create your LonWorks addresses. 9 Click to start the wizard to save the file to your PC. (The file will be saved with a .erl extension.) 10 Return to i-Vu CCN. 11 In the navigation tree, right-click on the custom equipment and click Configure.
The integration process 4 Wire the i-Vu Link's Port S2 to the SLTA-10's EIA-232 port using one of the following methods: ○ If you have an EIA-232/RS-232 straight-through cable with connectors and an S2-DB9 Adapter: Connect the adapter to the control module's port. Then connect one end of the cable to the adapter and the other end to the SLTA-10's EIA-232 port.
The integration process Field Notes Domain ID Locate this number in the .log file. The Domain ID is 1 2-character segment, 3 segments, or 6 segments. In the following example, the highlighted Domain ID is 1 2-character segment. In i-Vu CCN, type -00 after the ID as many times as needed so that the Domain ID field has 6 2-character sections. Subnet ID Locate this number in the .log file. The Subnet ID is highlighted in the following example.
The integration process 7 Verify the control module is set up correctly 1 Verify that the latest custom equipment have been downloaded into i-Vu CCN. 2 On i-Vu CCN's navigation tree, select the custom equipment for the i-Vu Link. 3 On the Properties page, select the Network Points tab. If... Then... You see the point value you expect with no errors in the Error column You have successfully established communication with the thirdparty device.
The integration process 3 On i-Vu CCN's navigation tree, right-click on custom equipment, select Driver Properties and then select Protocols. 4 Click Properties, select Enable Telnet diagnostics, then click Accept. 5 From the desktop, select Start > Programs > Accessories > Communications > HyperTerminal. 6 Type any name for your connection, then click OK. 7 In the Connect using field, select TCP/IP (Winsock). 8 In the Host address field, type the IP address of the i-Vu Link, then click OK.
Appendix B - Common HVAC SNVT's Appendix B - Common HVAC SNVT's SNVT # SNVT Name Element # Measurement Value 39 83 SNVT_temp SNVT_state 0 0 °C 84 SNVT_time_stamp 0 1 year month 2 day 3 hour -274 — 6,279.5 0 — 65,535 Each bit must be parsed out using control program logic. 0 — 3,000 1 — 12 = January — December 0 = month not specified 1 — 31 0 = day not specified 0 — 23 4 minute 0 — 59 5 second 0 — 59 0 1 zero offset span multiplier -163.84% — 163.835% 0 — 32.
Appendix B - Common HVAC SNVT's SNVT # LonWorks SNVT Name Element # Measurement Value 7 alarm type 8 priority level 9 index of NV in alarm -13 = Alarm header -12 = Alarm footer -11 = Alarm debug -10 = Alarm info -6 = Alarm system info -5 = Alarm value invalid -4 = Alarm constant -3 = Alarm offline -2 = Alarm unknown -1 = Value not available 0 = No alarm condition present 1 = Unspecified alarm condition present 2 = Total/service interval alarm 1 3 = Total/service interval alarm 2 4 = Total/servi
Appendix B - Common HVAC SNVT's SNVT # 95 SNVT Name SNVT_switch Element # Measurement Value 18 minute 0 — 59, 0=not specified 18 second 0 — 59, 0=not specified 20 millisecond 0 — 999, 0=not specified 21 — 24 alarm_limit 0 — 255, 0=not specified 0 value 0 — 100% 1 state enumerated 103 SNVT_hvac_emerg 0 106 SNVT_temp_setpt 0 °C occupied cool 0 = off, 1 = on, –1 = undefined 0 = normal 1 = emergency pressurize 2 = emergency depressurize 3 = emergency purge 4 = emergency shutdown
Appendix B - Common HVAC SNVT's SNVT # SNVT Name Element # Measurement Value 111 SNVT_hvac_overid 0 state 0 = Not overridden -1 = Value not available The next 16 override values apply to all devices or groups.
Appendix B - Common HVAC SNVT's SNVT # SNVT Name Element # Measurement Value 112 SNVT_hvac_status 0 mode 1 % primary heat output 0 = Controller automatically changes between application modes 1 = Heating only 2 = Application-specific morning warm-up 3 = Cooling only 4 = Application-specific night purge 5 = Application-specific pre-cool 6 = Controller not controlling outputs 7 = Equipment being tested 8 = Emergency heat mode (heat pump) 9 = Air not conditioned, fan turned on 10 = Cooling with com
Appendix B - Common HVAC SNVT's SNVT # SNVT Name Element # Measurement Value 4 1 = local 5 1 = limited 6 1 = chilled water flow 7 1 = conditioned water flow 2 Minutes to next state 0 = Area is occupied 1 = Area is unoccupied 2 = Area is temporarily occupied for the bypass period 3 = Area is temporarily unoccupied -1 = Value not available 0 = Area is occupied 1 = Area is unoccupied 2 = Area is temporarily occupied for the bypass period 3 = Area is temporarily unoccupied -1 = Value not availab
Appendix B - Obtain network, device, and network variable information Appendix B - Obtain network, device, and network variable information Use one of the following devices to temporarily connect a LAPTOP to the LonWorks network.
Appendix B - Obtain network, device, and network variable information 14. Type O (the letter, not zero). 15. Type a name for the file that NodeUtil will create with the LonWorks device's network variable information. EXAMPLE: vav_controller.log 16. Press Enter to create the file. 17. Push, then quickly release the service pin on the LonWorks device you want to get information from. The device number is displayed in the window.
Appendix B - Obtain network, device, and network variable information 4. In Search for software in, select Development Tools, click Find, then download NodeUtil Node Utility (latest version). 5. Run the Open LDV .exe file to install the software. 6. Unzip the file that you downloaded for the LonWorks SLTA-10 Serial LonTalk(R) Adapter Software. 7. Run slta10_Win.exe to install the software. Make note of the numeric base for the device name number. Typically, this number is 1. 8.
Appendix B - Obtain network, device, and network variable information 29. Push, then quickly release the service pin on the LonWorks device you want to get information from. The device number is displayed in the window. CAUTION Holding the service pin for 3 seconds or longer can delete memory from some third-party devices. TIP For some VAV devices, the connected sensor's override button may also function as a service pin. 30. Type G to go to the device menu. 31.
Appendix B - Obtain network, device, and network variable information To connect your computer to the LonWorks network: 7. Connect your computer to the iLon10 using a crossover cable alone or a straightthrough cable with a hub. The iLon10 must also be connected to the LonWorks network segment. 8. On the computer, select Start > Control Panel. 9. Double-click LonWorks Interfaces. 10. Click Add. 11. Type a name such as iLon10 and write down the name. You will use it later. 12. Click Next twice.
Appendix B - Obtain network, device, and network variable information 26. Type a name for the .xif file that NodeUtil will create containing the device and network information. Omit the file extension; NodeUtil will automatically add the .xif extension. NOTE If you do not specify a path, the file will be saved in the same folder as the NodeUtil.exe file. LonWorks 27. Press Enter to create the .xif file. 28. Type E to exit the device menu. 29. Close the Command Prompt window.
CARRIER CORPORATION ©2010 A member of the United Technologies Corporation family · Stock symbol UTX · Catalog No.
