CHIPKIN FS-8705-120 GenX And RM Instructions
- June 26, 2024
- CHIPKIN
Table of Contents
- CHIPKIN FS-8705-120 GenX And RM
- Zonex Description
- Connection Diagram
- Zonex Configuration
- Importing and Exporting Configurations
- Appendix A – Troubleshooting
- Appendix B – Example Configurations
- Appendix C – BACnet IP Objects
- represents the Damper number attached to GENX (1-20)
- represents the RM number (1-20)
- represents the RM number (1-20)
- represents the RM (1-20)
- Revision History
- Read User Manual Online (PDF format)
- Download This Manual (PDF format)
CHIPKIN FS-8705-120 GenX And RM
salesgroup1@chipkin.com
Tel: +1 866 383 1657
© 2024 CHIPKIN AUTOMATION SYSTEMS
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 IP
Zonex Configuration
To configure the Zonex driver, from the home page, either visit the following
link: http://{ip_address}/chipkinCore/ui/#/driver/zonex
Or click on the Zonex Configuration Card from the main menu at
http://{IP_ADDRESS}/chipkinCore/ui/
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.
Zonex Parameters
Name
| ****
Function
| ****
Legal Values
---|---|---
Url| The url of the Zonex web server| Text, must be a valid Url (include the
http://)
Read Interval| How often to poll the Zonex web server for data (in seconds)|
1-3600, 30
Write Interval| How 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
---|---|---
Adapter| The FieldServer network adapter to use for BACnet IP Communication|
N1 (or N2 if using a 2 port FieldServer)
Port| The UDP port to use for BACnet IP| Any legal IP port value (1 – 65535);
47808
Node ID| The BACnet Device Identifier to assign to this FieldServer acting as
a BACnet Server device| 0-4194302; 389001
COV Enable| Enables or disables COV (Change of Value) for this BACnet device|
Checked = enabled,
Unchecked = disabled
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.
If an error occurs, an error message will appear at the top of the web page in a red banner. For example:
ERR_BAD_REQUEST – Error [99] Request failed with status code 401.
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 (http://{IPAddress}/htm/fsgui.htm) page to perform a System Reboot for the changes to take effect.
• Zonex Configuration Successfully Saved. Navigate to FS GUI and click System Reboot.
Click on the link to return to the FS GUI page and click the System Reboot:
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
- Goto the system configuration page http://{IP_ADDRESS}/chipkin/ui/#/chipkinConfiguration
- Click the Export Configuration button.
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:
- Goto the system configuration page http://{IP_ADDRESS}/chipkin/ui/#/chipkinConfiguration
- Click the “Browse” button in the “Import/Export System Configuration” section and select the zip file containing the configuration to import.
- Click the “Import Configuration” button and wait for the configuration to finish importing.
- If successful, a success message will appear prompting a reboot of the Fieldserver for the changes to take effect.
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)
-
Verify comms by taking a wireshark log or a FieldServer diagnostics log.
Appendix B – Example Configurations
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
| Name | Object Type | Object Instance | Notes |
|---|
SysDiagnotistic Data Points
Genx_SysDiag_Leaving Air| AI| 0|
Genx_SysDiag_Return Air| AI| 1|
Genx_SysDiag_Outside Air| AI| 2|
Genx_SysDiag_AC Status| MI| 3| Off = 1,
Vent = 2,
Cool =3,
Heat = 4,
Changeover = 5,
Air balance = 6, Abort to reset = 7
Genx_SysDiag_FDD/ADR| MI| 4| No alert = 1, FDD alert = 2, ADR = 3
FDD & ADR = 4
SysConfig Data Points
GenX_SysCon_Fan Mode| BV| 30| Active = On,
Inactive = Auto
StatDataID Data Points
represents the Damper number attached to GENX (1-20)
Genx_StatDataID#_LockStatus| MV| #000| Unlock = 1,
| | | Lock 2 Degrees = 2,
Lock = 3
---|---|---|---
Genx_StatDataID#_CurrentRoomTemperature| AI| #001|
Genx_StatDataID#_OccupiedCool| AV| #002|
Genx_StatDataID#_OccupiedHeat| AV| #003|
Genx_StatDataID#_PriorityVote| AV| #004|
Genx_StatDataID#_ZoneStatus| MV| #005| Off = 1,
Vent = 2
Cool = 3
Heat = 4
Genx_StatDataID#_ZoneCall| MV| #006| Off = 1,
Vent = 2
Cool = 3
Heat = 4
Genx_StatDataID#_AutoMode| MV| #007| Off = 1,
Auto on (heat/cool) = 2, Cool only = 3,
Heat only = 4
Genx_StatDataID#_StatType| MI| #008| Wireless = 1,
Wire = 2,
Stand Alone(wire) = 3 WUC = 4,
EztouchX = 5,
SATouch = 6,
BLE = 7
Genx_StatDataID#_LeavingAir| AI| #009|
Genx_StatDataID#_ReturnAir| AI| #010|
Genx_StatDataID#_Humidity| AI| #011|
Genx_StatDataID#_OccupiedMode| BI| #012| Active = Occupied Inactive =
Unoccupied
Genx_StatDataID#_ADR| BV| #013| Active = Enable Inactive = Disabled
RMD Data Points
represents the RM number (1-20)
RM#_RMD_Leaving Air| AI| #00000|
RM#_RMD_Return Air| AI| #00001|
RM#_RMD_AC Status| MI| #00002| Off = 1,
Vent = 2,
Cool =3,
Heat = 4,
Changeover = 5, Air balance = 6,
Abort to reset = 7
RM#_RMD_FDD/ADR| MI| #00003| No alert = 1, FDD alert = 2, ADR = 3
FDD & ADR = 4
RMC Data Points
represents the RM number (1-20)
RM#_RMC_Fan Mode| BV| #00030| Active = On,
Inactive = Auto
RMS Data Points
represents the RM (1-20)
$$ represents the Damper number attached to RM # (01-20)
RM#_RMS$$_LockStatus| MV| #$$000| Unlock = 1,
Lock 2 Degrees = 2,
Lock = 3
RM#_RMS$$_CurrentRoomTemperature| AI| #$$001|
RM#_RMS$$_OccupiedCool| AV| #$$002|
RM#_RMS$$_OccupiedHeat| AV| #$$003|
RM#_RMS$$_PriorityVote| AV| #$$004|
RM#_RMS$$_ZoneStatus| MV| #$$005| Off = 1,
Vent = 2
Cool = 3
Heat = 4
RM#_RMS$$_ZoneCall| MV| #$$006| Off = 1,
Vent = 2
Cool = 3
Heat = 4
---|---|---|---
RM#_RMS$$_AutoMode| MV| #$$007| Off = 1,
Auto on (heat/cool) = 2, Cool only = 3,
Heat only = 4
RM#_RMS$$_StatType| MI| #$$008| Wireless = 1,
Wire = 2,
Stand Alone(wire) = 3 WUC = 4,
EztouchX = 5,
SATouch = 6,
BLE = 7
RM#_RMS$$_LeavingAir| AI| #$$009|
RM#_RMS$$_ReturnAir| AI| #$$010|
RM#_RMS$$_Humidity| AI| #$$011|
RM#_RMS$$_OccupiedMode| BI| #$$012| Active = Occupied Inactive = Unoccupied
RM#_RMS$$_ADR| BV| #$$013| Active = 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 2024| AF| 1| Created initial document
05 Mar 2024| AF| 2| Fixed Import/Export configuration url
18 Apr 2024
|
AF
|
3
| Removed Schedule data points Added Fan Mode point for RM
© 2024 CHIPKIN AUTOMATION SYSTEMS
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>