Aurora Platform 5.6 Release Notes

Release Date:  December 19, 2016

A PDF Version is available as an attachment at the bottom of the article.

Aurora Platform 

API

Version 1 of our Api will be deployed with this release of the Aurora Platform.   The Api will exist as an endpoint on the Aurora Server and allow for the retrieval of live and historical data by filter or individual tag.  A filter can be created in Aurora and is the best way to group a set of tags together for retrieval through the Api.

How to setup a filter:

1.  Select the trending option in the application header 2.png and Aurora Platform will display the Trending modal

 Trending1.PNG

2.  Select a tag by clicking on the tag row and Aurora Platform will display the tag in the “Select a tag from the grid to the left” area 

Note:  the column headers have filter options so that the list of tags can be reduced to a more granular list. 

Trending Filter3.PNG

3.  Repeat step 2 until you have selected all the desired tags for the API Filter

 Trending 4.PNG

4.  Type a Filter Name in the Save Tag Selection field

5.  Click the Save option and the Aurora Platform has a stored API Filter available for use

 Trending5.PNG

Note:  API Filters must be setup on each individual server. 

The Api uses basic authentication consisting of a user name and password.  It is suggested that a user is created in Aurora specifically for Api use and granted access to all systems containing tags that will be retrieved through the Api. 

GET /filters

Gets Filters owned by the authenticated user. Includes all associated tags and tag detail.

GET /filters/{filterId}/Historical

Gets historical data for the tags associated with the provided filter.

GET /filters/{filterId}/Live

Gets live data for the tags associated with the provided filter.

GET /tags/{tagId}/Historical

Gets historical data for the provided tag.

GET /tags/{tagId}/Live

Gets live data for the provided tag.


How to setup a header with basic authentication:

  1. Build a string of the form username:password
  2. Base64 encode the string
  3. Supply an “Authorization” header with content “Basic ” followed by the encoded string.
  4. For example, a user name of “test” with a password of “test” would be test:test which is dGVzdDp0ZXN0 after encoding. The request header should contain “Authorization: Basic dGVzdDp0ZXN0”.

GET /filters

Description

Gets Filters owned by the authenticated user. Includes all associated tags and tag detail.

Parameters

None

Supported Types

application/json

Sample Request

GET ../v1/filters 

Responses

A successful request will return a HTTP status code of 200 and a response containing a filters object.  See the Error Codes and Responses section for a full list of HTTP status codes and error codes.

GET /filters/{filterId}/Historical

Description

Gets historical data for the tags associated with the provided filter. 

Parameters

Name

Located In

Description

Required

FilterId

Path

The id of the filter containing the list of tags to return.

Yes

Interval

Query string

Interval of the data to be returned.  Valid values are ‘Minute’, ‘QuarterHour’, ‘Hour’ and ‘Day’.

Yes

Start

Query string

Starting date/time range of data to retrieve.

Yes

End

Query string

Ending date/time range of data to retrieve.

Yes

DateRangeType

Query string

Identifies the time zone to use when applying the Start and End date range.  Valid values are ‘UTC’ and ‘Site’.  If not set, the default is ‘Site’.

No 


Supported Types

application/json

text/csv

Sample Request

GET ../v1/filters/{filterId}/Historical?Interval=QuarterHour&DateRangeType=Site&Start=2016-07-26 01:00:00&End=2016-07-27 01:00:00

Responses

A successful request will return a HTTP status code of 200 and a response containing a historical data object.  See the Error Codes and Responses section for a full list of HTTP status codes and error codes.

GET /filters/{filterId}/Live

Description

Gets live data for the tags associated with the provided filter.

Parameters

Name

Located In

Description

Required

FilterId

Path

The id of the filter containing the list of tags to return.

Yes


Supported Types

application/json

Sample Request

GET ../v1/filters/{filterId}/Live

Responses

A successful request will return a HTTP status code of 200 and a response containing a live data object.  See the Error Codes and Responses section for a full list of HTTP status codes and error codes.

GET /tags/{tagId}/Historical

Description

Gets historical data for the provided tag.

Parameters

Name

Located In

Description

Required

TagId

Path

The id of the tag to return.

Yes

Interval

Query string

Interval of the data to be returned.  Valid values are ‘Minute’, ‘QuarterHour’, ‘Hour’ and ‘Day’.

Yes

Start

Query string

Starting date/time range of data to retrieve.

Yes

End

Query string

Ending date/time range of data to retrieve.

Yes

DateRangeType

Query string

Identifies the time zone to use when applying the Start and End date range.  Valid values are ‘UTC’ and ‘Site’.  If not set, the default is ‘Site’.

No


Supported Types

application/json

text/csv

Sample Request

GET ../v1/tags/{tagId}/Historical?Interval=QuarterHour&DateRangeType=Site&Start=2016-07-26 01:00:00&End=2016-07-27 01:00:00

Responses

A successful request will return a HTTP status code of 200 and a response containing a historical data object.  See the Error Codes and Responses section for a full list of HTTP status codes and error codes.

GET /tags/{tagId}/Live

Description

Gets live data for the provided tag.

Parameters

Name

Located In

Description

Required

TagId

Path

The id of the tag to return.

Yes


Supported Types

application/json

Sample Request

GET ../v1/tags/{tagId}/Live

Responses

A successful request will return a HTTP status code of 200 and a response containing a live data object.  See the Error Codes and Responses section for a full list of HTTP status codes and error codes.

Error Codes and Responses

HTTP Status Codes

Code

Text

Description

200

OK

Success!

400

Bad Request

The request was invalid.  An accompanying error message will explain further.

401

Unauthorized

Missing or invalid authentication credentials.

403

Forbidden

The request is understood, but it has been refused or access is not allowed.  An accompanying error message will explain further.

406

Not Acceptable

Invalid accept type in header.  Supported types are listed per route.  All routes support application/json and historical data routes also support text/csv.

413

Request Entity Too Large

The response is too large.  If making a request through an historical data route, try using a smaller Start and End date range. 

500

Internal Server Error

An unexpected exception occurred.  Contact BluePillar support and supply the x-logging-id in the response header.


Error Messages

All error messages are returned in json.  See error object for field description and sample.

Error Codes

Code

Text

Description

100

Authentication credentials are missing or incorrect.

Corresponds with an HTTP 401.

201

Content type not supported.

Corresponds with an HTTP 406.

202

Unexpected exception.

Corresponds with an HTTP 500.

203

Requested payload is too large. Try limiting date range or number of tags in request.

Corresponds with an HTTP 413.

205

Unauthorized resource requested.

Corresponds with an HTTP 403.

1001

Empty list of tag ids presented during live data retrieval.

Corresponds with an HTTP 400.  This will be returned if live data routes return no data. 

1100

Missing required Tag Id.

Corresponds with an HTTP 400. 

1101

Missing required start date.

Corresponds with an HTTP 400.  Returned by the historical data routes when start date parameter is missing. 

1103

Missing required end date.

Corresponds with an HTTP 400.  Returned by the historical data routes when end date parameter is missing. 

1105

Invalid end date. End date/time must be greater than start date/time.

Corresponds with an HTTP 400.  Returned by the historical data routes when specified date range is invalid. 

1106

Invalid interval. Supported values are Minute, QuarterHour, Hour or Day.

Corresponds with an HTTP 400.  Returned by the historical data routes when the interval parameter contains a non-supported value. 

1201

Missing required filter id.

Corresponds with an HTTP 400. 


Api Object Definitions

Filters Object

Field

Type

Description

Id

string

Unique identifier for the filter.

Name

string

Name of the filter.

Tags

array of Tag objects

 

Tag:Id

string

Unique identifier for the tag.

Tag:Name

string

Name of the tag.

Tag:Entity

string

Name of the entity associated to the tag.

Tag:SiteName

string

Name of the site associated with the entity, otherwise, empty string.

Tag:SiteId

string

Unique identifier for the site associated with the entity, otherwise, empty guid. Example: 00000000-0000-0000-0000-000000000000

Tag:Building

string

Name of the building associated with the entity, otherwise, empty string.

Tag:Floor

string

Name of the floor associated with the entity, otherwise, empty string.

Tag:Room

string

Name of the room associated with the entity, otherwise, empty string.

Tag:DataType

string

Contains discrete or analog.


Json Example of Filters Object

[{

                "Id": "80936624-938D-4854-8476-8B191C07A897",

                "Name": "filter1",

                "Tags": [{

                                "Id": "E7D98DE2-5EA1-4FC7-A5C4-712DD00D5FC5",

                                "Name": "tag1",

                                "Entity": "entity1",

                                “SiteName”:”testSite1",

                                “SiteId”:”D0955B4A-E340-4C5A-8029-4B40E3620F07",

                                "Building": "building1",

                                "Floor": "floor1",

                                "Room": "room2",

                                “DataType”: “analog”

                }, {

                                "Id": "1B44BD9A-DC32-43EF-82B6-E35A63743035",

                                "Name": "tag2",

                                "Entity": "entity2",

                                “SiteName”:”testSite2",

                                “SiteId”:”7F4B1CDB-C628-445A-8213-DE9235A29967",

                                "Building": "building1",

                                "Floor": "floor2",

                                "Room": "room1",

                                “DataType”: “discrete”

                }]

}, {

                "Id": "40D96DB0-1D95-485F-874D-8A00736DFE41",

                "Name": "filter2",

                "Tags": [{

                                "Id": "97E9B219-43BC-4A8B-904C-9E1EC71877BA",

                                "Name": "tag3",

                                "Entity": "entity3",

                                “SiteName”:”testSite3",

                                “SiteId”:”4363D000-072B-42E3-B266-9E3E2B768788",

                                "Building": "building2",

                                "Floor": "floor1",

                                "Room": "room1",

                                “DataType”: “analog”

                }]

}]

Historical Data Object

Field

Type

Description

SiteId

string

Unique identifier for the site associated with the entity, otherwise, empty guid.  Example: 00000000-0000-0000-0000-000000000000

SiteName

string

Can contain one of the following:

1.       Name of the site associated with the entity or empty string

2.       “Given tag is not authorized.” when the authenticated user is not authorized to view the entity associated with the tag.

 

TagId

string

Unique identifier for the tag.

SiteDateTime

string

The date/time for the data point expressed in the site time zone.

DateTimeUTC

string

The date/time for the data point expressed in UTC.

Mean

number

The average value over the interval.  For cumulative data this will represent the delta over the interval.

Min

number

The minimum value over the interval.

Max

number

The maximum value over the interval.

Median

number

The median value over the interval.

Total

number

The sum of the values over the interval.

StDev

number

The standard deviation over the interval.

SampleSize

integer

Expected number of data points used to evaluate the interval.

ActualSampleSize

integer

Actual number of data points used to evaluate the interval.

Quality

integer

Not implemented.


Json Example of Historical Data Object

[{

                "SiteId": "628A126D-9CEA-4DCD-B267-0EF0CA3A03A3",

                "SiteName": "Site1",

                "TagId": "EFB83F06-C4AA-43D1-84AF-93EA66FA357E",

                "SiteDateTime": “2016-07-27T15:30:00",

                "DateTimeUTC": "2016-07-27T19:30:00",

                "Mean": 7.168,

                "Min": 0,

                "Max": 89.6,

                "Median": 0,

                "Total": 6451.2,

                "StDev": 9.253848209,

                "SampleSize": 900,

                "ActualSampleSize": 5,

                "Quality": 1

}, {

                "SiteId": "13DA3496-7E4D-4B0F-A2F6-B6A06203A4AE",

                "SiteName": "Site2",

                "TagId": "DFBAF0B0-7581-41AA-8782-5C9B760A5F27",

                "SiteDateTime": "2016-07-27T15:45:00",

                "DateTimeUTC": "2016-07-27T19:45:00",

                "Mean": 0.798134359,

                "Min": 0.794062495,

                "Max": 0.803437471,

                "Median": 0,

                "Total": 718.3209234,

                "StDev": 0.001301139,

                "SampleSize": 900,

                "ActualSampleSize": 532,

                "Quality": 1

}]

Live Data Object

Field

Type

Description

TimeStampUTC

string

The date/time in UTC corresponding to the live value.

LiveData

array of Tag/Value pairs

 

TagId

string

Unique identifier for the tag.

Value

string

Can contain one of the following:

1.       Live tag value

2.       “Given tag is not authorized.” when the authenticated user is not authorized to view the entity associated with the tag.

3.       “Given tag is invalid.” when we are not capturing data for the tag.


Json Example of Live Data Object

{

                "TimeStampUTC": "2016-07-25 00:00:00",

                "LiveData": [{

                                "TagId": "0C92C503-DDCE-45A3-92CE-EB2A75FB2333",

                                "Value": 1

                }, {

                                "TagId": "82351CC2-21E3-4908-BE86-B991B742506D",

                                "Value": 162.391667683919

                }, {

                                "TagId": "E7D98DE2-5EA1-4FC7-A5C4-712DD00D5FC5",

                                "Value": 278.5

                }]

}

Error Object

Field

Type

Description

Status

string

HTTP status code for the response. See list of possible HTTP status codes.

Messages

array of message objects

 

Message:Message

string

Description of error.  See list of error messages and associated codes.

Message:ErrorCode

string

Code associated to the error.


Json Example of Error Object

{

"status":"406",

"messages":[{

"message":"Content type not supported.",

"errorCode":"201"

}]

}

Kepware Configuration

Inter-Request Delay

The Inter-Request Delay is a parameter in Kepware, this parameter specifies how long the driver waits before sending the next request to the target device. It overrides the normal polling frequency of tags associated with the device, as well as one-shot reads and writes. This delay can be useful when dealing with devices with slow turnaround times and in cases where network load is a concern. Configuring a delay for a device affects communications with all other devices on the channel. It is recommended that users segregate any device that requires an inter-request delay to a separate channel if possible. Other communications settings (such as Communication Serialization) can extend this delay. The valid range is 0 to300,000 milliseconds; however, some drivers may limit the maximum value due to a function of their particular design. The default setting is 0, which indicates no delay between requests with the target device. This setting is disabled if it is not supported by the driver.

The parameter field was added to Aurora Admin for Modbus devices in the Device Configuration.  When the device is created the default setting is 0ms.  With the initial save and with each modification the Inter-Request Delay setting gets pushed down to the Kepware configuration.  This field was added to resolve the issue of the field getting reset each time the Aurora configuration was saved and each time the server was rebooted. 

Admin Modbus Device Configuration

How to configure a modbus inter-request delay:

  1. Logon to the Aurora Admin as an Administrator
  2. Select the Admin menu option
  3. Select the Server Config menu option and the application presents the Server Config
  4. Create or select an existing Modbus Entity/Device
  5. Select the Entity Device (GIM) and the application presents the Device Configuration page
  6. Enter the Modbus Inter-Request Delay (ms)
  7. Select the Save option
  8. Navigate to the Server Config by selecting the server name in the hierarchal tree
  9. Select the Download to Server button and the application persists the new Inter-Request Delay value to the Kepware configuration

Device Operate Mode

The Device Operate Mode is a parameter in Kepware, this parameter determines whether the writable I/O points (object group 10 - Binary Outputs and object group 40 - Analog Outputs) use the Direct Operate or Select then Operate sequence. The default selection is Direct Operate.

  • The Select then Operate (SO) option sends two requests - the first with the select function code(3) followed by a request with the operate function code(4).
  • The Direct Operate (DO) option sends one request with the direct operate function code(5). 

The parameter field was added to Aurora Admin for DNP devices in the Device Configuration.  When the device is created the default setting is Direct Operate.  With the initial save and with each modification the Device Operate Mode setting gets pushed down to the Kepware configuration.  This field was added to resolve the issue of the field getting reset each time the Aurora configuration was saved and each time the server was rebooted. 

Admin DNP Device Configuration

How to configure the device operate mode for DNP device:

  1. Logon to the Aurora Admin as an Administrator
  2. Select the Admin menu option
  3. Select the Server Config menu option and the application presents the Server Config
  4. Create or select an existing DNP Entity/Device
  5. Select the Entity Device (GIM) and the application presents the Device Configuration page
  6. Enter the Device Operate Mode
  7. Select the Save option
  8. Navigate to the Server Config by selecting the server name in the hierarchal tree
  9. Select the Download to Server button and the application persists the new Operate Mode value to the Kepware configuration

iMonnit

iMonnit Electric KYZ Template

A template has been created so that each time an iMonnit device is created in Aurora Admin then a default list of tags is present. 

Here is a list of the tags with their associated configuration:

ENTITY_STATUS – the standard discrete entity status tag

PULSECOUNT_RAW – the raw value from the iMonnit API

KWHR – kilowatts per hour is a formulated tag "[ENTITY_DEVICE_PULSE_COUNT_RAW]"

SIGNAL – the wireless signal strength indicator from the iMonnit API

BATTERY – the battery strength indicator from the iMonnit API

In addition, the analog alarming for the Meter Battery and Signal are setup automatically for each iMonnit device created.

Alarm Detail for Meter Battery

Alarm Detail for Meter Signal

BACnet Protocol Configuration with Kepware

When there are multiple BACnet devices to one Kepware Channel then the BACnet devices need to be manually configured in Kepware.  See Addendum 1 for configuration steps.

BACnet Device OPC UA Access Path Configuration

When a BACnet device has been configured in Aurora Admin then the application will present a new field called OPC UA Access Path on the Device Configuration screen.  The OPC UA Access Path provided in the BACnet device configuration in Kepware needs to be entered into this new field.  Once a Save and Download is performed in the Aurora Admin then Kepware will be able to communicate with the BACnet device and deliver the tag values to Aurora Platform.

Admin-BACnet Device Configuration

Ignore Kepware Auto Configuration for BACnet Devices

When a Save and Download is performed in Aurora Admin on a config that contains a BACnet device then Control Manger will ignore the Kepware auto configuration for the BACnet devices and merge a manually configured BACnet xml file from a specified location.  The procedure was put in place so that the manually configured BACnet devices in Kepware will not get overwritten or blown away.

Bug Fixes

Work Item

Summary

Description of Bug

10231

Entity Details is Displaying Unmapped iMonnit Tags

Created a fixed list (template) of iMonnit tags for the KYZ Meters

14846

iMonnit isEnabled Key is not Installed in the iMonnit Config

Added the iMonnit "isEnabled" key to the iMonnet Config

15303

Runtime Install is Overwriting Certain iMonnit.Service.dll.config File Settings

Fixed the Runtime Installer so that it does not overwrite the iMonnit configuration

15328

Remove the try/catch that is causing the Operations Summary to return an error

Removed the "throw" that occurred when a try/catch ended so that the error will no longer occur

15376

Active Equipment Not Persisting on Sites With Active Equipment Screen

Fixed the Operations Summary screen to display the Sites with Active Equipment when the Active Equipment filter is selected

15504

DR App System Status Incorrect for No Load Test

Fixed the Demand Response Application to display the correct System Status of Test and the Equipment (ATS) status to be Inactive

15660

Cloud Foresite Displays A Lot of Error Messages In Chrome

Fixed the errors occurring in Cloud Foresite using a Chrome Browser

15662

Cloud Foresite Aurora - No Live Data on Live View or Entity Details

Fixed the https issues of being able to display the live data in Cloud Foresite

15829

Emergency and Utility Source Color Options Missing on Live View Designer in Chrome Browser

Fixed the Live View Designer to display the Emergency and Utility Source Color options using a Chrome Browser

15830

Admin Meter Config Not Retaining Selection After Save and Download

Fixed the Aurora Admin to retain the Meter Config Adds, Edits and Deletes after a Save and Download is conducted

15959

Runtime Install Overwrites iMonnit Tag Mapping Config With Default

Fixed the Runtime Installer so that it will not overwrite any currently mapped iMonnit tags

15989

When one 0.0.0.0 device entity goes offline it should not effect the other devices in any way including alarm processing.

 Added a configurable list of entity types to bypass device reuse

15992

Trending is not rendering the chart correctly when the interval is set to hour

Fixed the rendering of the Trending Chart when the Hour Interval was selected

16052

Gateway - KYZ Meter - can't click in admin tree view

Fixed the issue of not being able to select the Gateway KYZ Meter in Aurora Admin Entity Hierarchy Tree View

16173

Writable Discrete Tags Cannot Be Flipped in Entity Details Grid View

Fixed the Discrete Tags so that the User is able to control the tag value from the Entity Details Grid View

16341

Tag Filters Created at Aggregate Foresite Level do not Persist to Insite Node

Fixed the API Filter and Trending Tag Filter creation in Foresite so that it would save to the Insite Note

16344

Tag Filters Created Through Foresite Server Show Up as Selectable for Every Site

Fixed the Trending Tag Filter selection in Trending to be Site specific


Hotfixes

This includes any change to the release build post the release date.

Build

Hotfix Date

Summary

Description of Hotfix

5.6.0017.001

01/17/2017

OPC UA Writes

The Hotfix is an update to how we write values to the OPC UA server.  The Platform will verify the type of value we need to write first then convert the value to write to the proper value type and then commit the write.  This guarantees successful write to the register in the OPC UA server.

5.6.0020.001

01/20/2017

Equipment Trending

The ability to trend on equipment/tags that are not associated to a Site or System is now available.

5.6.0023.001

 

01/23/2017

 

Live View

 

Fixed the Live View display to show equipment with the correct status and power source color with the equipment is active by adding the Active Status Setter in the Admin Save and Download.

Fixed the Live View display so that when one of many entities attached to the bus bar goes offline it will retain the power source color for the other entities.

Hardware and Software Requirements

Aurora Server Requirements

  • Hardware – The server hardware can be provisioned using any of the following options:
    • Hosted as a Virtual Machine in Windows Azure
    • Deployed as Virtual Machine using the customer’s existing virtual infrastructure
    • Using a Blue Pillar provided Intel-based physical server
  • Recommended Operating System Software
    • Windows Server 2012 R2 or minimum Windows Server 2008 R2 SP1
  • Other Recommended Software
    • Windows Server 2012 R2 or minimum Windows Server 2008 R2 SP1
    • Microsoft SQL Server 2012 SP1 or minimum SQL Server 2008 SP1
    • Microsoft .Net framework Version 4.5
    • Windows Internet Information Server (IIS) (access to port 80/443 via http/https)
    • SMTP Server access
  • Server Sizing – The physical specifications of the server will depend on the total number of tag counts that will be managed by the server. As a minimum, the following is recommended:
    • 8 Core Machine
    • 16 GB of Memory
    • 1 x 60GB OS Partition, 1 x 375GB Data Partition, 1 x 275GB Log Partition, 1 x 100GB Backup Partition

Aurora Server Administration Requirements

  • Database Backups
    • SQL database backups are taken and stored locally for 24 hours in the event of data corruption and recovery.
    • Additional SQL backups can be conducted in accordance with the customer’s disaster recovery policies.
    • Blue Pillar can provide best practice guidelines for setting up and managing additional backups.
    • Blue Pillar can also provide services to manage the SQL backups on behalf of the customer.
  • Remote Access for Blue Pillar
    • For ongoing support, maintenance, and upgrades, Blue Pillar needs to ability to remote into the server via Remote Desktop Protocol. This is typically accomplished using the customer’s existing VPN connection method.
  • User Access
    • Facilities personnel will access the server via http/https on port(s) 80/443. Firewall traffic to prevent all other traffic may be implemented at the Customer’s discretion provided it doesn’t interfere with Blue Pillar’s Aurora product’s functionality.
  • Browser/Workstations
    • Supported and Tested Browsers
      • Internet Explorer 10 or higher
      • Google Chrome 32 or higher
    • Supported and Tested Operating Systems
      • Microsoft Client Operating Systems
    • Browsers demonstrating considerable compatibility
      • Microsoft Edge
      • Mozilla Firefox

Addendum 1

BACnet Device Configuration

IMPORTANT:  BACnet Device Configuration will be performed by Blue Pillar Field Engineers and/or Blue Pillar Administrators ONLY.

How to configure BACnet Devices in Kepware for one channel:

  1. Shut down Control Manager
  2. Open KEPServerEX Configuration
  3. Delete every channel in the tree menu until there are none left
  4. Click the New Channel icon in the toolbar (to the right of the Save As icon)
  5. Type a channel name and click Next
  6. Select BACnet/IP as the Device Driver and click Next
  7. Take the defaults for every box after this one until the channel is added
  8. Now select the Channel by clicking on it in the tree menu
  9. Click the New Device icon in the toolbar (to the right of the New Channel icon)
  10. Type a device name and click Next
  11. Enter 1.1 as the Device ID and click Next
  12. Scan Mode choose default and click Next
  13. Take defaults and click Next
  14. Defaults and click Next
  15. Defaults and click Next
  16. Defaults and click Next
  17. Defaults and click Next
  18. At the COV selections choose Do not use COV and click Next
  19. Defaults and click Next
  20. At the Discovery selections uncheck “Discover device using Who-Is/I-Am” and enter 10.1.15.250 in the IP address and click Next
  21. Click Finish
  22. Select File then Save As
  23. Save the file as bacnetconfiguration.xml in the C:\Temp directory (NOTE: if the C:\Temp directory does not exist then create it first before attempting to save this file)
  24. Now start control manager and then login to the legacy app
  25. In legacy go to Server Config and create a new entity and then in the GIM settings choose Bacnet as the protocol
  26. There’s a new textbox labeled Opc Access Path
  27. In that box type the Channel Name and Device Name you created in Kepware configuration in the steps above.  For example, if you named the channel Channel1 and the device Device1 then in the Opc Access Path box you will enter Channel1.Device1
  28. The channel and device MUST follow {ChannelName}.{DeviceName} format
  29. In the tags add a new Analog tag called Temperature
  30. In the IO Address type AnalogValue.5.PresentValue
  31. In the GIM settings ip address put 1.1.1.1
  32. Save and download
  33. Once back and after a few seconds you should be able to read a value from that Temperature tag.

How to change the default file location:

There should be a new setting in the database that gives the default file location to the bacnetconfiguration.xml file. 

  1. In the BluePillarConfiguration database open up the AviseInfo table. 
  2. Look for a new record named BacnetKepwareConfigurationFileLocation
  3. It should have a value of C:\Temp\bacnetconfiguration.xml
  4. Change that to whatever you want
  5. In step 22 above you saved the bacnetconfiguration.xml file to C:\Temp directory
  6. Copy that file from that Temp directory to whatever directory you just typed in step 4
  7. Restart control manager
  8. Now once you go back and do a save and download you should still be able to read the temperature tag

As a negative test you can just simply delete that file from your directory.  Restart control manager.  Then go back and do a save and download and you should not be seeing any value from the Temperature tag.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk