CHIPKIN-logo

CHIPKIN Zonex GenX and RM FS-8705-120 Automation System

CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System -product

Zonex Description

The Zonex Driver allows the FieldServer to poll and set data from Zonex devices over Ethernet using the HTTP protocol. The Zonex Driver uses HTTP request. The driver was developed to communicate with Zonex web-server enabled devices, specifically GenX and RM devices. The FieldServer acts as an HTTP Client. When configured the FieldServer polls for data from Zonex GenX and RM devices. This data is stored on the FieldServer to be mapped to BACnet IP or simply to be viewed. The Zonex driver will also periodically attempt to write any changes that were made to writable BACnet IP objects. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer.

Connection Diagram

This block diagram lists describes how the FieldServer connects to Zonex devices and makes the data available over BACnet IPCHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-1

Zonex ConfigurationCHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-2

To configure the FieldServer, follow the instructions below to auto-generate the Zonex polling and write tasks as well as the BACnet IP Server configuration

Meta-Configurer
On the Zonex Configuration page, use the form to fill out the details required to connect to the Zonex web server as the general BACnet information to assign to the FieldServer.CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-3

Zonex Parameters 

 

Name

 

Function

 

Legal Values

UrlThe url of the Zonex web serverText, must be a valid Url (include the http://)
Read IntervalHow often to poll the Zonex web server for data (in seconds)1-3600, 30
Write IntervalHow often to write values to the Zonex web server when data has changed via BACnet (in seconds)1-3600, 5
  • Bolded values are defaults

BACnet IP Configuration 

 

Name

 

Function

 

Legal Values

AdapterThe FieldServer network adapter to use for BACnet IP CommunicationN1 (or N2 if using a 2 port FieldServer)
PortThe UDP port to use for BACnet IPAny legal IP port value (1 – 65535); 47808
Node IDThe BACnet Device Identifier to assign to this FieldServer acting as a BACnet Server device0-4194302; 389001
COV EnableEnables or disables COV (Change of Value) for this BACnet deviceChecked = enabled,

Unchecked = disabled

  • Bolded values are defaults

Saving the Server Configuration
When the configuration is complete, click on the “Save Configuration” button to save. The FieldServer will query the Zonex web server and build both the Zonex Configurtion as well as the BACnetIP Server Configuration based on the findings.CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-4

If an error occurs, an error message will appear at the top of the web page in a red banner. For example: CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-5

If the configuration was generated successfully, a success message will appear at the top of the web page in a green banner, prompting the user to return to the MSA Diagnostic page to perform a System Reboot for the changes to take effectCHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-6

Click on the link to return to the FS GUI page and click the System Reboot:

CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-7

Importing and Exporting Configurations

It is possible to export the current configuration to back it up or simply to make some edits.

How to Export the Configuration

  1. Click the Export Configuration button.CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-8

How to Import the Configuration
The file to import the configuration must be a zip file. The zip file should contain the following folders:

  • ae – this folder contains any configuration files for the Zonex configuration
  • pe – this folder contains one config.csv file for the pe configuration. To make sure the folder directory is correct, do an Export first, then extract the files, edit them, then zip them up again.

To import the configuration:

  1. Click the “Browse” button in the “Import/Export System Configuration” section and select the zip file containing the configuration to import.
  2. Click the “Import Configuration” button and wait for the configuration to finish importing.
  3. If successful, a success message will appear prompting a reboot of the Fieldserver for the changes to take effect.CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-9

Appendix A – Troubleshooting

Appendix A.1 – Debugging a Zonex Connection

  • If the FieldServer is not receiving any data, verify the URL of the Zonex web server.
  • Verify the network and ensure that the FieldServer has direct access to the Zonex web server (either both devices are on the same subnet, or the network has been setup to allow for proper routing)
  • Double check the FieldServer Network settings in the FS GUI (MSA Diagnostics page) CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-10
  • Verify comms by taking a wireshark log or a FieldServer diagnostics log. CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-12

Appendix B – Example Configurations

Zonex Configuration CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-13 CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-14CHIPKIN-Zonex-GenX-and-RM-FS-8705-120-Automation-System-fig-15

Appendix C – BACnet IP Objects

The following table contains the BACnet IP Objects generated in the Meta-Configurer. The configuration uses the BACnet Object Instance of the objects to sort the objects.

Note: Depending on the configuration of the Zonex devices, there can be a large amount of generated BACnet objects which could cause the discovery of this BACnet device to take a long time.

Supported Object Types:

  • AI = Analog Input
  • AV = Analog Value
  • BI = Binary Input
  • BV = Binary Value
  • MI = Multi-State Input
  • MV = Multi-State Value
NameObject TypeObject InstanceNotes
SysDiagnotistic Data Points
Genx_SysDiag_Leaving AirAI0
Genx_SysDiag_Return AirAI1
Genx_SysDiag_Outside AirAI2
GenX_SysDiag_Stat1 Comm StatusMI3Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat2 Comm StatusMI4Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat3 Comm StatusMI5Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat4 Comm StatusMI6Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat5 Comm StatusMI7Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat6 Comm StatusMI8Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat7 Comm StatusMI9Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat8 Comm StatusMI10Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat9 Comm StatusMI11Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat10 Comm StatusMI12Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat11 Comm StatusMI13Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat12 Comm StatusMI14Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat13 Comm StatusMI15Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat14 Comm StatusMI16Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat15 Comm StatusMI17Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat16 Comm StatusMI18Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat17 Comm StatusMI19Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat18 Comm StatusMI20Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat19 Comm StatusMI21Communication OK = 1 Communication Error = 2
GenX_SysDiag_Stat20 Comm StatusMI22Communication OK = 1 Communication Error = 2
Genx_SysDiag_AC StatusMI23Off = 1,

Vent = 2,

Cool =3,

Heat = 4,

Changeover = 5,

Air balance = 6,

Genx_SysDiag_FDD/ADRMI24No alert = 1, FDD alert = 2, ADR = 3

FDD & ADR = 4

SysConfig Data Points
GenX_SysCon_Fan ModeBV30Active = On,

Inactive = Auto

StatDataID Data Points

# represents the Damper number attached to GENX (1-20)

Genx_StatDataID#_LockStatusMV#000Unlock = 1,

Lock +/-2 Degrees = 2, Lock = 3

Genx_StatDataID#_CurrentRoomTemperatureAI#001
Genx_StatDataID#_OccupiedCoolAV#002
Genx_StatDataID#_OccupiedHeatAV#003
Genx_StatDataID#_PriorityVoteAV#004
Genx_StatDataID#_ZoneStatusMV#005Off = 1,

Vent = 2

Cool = 3

Heat = 4

Genx_StatDataID#_ZoneCallMV#006Off = 1,

Vent = 2

Cool = 3

Heat = 4

Genx_StatDataID#_AutoModeMV#007Off = 1,

Auto on (heat/cool) = 2, Cool only = 3,

Heat only = 4

Genx_StatDataID#_StatTypeMI#008EztouchX = 5,

SATouch = 6,

Genx_StatDataID#_LeavingAirAI#009
Genx_StatDataID#_ADRBV#010Active = Enable Inactive = Disabled
RMD Data Points

# represents the RM number (1-20)

RM#_RMD_Leaving AirAI#00000
RM#_RMD_Return AirAI#00001
RM1_RMD_Stat1 Comm StatusMI#00002Communication OK = 1 Communication Error = 2
RM1_RMD_Stat2 Comm StatusMI#00003Communication OK = 1 Communication Error = 2
RM1_RMD_Stat3 Comm StatusMI#00004Communication OK = 1 Communication Error = 2
RM1_RMD_Stat4 Comm StatusMI#00005Communication OK = 1 Communication Error = 2
RM1_RMD_Stat5 Comm StatusMI#00006Communication OK = 1 Communication Error = 2
RM1_RMD_Stat6 Comm StatusMI#00007Communication OK = 1 Communication Error = 2
RM1_RMD_Stat7 Comm StatusMI#00008Communication OK = 1 Communication Error = 2
RM1_RMD_Stat8 Comm StatusMI#00009Communication OK = 1 Communication Error = 2
RM1_RMD_Stat9 Comm StatusMI#00010Communication OK = 1 Communication Error = 2
RM1_RMD_Stat10 Comm StatusMI#00011Communication OK = 1 Communication Error = 2
RM1_RMD_Stat11 Comm StatusMI#00012Communication OK = 1 Communication Error = 2
RM1_RMD_Stat12 Comm StatusMI#00013Communication OK = 1 Communication Error = 2
RM1_RMD_Stat13 Comm StatusMI#00014Communication OK = 1 Communication Error = 2
RM1_RMD_Stat14 Comm StatusMI#00015Communication OK = 1 Communication Error = 2
RM1_RMD_Stat15 Comm StatusMI#00016Communication OK = 1 Communication Error = 2
RM1_RMD_Stat16 Comm StatusMI#00017Communication OK = 1 Communication Error = 2
RM1_RMD_Stat17 Comm StatusMI#00018Communication OK = 1 Communication Error = 2
RM1_RMD_Stat18 Comm StatusMI#00019Communication OK = 1 Communication Error = 2
RM1_RMD_Stat19 Comm StatusMI#00020Communication OK = 1 Communication Error = 2
RM1_RMD_Stat20 Comm StatusMI#00021Communication OK = 1 Communication Error = 2
RM#_RMD_AC StatusMI#00022Off = 1,

Vent = 2,

Cool =3,

Heat = 4,

Changeover = 5,

Air balance = 6,

RM#_RMD_FDD/ADRMI#00023No alert = 1, FDD alert = 2, ADR = 3

FDD & ADR = 4

RMC Data Points

# represents the RM number (1-20)

RM#_RMC_Fan ModeBV#00030Active = On,

Inactive = Auto

RMS Data Points

# represents the RM (1-20)

$$ represents the Damper number attached to RM # (01-20)

RM#_RMS$$_LockStatusMV#$$000Unlock = 1,

Lock +/-2 Degrees = 2, Lock = 3

RM#_RMS$$_CurrentRoomTemperatureAI#$$001
RM#_RMS$$_OccupiedCoolAV#$$002
RM#_RMS$$_OccupiedHeatAV#$$003
RM#_RMS$$_PriorityVoteAV#$$004
RM#_RMS$$_ZoneStatusMV#$$005Off = 1,

Vent = 2

Cool = 3

Heat = 4

RM#_RMS$$_ZoneCallMV#$$006Off = 1,

Vent = 2

Cool = 3

Heat = 4
RM#_RMS$$_AutoModeMV#$$007Off = 1,

Auto on (heat/cool) = 2, Cool only = 3,

Heat only = 4

RM#_RMS$$_StatTypeMI#$$008EztouchX = 5,

SATouch = 6,

RM#_RMS$$_LeavingAirAI#$$009
RM#_RMS$$_ADRBV#$$010Active = Enable Inactive = Disabled

Revision History

This table summarizes the update history for this document. Please contact Chipkin for an updated version of this document if required.

 

DATE

 

RESP

DOC. REV. 

COMMENT

21 Feb 2024AF1Created initial document
05 Mar 2024AF2Fixed Import/Export configuration url
 

18 Apr 2024

 

AF

 

3

Removed Schedule data points Added Fan Mode point for RM
 

 

 

01 May 2024

 

 

 

AF

 

 

 

4

Removed ReturnAir, Humidiity, and Occuipied Mode from StatData and RMD points

Added Stat1-20 Error Code from SysDiagnosticID and RMD

Removed some Stat Type values

02 May 2024AF5Updated Error Code data point values
10 May 2024AF6Updated images and data point description text

Specifications

  • Product Name: Zonex GenX and RM FS-8705-120
  • Manufacturer: Chipkin – Enabling Integration
  • Driver Version: 1.0.5
  • Document Revision: 6

Product Information

The Zonex Driver allows the FieldServer to poll and set data from Zonex devices over Ethernet using the HTTP protocol. It communicates with Zonex web-server-enabled devices, specifically GenX and RM devices. The FieldServer acts as an HTTP Client, polling for data and storing it to be mapped to BACnet IP or viewed. It can also write changes to writable BACnet IP objects.

Connection Diagram
This block diagram illustrates how the FieldServer connects to Zonex devices and makes the data available over BACnet IP.

Frequently Asked Questions

Q: What are the default read and write intervals for Zonex parameters?
A: The default read interval is 30 seconds, and the default write interval is 5 seconds.

Q: How can I enable or disable COV for the BACnet device?
A: You can enable or disable COV by checking or unchecking the corresponding checkbox in the adapter settings.

Documents / Resources

CHIPKIN Zonex GenX and RM FS-8705-120 Automation System [pdf] Instruction Manual
FS-8705-120, FS-8705-120, Zonex GenX and RM FS-8705-120 Automation System, Zonex GenX and RM FS-8705-120, Automation System, System

References

Leave a comment

Your email address will not be published. Required fields are marked *