CHC Data Fact Sheet
Up one levelChipkin Automation Systems has developed a FieldServer driver which communicates with Mitsubishi's CHC Air Conditioning Controller. The driver can read process/status information and can send commands and setpoints. Combining this driver with any of the other FieldServer drivers allows you to easily transfer data between:
![]() |
![]() |
Web
|
FS87xx-yy
MITSUBISHI CHC-MF
Description
This driver is used to exchange data between a FieldServer and a Mitsubishi Heavy Industries communication interface known as a CHC-MF.
The driver is a serial driver using a RS232 serial port to connect between the FieldServer and the CHC-MF. An RS485 port together with a converter can also be used for the connection.
The driver provides client and server functionality.
As a client the driver can poll for data from Air Conditioning Units via the CHC-MF interface as well as writing some control and set points.
Server functionality is provided only to support our ongoing quality assurance program by facilitating automated testing of the driver. It is not documented or supported. If required please contact the FST sales group to discuss your requirements.
| Fieldserver Mode | Nodes | Comments |
| Client | 1 | A maximum of 1 Mitsubishi CHC-MF device per FieldServer Port. |
| Server | 1 | A maximum of 1 Mitsubishi CHC-MF device per FieldServer Port. |
Formal Driver Type
- Serial
- Client or Server
Compatibility Matrix
| FieldServer Model | Compatible with this driver |
| FS-x2010 | Yes, No |
| FS-x2011 | Yes, No |
| FS-x40 | Yes, No |
Connection Information
| Connection type: | EIA232 |
| Baud Rates: | Driver Supports : 110; 300; 600; 1200; 2400; 4800; 9600; 19200; 28800; 38400; 57600; 115200 Baud Vendor Equipment Supports : 4800 Baud |
| Data Bits: | Driver Supports : 7,8 Vendor Equipment Supports : 7 |
| Stop Bits: | Driver Supports : 1,2 Vendor Equipment Supports: 1 |
| Parity: | Driver Supports : Odd, Even, None |
| Hardware interface: | N/A |
| Multidrop Capability | No |
Devices Tested
| Device | Tested (FACTORY, SITE) |
| This driver has not been field or factory tested against any devices. Call Chipkin Automation Systems for an update on this information. |
Connection Configurations
Connection Notes
Vendor information on the specific connection/terminals/D-Type connector to be found on the CHC-MF is yet to be determined.
Communications Functions - Supported functions at a glance:
Read/Write Operations supported
| FieldServer as a Client | FieldServer as a Server |
| Start / Stop Operation | Digital Start/Stop Response |
| One Point Request | Digital Start/Stop Point |
| Parameter Setting Operation | Start / Stop Operation |
| Initial Data Request Processing | System Clock Time Notification |
| Forced Shutdown in a Fire | Analog Point Response |
| Parameter Point Response | |
| Add Up Point Response | |
| Completion of parameter Setting operation |
When the connection is first opened to the CHC unit or when the driver is recovering a connection (after a loss of connection) then the driver will wait for an Initial Data Request and respond appropriately. Thereafter, normal polling will occur. In the event that the driver does not receive the Initial Data Request from the CHC within a specified time it will default to normal polling behavior.
Data Points
The FieldServer reads data from the ICSII device. The data points below are the points available to the FieldServer but this does not necessarily mean that they are valid for the HVAC device connected to the ICSII.
| Point Number | Point | Read/ Write |
| 1 | Start/Stop | RW |
| 2 | Temp. Setting | R |
| 3 | Automatic temperature control mode setting | RW |
| 4 | Temperature control mode setting | RW |
| 5 | Room Temperature | R |
| 6 | Remote control mode, setting 1 | RW |
| 7 | Remote control mode, setting 2 | RW |
| 8 | Remote control mode, setting 3 | RW |
| 9 | Filter sign reset | RW |
| 10 | Forced Thermo off | RW |
| 20 | Electrical Energy | R |
Configuration
The driver can be configured to read everything with a "single line" configuration. Data will be read and stored in Data Arrays at fixed locations. Alternatively, the driver can be configured to read one/more single data points and have the data stored in any location.

