Smart Home Automation Forum - "KCS" v3 firmware

KCS VERSUS ESPHOME

Thu, 20 Aug 2026 23:21:58 +0800

I just bought a KinCony 32 Pro to control basically the lighting in my house. This was a retrofit: I replaced an old automation system with the KinCony on a DIY basis.
My plan is to use Home Assistant to control everything. Today, the KinCony A32 Pro physically controls the lights ON/OFF. Now I need to install the firmware, and the big question is: ESPHome or KCS?
I asked ChatGPT, Gemini, and Copilot, and they gave contradictory answers.
What ChatGPT said
ChatGPT initially recommended KCS + Home Assistant, arguing that KCS can integrate the A32 Pro through MQTT and MQTT Auto Discovery, and that I would not need ESPHome.
It cited KinCony’s forum, including a discussion where the administrator said that KCS and ESPHome cannot run simultaneously and recommended KCS v3 for users who do not know how to configure ESPHome.
It also cited the KinCony forum thread “A32 pro lost control”, where a user had flashed ESPHome and lost KCS. The administrator explained that KCS and ESPHome cannot coexist, and suggested enabling MQTT Auto Discovery in KCS to integrate the A32 Pro with Home Assistant.
Based on this, ChatGPT concluded:

I do not need ESPHome.
I can install KCS and integrate it with Home Assistant.
KCS + MQTT Auto Discovery is the simpler solution for my case.

What Copilot said
Copilot strongly disagreed and said Gemini was right and ChatGPT was wrong.
Its main argument is that KCS does not expose all 32 digital inputs of the A32 Pro to Home Assistant.
According to Copilot, KCS exposes:

Relays through MQTT
Basic sensors
Some internal states

But it does not expose DI1–DI32.
This is critical for my application because I want to use physical inputs/dry contacts to trigger automations such as:

Quote:Press a button → turn on one, two, or three lights.

Copilot says that without the digital inputs being available in Home Assistant, this type of automation cannot work as intended.
It also claims that KinCony has stated on its forum that if you want all inputs and outputs in Home Assistant, you should use ESPHome.
Copilot's other arguments are:

KCS + MQTT Auto Discovery does not automatically expose the 32 digital inputs.
Saying that KCS is simpler may be true for some smaller KinCony controllers, but not necessarily for the A32 Pro.
The A32 Pro uses multiple I/O expanders, and ESPHome provides a more complete mapping of its inputs and outputs to Home Assistant.

My questions
I do not want a generic comparison between ESPHome and KCS. I want the answer specifically for the KinCony KC868-A32 Pro + Home Assistant, considering that my primary objective is to control lighting and use the physical digital inputs for automations.
1. Who is technically correct: Gemini/Copilot or ChatGPT?
More specifically: Does KCS v3 with MQTT Auto Discovery expose all 32 digital inputs of the A32 Pro to Home Assistant, or do I need ESPHome for that?
2. If I need ESPHome on the KinCony A32 Pro:
Where is the latest official A32 Pro ESPHome YAML/configuration for Home Assistant?
Is this KinCony forum thread the correct/latest source?
https://www.kincony.com/forum/showthread.php?tid=5520
3. If KCS should be installed instead:
Is this the latest KCS version/configuration for the A32 Pro, including MQTT Auto Discovery?
https://www.kincony.com/forum/showthread...3#pid25773
I want to resolve the contradiction before flashing the controller, because KCS and ESPHome cannot coexist, so choosing the wrong firmware means having to reflash the device.
Please base the answer on the current KinCony A32 Pro documentation/forum information, not on assumptions about other KinCony models.
Summary: I need to decide between KCS + MQTT Auto Discovery and ESPHome for an A32 Pro whose relays control my lights and whose digital inputs will be used by Home Assistant for physical-button/dry-contact automations. The key question is whether KCS exposes the 32 digital inputs to Home Assistant.

"KCS" v3.26.1 firmware BIN file download

Sun, 19 Jul 2026 09:14:31 +0800

new version improvement:

1: add support new model: MT4
2: add auto feedback DAC and ADC value by TCP string command.
3: fixed bug temperature sensor trigger SMS or phone call.
4: support use negative temperature value.
5: add "Duration" for IF condition using IFTTT.
6: if repalce new DS18B20 sensor, add auto detect function. Not need to re config sensor manually.
7: full unicode support for 4G module and Longer SMS Message content. You can use local language for SMS.Even emojis in SMS.

  KCS_A2V3_V3.26.1.zip (Size: 1.19 MB / Downloads: 127)

  KCS_A6V3_V3.26.1.zip (Size: 1.17 MB / Downloads: 85)

  KCS_A8V3_V3.26.1.zip (Size: 1.22 MB / Downloads: 114)

  KCS_A16V3_V3.26.1.zip (Size: 1.24 MB / Downloads: 136)

  KCS_A32PRO_V3.26.1.zip (Size: 1.2 MB / Downloads: 102)

  KCS_AG8_V3.26.1.zip (Size: 1.18 MB / Downloads: 77)

  KCS_AGV3_V3.26.1.zip (Size: 1.13 MB / Downloads: 103)

  KCS_AIO_HYBRID_V3.26.1.zip (Size: 1.41 MB / Downloads: 97)

  KCS_ALR_V3.26.1.zip (Size: 1.17 MB / Downloads: 77)

  KCS_B4_V3.26.1.zip (Size: 1.23 MB / Downloads: 102)

  KCS_B4M_V3.26.1.zip (Size: 1.23 MB / Downloads: 79)

  KCS_B8_V3.26.1.zip (Size: 1.23 MB / Downloads: 88)

  KCS_B8M_V3.26.1.zip (Size: 1.23 MB / Downloads: 74)

  KCS_B16_V3.26.1.zip (Size: 1.23 MB / Downloads: 87)

  KCS_B16M_V3.26.1.zip (Size: 1.23 MB / Downloads: 94)

  KCS_B24_V3.26.1.zip (Size: 1.23 MB / Downloads: 88)

  KCS_B24M_V3.26.1.zip (Size: 1.23 MB / Downloads: 102)

  KCS_B32M_V3.26.1.zip (Size: 1.23 MB / Downloads: 81)

  KCS_DM4_V3.26.1.zip (Size: 1.23 MB / Downloads: 79)

  KCS_DM8_V3.26.1.zip (Size: 1.23 MB / Downloads: 90)

  KCS_DM16_V3.26.1.zip (Size: 1.2 MB / Downloads: 95)

  KCS_DM32_V3.26.1.zip (Size: 1.23 MB / Downloads: 105)

  KCS_F4_V3.26.1.zip (Size: 1.22 MB / Downloads: 85)

  KCS_F8_V3.26.1.zip (Size: 1.22 MB / Downloads: 78)

  KCS_F16_V3.26.1.zip (Size: 1.23 MB / Downloads: 99)

  KCS_F24_V3.26.1.zip (Size: 1.23 MB / Downloads: 73)

  KCS_F32_V3.26.1.zip (Size: 1.23 MB / Downloads: 83)

  KCS_G1_V3.26.1.zip (Size: 1.19 MB / Downloads: 107)

  KCS_KC_TA_V3.26.1.zip (Size: 1.18 MB / Downloads: 89)

  KCS_MT4_V3.26.1.zip (Size: 1.18 MB / Downloads: 101)

  KCS_N10_V3.26.1.zip (Size: 1.09 MB / Downloads: 105)

  KCS_N20_V3.26.1.zip (Size: 1.09 MB / Downloads: 80)

  KCS_N30_V3.26.1.zip (Size: 1.09 MB / Downloads: 79)

  KCS_N60_V3.26.1.zip (Size: 1.11 MB / Downloads: 96)

  KCS_T16M_V3.26.1.zip (Size: 1.17 MB / Downloads: 90)

  KCS_T32M_V3.26.1.zip (Size: 1.2 MB / Downloads: 93)

  KCS_T64M_V3.26.1.zip (Size: 1.2 MB / Downloads: 89)

  KCS_T128M_V3.26.1.zip (Size: 1.2 MB / Downloads: 93)

  KCS_TR_V3.26.1.zip (Size: 1.15 MB / Downloads: 93)

  KCS_Z1_V3.26.1.zip (Size: 1.32 MB / Downloads: 70)

"KCS" v3.25.4 firmware BIN file download

Mon, 22 Jun 2026 13:11:41 +0800

new version improvement:

1. IFTTT timer accuracy adjusted to second-level precision
2. IFTTT added time range options for IFTTT
3. Fixed HomeKit DAC shutdown function
4. N-series electricity meter Home assistant MQTT reporting energy accuracy changed to 3 decimal places
5. Disable/Enable ESP32 wifi option

  KCS_A2V3_V3.25.4.zip (Size: 1.19 MB / Downloads: 180)

  KCS_A6V3_V3.25.4.zip (Size: 1.16 MB / Downloads: 178)

  KCS_A8V3_V3.25.4.zip (Size: 1.21 MB / Downloads: 150)

  KCS_A16V3_V3.25.4.zip (Size: 1.23 MB / Downloads: 219)

  KCS_A32PRO_V3.25.4.zip (Size: 1.2 MB / Downloads: 175)

  KCS_AG8_V3.25.4.zip (Size: 1.17 MB / Downloads: 163)

  KCS_AGV3_V3.25.4.zip (Size: 1.13 MB / Downloads: 144)

  KCS_AIO_HYBRID_V3.25.4.zip (Size: 1.4 MB / Downloads: 187)

  KCS_ALR_V3.25.4.zip (Size: 1.16 MB / Downloads: 166)

  KCS_B4_V3.25.4.zip (Size: 1.22 MB / Downloads: 171)

  KCS_B4M_V3.25.4.zip (Size: 1.22 MB / Downloads: 169)

  KCS_B8_V3.25.4.zip (Size: 1.22 MB / Downloads: 151)

  KCS_B8M_V3.25.4.zip (Size: 1.22 MB / Downloads: 132)

  KCS_B16_V3.25.4.zip (Size: 1.22 MB / Downloads: 169)

  KCS_B16M_V3.25.4.zip (Size: 1.22 MB / Downloads: 135)

  KCS_B24_V3.25.4.zip (Size: 1.22 MB / Downloads: 166)

  KCS_B24M_V3.25.4.zip (Size: 1.22 MB / Downloads: 145)

  KCS_B32M_V3.25.4.zip (Size: 1.22 MB / Downloads: 137)

  KCS_DM4_V3.25.4.zip (Size: 1.22 MB / Downloads: 158)

  KCS_DM8_V3.25.4.zip (Size: 1.22 MB / Downloads: 146)

  KCS_DM16_V3.25.4.zip (Size: 1.19 MB / Downloads: 165)

  KCS_DM32_V3.25.4.zip (Size: 1.22 MB / Downloads: 163)

  KCS_F4_V3.25.4.zip (Size: 1.21 MB / Downloads: 136)

  KCS_F8_V3.25.4.zip (Size: 1.21 MB / Downloads: 139)

  KCS_F16_V3.25.4.zip (Size: 1.22 MB / Downloads: 146)

  KCS_F24_V3.25.4.zip (Size: 1.22 MB / Downloads: 163)

  KCS_F32_V3.25.4.zip (Size: 1.22 MB / Downloads: 135)

  KCS_G1_V3.25.4.zip (Size: 1.18 MB / Downloads: 179)

  KCS_KC_TA_V3.25.4.zip (Size: 1.17 MB / Downloads: 148)

  KCS_N10_V3.25.4.zip (Size: 1.08 MB / Downloads: 167)

  KCS_N20_V3.25.4.zip (Size: 1.08 MB / Downloads: 168)

  KCS_N30_V3.25.4.zip (Size: 1.08 MB / Downloads: 138)

  KCS_N60_V3.25.4.zip (Size: 1.1 MB / Downloads: 140)

  KCS_T16M_V3.25.4.zip (Size: 1.17 MB / Downloads: 150)

  KCS_T32M_V3.25.4.zip (Size: 1.19 MB / Downloads: 141)

  KCS_T64M_V3.25.4.zip (Size: 1.19 MB / Downloads: 134)

  KCS_T128M_V3.25.4.zip (Size: 1.19 MB / Downloads: 138)

  KCS_TR_V3.25.4.zip (Size: 1.14 MB / Downloads: 167)

  KCS_Z1_V3.25.4.zip (Size: 1.32 MB / Downloads: 155)

"KCS" v3 Nx energy meter RS485 TCP/IP Modbus protocol document

Sun, 07 Jun 2026 09:39:23 +0800

"KCS" v3 Nx energy meter RS485 TCP/IP Modbus protocol document:

  n10_energy_modbus_protocol_20260324.txt (Size: 11.98 KB / Downloads: 108)

  n20_energy_modbus_protocol_20260324.txt (Size: 13.6 KB / Downloads: 117)

  n30_energy_modbus_protocol_20260324.txt (Size: 15.9 KB / Downloads: 103)

  n60_energy_modbus_protocol_20260324.txt (Size: 12.18 KB / Downloads: 99)

"KCS" v3 TCP/IP Standard Modbus protocol document

Sun, 07 Jun 2026 09:36:16 +0800

KCS protocol webpage, "TCP Server" = "Modbus TCP". it's a standard modbus protocol.

Code:
KCSv3 Modbus TCP Protocol Specification

=======================================

1. Overview

-----------

This document specifies the standard Modbus TCP protocol exposed by the

KCSv3 firmware TCP server.

This mode uses the standard Modbus TCP ADU with an MBAP header. It does not use

the RTU CRC field.

2. Communication Parameters

---------------------------

- Protocol: Standard Modbus TCP

- TCP port: configured by tcp_server_port

- Unit ID: configured by tcp_server_protocol_modbus_local_addr

- Register addressing: 0-based Modbus protocol address

- Frame format: [MBAP Header][PDU]

- Protocol ID in MBAP: 0x0000

- CRC: not used

MBAP header format:

+--------+----------------+----------------------------------------------+

| Bytes  | Field          | Description                                  |

+--------+----------------+----------------------------------------------+

| 0..1   | Transaction ID | Echoed in the response                       |

| 2..3   | Protocol ID    | Must be 0x0000                               |

| 4..5   | Length         | Unit ID byte + PDU length                    |

| 6      | Unit ID        | Must match tcp_server_protocol_modbus_local_addr |

+--------+----------------+----------------------------------------------+

The firmware validates the MBAP Protocol ID, Length, and Unit ID before

processing the PDU. Responses are sent only to the requesting TCP client.

3. Supported Function Codes

---------------------------

+---------------+---------------------------+-------------------------------+

| Function Code | Name                      | Usage                         |

+---------------+---------------------------+-------------------------------+

| 0x01          | Read Coils                | Read DO output state          |

| 0x02          | Read Discrete Inputs      | Read DI input state           |

| 0x03          | Read Holding Registers    | Read DAC/IR/RF/energy data    |

| 0x04          | Read Input Registers      | Read ADC/temperature/humidity |

| 0x05          | Write Single Coil         | Set one DO or trigger toggle  |

| 0x06          | Write Single Register     | Set DAC or trigger IR/RF      |

| 0x0F          | Write Multiple Coils      | Set multiple DO channels      |

| 0x10          | Write Multiple Registers  | Set multiple DAC channels     |

+---------------+---------------------------+-------------------------------+

4. Addressing Notes

-------------------

All addresses in this document are 0-based Modbus protocol addresses.

Examples:

- Holding register address 100 is sent as 0x0064 in the Modbus PDU.

- In pymodbus, use read_holding_registers(100, count=2, slave=).

- Some Modbus tools display holding register 100 as 40101 or similar. Use the

  tool's 0-based/1-based setting carefully.

5. Coils (Function Codes 0x01, 0x05, 0x0F)

-------------------------------------------

5.1 DO Output State and Control

-------------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DO_NUM-1          | DO output channels   | 0x01 read, 0x05/0x0F write  |

+------------------------+----------------------+-----------------------------+

Write value for function code 0x05:

- 0xFF00: turn ON

- 0x0000: turn OFF

Function code 0x0F supports only the normal DO output range starting at address

0.

5.2 DO Toggle Control

---------------------

+-----------------------------+----------------------+--------------------------+

| Address Range               | Description          | Access                   |

+-----------------------------+----------------------+--------------------------+

| 0x0100 .. 0x0100+DO_NUM-1   | Toggle DO channels   | 0x05 write only          |

+-----------------------------+----------------------+--------------------------+

Write 0xFF00 to address 0x0100 + channel_index to toggle that output channel.

Writing 0x0000 is accepted but does not toggle the output.

6. Discrete Inputs (Function Code 0x02)

---------------------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DI_NUM-1          | DI input channels    | 0x02 read                   |

+------------------------+----------------------+-----------------------------+

DI inputs are active-low in the firmware mapping:

- Hardware low / active input returns 1

- Hardware high / inactive input returns 0

7. Holding Registers (Function Codes 0x03, 0x06, 0x10)

------------------------------------------------------

7.1 DAC Output Registers

------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DAC_NUM-1         | DAC output channels  | 0x03 read, 0x06/0x10 write  |

+------------------------+----------------------+-----------------------------+

DAC write value range: 0 .. 255.

Function code 0x10 supports only this DAC register range.

7.2 IR/RF Control Registers

---------------------------

+----------+-------------+----------------------+-----------------------------+

| Address  | Name        | Description          | Access                      |

+----------+-------------+----------------------+-----------------------------+

| 0x0040   | IR_SEND     | Send learned IR slot | 0x03 read, 0x06 write       |

| 0x0041   | IR_LEARN    | Learn IR slot/port   | 0x03 read, 0x06 write       |

| 0x0042   | IR_DELETE   | Delete IR slot       | 0x03 read, 0x06 write       |

| 0x0050   | RF_SEND     | Send learned RF slot | 0x03 read, 0x06 write       |

+----------+-------------+----------------------+-----------------------------+

IR_SEND:

- Value: IR memory slot index

- Valid range: 0 .. IR_MEM_NUM-1

IR_LEARN:

- High byte: IR memory slot index

- Low byte: IR send port number, starting from 1

IR_DELETE:

- Value: IR memory slot index

- Valid range: 0 .. IR_MEM_NUM-1

RF_SEND:

- Value: RF memory slot index

- The selected RF slot must exist and be learned

These registers exist only on board variants with the corresponding IR/RF

feature enabled. Otherwise accesses return an illegal data address exception.

7.3 Energy Measurement Registers

--------------------------------

Energy data is exposed as read-only Holding Registers and is read with function

code 0x03.

Each energy chip uses 68 holding registers. The base address is:

  base = 100 + chip_index * 100

where chip_index starts from 0.

+--------------+----------------+----------------+--------------------------+

| Offset Range | Parameter      | Format         | Resolution / Notes       |

+--------------+----------------+----------------+--------------------------+

| 0 .. 19      | RMS_1..RMS_10  | uint32 CDAB    | Current in A * 1000      |

| 20 .. 39     | WATT_1..WATT_10| int32 CDAB     | Power in W * 10          |

| 40 .. 59     | Energy_1..10   | float32 CDAB   | Energy in kWh            |

| 60 .. 61     | Energy_Sum     | float32 CDAB   | Total energy in kWh      |

| 62           | RMS_V          | uint16         | Voltage in V * 100       |

| 63           | Period         | uint16         | Frequency in Hz * 100    |

| 64 .. 65     | TPS1           | float32 CDAB   | Temperature in deg C     |

| 66 .. 67     | PF             | float32 CDAB   | Power factor             |

+--------------+----------------+----------------+--------------------------+

Per-channel offsets:

+----------------+----------------+----------------+--------------------------+

| Channel        | Current Offset | Power Offset   | Energy Offset            |

+----------------+----------------+----------------+--------------------------+

| 1              | 0              | 20             | 40                       |

| 2              | 2              | 22             | 42                       |

| 3              | 4              | 24             | 44                       |

| 4              | 6              | 26             | 46                       |

| 5              | 8              | 28             | 48                       |

| 6              | 10             | 30             | 50                       |

| 7              | 12             | 32             | 52                       |

| 8              | 14             | 34             | 54                       |

| 9              | 16             | 36             | 56                       |

| 10             | 18             | 38             | 58                       |

+----------------+----------------+----------------+--------------------------+

For 32-bit integer and float values, read two consecutive registers. The lower

16-bit word is returned first, followed by the upper 16-bit word.

Examples:

- Chip 1 current channel 1: read holding registers 100 and 101

- Chip 2 power channel 1: read holding registers 220 and 221

- Chip 1 voltage: read holding register 162

- Chip 1 frequency: read holding register 163

8. Input Registers (Function Code 0x04)

---------------------------------------

+-------------------------------+----------------------+--------------------------+

| Address Range                 | Description          | Format                   |

+-------------------------------+----------------------+--------------------------+

| 0 .. ADC_NUM-1                | ADC input channels   | uint16 raw ADC value     |

| 0x0100 .. 0x0100+SENSOR_NUM-1 | Temperature sensors  | int16, deg C * 10        |

| 0x0120 .. 0x0120+SENSOR_NUM-1 | Humidity sensors     | int16, %RH * 10          |

+-------------------------------+----------------------+--------------------------+

If a temperature or humidity sensor is invalid or not present, the returned

value is 0x7FFF.

9. Board-Dependent Limits

-------------------------

The following symbols depend on the compiled board model:

- DO_NUM: number of digital outputs

- DI_NUM: number of digital inputs

- DAC_NUM: number of DAC outputs

- ADC_NUM: number of ADC inputs

- SENSOR_NUM: maximum temperature/humidity sensor slots

- ENERGY_NUM: number of energy measurement chips

N-series energy chip bases:

+-------+------------+--------------------------------------+

| Board | ENERGY_NUM | Energy Holding Register Bases        |

+-------+------------+--------------------------------------+

| N10   | 1          | 100                                  |

| N20   | 2          | 100, 200                             |

| N30   | 3          | 100, 200, 300                        |

| N60   | 6          | 100, 200, 300, 400, 500, 600         |

+-------+------------+--------------------------------------+

10. Exception Codes

-------------------

+----------------+----------------------------+-------------------------------+

| Exception Code | Name                       | Meaning                       |

+----------------+----------------------------+-------------------------------+

| 0x01           | Illegal Function           | Unsupported function code     |

| 0x02           | Illegal Data Address       | Unsupported address/range     |

| 0x03           | Illegal Data Value         | Invalid value or quantity     |

| 0x04           | Slave Device Failure       | Runtime failure or overflow   |

+----------------+----------------------------+-------------------------------+

11. Request Size Limits

-----------------------

- Read coils/discrete inputs: quantity 1 .. 2000

- Read holding/input registers: quantity 1 .. 125

- Write multiple coils: quantity 1 .. 1968

- Write multiple registers: quantity 1 .. 123

download protocol:

Modbus_TCP_Protocol.txt (Size: 11.59 KB / Downloads: 123)

"KCS" v3 Modbus RTU over TCP/IP protocol document

Sun, 07 Jun 2026 09:33:35 +0800

KCS protocol webpage, "TCP Server" = "Modbus-RTU-V2". Just RS485 modbus protocol over TCP/IP.

Code:
KCSv3 Modbus RTU over TCP Protocol Specification

================================================

1. Overview

-----------

This document specifies the Modbus RTU over TCP protocol exposed by the

KCSv3 firmware TCP server when the TCP protocol mode is configured for Modbus RTU

frames.

This mode transports a complete Modbus RTU ADU over a TCP socket. It does not use

the standard Modbus TCP MBAP header.

2. Communication Parameters

---------------------------

- Protocol: Modbus RTU ADU transported over TCP

- TCP port: configured by tcp_server_port

- Slave address: configured by tcp_server_protocol_modbus_local_addr

- Register addressing: 0-based Modbus protocol address

- Frame format: [Slave Address][PDU][CRC Lo][CRC Hi]

- CRC: Modbus CRC16, low byte first

- MBAP header: not used

Clients should send one complete RTU ADU frame per TCP request. The firmware

validates the RTU slave address and CRC before processing the PDU.

3. Supported Function Codes

---------------------------

+---------------+---------------------------+-------------------------------+

| Function Code | Name                      | Usage                         |

+---------------+---------------------------+-------------------------------+

| 0x01          | Read Coils                | Read DO output state          |

| 0x02          | Read Discrete Inputs      | Read DI input state           |

| 0x03          | Read Holding Registers    | Read DAC/IR/RF/energy data    |

| 0x04          | Read Input Registers      | Read ADC/temperature/humidity |

| 0x05          | Write Single Coil         | Set one DO or trigger toggle  |

| 0x06          | Write Single Register     | Set DAC or trigger IR/RF      |

| 0x0F          | Write Multiple Coils      | Set multiple DO channels      |

| 0x10          | Write Multiple Registers  | Set multiple DAC channels     |

+---------------+---------------------------+-------------------------------+

4. Addressing Notes

-------------------

All addresses in this document are 0-based Modbus protocol addresses.

Examples:

- Holding register address 100 is sent as 0x0064 in the Modbus PDU.

- Some Modbus tools display holding register 100 as 40101 or similar. Use the

  tool's 0-based/1-based setting carefully.

5. Coils (Function Codes 0x01, 0x05, 0x0F)

-------------------------------------------

5.1 DO Output State and Control

-------------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DO_NUM-1          | DO output channels   | 0x01 read, 0x05/0x0F write  |

+------------------------+----------------------+-----------------------------+

Write value for function code 0x05:

- 0xFF00: turn ON

- 0x0000: turn OFF

Function code 0x0F supports only the normal DO output range starting at address

0.

5.2 DO Toggle Control

---------------------

+-----------------------------+----------------------+--------------------------+

| Address Range               | Description          | Access                   |

+-----------------------------+----------------------+--------------------------+

| 0x0100 .. 0x0100+DO_NUM-1   | Toggle DO channels   | 0x05 write only          |

+-----------------------------+----------------------+--------------------------+

Write 0xFF00 to address 0x0100 + channel_index to toggle that output channel.

Writing 0x0000 is accepted but does not toggle the output.

6. Discrete Inputs (Function Code 0x02)

---------------------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DI_NUM-1          | DI input channels    | 0x02 read                   |

+------------------------+----------------------+-----------------------------+

DI inputs are active-low in the firmware mapping:

- Hardware low / active input returns 1

- Hardware high / inactive input returns 0

7. Holding Registers (Function Codes 0x03, 0x06, 0x10)

------------------------------------------------------

7.1 DAC Output Registers

------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DAC_NUM-1         | DAC output channels  | 0x03 read, 0x06/0x10 write  |

+------------------------+----------------------+-----------------------------+

DAC write value range: 0 .. 255.

Function code 0x10 supports only this DAC register range.

7.2 IR/RF Control Registers

---------------------------

+----------+-------------+----------------------+-----------------------------+

| Address  | Name        | Description          | Access                      |

+----------+-------------+----------------------+-----------------------------+

| 0x0040   | IR_SEND     | Send learned IR slot | 0x03 read, 0x06 write       |

| 0x0041   | IR_LEARN    | Learn IR slot/port   | 0x03 read, 0x06 write       |

| 0x0042   | IR_DELETE   | Delete IR slot       | 0x03 read, 0x06 write       |

| 0x0050   | RF_SEND     | Send learned RF slot | 0x03 read, 0x06 write       |

+----------+-------------+----------------------+-----------------------------+

IR_SEND:

- Value: IR memory slot index

- Valid range: 0 .. IR_MEM_NUM-1

IR_LEARN:

- High byte: IR memory slot index

- Low byte: IR send port number, starting from 1

IR_DELETE:

- Value: IR memory slot index

- Valid range: 0 .. IR_MEM_NUM-1

RF_SEND:

- Value: RF memory slot index

- The selected RF slot must exist and be learned

These registers exist only on board variants with the corresponding IR/RF

feature enabled. Otherwise accesses return an illegal data address exception.

7.3 Energy Measurement Registers

--------------------------------

Energy data is exposed as read-only Holding Registers and is read with function

code 0x03.

Each energy chip uses 68 holding registers. The base address is:

  base = 100 + chip_index * 100

where chip_index starts from 0.

+--------------+----------------+----------------+--------------------------+

| Offset Range | Parameter      | Format         | Resolution / Notes       |

+--------------+----------------+----------------+--------------------------+

| 0 .. 19      | RMS_1..RMS_10  | uint32 CDAB    | Current in A * 1000      |

| 20 .. 39     | WATT_1..WATT_10| int32 CDAB     | Power in W * 10          |

| 40 .. 59     | Energy_1..10   | float32 CDAB   | Energy in kWh            |

| 60 .. 61     | Energy_Sum     | float32 CDAB   | Total energy in kWh      |

| 62           | RMS_V          | uint16         | Voltage in V * 100       |

| 63           | Period         | uint16         | Frequency in Hz * 100    |

| 64 .. 65     | TPS1           | float32 CDAB   | Temperature in deg C     |

| 66 .. 67     | PF             | float32 CDAB   | Power factor             |

+--------------+----------------+----------------+--------------------------+

Per-channel offsets:

+----------------+----------------+----------------+--------------------------+

| Channel        | Current Offset | Power Offset   | Energy Offset            |

+----------------+----------------+----------------+--------------------------+

| 1              | 0              | 20             | 40                       |

| 2              | 2              | 22             | 42                       |

| 3              | 4              | 24             | 44                       |

| 4              | 6              | 26             | 46                       |

| 5              | 8              | 28             | 48                       |

| 6              | 10             | 30             | 50                       |

| 7              | 12             | 32             | 52                       |

| 8              | 14             | 34             | 54                       |

| 9              | 16             | 36             | 56                       |

| 10             | 18             | 38             | 58                       |

+----------------+----------------+----------------+--------------------------+

For 32-bit integer and float values, read two consecutive registers. The lower

16-bit word is returned first, followed by the upper 16-bit word.

Examples:

- Chip 1 current channel 1: read holding registers 100 and 101

- Chip 2 power channel 1: read holding registers 220 and 221

- Chip 1 voltage: read holding register 162

- Chip 1 frequency: read holding register 163

8. Input Registers (Function Code 0x04)

---------------------------------------

+-------------------------------+----------------------+--------------------------+

| Address Range                 | Description          | Format                   |

+-------------------------------+----------------------+--------------------------+

| 0 .. ADC_NUM-1                | ADC input channels   | uint16 raw ADC value     |

| 0x0100 .. 0x0100+SENSOR_NUM-1 | Temperature sensors  | int16, deg C * 10        |

| 0x0120 .. 0x0120+SENSOR_NUM-1 | Humidity sensors     | int16, %RH * 10          |

+-------------------------------+----------------------+--------------------------+

If a temperature or humidity sensor is invalid or not present, the returned

value is 0x7FFF.

9. Board-Dependent Limits

-------------------------

The following symbols depend on the compiled board model:

- DO_NUM: number of digital outputs

- DI_NUM: number of digital inputs

- DAC_NUM: number of DAC outputs

- ADC_NUM: number of ADC inputs

- SENSOR_NUM: maximum temperature/humidity sensor slots

- ENERGY_NUM: number of energy measurement chips

N-series energy chip bases:

+-------+------------+--------------------------------------+

| Board | ENERGY_NUM | Energy Holding Register Bases        |

+-------+------------+--------------------------------------+

| N10   | 1          | 100                                  |

| N20   | 2          | 100, 200                             |

| N30   | 3          | 100, 200, 300                        |

| N60   | 6          | 100, 200, 300, 400, 500, 600         |

+-------+------------+--------------------------------------+

10. Exception Codes

-------------------

+----------------+----------------------------+-------------------------------+

| Exception Code | Name                       | Meaning                       |

+----------------+----------------------------+-------------------------------+

| 0x01           | Illegal Function           | Unsupported function code     |

| 0x02           | Illegal Data Address       | Unsupported address/range     |

| 0x03           | Illegal Data Value         | Invalid value or quantity     |

| 0x04           | Slave Device Failure       | Runtime failure or overflow   |

+----------------+----------------------------+-------------------------------+

11. Request Size Limits

-----------------------

- Read coils/discrete inputs: quantity 1 .. 2000

- Read holding/input registers: quantity 1 .. 125

- Write multiple coils: quantity 1 .. 1968

- Write multiple registers: quantity 1 .. 123

download protocol:

Modbus_RTU_over_TCP_Protocol.txt (Size: 11.05 KB / Downloads: 114)

"KCS" v3 RS485 Standard Modbus protocol document

Sun, 07 Jun 2026 09:28:35 +0800

KCS protocol webpage, set to "Modbus_RTU-v2" option. it's a standard modbus protocol.

Code:
KCSv3 Modbus RTU Protocol Specification

=======================================

1. Overview

-----------

This document specifies the Modbus RTU protocol exposed by the KCSv3

firmware on the RS485 interface.

2. Communication Parameters

---------------------------

- Protocol: Modbus RTU

- Physical interface: RS485

- Slave address: configured by rs485_local_addr

- Register addressing: 0-based Modbus protocol address

- Frame format: [Slave Address][PDU][CRC Lo][CRC Hi]

- CRC: Modbus CRC16, low byte first

Serial port parameters are configured by the firmware RS485 settings.

3. Supported Function Codes

---------------------------

+---------------+---------------------------+-------------------------------+

| Function Code | Name                      | Usage                         |

+---------------+---------------------------+-------------------------------+

| 0x01          | Read Coils                | Read DO output state          |

| 0x02          | Read Discrete Inputs      | Read DI input state           |

| 0x03          | Read Holding Registers    | Read DAC/IR/RF/energy data    |

| 0x04          | Read Input Registers      | Read ADC/temperature/humidity |

| 0x05          | Write Single Coil         | Set one DO or trigger toggle  |

| 0x06          | Write Single Register     | Set DAC or trigger IR/RF      |

| 0x0F          | Write Multiple Coils      | Set multiple DO channels      |

| 0x10          | Write Multiple Registers  | Set multiple DAC channels     |

+---------------+---------------------------+-------------------------------+

4. Addressing Notes

-------------------

All addresses in this document are 0-based Modbus protocol addresses.

Examples:

- Holding register address 100 is sent as 0x0064 in the Modbus PDU.

- Some Modbus tools display holding register 100 as 40101 or similar. Use the

  tool's 0-based/1-based setting carefully.

5. Coils (Function Codes 0x01, 0x05, 0x0F)

-------------------------------------------

5.1 DO Output State and Control

-------------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DO_NUM-1          | DO output channels   | 0x01 read, 0x05/0x0F write  |

+------------------------+----------------------+-----------------------------+

Write value for function code 0x05:

- 0xFF00: turn ON

- 0x0000: turn OFF

Function code 0x0F supports only the normal DO output range starting at address

0.

5.2 DO Toggle Control

---------------------

+-----------------------------+----------------------+--------------------------+

| Address Range               | Description          | Access                   |

+-----------------------------+----------------------+--------------------------+

| 0x0100 .. 0x0100+DO_NUM-1   | Toggle DO channels   | 0x05 write only          |

+-----------------------------+----------------------+--------------------------+

Write 0xFF00 to address 0x0100 + channel_index to toggle that output channel.

Writing 0x0000 is accepted but does not toggle the output.

6. Discrete Inputs (Function Code 0x02)

---------------------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DI_NUM-1          | DI input channels    | 0x02 read                   |

+------------------------+----------------------+-----------------------------+

DI inputs are active-low in the firmware mapping:

- Hardware low / active input returns 1

- Hardware high / inactive input returns 0

7. Holding Registers (Function Codes 0x03, 0x06, 0x10)

------------------------------------------------------

7.1 DAC Output Registers

------------------------

+------------------------+----------------------+-----------------------------+

| Address Range          | Description          | Access                      |

+------------------------+----------------------+-----------------------------+

| 0 .. DAC_NUM-1         | DAC output channels  | 0x03 read, 0x06/0x10 write  |

+------------------------+----------------------+-----------------------------+

DAC write value range: 0 .. 255.

Function code 0x10 supports only this DAC register range.

7.2 IR/RF Control Registers

---------------------------

+----------+-------------+----------------------+-----------------------------+

| Address  | Name        | Description          | Access                      |

+----------+-------------+----------------------+-----------------------------+

| 0x0040   | IR_SEND     | Send learned IR slot | 0x03 read, 0x06 write       |

| 0x0041   | IR_LEARN    | Learn IR slot/port   | 0x03 read, 0x06 write       |

| 0x0042   | IR_DELETE   | Delete IR slot       | 0x03 read, 0x06 write       |

| 0x0050   | RF_SEND     | Send learned RF slot | 0x03 read, 0x06 write       |

+----------+-------------+----------------------+-----------------------------+

IR_SEND:

- Value: IR memory slot index

- Valid range: 0 .. IR_MEM_NUM-1

IR_LEARN:

- High byte: IR memory slot index

- Low byte: IR send port number, starting from 1

IR_DELETE:

- Value: IR memory slot index

- Valid range: 0 .. IR_MEM_NUM-1

RF_SEND:

- Value: RF memory slot index

- The selected RF slot must exist and be learned

These registers exist only on board variants with the corresponding IR/RF

feature enabled. Otherwise accesses return an illegal data address exception.

7.3 Energy Measurement Registers

--------------------------------

Energy data is exposed as read-only Holding Registers and is read with function

code 0x03.

Each energy chip uses 68 holding registers. The base address is:

  base = 100 + chip_index * 100

where chip_index starts from 0.

+--------------+----------------+----------------+--------------------------+

| Offset Range | Parameter      | Format         | Resolution / Notes       |

+--------------+----------------+----------------+--------------------------+

| 0 .. 19      | RMS_1..RMS_10  | uint32 CDAB    | Current in A * 1000      |

| 20 .. 39     | WATT_1..WATT_10| int32 CDAB     | Power in W * 10          |

| 40 .. 59     | Energy_1..10   | float32 CDAB   | Energy in kWh            |

| 60 .. 61     | Energy_Sum     | float32 CDAB   | Total energy in kWh      |

| 62           | RMS_V          | uint16         | Voltage in V * 100       |

| 63           | Period         | uint16         | Frequency in Hz * 100    |

| 64 .. 65     | TPS1           | float32 CDAB   | Temperature in deg C     |

| 66 .. 67     | PF             | float32 CDAB   | Power factor             |

+--------------+----------------+----------------+--------------------------+

Per-channel offsets:

+----------------+----------------+----------------+--------------------------+

| Channel        | Current Offset | Power Offset   | Energy Offset            |

+----------------+----------------+----------------+--------------------------+

| 1              | 0              | 20             | 40                       |

| 2              | 2              | 22             | 42                       |

| 3              | 4              | 24             | 44                       |

| 4              | 6              | 26             | 46                       |

| 5              | 8              | 28             | 48                       |

| 6              | 10             | 30             | 50                       |

| 7              | 12             | 32             | 52                       |

| 8              | 14             | 34             | 54                       |

| 9              | 16             | 36             | 56                       |

| 10             | 18             | 38             | 58                       |

+----------------+----------------+----------------+--------------------------+

For 32-bit integer and float values, read two consecutive registers. The lower

16-bit word is returned first, followed by the upper 16-bit word.

Examples:

- Chip 1 current channel 1: read holding registers 100 and 101

- Chip 2 power channel 1: read holding registers 220 and 221

- Chip 1 voltage: read holding register 162

- Chip 1 frequency: read holding register 163

8. Input Registers (Function Code 0x04)

---------------------------------------

+-------------------------------+----------------------+--------------------------+

| Address Range                 | Description          | Format                   |

+-------------------------------+----------------------+--------------------------+

| 0 .. ADC_NUM-1                | ADC input channels   | uint16 raw ADC value     |

| 0x0100 .. 0x0100+SENSOR_NUM-1 | Temperature sensors  | int16, deg C * 10        |

| 0x0120 .. 0x0120+SENSOR_NUM-1 | Humidity sensors     | int16, %RH * 10          |

+-------------------------------+----------------------+--------------------------+

If a temperature or humidity sensor is invalid or not present, the returned

value is 0x7FFF.

9. Board-Dependent Limits

-------------------------

The following symbols depend on the compiled board model:

- DO_NUM: number of digital outputs

- DI_NUM: number of digital inputs

- DAC_NUM: number of DAC outputs

- ADC_NUM: number of ADC inputs

- SENSOR_NUM: maximum temperature/humidity sensor slots

- ENERGY_NUM: number of energy measurement chips

N-series energy chip bases:

+-------+------------+--------------------------------------+

| Board | ENERGY_NUM | Energy Holding Register Bases        |

+-------+------------+--------------------------------------+

| N10   | 1          | 100                                  |

| N20   | 2          | 100, 200                             |

| N30   | 3          | 100, 200, 300                        |

| N60   | 6          | 100, 200, 300, 400, 500, 600         |

+-------+------------+--------------------------------------+

10. Exception Codes

-------------------

+----------------+----------------------------+-------------------------------+

| Exception Code | Name                       | Meaning                       |

+----------------+----------------------------+-------------------------------+

| 0x01           | Illegal Function           | Unsupported function code     |

| 0x02           | Illegal Data Address       | Unsupported address/range     |

| 0x03           | Illegal Data Value         | Invalid value or quantity     |

| 0x04           | Slave Device Failure       | Runtime failure or overflow   |

+----------------+----------------------------+-------------------------------+

11. Request Size Limits

-----------------------

- Read coils/discrete inputs: quantity 1 .. 2000

- Read holding/input registers: quantity 1 .. 125

- Write multiple coils: quantity 1 .. 1968

- Write multiple registers: quantity 1 .. 123

download protocol:

Modbus_RTU_Protocol.txt (Size: 10.7 KB / Downloads: 125)

"KCS" v3.25.0 firmware BIN file download

Sat, 16 May 2026 13:13:21 +0800

new version improvement:

1. Daylight saving time adaptation (add DST configuration to firmware system + IFTTT automatic adjustment to new time)
2. Multi-channel configuration support for the Wiegand protocol
3. Display cumulative online duration on the web page (web + MQTT + HA)
4. Support for third-party sensor integration using the standard Modbus protocol
5. add send IR signal to ALL GPIO channels
6. add mqtt "force update" option for home assistant

  wiegand-multi.png (Size: 94.14 KB / Downloads: 982)

  HA-mqtt-force-update.png (Size: 65.01 KB / Downloads: 989)

  modbus-sensor.png (Size: 81.12 KB / Downloads: 976)

  DST.png (Size: 62.41 KB / Downloads: 983)

  uptime.png (Size: 47.84 KB / Downloads: 963)

  KCS_A2V3_V3.25.0.zip (Size: 1.18 MB / Downloads: 296)

  KCS_A6V3_V3.25.0.zip (Size: 1.15 MB / Downloads: 255)

  KCS_A8V3_V3.25.0.zip (Size: 1.21 MB / Downloads: 314)

  KCS_A16V3_V3.25.0.zip (Size: 1.22 MB / Downloads: 293)

  KCS_A32PRO_V3.25.0.zip (Size: 1.19 MB / Downloads: 218)

  KCS_AG8_V3.25.0.zip (Size: 1.17 MB / Downloads: 200)

  KCS_AGV3_V3.25.0.zip (Size: 1.12 MB / Downloads: 249)

  KCS_AIO_HYBRID_V3.25.0.zip (Size: 1.4 MB / Downloads: 248)

  KCS_ALR_V3.25.0.zip (Size: 1.16 MB / Downloads: 227)

  KCS_B4_V3.25.0.zip (Size: 1.21 MB / Downloads: 203)

  KCS_B4M_V3.25.0.zip (Size: 1.21 MB / Downloads: 217)

  KCS_B8_V3.25.0.zip (Size: 1.21 MB / Downloads: 198)

  KCS_B8M_V3.25.0.zip (Size: 1.21 MB / Downloads: 240)

  KCS_B16_V3.25.0.zip (Size: 1.21 MB / Downloads: 226)

  KCS_B16M_V3.25.0.zip (Size: 1.21 MB / Downloads: 275)

  KCS_B24_V3.25.0.zip (Size: 1.21 MB / Downloads: 240)

  KCS_B24M_V3.25.0.zip (Size: 1.21 MB / Downloads: 209)

  KCS_B32M_V3.25.0.zip (Size: 1.21 MB / Downloads: 207)

  KCS_DM4_V3.25.0.zip (Size: 1.22 MB / Downloads: 200)

  KCS_DM8_V3.25.0.zip (Size: 1.22 MB / Downloads: 228)

  KCS_DM16_V3.25.0.zip (Size: 1.19 MB / Downloads: 251)

  KCS_DM32_V3.25.0.zip (Size: 1.22 MB / Downloads: 210)

  KCS_F4_V3.25.0.zip (Size: 1.21 MB / Downloads: 194)

  KCS_F8_V3.25.0.zip (Size: 1.21 MB / Downloads: 253)

  KCS_F16_V3.25.0.zip (Size: 1.22 MB / Downloads: 247)

  KCS_F24_V3.25.0.zip (Size: 1.22 MB / Downloads: 200)

  KCS_F32_V3.25.0.zip (Size: 1.22 MB / Downloads: 203)

  KCS_G1_V3.25.0.zip (Size: 1.17 MB / Downloads: 201)

  KCS_KC_TA_V3.25.0.zip (Size: 1.17 MB / Downloads: 227)

  KCS_N10_V3.25.0.zip (Size: 1.08 MB / Downloads: 205)

  KCS_N20_V3.25.0.zip (Size: 1.08 MB / Downloads: 223)

  KCS_N30_V3.25.0.zip (Size: 1.08 MB / Downloads: 232)

  KCS_N60_V3.25.0.zip (Size: 1.09 MB / Downloads: 231)

  KCS_T16M_V3.25.0.zip (Size: 1.16 MB / Downloads: 215)

  KCS_T32M_V3.25.0.zip (Size: 1.18 MB / Downloads: 217)

  KCS_T64M_V3.25.0.zip (Size: 1.18 MB / Downloads: 195)

  KCS_T128M_V3.25.0.zip (Size: 1.18 MB / Downloads: 233)

  KCS_TR_V3.25.0.zip (Size: 1.14 MB / Downloads: 223)

  KCS_Z1_V3.25.0.zip (Size: 1.31 MB / Downloads: 221)

Factor settings and calculations

Thu, 14 May 2026 17:27:23 +0800

Hi,

I see some weird bahavior on my N30 that I do not understand:

Using CT with factor 1000:1 and after measering the actual curren with MID approved device I found that factor 2.1 was the best.
When I save the factor 2.1 it results in 2.0999... etc and that might very well be because of how the factor is binary processed in the chip.
So initially I started with setting all factors to 2.1 (for testing I have now set CH01 to factor 2 and CH02 to 1)

But on Channel 2 (first 901 chip) I got strange values and the Power Factor keeps changing in the header of the dat for that chip.
On the other two chips it stays on 1.0000 and the data looked correct.

When I move the CT connector for 1..10 to the position of the 11..20 I see that CH12 is displaying the expected values.
Looks like CHIP 1 is behaving differtent from CHIP 2&3.

Any idea what could cause this?

Related to this I would like to know how to best set the factors I it necessary to set all columns with same factor? (Please provide a field for the default setting for all columns)
Power = Voltage * Current
Energy = Power over time accumulated. It is not fully clear if I need the factor (2.1) there also, or should it be 1 since the power is already corrected.

Thanks,
GWS

2026-05-14 111107_N30_Monitor.png (Size: 82.7 KB / Downloads: 170)

2026-05-14 111226_N30_Energy-Configuration.png (Size: 76.53 KB / Downloads: 171)

N30 - Modbus-TCP

Thu, 14 May 2026 16:57:50 +0800

Hi,

I am trying to get the N30 to work as a modbus device that I can read from via TCP on port 502. Could not get it to work on the IP address of the N30

Hooked up a Hi-Flying EW11 TCP to modbus converter to the RS485 port in modbus mode and that does work. Can see all the registers for chips on address 100/200/300
I was assuming that the setting

TCP Server: enable
Protocol: Modbus
local port: 502
modbus local addr 1

Would be sufficient to read the registers via the N30 IP address on port 502

Whatever I try I do get a time-out

Port 502 is open if I test with ModbusDoctor or Powershell I get connected but no readings at the expected adresses.

Also tried with setting Modbus-RTU-v2 and a virtual COM port without any responce. Please provide instructions if this should work and if so how?

Thanks,
GWS

N30 no Energy (kWh)

Thu, 14 May 2026 03:46:59 +0800

I have buy 3 N30 to monitor energy.
I use latest software

Board Model
N30
Software Version
v3.24.5
Build Date
Apr 29 2026 05:26:42
Serial Number
D0CF13020568

I connect 1,2,3 voltage and connect 3 phase conditionner to CH2
Energy Monitor 1
CH 2
Energy Monitor 2
CH 2
Energy Monitor 3
CH 2

and other 1 pahse load to other ports.

How make to get Energy (kWh)?

  energy2.jpg (Size: 52.14 KB / Downloads: 217)

  energy3.jpg (Size: 117.58 KB / Downloads: 203)

  energy4.jpg (Size: 110.91 KB / Downloads: 197)

  energy5.jpg (Size: 116.71 KB / Downloads: 199)

  energy6.jpg (Size: 44.73 KB / Downloads: 191)

  energy1.jpg (Size: 105.9 KB / Downloads: 194)

"KCS" v3.24.5 firmware BIN file download

Thu, 30 Apr 2026 07:38:46 +0800

v3.24.5 improvement:

1: N series energy meter board support rename for every CT channel.
2: DM series dimmer board support "DAC Dimmer" option, use for one button adjust OUTPUT brightness and ON/OFF. So that one lamp control by one digital input.

  KCS_A8V3_V3.24.5.zip (Size: 1.2 MB / Downloads: 346)

  KCS_A2V3_V3.24.5.zip (Size: 1.17 MB / Downloads: 255)

  KCS_A6V3_V3.24.5.zip (Size: 1.14 MB / Downloads: 335)

  KCS_A16V3_V3.24.5.zip (Size: 1.21 MB / Downloads: 282)

  KCS_A32PRO_V3.24.5.zip (Size: 1.18 MB / Downloads: 299)

  KCS_AG8_V3.24.5.zip (Size: 1.16 MB / Downloads: 248)

  KCS_AIO_HYBRID_V3.24.5.zip (Size: 1.39 MB / Downloads: 309)

  KCS_ALR_V3.24.5.zip (Size: 1.15 MB / Downloads: 240)

  KCS_B4_V3.24.5.zip (Size: 1.2 MB / Downloads: 250)

  KCS_B4M_V3.24.5.zip (Size: 1.2 MB / Downloads: 297)

  KCS_B8_V3.24.5.zip (Size: 1.21 MB / Downloads: 297)

  KCS_B8M_V3.24.5.zip (Size: 1.21 MB / Downloads: 241)

  KCS_B16_V3.24.5.zip (Size: 1.2 MB / Downloads: 255)

  KCS_B16M_V3.24.5.zip (Size: 1.2 MB / Downloads: 296)

  KCS_B24_V3.24.5.zip (Size: 1.21 MB / Downloads: 274)

  KCS_B24M_V3.24.5.zip (Size: 1.21 MB / Downloads: 231)

  KCS_B32M_V3.24.5.zip (Size: 1.21 MB / Downloads: 235)

  KCS_DM4_V3.24.5.zip (Size: 1.21 MB / Downloads: 236)

  KCS_DM8_V3.24.5.zip (Size: 1.21 MB / Downloads: 318)

  KCS_DM16_V3.24.5.zip (Size: 1.18 MB / Downloads: 245)

  KCS_DM32_V3.24.5.zip (Size: 1.21 MB / Downloads: 252)

  KCS_F4_V3.24.5.zip (Size: 1.2 MB / Downloads: 257)

  KCS_F8_V3.24.5.zip (Size: 1.2 MB / Downloads: 235)

  KCS_F16_V3.24.5.zip (Size: 1.21 MB / Downloads: 259)

  KCS_F24_V3.24.5.zip (Size: 1.21 MB / Downloads: 280)

  KCS_F32_V3.24.5.zip (Size: 1.21 MB / Downloads: 244)

  KCS_G1_V3.24.5.zip (Size: 1.17 MB / Downloads: 298)

  KCS_KC_TA_V3.24.5.zip (Size: 1.16 MB / Downloads: 268)

  KCS_N10_V3.24.5.zip (Size: 1.07 MB / Downloads: 302)

  KCS_N20_V3.24.5.zip (Size: 1.07 MB / Downloads: 279)

  KCS_N30_V3.24.5.zip (Size: 1.07 MB / Downloads: 239)

  KCS_N60_V3.24.5.zip (Size: 1.09 MB / Downloads: 242)

  KCS_T16M_V3.24.5.zip (Size: 1.15 MB / Downloads: 236)

  KCS_T32M_V3.24.5.zip (Size: 1.17 MB / Downloads: 241)

  KCS_T64M_V3.24.5.zip (Size: 1.17 MB / Downloads: 282)

  KCS_T128M_V3.24.5.zip (Size: 1.18 MB / Downloads: 233)

  KCS_TR_V3.24.5.zip (Size: 1.13 MB / Downloads: 288)

  KCS_Z1_V3.24.5.zip (Size: 1.3 MB / Downloads: 263)

KC868-A16-V3.1 MODBUS RS485

Mon, 20 Apr 2026 18:32:34 +0800

this command work ok:
01 05 00 00 ff 00 8c 3a

but read coil report 07 coils enabled (shifted)

coil write from 08 coil and above does nothing: no LEDs, no affection on coils read

[Bug] A16v3 (v3.24.3) - Write Single Coil (FC05) Modbus standard violation

Mon, 20 Apr 2026 18:06:12 +0800

- Firmware Version: v3.24.3 (Build Date: Apr 12 2026)
- Hardware: A16v3
- Communication: Modbus RTU (RS485)

## Description:

I have encountered an issue regarding the implementation of Modbus Function Code 05 (Write Single Coil).

According to the official Modbus specification, to turn a coil ON, the data field must send FF00. To turn it OFF, the data field must send 0000. However, my A16v3 running firmware v3.24.3 does not seem to accept this standard.

## Observed Behavior:

The device expects (or only responds to) a "bit-encoded" state in the data field. For example:

Instead of FF 00, the device expects 01 00 (or similar bit masks) to activate the coil.

Instead of 00 00, it expects 00 00.

This behavior is non-standard. It appears the firmware is treating FC05 as if it were a "Mask" or mimicking the data structure of FC15 (Write Multiple Coils) rather than the strict FF00/0000 pattern required by the Modbus standard.

## Steps to Reproduce:

Establish Modbus TCP connection to the device (IP: 10.130.1.43).

Send standard Modbus FC05 frame to any valid coil address (e.g., 00 01):

Standard ON: [Slave ID] 05 [Addr High] [Addr Low] FF 00 [CRC]

Standard OFF: [Slave ID] 05 [Addr High] [Addr Low] 00 00 [CRC]

Observe that the coil state does not change (or the device returns an exception/incorrect response).

Send a modified frame using bit-encoded data (e.g., 01 00 for ON).

Observe that the coil toggles successfully.

## Expected Behavior:

The device should strictly adhere to the Modbus specification for Function Code 05, using FF00 for ON and 0000 for OFF.

## Questions / Requests:

- Is this a known issue in v3.24.3?

-Is there a configuration flag in the Web UI (e.g., "Strict Mode," "Legacy Mode," or "Compatibility Mode") that can switch the device to standard Modbus compliance?

-If not, is this planned to be fixed in a future firmware update?

## Additional Context:

Software Version: v3.24.3

Build Date: Apr 12 2026

I am using a standard Modbus master software (PLC/SCADA) that strictly adheres to the FF00 standard, so I cannot easily modify the protocol structure on the master side.

"KCS" v3.24.3 firmware BIN file download

Mon, 13 Apr 2026 11:02:36 +0800

v3.24.3 improvement:
1: add debounce capability to digital input ports.
2: support wiegand protocol for access control panel.
3: add RS485 bridge protocol, support TR RS485 device digital input and sensor feedback for MASTER controller's mqtt message.
4: fixed bug when IF conditon have multi DI.

  KCS_A2V3_V3.24.3.zip (Size: 1.17 MB / Downloads: 290)

  KCS_A6V3_V3.24.3.zip (Size: 1.14 MB / Downloads: 315)

  KCS_A8V3_V3.24.3.zip (Size: 1.2 MB / Downloads: 275)

  KCS_A16V3_V3.24.3.zip (Size: 1.21 MB / Downloads: 348)

  KCS_A32PRO_V3.24.3.zip (Size: 1.18 MB / Downloads: 250)

  KCS_AG8_V3.24.3.zip (Size: 1.16 MB / Downloads: 253)

  KCS_AIO_HYBRID_V3.24.3.zip (Size: 1.39 MB / Downloads: 312)

  KCS_ALR_V3.24.3.zip (Size: 1.15 MB / Downloads: 291)

  KCS_B4_V3.24.3.zip (Size: 1.2 MB / Downloads: 250)

  KCS_B4M_V3.24.3.zip (Size: 1.2 MB / Downloads: 292)

  KCS_B8_V3.24.3.zip (Size: 1.2 MB / Downloads: 292)

  KCS_B8M_V3.24.3.zip (Size: 1.2 MB / Downloads: 294)

  KCS_B16_V3.24.3.zip (Size: 1.2 MB / Downloads: 319)

  KCS_B16M_V3.24.3.zip (Size: 1.2 MB / Downloads: 303)

  KCS_B24_V3.24.3.zip (Size: 1.2 MB / Downloads: 297)

  KCS_B24M_V3.24.3.zip (Size: 1.2 MB / Downloads: 247)

  KCS_B32M_V3.24.3.zip (Size: 1.2 MB / Downloads: 249)

  KCS_DM4_V3.24.3.zip (Size: 1.2 MB / Downloads: 279)

  KCS_DM8_V3.24.3.zip (Size: 1.2 MB / Downloads: 242)

  KCS_DM16_V3.24.3.zip (Size: 1.17 MB / Downloads: 249)

  KCS_DM32_V3.24.3.zip (Size: 1.21 MB / Downloads: 250)

  KCS_F4_V3.24.3.zip (Size: 1.2 MB / Downloads: 249)

  KCS_F8_V3.24.3.zip (Size: 1.2 MB / Downloads: 227)

  KCS_F16_V3.24.3.zip (Size: 1.21 MB / Downloads: 246)

  KCS_F24_V3.24.3.zip (Size: 1.21 MB / Downloads: 294)

  KCS_F32_V3.24.3.zip (Size: 1.21 MB / Downloads: 300)

  KCS_G1_V3.24.3.zip (Size: 1.16 MB / Downloads: 273)

  KCS_KC_TA_V3.24.3.zip (Size: 1.16 MB / Downloads: 248)

  KCS_N10_V3.24.3.zip (Size: 1.07 MB / Downloads: 265)

  KCS_N20_V3.24.3.zip (Size: 1.07 MB / Downloads: 302)

  KCS_N30_V3.24.3.zip (Size: 1.07 MB / Downloads: 254)

  KCS_N60_V3.24.3.zip (Size: 1.08 MB / Downloads: 251)

  KCS_T16M_V3.24.3.zip (Size: 1.15 MB / Downloads: 242)

  KCS_T32M_V3.24.3.zip (Size: 1.17 MB / Downloads: 236)

  KCS_T64M_V3.24.3.zip (Size: 1.17 MB / Downloads: 307)

  KCS_T128M_V3.24.3.zip (Size: 1.17 MB / Downloads: 235)

  KCS_TR_V3.24.3.zip (Size: 1.13 MB / Downloads: 277)

  KCS_Z1_V3.24.3.zip (Size: 1.3 MB / Downloads: 277)