THERMEx THW100 Скачать руководство пользователя страница 27

Страница: 27 / 58

Heat Pump Manual

INSTALLATION

The  SNMP,  BACnet  IP  and  Modbus  TCP  interfaces  provide  full  control,  monitoring  and
configuration of the Pump and Transfer Unit via the mapped data points. All of the interfaces
are IP based and  share a  single 10/100Base-T  thernet physical layer which is also shared
with the local HTTP web server. As such, an SNMP, BACnet IP or Modbus TCP client that is
running  on  an  external  BMS  will  need  to

‘point to’ the Pump and Transfer Current Local IP

address. This IP address can be found by pressing the

‘up’ key once on the control unit from

the home screen. IP ports for connection are standard for each service (shown above).

Connection  to  the  SNMP  V2C  agent  requires  correct  community  names  (shown  above).
Connection to BACnet IP requires a correct device number (instance) also shown above. This
device  number  can  be  changed  by  going  to  the  local  web  server

‘Heat pump ID’ page and

changing the BACnet device number shown.

All data points can be accessed via BACnet

‘Objects’. Analog Inputs, Analog Outputs and

Analog Values and Binary Inputs, Binary Outputs and Binary Values only are implemented.
Object numbers begin at 1 and the maximum number of each data point is shown in notes on
the Web Server

‘Upload’ page. In general the standard BACnet Read property and Write

Property  services  are  available  on  Analog  Output,  Analog  Value,  Binary  Output  and  Binary
Value objects. BACnet Read Property services are available on Analog Input and Binary Input
objects.  BACnet  Read  Object  Name  is  also  available  on  all  objects.  Mandatory  object
properties are implemented but most optional object properties are not. Present value priority
arrays  are  not  implemented  for  Analog  Values  or  Binary  Values.  Other  optional  object
properties  and  some  BACnet  services  may  not  be  available  from  the  local  server.
Unimplemented properties will respond with a BACnet

‘Unknown Property’ error message and

unimplemented services will respond with a BACnet

‘Service Unavailable’ error message.

All data points can also be accessed via Modbus

‘Holding Registers’. Register numbers for

Analog objects can be calculated by multiplying the hundreds, tens and units portion of the
localreg number by two, subtracting one then adding 40,000 and the thousands portion of the
localreg numbers on the xml mapping file (for example, an analog value object localreg
number 2003 would be Modbus holding register 2*3

– 1 + 2000 + 40,000 = 42,005). Register

numbers for Binary objects can be calculated by adding 40,000 to the localreg numbers on
the xml mapping file. Registers are 16 bits long and so 32 bit real (Analog 32 bit floating point)
values are transmitted as two successive 16 bit registers in

‘big endian’ format. Should 32 bit

analog  real  values  received  from  the  Pump  and  Transfer  Modbus  TCP  interface  be
unintelligible on an external BMS then the  external BMS may be attempting to send/ receive
32 bit real values with the registers in reverse order. In this  case a

‘Modbus Register Swap’

tick box can be set by going to the

‘Network’ page of the Pump and Transfer control unit local

web server and following the

‘Save Network Config’ procedure.

Local Register numbers 2001 to 2999 are Analog Value Objects mostly comprising set-points
that allow the BMS to adjust operating points of the Pump and Transfer unit as necessary. To
be able to change these values SNMP data point 1.3.6.1.4.1.33888.1.6.2.3.0

–

‘P264ControlSetSetparenable’ must be set to 1 if the ‘Network’ page ‘Set-Point Enable
Restrict

’ tick box is checked. If the ‘Network’ page ‘Set-Point Enable Restrict’ tick box is

unchecked, full backward compatibility is maintained with existing Babel Buster interfaces that
may simply write any value to

‘P264ControlSetSetparenable’ to give a 5 minute window for

set-point edits.

The

‘Network’

page

‘Set-Point

Enable

Restrict

’