BLX LinX User Manual - BuildingLogixsvn.buildinglogix.net/.../BLX_LinX_User_Manual.pdf · BLX LinX User Manual BuildingLogix Rev. 7/2013 Page 1 of 15 BLX LinX User Manual Introduction:

BLX LinX User Manual BuildingLogix

Rev. 7/2013 Page 1 of 15

BLX LinX User Manual Introduction: This manual will cover the installation, licensing and usage of the BLinX application. The BLinX application is a licensed .jar file containing palletized objects that makes the integration of Trane BACnet BCU devices and into

the Niagara Network seamless. BLinX works with BMTW and BMTX BCU’s. Prerequisites and requirements: - Registered account on http://www.blxcentral.com

- Niagara Workplace AX - Jace/SoftJace/WebSup with running station and BACnet network setup (BACnet driver license required) - blinx.jar and blxcore2.jar files

- Knowledge of computers and networking - Knowledge of BACnet networks - Knowledge of Summit, Trane BCU’s and devices - Niagara Host ID - Number of devices and objects to integrate Guide: 1) Downloading, Installing and Licensing BLinX

a) Download the BLinX module (blinx.jar) and BLX Core 2 module (blxcore2.jar) from the

BuildingLogix wiki http://www.blxcentral.com/wiki/BLinX

*Note: Some browsers (internet explorer) may automatically change the file extension from .jar to .zip

upon saving. If this happens, you must change the file extension back to .jar

b) Install the modules (.jar files) to the modules folder of the target Niagara installation or platform using

software manager or file transfer client and restart WorkPlace AX or the station. i.e. C:\Niagara\Niagara-3.X.XX\modules

c) Log in to the target station d) Create and setup a BacnetNetwork (See Niagara Documentation)

e) Open the palette for the blinx module f) Drag and drop an instance of ‘BLXBacnetService’ on to ‘Services’ in the nav tree


Rev. 7/2013 Page 2 of 15

g) Double click on ‘BLXBacnetService’ from the nav tree. The BuildingLogix License Wizard will display. Follow the steps and enter the License Key supplied by BuildingLogix. *Note: BLinX must be licensed before it can be used. Contact BuildingLogix to obtain a license. http://www.blxcentral.com/licenses or 1-888-4-BLOGIX (1-888-425-6449)

Save the station after successful licensing. *Note: BLinX is licensed by the number of devices and objects needed to integrate. Please have the number of devices and objects ready when ordering a license.

*Note: The BlxBacnetService License screen displays the number of devices/objects the host is licensed for along with the number of devices/objects running (used), and if exceeded, the number of devices/objects over the license limit.

*Note: BLinX can run in demo mode, without being licensed. Devices and objects can be added (see below for further information) but will be disabled until successfully licensed.


Rev. 7/2013 Page 3 of 15

2) Setting up BLinX

a) From the nav tree, expand Drivers > BacnetNetwork > Bacnet Comm > Network > IP Port > Poll Service b) Change the “Slow Rate” to 2 minutes and click “Save”

c) Double click “Tuning Policies” from the nav tree d) From the blinx palette, expand “TuningPolicies” e) Drag and drop an instance of “blxBacnetPolicy” from the palette onto Tuning Policies

f) Double click “BacnetNetwork” to display the Bacnet Device Manager g) Click “Discover” to discover a BCU

*Note: Do not ADD the discovered BCU to the Bacnet Network h) From the blinx palette, expand “BCU” i) Drag and drop an instance of “BlxBacnetDevice” from the pallet into the Database pane


Rev. 7/2013 Page 4 of 15

j) Name the device the same as the BCU

k) Select the Discovered BCU then Select the BLX Bacnet Device and click “Match” then “OK”

l) Expand the added BCU from the nav tree m) Double click on the “Points” folder n) Drag and drop a “BCUAX_COM” folder from the pallet into the Database pane o) Drag and drop a “BCUStatus” folder from the pallet into the Database pane


Rev. 7/2013 Page 5 of 15

p) Expand the “Points” folder from the nav tree q) Double click on the “BCUAX_COM” folder r) In Summit, create a new CPL object in the BCU by copying and pasting the BCUAX_COM code

• Follow the instructions in the code’s comments

• Copy and paste the entire code

• Edit the quantity of controlled PV’s

• Define the PV object names

• Compile and create the CPL with a frequency of 1 minute *Note: The BCUAX_COM CPL is designed to release all present value control back to the BCU when communication to Niagara is lost.


Rev. 7/2013 Page 6 of 15

s) In Niagara, double click on the “Points” folder to display the BLX Bacnet Point Manager t) Click “Discover” to discover the BCUAX_COM CPL within the BCU

*Note: Do not ADD the discovered CPL to the points list u) Use the Object Description to identify the CPL Address

v) Right click on the “BCUAX_COM” folder and select “Views” and then the “Config” view

w) Enter the CPL address in the “Device Address” field x) Click “Save” y) Click “Change Address”

z) Double click “BacnetNetwork” to display the Bacnet Device Manager aa) Use the BCU “Device ID” number to identify the BCU Address

bb) Right click on the “BCUStatus” folder and select “Views” and then the “Config” view

cc) Enter the BCU address in the “Device Address” field dd) Click “Save” ee) Click “Change Address”


Rev. 7/2013 Page 7 of 15

3) Adding devices and changing addresses *Note: Before adding devices, double click on the “BCUStatus” folder to display the view for the BCU. If the processor idle time or free memory resources are below 50%, you may be limited to how many devices you can add. Refer to the BCUStatus view periodically to check the amount of free resources. If the resources fall below 20%, consider removing objects from the BCU.

a) Double click on the “Points” folder to display the Blx Bacnet Point Manager b) Click “Discover” to discover the devices within the BCU

*Note: Do not ADD the discovered devices to the points list c) Use the Object Description to match up the device type and ID Number with the devices listed in the blinx

palette *Note: Take note of the device Address

d) Drag and drop the appropriate device folder from the palette into the Database pane *Note: The “v” number after the device name in the palette is the corresponding device ID

e) Name the device

*Note: BLinX Devices come in with a default address of -1. To change the address, use the following steps.

f) Right click on the device and select “Views” and then the “Config” view

g) Enter the device address in the “Device Address” field h) Click “Save” i) Click “Change Address” j) Repeat adding devices and changing addresses until all desired devices are integrated


Rev. 7/2013 Page 8 of 15

*Note: Devices and points will be automatically brought in to Niagara complete with correct names, organized folder structure and a default px view graphic. If a particular device is not listed in the blinx palette or a device is missing a point, please contact BuildingLogix to request the device/point be added to the next product version release.


Rev. 7/2013 Page 9 of 15

4) Obtaining Point Names from Programmable Controllers (MP580/581, PCM) Since point names in programmable controllers are customizable and not static, the names must be read from the device and changed to match in Niagara. The “Auto-Namer” performs this functionality. Auto-naming is only available on devices with a “PointNames” view. To auto-name points, use the following

steps. a) Right click on the device and select “Views” and then the “PointNames” view

b) If needed, click the “Read Point Names” button c) If needed, refresh the point names as they are read by clicking the “Refresh List” button d) Click the “Auto Name Points” button e) Repeat as necessary for all point types The Auto Name macro renames the Niagara points under the device to what was read from Summit. Do not re-order the points list in the Niagara tree, otherwise the auto-namer will not function properly.


Rev. 7/2013 Page 10 of 15

5) Using BLinX – Advanced Information

Devices and Objects BLinX currently supports the following devices.

1) CSC Com3 (15 kRU) 2) Chiller CGA Com3 (12 kRU) 3) Chiller CH530 LON (17 kRU) 4) Chiller RTA Com3 (21 kRU) 5) Chiller UCP1CV Com2 (21 kRU) 6) Chiller UCP2AB Com4 (23 kRU) 7) Chiller UCP2CV Com4 (21 kRU) 8) Chiller UCP2HR Com4 (18 kRU) 9) DAC LON (13 kRU) 10) Intellipak Com4 (18 kRU) 11) LCP Com3 (22 kRU) 12) MP580 LON (95 kRU) 13) PCM Com3 (27 kRU) 14) SCC LON (16 kRU) 15) TCM Com3 (7 kRU) 16) TUC Com4 (14 kRU) 17) UPCM Com4 (84 kRU) 18) VAV Com3 Non Iso (24 kRU) 19) VAV Com4 (24 kRU) 20) VAV LON (17 kRU) 21) Voyager Com4 (14 kRU) 22) Voyager Com3 (14 kRU) 23) WSHP LON (17 kRU)

BLinX currently supports the following objects. 1) Area (4 kRU) 2) Chiller Plant (48 kRU) 3) VAS Com3/Com4 (2 kRU) 4) VAS Lon (2 kRU) 5) BCU Status (4 kRU) 6) BCUAX COM (CPL) (3 kRU)

An integrator can still create individual points in the BCU, discover those points and bring them in to the Bacnet network. If a device or point does not exist, please contact BuildingLogix to request the device/point be added to the next product version release. Addresses Devices and points associated with the device will automatically be brought in to the Bacnet network (and thus Niagara framework) when added from the blinx palette. All devices come in with an address of -1. See above for information on using the Config view to change the device address. Graphics Each device comes in with simple integrated graphics and views with basic functions and information such as status/summary information and override capabilities. These views reside in the JAR can be used or discarded for custom views. *Note: BLinX Graphics are fully functional with an iPad on Niagara 3.7 or higher.


Rev. 7/2013 Page 11 of 15

Alarms Each device has an alarm on its communication status point. The point will go into alarm when comm is down. The alarm is pushed to the default alarm class. Disabled/Enabled Points BLinX has automated enable/disable functionality within it that disables the points in Niagara when comm to the BCU is lost, and re-enables them when comm is restored. This mitigates “killing” of the BCU. The integrator should not manually enable/disable the points in Niagara, instead, verify good comm states first. BLinX will also disable points when it is not licensed, the BlxBacnetService is not present, or the number of licensed devices has been exceeded. Override and Auto buttons The Override and Auto action buttons on the BLinX graphics set the “Present Value” (occupancy) point in Niagara in accordance with standard Summit facets. This action is functional only if Niagara is allowed to have control. See below for more information.

Summit Control vs. Niagara Control BLinX is designed to not only read points from a BCU but it has the ability to write to and control points as well. However, special action must be taken in different scenarios to ensure proper operation and control between Summit and Niagara. Niagara Control: All BLinX points wrote to the BCU from Niagara are assigned a priority level of “16 – Custom Programming – Low” in Summit. Thus, any point in Summit with a higher priority level (i.e. 9 – VAS, 11 – Area, 15 – Schedules) will be controlled by Summit and not Niagara. This is completely independent of the Niagara priority level.

To allow Niagara to control a point, the Summit priorities must be removed or relinquished, or the device must be removed from the controlling object (i.e. CPC, Area, VAS, Direct Schedule), or the controlling object itself must be removed, or any controlling CPL (custom programming logic) must be released.


Rev. 7/2013 Page 12 of 15

Once control is given to Niagara at a priority level of 16, the control remains. An ‘Auto’ action in Niagara will not relinquish control back to the defaults in Summit; instead, the control must be released in Summit using the RELEASE button on the BCUAX_COM. The BCUAX_COM CPL will also relinquish control back to the defaults in Summit if it see’s comm loss (See CPL). Area Control: BLinX can control an Area in Summit, thus it is recommended to keep the Areas. To control an Area, drag and drop an “Area_v130” object folder from the BLinX pallet on to the Points folder. Change the address from -1 to its value. The Area points will automatically be brought in to the Bacnet network (and thus Niagara framework). Schedule Control: BLinX cannot read schedules from a BCU and thus, cannot control them either. However, a Niagara schedule can be used to control the point the BCU schedule was controlling. To control a BCU point using a Niagara Schedule, first remove the Summit schedule or the schedules control on the point. Then create the Niagara schedule, and link it to the BLinX point (i.e. Present Value). Since the point control is coming from Niagara, remember the points will be assigned a priority level of 16 in Summit. Use this method to have Summit objects (i.e. Area, VAV, CPC) retain control of the points but have the scheduling controlled in Niagara.


Rev. 7/2013 Page 13 of 15

Set Point Control (with VAS): As stated above, it is recommended to remove the VAS from Summit and control the system in Niagara (i.e. with ASO, other logic or via graphics). In order for the BLinX VAV set points to be controlled in Niagara, VAS must not have control. If VAS has control, set point changes will quickly revert back to the VAS values. However, it is possible to retain the VAS and control the set points in Niagara. This is accomplished by using the “BLinX_VAV_SetptCntrl” program object.

• Drag and drop a “BLinX_VAV_SetptCntrl” object from the palette onto the VAV

• Double click on the object

• Change the “Enable” field to “True”

• Link mark the VAV’s “Present Value” point (from the Overrides folder) into the “PV” slot of the object

• Click “Save”

• Use the Set Points in the BLinX_VAV_SetptCntrl program object on Niagara graphics to control the VAV set points.


Rev. 7/2013 Page 14 of 15

Created Points in Summit: All points which were created in the BCU (analog-out, binary-out, non-BLinX points) that are discovered in Niagara will follow the Niagara priority level in Summit. For example, overrides in Niagara at level 8 are assigned a priority level in Summit also at level 8. Use the “Sites Bacnet Report” in Summit to see which points have been created in the BCU.

BlxBacnetService The BlxBacnetService service is used to license and run the BLinX application. BLinX is licensed by number of devices and objects. See above for information on how to license BLinX and which devices/objects are currently supported. If the number of licensed devices is exceeded or the BlxBacnetService is not present, points will be disabled. Tuning Policy The BlxBacnetPolicy object is used by all points to define the tuning policy for BLinX Devices. It is required and optimized for proper BCU communication. This tuning policy uses the “SlowRate” from the BACnet poll service which is set to 2 minutes in the setup. See above for information on how to add the policy. Area 130 Read-only points from and write Present Value to the Area object in Summit. VAS Com3/Com4 153 and VAS LON 190 Read-only points from the VAS object in Summit. ChillerPlant 173 Read-only points from the Chiller Plant object in Summit. BLinX VAV SetptCntrl Program object to allow VAV set point control in Niagara while retaining VAS in Summit. BCUAX_COM The purpose of the BCUAX_COM CPL created in the BCU is to automatically release control back to Summit defaults upon comm loss to Niagara. The release button in the BCUAX_COM view simply runs the release CPL on demand.


Rev. 7/2013 Page 15 of 15

BCU Status The BCUStatus folder contains certain status points associated with the BCU along with simple integrated graphics and alarms to monitor the BCU health. The BCUStatus folder has alarms for communication status, percent NVM available, percent VM available and percent processor idle time. The points will go into alarm when comm is down or percents are out of range. The alarms are pushed to the default alarm class.

Documents

BLX LinX User Manual - BuildingLogixsvn.buildinglogix.net/.../BLX_LinX_User_Manual.pdf · BLX LinX User Manual BuildingLogix Rev. 7/2013 Page 1 of 15 BLX LinX User Manual Introduction: