To build a FieldServer configuration a list of points needs to be configured. This requires knowledge of the Points Hardware Reference in card-point-subpoint format. Unfortunately the point ‘name’ looks similar to a Hardware Reference but cannot be used. The following notes outline where the required information can be found using the Simplex Programming Software or from one of the reports produced by the software.

Extract from a report with appropriate Hardware Addresses for FieldServer configuration

Cannot use ‘Point Name’ (2^nd column). The HW Ref will always be unique. Some Point names look like HW Refs but are not .

There is no (implied or otherwise) relationship between a point name and a hardware reference. A point name consists of a tag similar to this one; “M4-1-1″, In this example all we can tell is that this point is on the 4th mapnet device added to the system. A hardware reference is declared in a manner similar to this one; “1-1-0″ and is used to indicate c-p-s (card-point-subpoint). The hardware reference is absolute and is based on the position/location in the hardware bays.

When an event occurs a message with the hardware reference is produced. Based on the notes above you can see that it is impossible to produce a configuration unless the mapping file provided by the customer contains hardware references. I cannot find a ‘report’ which can be produced by the 4100 programmer software which provides the information required.

Using the System Points Summary Report from the FACP configuration tool

To monitor this point passively:

Use the following Map Descriptor.  The length has been set to a large number to allow all the networked points to be collected. Other than that there is no difference between receiving events from a local FACP or a networked FACP.

Map_Descriptors

Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name  ,sim4100_func ,sim4100_card ,sim4100_point ,sim4100_sub ,protocol ,length ,da_byte_name ,da_float_name

Card_03_Points      ,DA_CARD3        ,0                 ,passive  ,Simplex_01 ,xpoint       ,3            ,0             ,256         ,sim4100  ,10000  ,DA_P         ,DA_F

To Serve this Point

To serve the point you need to know the offset into the data array where the example point can be found. Data is stored in array = DA_Card3

The point=Zone ZD1-1 is found at offset 13792 in the data array. At that location is a UINT with 16 bits. Each bit’s state represents the state of each possible event.

To read this point

You need to know the C-p-S Card-Point-Subpoint.

Card = 3 (Given)

Point = truncate ( Address / 256 ) – ie. Divide by 256 and use only the whole number result

SubPoint = Remainder ( Address / 256 ) * 256 – ie divide by 256 and use the remainder as the result.

Eg. 3-13792

Card = 3

Point = trunk( 13792 / 256)  = trunk(53.875) = 53

Sub Point = 256* Remainder (13792 / 256)  = 256 * Remainder (53.875) =  256 * 0.875 = 224

Wait passively for events to be sent from the panel.

These Map descriptors each capture event data from different Cards.

Map_Descriptors,

A single point can report 8 states. We store these 8 states as bits inside a storage word. The word can be served on BACnet (or Modbus) as a number or it can be unpacked into individual bits and served bit by bit.

For example.  1-0-0 reports an alarm. We store the value 1 in the word allocated for this point.

For example.  1-0-0 reports an trouble. We store the value 16 in the word allocated for this point.

Thus if 1-0-0 was in an alarm and trouble at the same time, we would store the value 17 = 1 + 16.

Bit Identifier Description

0 F Fire Alarm

1 P Priority 2

2 S Supervisory

3 T Trouble

4 U Utility

5 C Control

6 D Disable

7 A Primary state (based on point type – F if smoke detector, C if signal circuit, etc.)

In the example

Bacnet Object AI(101) contains the number

CPS=1-0-0 State No , Server  , DA_C_001       , 0                , Virtual_Panel ,AI       , Present_Value,00101      , 1     ,No_Units

Bacnet Object BI(101) contains the alarm state. You can see the server map descriptor references DA_C_001b (a bit array). The bit array gets its data from a Move. The Move unpacks bits from the number values into individual bits.

CPS=1-0-0 Alarm    , Server  , DA_C_001b      , 0                , Virtual_Panel ,bI       , Present_Value,00101      , 1     ,Alarm        ,Normal

Each BACnet object must have a unique (Type,Object_ID) pair.

If the computer that is running the CAS BACnet Explorer does not have internet access then an FYI will be added to the main dialog.

Chipkin Automation Systems and Feedback Solutions enter Joint Venture to Integrate People Counting Solution and Building Automation System

ATLANTA (April 30, 2013) – The Irisys IRC 3020 People Counter – the latest model in the Irisys Thermal Array-based People Counter family – is a key component to a new integrated Smart Building solution that helps property and building managers generate huge savings on their energy bills.

The Gateway, developed as a joint venture between Chipkin Automation Systems and Feedback Solutions, is among the first Smart Building systems to integrate thermal People Counting technology.

“The Gateway brings to life the newest generation of Smart Building technology,” says Jeff Riordan, business development director for Irisys. “The introduction of People Counting data into this system gives it more advanced capabilities – and more opportunities to cut a facility’s energy consumption and operating costs.”

Integrating People Counting technology into a Smart Building system helps derive deeper, more accurate data and actionable analytics about a facility’s occupancy and utilization – and it is gaining ground as a key tool toward understanding the flow of people within a building, as well as occupancy and other facility trends.

A thermal People Counting solution detects building users by their body heat and is well suited for Smart Building technology because of its accuracy in all lighting conditions; minimal energy requirements; and ease of set-up and maintenance. And because a thermal system detects body only heat – instead of taking pictures or video – it protects building users’ privacy.

Integrating People Counting capabilities with a Building Automation System (BAS) that controls HVAC systems can reduce energy consumption and expenses. The Gateway seamlessly brings together Chipkin Automation Solutions and Feedback Solutions’ technologies to feed accurate count and occupancy data to a BAS that uses BACnet, Modbus, JSON, SNMP, and other protocols. The resulting data helps automation providers identify strategic optimization and trigger-control opportunities.

Chipkin Automation Systems, headed by President Peter Chipkin, has a demonstrated track record of providing highly effective integration interfaces and deep expertise developing and deploying remote monitoring, control and integration solutions. Visit www.chipkin.com for more information.

Feedback Solutions is headed by Chandan Chowdhury, an industry veteran with more than 20 years of international experience in the People Counting market. Visit www.feedbacksolutions.ca for more information.

About Irisys
Irisys is a global innovator in award-winning technologies that make a significant, measurable impact on business efficiency and improve the quality of people’s lives. Irisys is the global leader in people counting technologies and real-time checkout management solutions. Its infrared thermal imaging solutions are used by some of the world’s leading retailers to boost customer service, operational efficiency and profitability. Irisys pioneered the introduction of low cost thermal imaging cameras for industrial applications and its security technologies are predicted to transform the intruder detection market. Irisys healthcare solutions aim to make hospitals safer and cleaner, and improve home monitoring for the elderly and infirm. Learn more at www.irisys.net.

Instructions: 

1. Get the current time in unix epoch time (Current time)
   Example: 1365092464 would be 4:21:04 pm UTC , Thursday, April 4, 2013
2. From your browser using this format set the current time by visting this page. http://{CAS Gateway IP address}/bin/xml/?act=set&current_time={unix epoch time}
   Example: http://192.168.1.113/bin/xml/?act=set&current_time=1365092464

5.1 Current time

This request will sets the current time in the system to a unix epoch time

Parameters:
{time in secs} - The number of seconds that have elapsed since midnight Coordinated Universal Time (UTC), January 1, 1970

Example Request:
act=set&current_time=1234567890

Example XML Response:

<HttpXML>
   <query>
      <act>set</act>
      <current_time>1234567890</current_time>
   </query>
   <response status="OK" count="1">
      <current_time>OK</current_time>
   </response>
</HttpXML>

Please follow the steps below in order to change the Connection Parameters on Veeder Root panel.

1. The connection parameters can be changed from “Communications Setup” in “FUNCTION”. Therefore, press ‘FUNCTION’ until you see a message as the one shown in image below;

2. Press ‘STEP’ to continue and keep pressing ‘STEP’ until it shows ‘PORT SETTINGS’ as shown in image below;

PORT SETTINGS option shown in image above allows the access to the communication parameter settings such as Baud Rate, Parity, Stop Bits, Data Length (Data Bits), etc… for any board installed on the console’s Comm Bay.

3. Pressing ‘ENTER’ here at ‘PORT SETTINGS’ leads to the Baud Rate setting as shown in the image below;

Here, choose the baud rate that is same as that of the gateway device connected to the Veeder Root Panel. To set the baud rate shown on the display, press ‘STEP’. To choose another baud rate, press ‘CHANGE’ until the correct baud rate is displayed, and then press ‘ENTER’ to confirm the choice. The system displays the message as shown in the image below;

Press ‘STEP’ here in order to set the Baud Rate shown on the display. On pressing ‘STEP’, PARITY message appears.

4. Parity message appears as shown in image below;

Here, set the parity same as on the gateway device to be connected to the panel. There are three choices, i.e., NONE, ODD and EVEN.

To set the ‘PARITY’ shown in the message press ‘STEP’. To choose another parity option, press ‘CHANGE’ until you see the correct parity option. Press ‘ENTER’ to confirm the correct choice. The system displays a message similar to the one shown in image below;

Pressing ‘STEP’ here opens up the STOP BIT message.

5. Stop Bit message appears as shown in image below;

Set the parity same as on the gateway device to be connected to the panel. There are two options, i.e., 1 or 2. To set ’1′, press ‘STEP’ and to select and set ’2′, press ‘CHANGE’ and press ‘ENTER’. The system confirms the choice with the message shown below;

Press ‘STEP’ here to continue and it opens the DATA LENGTH message.

6. Data length message appears as shown in image below;

Set the data length same as on the gateway device to be connected to the panel. There are two options, i.e., 7 or 8. To set ’7′ press ‘STEP’ and to select 8 press ‘CHANGE’ and then press ‘ENTER’. The system confirms the choice with the message shown below;

Here, press ‘STEP’ to continue.

While changing and setting the communication parameters please make sure you are changing the communication settings for the appropriate COMM BOARD on the Veeder Root panel, i.e., the comm board where the gateway device is to be connected on the panel.

Please note that the system shows the communications module in the leftmost slot as “COMM BOARD: 1″. Press ‘TANK/SENSOR’ in order to access the port settings for the other communication modules (COMM BOARDS).

Instructions 

1. Start Wireshark
2. Load or capture some BACnet packets on a non standard port
3. From the “Analyse” menu select “Decode as”
4. Select the non default BACnet IP udp port number in the drop down box.
5. Select “BVLC” from the right hand menu.
   Note: “BVLC” stands for “BACnet Virtual Link Control” and is the header to all BACnet IP messages.
6. Click OK

- First Time Use – http://www.chipkin.com/visual-test-shell-%E2%80%93-first-time-use/

- Installation – http://www.chipkin.com/visual-test-shell-%E2%80%93-installation/

- Configuring Devices – http://www.chipkin.com/visual-test-shell-%E2%80%93-configuring-devices/

- Configuring Ports – http://www.chipkin.com/visual-test-shell-%E2%80%93-configuring-ports/

- Configuring Names – http://www.chipkin.com/visual-test-shell-%E2%80%93-configuring-names/

How to Test COV Server using VTS  

1.  Start the BACnet Serving application or device.

2.  Run the VTS executable.

3.  Click on the “Send” menu.  Hover over the “Alarm and Event” submenu.  Then click on the “Subscribe COV” submenu item.

4.  In the Subscribe COV window build the Subscribe COV message.

a.  First click on the “IP” tab and fill out the IP address and port as follows:  IP:PORT

b.  Next click on the “BVLCI” tab and make sure only “Original Unicast” is selected.

c.  Click on the “NPCI” tab and fill out the DNET, DADR (if needed), and Hop Count.
Make sure Data Expecting Reply is checked.  Set DNET to zero if BACnet COV Server is on the same network as the computer running VTS.

d.  Click on the “Confirmed-Request” tab and set the Max APDU length accepted to 1476 (ISO 8802-3).

e.  Finally click on the “Subscribe COV” tab and fill out the all the fields.

- Subscriber Process ID – can be any unsigned short number
- Monitored Object ID – the Object Identifier of the object you are testing COV
- Issue Confirmed Notifications – 0 = Unconfirmed Notification; 1 = Confirmed Notification
- Lifetime – how long to subscribe for in seconds

  5.  Once the message is ready, click the “Send” or “Send & Close” button.  This will send the message to the device.

6.   You should see three messages in the log.  The first one will be the Subscribe COV message sent from the VTS.
The second will be the ACK to the Subscribe COV sent from the device.
The third will be either an unconfirmed or confirmed COV notification based on what value was used for the Issue Confirmed Notifications.
See below for examples of the messages.

a.  Subscribe COV Message

b.  Subscribe COV ACK

c.  Unconfirmed / Confirmed COV Notification

  7.  Change the value of the monitored object in the device.  You should receive another unconfirmed / confirmed COV Notification with the updated value

]]> http://www.chipkin.com/testing-a-bacnet-cov-server-using-vts/feed/ 0