<![CDATA[Smart Home Automation Forum - Extender module]]> https://www.kincony.com/forum/ Sun, 05 Apr 2026 23:29:37 +0000 MyBB <![CDATA[smoke sensor user manual]]> https://www.kincony.com/forum/showthread.php?tid=8955 Mon, 19 Jan 2026 16:34:13 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8955
.pdf   smoke_sensor_user_manual.pdf (Size: 2.56 MB / Downloads: 108) ]]>
.pdf   smoke_sensor_user_manual.pdf (Size: 2.56 MB / Downloads: 108) ]]> <![CDATA[gas sensor user manual]]> https://www.kincony.com/forum/showthread.php?tid=8954 Mon, 19 Jan 2026 16:32:19 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8954
.pdf   gas-sensor-manual.pdf (Size: 1.84 MB / Downloads: 88) ]]>
.pdf   gas-sensor-manual.pdf (Size: 1.84 MB / Downloads: 88) ]]> <![CDATA[temperature humidity sensor convertor – TR ESP32 Pin define]]> https://www.kincony.com/forum/showthread.php?tid=8741 Sat, 15 Nov 2025 07:58:27 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8741
SDA:GPIO10
SCL:GPIO9

24C02 EPROM i2c address: 0x50

-----------------
1-wire GPIOs (with pull-up resistance on PCB):
1-wire-1:GPIO17
1-wire-2:GPIO16
1-wire-3:GPIO15
1-wire-4:GPIO7
-----------------
free GPIOs (without pull-up resistance on PCB):
GPIO4  GPIO1
GPIO5  GPIO2
GPIO6
GPIO18
GPIO8  GPIO42
GPIO3  GPIO41
GPIO21  GPIO40
GPIO47  GPIO39
GPIO48  GPIO38
-----------------

RS485:
RXD:GPIO14
TXD:GPIO13]]>
SDA:GPIO10
SCL:GPIO9

24C02 EPROM i2c address: 0x50

-----------------
1-wire GPIOs (with pull-up resistance on PCB):
1-wire-1:GPIO17
1-wire-2:GPIO16
1-wire-3:GPIO15
1-wire-4:GPIO7
-----------------
free GPIOs (without pull-up resistance on PCB):
GPIO4  GPIO1
GPIO5  GPIO2
GPIO6
GPIO18
GPIO8  GPIO42
GPIO3  GPIO41
GPIO21  GPIO40
GPIO47  GPIO39
GPIO48  GPIO38
-----------------

RS485:
RXD:GPIO14
TXD:GPIO13]]> <![CDATA[temperature humidity sensor convertor – TR RS485 Modbus protocol]]> https://www.kincony.com/forum/showthread.php?tid=8686 Tue, 28 Oct 2025 08:42:35 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8686
Code:
================================================================================
  RS485 TEMPERATURE & HUMIDITY SENSOR PROTOCOL SPECIFICATION
================================================================================

Communication: RS485 (Modbus-based Custom Protocol)

================================================================================
1. OVERVIEW
================================================================================

This document describes the custom Modbus-based protocol for communicating with
temperature and humidity sensors over RS485. The protocol supports up to 32
sensors per slave device, allowing for distributed sensor networks.

Key Features:
- Modbus RTU framing with CRC16
- Custom function code for sensor data reading
- Support for 1-32 sensors per slave address
- Temperature and humidity readings with 0.1 degree/percent precision
- Explicit encoding for unavailable sensor data

================================================================================
2. PROTOCOL PARAMETERS
================================================================================

Modbus Function Code: 0x0A (READ_SENSOR_DATA)
Baud Rate: As configured by RS485 driver
Data Format: 8N1 (8 data bits, no parity, 1 stop bit)
CRC: Modbus CRC16 (polynomial 0xA001)

Sensor Address Range: 1-32 (0x01-0x20)
Slave Address Range: 1-247 (0x01-0xF7, standard Modbus range)

================================================================================
3. REQUEST FORMAT
================================================================================

The master sends a request to read sensor data from a specific sensor.

Request Frame Structure:
┌──────────────┬──────────────┬────────────────┬────────────────┬──────────┐
│ Byte Index   │ 0            │ 1              │ 2              │ 3        │
├──────────────┼──────────────┼────────────────┼────────────────┼──────────┤
│ Field        │ Slave Addr   │ Function Code  │ Sensor ID High │ Sensor ID│
│              │              │                │                │ Low      │
├──────────────┼──────────────┼────────────────┼────────────────┼──────────┤
│ Value        │ 0x01-0xF7    │ 0x0A           │ 0x00           │ 0x01-0x20│
└──────────────┴──────────────┴────────────────┴────────────────┴──────────┘
┌──────────────┬──────────────┐
│ Byte Index   │ 4-5          │
├──────────────┼──────────────┤
│ Field        │ CRC16        │
├──────────────┼──────────────┤
│ Value        │ Lo-Hi bytes  │
└──────────────┴──────────────┘

Total Length: 6 bytes

Field Descriptions:
- Slave Address: The Modbus slave device address (1-247)
- Function Code: Always 0x0A for sensor data reading
- Sensor ID High: Always 0x00 (reserved for future use)
- Sensor ID Low: Sensor number (1-32) on the slave device
- CRC16: Modbus CRC16 checksum (low byte first, then high byte)

Example Request (Read sensor 1 from slave 0x01):
  Request: 01 0A 00 01 [CRC_LOW] [CRC_HIGH]

================================================================================
4. RESPONSE FORMAT
================================================================================

The slave responds with temperature and humidity data for the requested sensor.

Response Frame Structure:
┌─────────────┬────────────┬──────────────┬────────────┬──────────────────┐
│ Byte Index  │ 0          │ 1            │ 2          │ 3-7              │
├─────────────┼────────────┼──────────────┼────────────┼──────────────────┤
│ Field       │ Slave Addr │ Function Code│ Byte Count │ Temperature Data │
│             │            │              │            │ (5 bytes)        │
├─────────────┼────────────┼──────────────┼────────────┼──────────────────┤
│ Value       │ 0x01-0xF7  │ 0x0A         │ 0x0A (10)  │ See section 5    │
└─────────────┴────────────┴──────────────┴────────────┴──────────────────┘
┌─────────────┬──────────────────┬──────────┐
│ Byte Index  │ 8-12             │ 13-14    │
├─────────────┼──────────────────┼──────────┤
│ Field       │ Humidity Data    │ CRC16    │
│             │ (5 bytes)        │          │
├─────────────┼──────────────────┼──────────┤
│ Value       │ See section 5    │ Lo-Hi    │
└─────────────┴──────────────────┴──────────┘

Total Length: 15 bytes

Field Descriptions:
- Slave Address: Echo of the slave address from request
- Function Code: Echo of 0x0A
- Byte Count: Always 0x0A (10 decimal) - 5 bytes temp + 5 bytes humidity
- Temperature Data: 5-byte encoded temperature value
- Humidity Data: 5-byte encoded humidity value
- CRC16: Modbus CRC16 checksum (low byte first, then high byte)

Minimum Valid Response Length: 14 bytes
Expected Response Length: 15 bytes (with CRC)

================================================================================
5. DATA ENCODING
================================================================================

Both temperature and humidity use the same 5-byte encoding format:

5.1 Data Structure
┌──────────────┬──────────┬──────────┬──────────┬──────────┬──────────┐
│ Byte Index   │ 0        │ 1        │ 2        │ 3        │ 4        │
├──────────────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ Field        │ Sign     │ Hundreds │ Tens     │ Ones     │ Decimal  │
├──────────────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ Value Range  │ 0 or 1   │ 0-9      │ 0-9      │ 0-9      │ 0-9      │
└──────────────┴──────────┴──────────┴──────────┴──────────┴──────────┘

5.2 Field Definitions
- Sign: 0 = positive, 1 = negative
- Hundreds: Hundreds digit (0-9)
- Tens: Tens digit (0-9)
- Ones: Ones digit (0-9)
- Decimal: First decimal place (0-9, represents 0.0-0.9)

5.3 Value Calculation
Final Value = Sign × (Hundreds × 100 + Tens × 10 + Ones + Decimal × 0.1)

Where Sign is: +1 if sign byte is 0, -1 if sign byte is 1

5.4 Data Not Available Indicator
When sensor data is not available or invalid, ALL 5 bytes are set to 0xFF:
  0xFF 0xFF 0xFF 0xFF 0xFF

The receiver should check if any byte is NOT 0xFF to determine if data is valid.
If all bytes are 0xFF, the data should be treated as unavailable (-100.0 default).

5.5 Encoding Examples

Example 1: Temperature = 25.3°C
  Bytes: 00 00 02 05 03
  Calculation: +(0×100 + 2×10 + 5 + 3×0.1) = +25.3

Example 2: Temperature = -5.7°C
  Bytes: 01 00 00 05 07
  Calculation: -(0×100 + 0×10 + 5 + 7×0.1) = -5.7

Example 3: Humidity = 65.0%
  Bytes: 00 00 06 05 00
  Calculation: +(0×100 + 6×10 + 5 + 0×0.1) = +65.0

Example 4: Data not available
  Bytes: FF FF FF FF FF
  Interpretation: No valid data (-100.0 default value)

Example 5: Temperature = 100.5°C
  Bytes: 00 01 00 00 05
  Calculation: +(1×100 + 0×10 + 0 + 5×0.1) = +100.5

================================================================================
6. COMPLETE TRANSACTION EXAMPLE
================================================================================

Master requests data from sensor 1 on slave 0x01:

REQUEST (6 bytes):
  01 0A 00 01 XX XX
  └─ Slave address: 0x01
     └─ Function code: 0x0A
        └─ Sensor ID high: 0x00
           └─ Sensor ID low: 0x01
              └─ CRC16 (calculated over bytes 0-3)

RESPONSE (15 bytes):
  01 0A 0A 00 00 02 05 03 00 00 06 05 00 XX XX
  └─ Slave address: 0x01
     └─ Function code: 0x0A
        └─ Byte count: 0x0A (10 bytes)
           └─ Temperature: 00 00 02 05 03 (+25.3°C)
                          └─ Humidity: 00 00 06 05 00 (+65.0%)
                                      └─ CRC16

Decoded Result:
  Temperature: +25.3°C
  Humidity: +65.0%

================================================================================
7. ERROR HANDLING
================================================================================

7.1 Invalid Response Conditions
The receiver should reject responses in the following cases:

1. Slave address mismatch: Response slave address ≠ request slave address
2. Function code mismatch: Response function code ≠ 0x0A
3. Insufficient length: Response length < 14 bytes
4. Invalid byte count: Byte count field ≠ 0x0A (10)
5. CRC error: Calculated CRC ≠ received CRC

7.2 Data Validation
After successful frame validation, check each sensor value:

- If all 5 bytes are 0xFF: Data not available, use default (-100.0)
- If at least one byte is NOT 0xFF: Decode the value normally
- Value range checking should be performed at application level

7.3 Timeout Handling
Recommended timeout: 50-100ms after sending request
If no response within timeout: Retry or report communication error

7.4 Modbus Exception Responses
Standard Modbus exception codes may be returned:
  [Slave Addr] [0x8A] [Exception Code] [CRC]

Where 0x8A = 0x0A + 0x80 (function code with MSB set)

Common exception codes:
- 0x01: Illegal Function (function code not supported)
- 0x02: Illegal Data Address (sensor address out of range)
- 0x03: Illegal Data Value (invalid request parameters)
- 0x04: Slave Device Failure (sensor read error)

================================================================================
8. IMPLEMENTATION NOTES
================================================================================

8.1 Multi-Sensor Support
- A single slave device can support 1-32 sensors (addresses 1-32)
- Each sensor must be initialized before reading
- Sensor addresses are independent of slave addresses
- Multiple slaves can exist on the same RS485 bus

8.2 Polling Frequency
- Recommended polling interval: 1-5 seconds per sensor
- Add delays between consecutive requests to prevent bus collisions
- Minimum delay between requests: 50ms

8.3 Bus Configuration
- RS485 requires proper termination resistors (120Ω)
- Maximum bus length depends on baud rate (typically 1200m at 9600 baud)
- Maximum number of devices: 32-247 (depending on hardware)

8.4 Data Caching
- The master typically caches the last received values
- Cached values are updated when new responses arrive
- Applications read from cache rather than directly from bus

8.5 CRC Calculation
- Use standard Modbus CRC16 algorithm
- Polynomial: 0xA001 (reversed 0x8005)
- Initial value: 0xFFFF
- CRC bytes transmitted: low byte first, then high byte

================================================================================
9. PROTOCOL LIMITATIONS
================================================================================

- Maximum sensors per slave: 32
- Temperature/humidity precision: 0.1 units
- Maximum value range: -999.9 to +999.9
- No timestamp or sensor identification in response
- No batch reading (must query each sensor individually)
- No sensor configuration commands in this protocol version

================================================================================
END OF SPECIFICATION
================================================================================
]]>
Code:
================================================================================
  RS485 TEMPERATURE & HUMIDITY SENSOR PROTOCOL SPECIFICATION
================================================================================

Communication: RS485 (Modbus-based Custom Protocol)

================================================================================
1. OVERVIEW
================================================================================

This document describes the custom Modbus-based protocol for communicating with
temperature and humidity sensors over RS485. The protocol supports up to 32
sensors per slave device, allowing for distributed sensor networks.

Key Features:
- Modbus RTU framing with CRC16
- Custom function code for sensor data reading
- Support for 1-32 sensors per slave address
- Temperature and humidity readings with 0.1 degree/percent precision
- Explicit encoding for unavailable sensor data

================================================================================
2. PROTOCOL PARAMETERS
================================================================================

Modbus Function Code: 0x0A (READ_SENSOR_DATA)
Baud Rate: As configured by RS485 driver
Data Format: 8N1 (8 data bits, no parity, 1 stop bit)
CRC: Modbus CRC16 (polynomial 0xA001)

Sensor Address Range: 1-32 (0x01-0x20)
Slave Address Range: 1-247 (0x01-0xF7, standard Modbus range)

================================================================================
3. REQUEST FORMAT
================================================================================

The master sends a request to read sensor data from a specific sensor.

Request Frame Structure:
┌──────────────┬──────────────┬────────────────┬────────────────┬──────────┐
│ Byte Index   │ 0            │ 1              │ 2              │ 3        │
├──────────────┼──────────────┼────────────────┼────────────────┼──────────┤
│ Field        │ Slave Addr   │ Function Code  │ Sensor ID High │ Sensor ID│
│              │              │                │                │ Low      │
├──────────────┼──────────────┼────────────────┼────────────────┼──────────┤
│ Value        │ 0x01-0xF7    │ 0x0A           │ 0x00           │ 0x01-0x20│
└──────────────┴──────────────┴────────────────┴────────────────┴──────────┘
┌──────────────┬──────────────┐
│ Byte Index   │ 4-5          │
├──────────────┼──────────────┤
│ Field        │ CRC16        │
├──────────────┼──────────────┤
│ Value        │ Lo-Hi bytes  │
└──────────────┴──────────────┘

Total Length: 6 bytes

Field Descriptions:
- Slave Address: The Modbus slave device address (1-247)
- Function Code: Always 0x0A for sensor data reading
- Sensor ID High: Always 0x00 (reserved for future use)
- Sensor ID Low: Sensor number (1-32) on the slave device
- CRC16: Modbus CRC16 checksum (low byte first, then high byte)

Example Request (Read sensor 1 from slave 0x01):
  Request: 01 0A 00 01 [CRC_LOW] [CRC_HIGH]

================================================================================
4. RESPONSE FORMAT
================================================================================

The slave responds with temperature and humidity data for the requested sensor.

Response Frame Structure:
┌─────────────┬────────────┬──────────────┬────────────┬──────────────────┐
│ Byte Index  │ 0          │ 1            │ 2          │ 3-7              │
├─────────────┼────────────┼──────────────┼────────────┼──────────────────┤
│ Field       │ Slave Addr │ Function Code│ Byte Count │ Temperature Data │
│             │            │              │            │ (5 bytes)        │
├─────────────┼────────────┼──────────────┼────────────┼──────────────────┤
│ Value       │ 0x01-0xF7  │ 0x0A         │ 0x0A (10)  │ See section 5    │
└─────────────┴────────────┴──────────────┴────────────┴──────────────────┘
┌─────────────┬──────────────────┬──────────┐
│ Byte Index  │ 8-12             │ 13-14    │
├─────────────┼──────────────────┼──────────┤
│ Field       │ Humidity Data    │ CRC16    │
│             │ (5 bytes)        │          │
├─────────────┼──────────────────┼──────────┤
│ Value       │ See section 5    │ Lo-Hi    │
└─────────────┴──────────────────┴──────────┘

Total Length: 15 bytes

Field Descriptions:
- Slave Address: Echo of the slave address from request
- Function Code: Echo of 0x0A
- Byte Count: Always 0x0A (10 decimal) - 5 bytes temp + 5 bytes humidity
- Temperature Data: 5-byte encoded temperature value
- Humidity Data: 5-byte encoded humidity value
- CRC16: Modbus CRC16 checksum (low byte first, then high byte)

Minimum Valid Response Length: 14 bytes
Expected Response Length: 15 bytes (with CRC)

================================================================================
5. DATA ENCODING
================================================================================

Both temperature and humidity use the same 5-byte encoding format:

5.1 Data Structure
┌──────────────┬──────────┬──────────┬──────────┬──────────┬──────────┐
│ Byte Index   │ 0        │ 1        │ 2        │ 3        │ 4        │
├──────────────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ Field        │ Sign     │ Hundreds │ Tens     │ Ones     │ Decimal  │
├──────────────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ Value Range  │ 0 or 1   │ 0-9      │ 0-9      │ 0-9      │ 0-9      │
└──────────────┴──────────┴──────────┴──────────┴──────────┴──────────┘

5.2 Field Definitions
- Sign: 0 = positive, 1 = negative
- Hundreds: Hundreds digit (0-9)
- Tens: Tens digit (0-9)
- Ones: Ones digit (0-9)
- Decimal: First decimal place (0-9, represents 0.0-0.9)

5.3 Value Calculation
Final Value = Sign × (Hundreds × 100 + Tens × 10 + Ones + Decimal × 0.1)

Where Sign is: +1 if sign byte is 0, -1 if sign byte is 1

5.4 Data Not Available Indicator
When sensor data is not available or invalid, ALL 5 bytes are set to 0xFF:
  0xFF 0xFF 0xFF 0xFF 0xFF

The receiver should check if any byte is NOT 0xFF to determine if data is valid.
If all bytes are 0xFF, the data should be treated as unavailable (-100.0 default).

5.5 Encoding Examples

Example 1: Temperature = 25.3°C
  Bytes: 00 00 02 05 03
  Calculation: +(0×100 + 2×10 + 5 + 3×0.1) = +25.3

Example 2: Temperature = -5.7°C
  Bytes: 01 00 00 05 07
  Calculation: -(0×100 + 0×10 + 5 + 7×0.1) = -5.7

Example 3: Humidity = 65.0%
  Bytes: 00 00 06 05 00
  Calculation: +(0×100 + 6×10 + 5 + 0×0.1) = +65.0

Example 4: Data not available
  Bytes: FF FF FF FF FF
  Interpretation: No valid data (-100.0 default value)

Example 5: Temperature = 100.5°C
  Bytes: 00 01 00 00 05
  Calculation: +(1×100 + 0×10 + 0 + 5×0.1) = +100.5

================================================================================
6. COMPLETE TRANSACTION EXAMPLE
================================================================================

Master requests data from sensor 1 on slave 0x01:

REQUEST (6 bytes):
  01 0A 00 01 XX XX
  └─ Slave address: 0x01
     └─ Function code: 0x0A
        └─ Sensor ID high: 0x00
           └─ Sensor ID low: 0x01
              └─ CRC16 (calculated over bytes 0-3)

RESPONSE (15 bytes):
  01 0A 0A 00 00 02 05 03 00 00 06 05 00 XX XX
  └─ Slave address: 0x01
     └─ Function code: 0x0A
        └─ Byte count: 0x0A (10 bytes)
           └─ Temperature: 00 00 02 05 03 (+25.3°C)
                          └─ Humidity: 00 00 06 05 00 (+65.0%)
                                      └─ CRC16

Decoded Result:
  Temperature: +25.3°C
  Humidity: +65.0%

================================================================================
7. ERROR HANDLING
================================================================================

7.1 Invalid Response Conditions
The receiver should reject responses in the following cases:

1. Slave address mismatch: Response slave address ≠ request slave address
2. Function code mismatch: Response function code ≠ 0x0A
3. Insufficient length: Response length < 14 bytes
4. Invalid byte count: Byte count field ≠ 0x0A (10)
5. CRC error: Calculated CRC ≠ received CRC

7.2 Data Validation
After successful frame validation, check each sensor value:

- If all 5 bytes are 0xFF: Data not available, use default (-100.0)
- If at least one byte is NOT 0xFF: Decode the value normally
- Value range checking should be performed at application level

7.3 Timeout Handling
Recommended timeout: 50-100ms after sending request
If no response within timeout: Retry or report communication error

7.4 Modbus Exception Responses
Standard Modbus exception codes may be returned:
  [Slave Addr] [0x8A] [Exception Code] [CRC]

Where 0x8A = 0x0A + 0x80 (function code with MSB set)

Common exception codes:
- 0x01: Illegal Function (function code not supported)
- 0x02: Illegal Data Address (sensor address out of range)
- 0x03: Illegal Data Value (invalid request parameters)
- 0x04: Slave Device Failure (sensor read error)

================================================================================
8. IMPLEMENTATION NOTES
================================================================================

8.1 Multi-Sensor Support
- A single slave device can support 1-32 sensors (addresses 1-32)
- Each sensor must be initialized before reading
- Sensor addresses are independent of slave addresses
- Multiple slaves can exist on the same RS485 bus

8.2 Polling Frequency
- Recommended polling interval: 1-5 seconds per sensor
- Add delays between consecutive requests to prevent bus collisions
- Minimum delay between requests: 50ms

8.3 Bus Configuration
- RS485 requires proper termination resistors (120Ω)
- Maximum bus length depends on baud rate (typically 1200m at 9600 baud)
- Maximum number of devices: 32-247 (depending on hardware)

8.4 Data Caching
- The master typically caches the last received values
- Cached values are updated when new responses arrive
- Applications read from cache rather than directly from bus

8.5 CRC Calculation
- Use standard Modbus CRC16 algorithm
- Polynomial: 0xA001 (reversed 0x8005)
- Initial value: 0xFFFF
- CRC bytes transmitted: low byte first, then high byte

================================================================================
9. PROTOCOL LIMITATIONS
================================================================================

- Maximum sensors per slave: 32
- Temperature/humidity precision: 0.1 units
- Maximum value range: -999.9 to +999.9
- No timestamp or sensor identification in response
- No batch reading (must query each sensor individually)
- No sensor configuration commands in this protocol version

================================================================================
END OF SPECIFICATION
================================================================================
]]> <![CDATA[how to use HAv2 RS485 switch adapter work with E16S relay board]]> https://www.kincony.com/forum/showthread.php?tid=8119 Thu, 29 May 2025 10:13:51 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8119
.jpg   E16S-HAv2-1.JPG (Size: 250.08 KB / Downloads: 433)
1. download KCS v2 firmware to KC868-E16S board, enable RS485 with "MODBUS-HA" mode.

.png   KCS-setting.png (Size: 52.56 KB / Downloads: 501)
2. use HAv2 PC config tool set the button action.

.png   HAv2-pc-software.png (Size: 225.68 KB / Downloads: 436)
3. connect HAv2 with wall switch panel's K1,K2,K3,K4,K5,K6,KCOM to HAv2 board (use for buttons). D1,D2,D3,D4,D5,D6,DC12V to HAv2 board (use for LED state feedback) 

.jpg   E16S-HAv2-3.JPG (Size: 144.56 KB / Downloads: 429)
4. when press switch panel button or control by KCS monitor webpage or tuya app, the switch LED state will be updated.

.jpg   E16S-HAv2-2.JPG (Size: 279.87 KB / Downloads: 449)

.jpg   E16S-HAv2-4.JPG (Size: 218.04 KB / Downloads: 423)

.jpg   E16S-HAv2-5.JPG (Size: 127.19 KB / Downloads: 430)

this just demo for 6 relay, if you want many more switch panel control for 16 channel relay. just add switch panel and HAv2 module, parallel connection with RS485 port on KC868-E16S.

]]>
.jpg   E16S-HAv2-1.JPG (Size: 250.08 KB / Downloads: 433)
1. download KCS v2 firmware to KC868-E16S board, enable RS485 with "MODBUS-HA" mode.

.png   KCS-setting.png (Size: 52.56 KB / Downloads: 501)
2. use HAv2 PC config tool set the button action.

.png   HAv2-pc-software.png (Size: 225.68 KB / Downloads: 436)
3. connect HAv2 with wall switch panel's K1,K2,K3,K4,K5,K6,KCOM to HAv2 board (use for buttons). D1,D2,D3,D4,D5,D6,DC12V to HAv2 board (use for LED state feedback) 

.jpg   E16S-HAv2-3.JPG (Size: 144.56 KB / Downloads: 429)
4. when press switch panel button or control by KCS monitor webpage or tuya app, the switch LED state will be updated.

.jpg   E16S-HAv2-2.JPG (Size: 279.87 KB / Downloads: 449)

.jpg   E16S-HAv2-4.JPG (Size: 218.04 KB / Downloads: 423)

.jpg   E16S-HAv2-5.JPG (Size: 127.19 KB / Downloads: 430)

this just demo for 6 relay, if you want many more switch panel control for 16 channel relay. just add switch panel and HAv2 module, parallel connection with RS485 port on KC868-E16S.

]]> <![CDATA[smoke sensor pin define]]> https://www.kincony.com/forum/showthread.php?tid=8077 Thu, 15 May 2025 08:22:59 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=8077 RED: DC12V+
BLACK: GND
WHITE: COM
ORANGE: Normal Open
YELLOW: Normal Close

.jpg   smoke-sensor-1.jpg (Size: 263.03 KB / Downloads: 366)

.jpg   smoke-sensor-2.jpg (Size: 118.24 KB / Downloads: 390)

.jpg   smoke-sensor-3.jpg (Size: 234 KB / Downloads: 369) ]]> RED: DC12V+
BLACK: GND
WHITE: COM
ORANGE: Normal Open
YELLOW: Normal Close

.jpg   smoke-sensor-1.jpg (Size: 263.03 KB / Downloads: 366)

.jpg   smoke-sensor-2.jpg (Size: 118.24 KB / Downloads: 390)

.jpg   smoke-sensor-3.jpg (Size: 234 KB / Downloads: 369) ]]> <![CDATA[Presence Sensor Remote Control User Manual]]> https://www.kincony.com/forum/showthread.php?tid=7823 Tue, 18 Mar 2025 08:39:35 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=7823
.pdf   Presence-Sensor-Remote-Control-User-Manual.pdf (Size: 558.23 KB / Downloads: 481) ]]>
.pdf   Presence-Sensor-Remote-Control-User-Manual.pdf (Size: 558.23 KB / Downloads: 481) ]]> <![CDATA[Issues with KinCony ESP32-S3-WROOM-1U N16R8 Core Development Board]]> https://www.kincony.com/forum/showthread.php?tid=7737 Fri, 28 Feb 2025 00:32:54 +0800 dammyr7a]]> https://www.kincony.com/forum/showthread.php?tid=7737
I am having issues with programming this module in arduino. 
1. need possibly a demo code to get the ethernet to work and how to work with its inbuilt adc, 
2.Also, the demo code in arduinoide for other features such as rs485 and co would be good as well. 
3. Can i connect a display screen to the socket for the 4g modemand hope i canalso use the port for sd card module for dat logging purposes. 

Pleas note, number one is urgent and most important to me. 
thanks
Dammy]]>
I am having issues with programming this module in arduino. 
1. need possibly a demo code to get the ethernet to work and how to work with its inbuilt adc, 
2.Also, the demo code in arduinoide for other features such as rs485 and co would be good as well. 
3. Can i connect a display screen to the socket for the 4g modemand hope i canalso use the port for sd card module for dat logging purposes. 

Pleas note, number one is urgent and most important to me. 
thanks
Dammy]]> <![CDATA[KinCony TS Tiny sensor PC software and modbus protocol]]> https://www.kincony.com/forum/showthread.php?tid=7428 Tue, 21 Jan 2025 08:40:58 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=7428
A. input register function:

temperature : 16bit unsigned integer register
humidity: 16bit unsigned integer register

address    function
0000H        temperature value
            unit: ℃
            fixed 1 decimal
            (1) >0℃: register data<10000
                          for example: register value=250, actual temperature: 250*0.1=25℃
            (2) <0℃: register data>=10000
                          for example: register value=10250, actual temperature: -1*(10250-10000)*0.1=25℃
------------------------------------
0001H        humidity value
            unit: %RH
            fixed 1 decimal
                          for example: register value=500, actual humidity: 500*0.1=50(%RH)
------------------------------------
0002H        temperature value
0003H        unit: ℃  decode: 32bit float data
------------------------------------
0004H        humidity value
0005H        unit: %RH  decode: 32bit float data


B. Hold register function:
The contents of the register are saved when power is turned off. The holding register is a readable and writable register. The value in each register is a 16-bit unsigned integer.

address    function
0000H        temperature value
            unit: ℃
            fixed 1 decimal
            (1) >0℃: register data<10000
                          for example: register value=250, actual temperature: 250*0.1=25℃
            (2) <0℃: register data>=10000
                          for example: register value=10250, actual temperature: -1*(10250-10000)*0.1=25℃
------------------------------------
0001H        humidity value
            unit: %RH
            fixed 1 decimal
                          for example: register value=500, actual humidity: 500*0.1=50(%RH)
------------------------------------
0002H        temperature value
0003H        unit: ℃  decode: 32bit float data
------------------------------------
0004H        humidity value
0005H        unit: %RH  decode: 32bit float data
------------------------------------
000AH        RS485 bus address(1-255), default:1 
            Note: This parameter is saved after power-off and will take effect after power-on again after modification.
------------------------------------
000BH        Baud rate setting:
            0:4800  1:9600(default) 2:14400 3:19200 4:38400 5:56000 6:57600 7:115200
            Note: This parameter is saved after power-off and will take effect after power-on again after modification.
------------------------------------
003DH        Parity settings
            0:None(default)  1:odd parity 2:even parity
            Note: This parameter is saved after power-off and will take effect after power-on again after modification.

modify RS485 setting command:

register:
1001：SLAVE address 1-250
1002：Baud rate: baud_arr[8] = {4800,9600,14400,19200,38400,56000,57600,115200}
1003: Parity bit: parity_arr[3] = {UART_PARITY_NONE,UART_PARITY_EVEN,UART_PARITY_ODD}


how to remember RS485 address if you forget it.
1: every time power on will output board information by RS485 (9600,8,N,1) if you forget the board's address.
2: hold on button > 2 seconds, will reset to factory setting, default RS485 address=1

KinCony TS Temperature and humidity Application download]]>
A. input register function:

temperature : 16bit unsigned integer register
humidity: 16bit unsigned integer register

address    function
0000H        temperature value
            unit: ℃
            fixed 1 decimal
            (1) >0℃: register data<10000
                          for example: register value=250, actual temperature: 250*0.1=25℃
            (2) <0℃: register data>=10000
                          for example: register value=10250, actual temperature: -1*(10250-10000)*0.1=25℃
------------------------------------
0001H        humidity value
            unit: %RH
            fixed 1 decimal
                          for example: register value=500, actual humidity: 500*0.1=50(%RH)
------------------------------------
0002H        temperature value
0003H        unit: ℃  decode: 32bit float data
------------------------------------
0004H        humidity value
0005H        unit: %RH  decode: 32bit float data


B. Hold register function:
The contents of the register are saved when power is turned off. The holding register is a readable and writable register. The value in each register is a 16-bit unsigned integer.

address    function
0000H        temperature value
            unit: ℃
            fixed 1 decimal
            (1) >0℃: register data<10000
                          for example: register value=250, actual temperature: 250*0.1=25℃
            (2) <0℃: register data>=10000
                          for example: register value=10250, actual temperature: -1*(10250-10000)*0.1=25℃
------------------------------------
0001H        humidity value
            unit: %RH
            fixed 1 decimal
                          for example: register value=500, actual humidity: 500*0.1=50(%RH)
------------------------------------
0002H        temperature value
0003H        unit: ℃  decode: 32bit float data
------------------------------------
0004H        humidity value
0005H        unit: %RH  decode: 32bit float data
------------------------------------
000AH        RS485 bus address(1-255), default:1 
            Note: This parameter is saved after power-off and will take effect after power-on again after modification.
------------------------------------
000BH        Baud rate setting:
            0:4800  1:9600(default) 2:14400 3:19200 4:38400 5:56000 6:57600 7:115200
            Note: This parameter is saved after power-off and will take effect after power-on again after modification.
------------------------------------
003DH        Parity settings
            0:None(default)  1:odd parity 2:even parity
            Note: This parameter is saved after power-off and will take effect after power-on again after modification.

modify RS485 setting command:

register:
1001：SLAVE address 1-250
1002：Baud rate: baud_arr[8] = {4800,9600,14400,19200,38400,56000,57600,115200}
1003: Parity bit: parity_arr[3] = {UART_PARITY_NONE,UART_PARITY_EVEN,UART_PARITY_ODD}


how to remember RS485 address if you forget it.
1: every time power on will output board information by RS485 (9600,8,N,1) if you forget the board's address.
2: hold on button > 2 seconds, will reset to factory setting, default RS485 address=1

KinCony TS Temperature and humidity Application download]]> <![CDATA[ESP32 S3 set up issue]]> https://www.kincony.com/forum/showthread.php?tid=7216 Fri, 13 Dec 2024 01:35:57 +0800 omarzamudio]]> https://www.kincony.com/forum/showthread.php?tid=7216 Hello,
In a previous email I mentioned that I am using the SIM 7600 module with the ESP32 S3 WROOM 1U, however I can't use the serial monitor in order to receive information (I can't see data), I would like to know if you have any advice for the ESP32 S3 set up in Arduino firmware. See my below set up in tools menu:

[Image: 0?ui=2&ik=2d79881756&attid=0.1&permmsgid...j58g7e0&zw]

I followed you recommendation with ''USB CDC On Boot'' = ENABLE, and now I have below information in the Serial Monitor:

ELF file SHA256: 587cb4fa5
E (159) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
E (167) esp_core_dump_elf: Elf write init failed!
E (172) esp_core_dump_common: Core dump write failed with error=-1
Rebooting...
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40376f0d
SPIWP:0xee
modeBig GrinIO, clock div:1
load:0x3fce2810,len:0xfdc
load:0x403c8700,len:0x4
load:0x403c8704,len:0xabc
load:0x403cb700,len:0x2d40
entry 0x403c8890
E (113) quad_psram: PSRAM ID read error: 0x00ffffff, PSRAM chip not found or not supported, or wrong PSRAM line mode
E (116) spi_flash: Detected size(8192k) smaller than the size in the binary image header(16384k). Probe failed.
assert failed: __esp_system_init_fn_init_flash startup_funcs.c:95 (flash_ret == ESP_OK)
Backtrace: 0x4037654e:0x3fceb120 0x4037c65d:0x3fceb140 0x403830bd:0x3fceb160 0x4200a903:0x3fceb290 0x4200bd8b:0x3fceb2b0 0x4200bdc5:0x3fceb2d0 0x403768f5:0x3fceb300 0x403cc974:0x3fceb340 0x403ccd39:0x3fceb380 0x403c88fd:0x3fceb4b0 0x40045c01:0x3fceb570 0x40043ab6:0x3fceb6f0 0x40034c45:0x3fceb710

I think I need to change something else in the Tool config but I'm not sure.

Thanks.]]> Hello,
In a previous email I mentioned that I am using the SIM 7600 module with the ESP32 S3 WROOM 1U, however I can't use the serial monitor in order to receive information (I can't see data), I would like to know if you have any advice for the ESP32 S3 set up in Arduino firmware. See my below set up in tools menu:

[Image: 0?ui=2&ik=2d79881756&attid=0.1&permmsgid...j58g7e0&zw]

I followed you recommendation with ''USB CDC On Boot'' = ENABLE, and now I have below information in the Serial Monitor:

ELF file SHA256: 587cb4fa5
E (159) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
E (167) esp_core_dump_elf: Elf write init failed!
E (172) esp_core_dump_common: Core dump write failed with error=-1
Rebooting...
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40376f0d
SPIWP:0xee
modeBig GrinIO, clock div:1
load:0x3fce2810,len:0xfdc
load:0x403c8700,len:0x4
load:0x403c8704,len:0xabc
load:0x403cb700,len:0x2d40
entry 0x403c8890
E (113) quad_psram: PSRAM ID read error: 0x00ffffff, PSRAM chip not found or not supported, or wrong PSRAM line mode
E (116) spi_flash: Detected size(8192k) smaller than the size in the binary image header(16384k). Probe failed.
assert failed: __esp_system_init_fn_init_flash startup_funcs.c:95 (flash_ret == ESP_OK)
Backtrace: 0x4037654e:0x3fceb120 0x4037c65d:0x3fceb140 0x403830bd:0x3fceb160 0x4200a903:0x3fceb290 0x4200bd8b:0x3fceb2b0 0x4200bdc5:0x3fceb2d0 0x403768f5:0x3fceb300 0x403cc974:0x3fceb340 0x403ccd39:0x3fceb380 0x403c88fd:0x3fceb4b0 0x40045c01:0x3fceb570 0x40043ab6:0x3fceb6f0 0x40034c45:0x3fceb710

I think I need to change something else in the Tool config but I'm not sure.

Thanks.]]> <![CDATA[wired temperature and humidity sensor pin define]]> https://www.kincony.com/forum/showthread.php?tid=6953 Thu, 31 Oct 2024 09:58:06 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=6953
.png   temperature-humidity-sensor.png (Size: 178.23 KB / Downloads: 331)
RED: VCC 3.3--5v
BLACK: GND
YELLOW: humidity output
WHITE: temperature output]]>
.png   temperature-humidity-sensor.png (Size: 178.23 KB / Downloads: 331)
RED: VCC 3.3--5v
BLACK: GND
YELLOW: humidity output
WHITE: temperature output]]> <![CDATA[wired gas sensor pin define]]> https://www.kincony.com/forum/showthread.php?tid=6952 Thu, 31 Oct 2024 09:52:57 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=6952
.png   gas-sensor-pin-define.png (Size: 253.84 KB / Downloads: 298)
1: +12V
2: GND
3-4: relay output]]>
.png   gas-sensor-pin-define.png (Size: 253.84 KB / Downloads: 298)
1: +12V
2: GND
3-4: relay output]]> <![CDATA[Like the A6 but more 0-10V outputs]]> https://www.kincony.com/forum/showthread.php?tid=6893 Tue, 22 Oct 2024 00:45:46 +0800 tarajas]]> https://www.kincony.com/forum/showthread.php?tid=6893
Basically none of the dev boards offerred by Kincony have more 0-10V outputs than 2, while also having SSR digital outputs, instead of mechanical relays right?

So the only way is to buy at least minimum an A6 board (it has the I2C port needed for the extenders), then use an extender right? Which extender should I go for?

For the the SSR outputs are the main focus and multiple 0-10V outputs as well.]]>
Basically none of the dev boards offerred by Kincony have more 0-10V outputs than 2, while also having SSR digital outputs, instead of mechanical relays right?

So the only way is to buy at least minimum an A6 board (it has the I2C port needed for the extenders), then use an extender right? Which extender should I go for?

For the the SSR outputs are the main focus and multiple 0-10V outputs as well.]]> <![CDATA[RS485 Temperature and Humidity Sensor Modbus RTU]]> https://www.kincony.com/forum/showthread.php?tid=6598 Wed, 04 Sep 2024 19:18:52 +0800 Trapasin]]> https://www.kincony.com/forum/showthread.php?tid=6598 https://shop.kincony.com/products/rs485-...e-by-sht30

Please tell me the parameters of the Sensor to connect it to the controller via the MODBUS bus

1. Device address: What is the default address, how can it be changed?
2. Data transfer rate (Baud Rate)
3. Number of stop bits
4. Number of data bits
5. Parity
6. Transfer type: RTU or ASCII
7. Bus type: I use 4 wires: RS-485
8. Timeouts and delays: which are preferable for it?]]> https://shop.kincony.com/products/rs485-...e-by-sht30

Please tell me the parameters of the Sensor to connect it to the controller via the MODBUS bus

1. Device address: What is the default address, how can it be changed?
2. Data transfer rate (Baud Rate)
3. Number of stop bits
4. Number of data bits
5. Parity
6. Transfer type: RTU or ASCII
7. Bus type: I use 4 wires: RS-485
8. Timeouts and delays: which are preferable for it?]]> <![CDATA[Modbus]]> https://www.kincony.com/forum/showthread.php?tid=6597 Wed, 04 Sep 2024 18:56:14 +0800 charles.garand]]> https://www.kincony.com/forum/showthread.php?tid=6597
anybody had implement Modbus ?
I'm having hard time to get mine working.
I'm using esp32ModbusRTU library.

here is my code;

esp32ModbusRTU modbus(&Serial1, -1); 


void modbusTask(void *pvParameters) {
  Serial1.begin(4800, SERIAL_8N1, RX, TX); 
  printf("Serial1 initialized for Modbus\n");
  vTaskDelay(pdMS_TO_TICKS(1000)); 

    // callbacks  Modbus
    modbus.onData([](uint8_t serverAddress, esp32Modbus::FunctionCode fc, uint8_t* data, size_t length) {
        printf("Modbus Response Received - Server ID: 0x%02x, Function Code: 0x%02x, Length: %u\n", serverAddress, fc, length);
        for (size_t i = 0; i < length; ++i) {
            printf("%02x ", data[i]);
        }
        printf("\n");
    });

    modbus.onError([](esp32Modbus::Error error) {
        printf("Modbus Error: 0x%02x\n", static_cast<uint8_t>(error));
    });

   
    modbus.begin();
  vTaskDelay(pdMS_TO_TICKS(1000)); 

   
    while (true) {
        modbus.readHoldingRegisters(0x01, 0x0000, 4); 
        //vTaskDelay(pdMS_TO_TICKS(1000)); 
    }
}

extern "C" void app_main(void)
{
  vTaskDelay(6000 / portTICK_PERIOD_MS);
  printf("Hello world!\n");
 
    xTaskCreate(modbusTask, "modbusTask", 8192, NULL, 5, NULL);

    while (true) {
        std::cout << "In the while\n" << std::endl;
        //vTaskDelay(pdMS_TO_TICKS(1000));
    }

}

...
#include <esp32ModbusRTU.h>
#include "driver/uart.h"

// Declaration Modbus
esp32ModbusRTU modbus(&Serial1, 10); // 10 is arbitary GPIO because don't use RTS pin


void modbusTask(void *pvParameters) {
// Configurer la communication UART pour Modbus
Serial1.begin(4800, SERIAL_8N1, RX, TX); // Initialise Serial1
printf("Serial1 initialized for Modbus\n");
vTaskDelay(pdMS_TO_TICKS(1000)); // stabilisation time

// Configurer les callbacks de Modbus
modbus.onData([](uint8_t serverAddress, esp32Modbus::FunctionCode fc, uint8_t* data, size_t length) {

printf("Modbus Response Received - Server ID: 0x%02x, Function Code: 0x%02x, Length: %u\n", serverAddress, fc, length);

if (length % 2 != 0) {
printf("Invalid data length\n");
return;
}

for (size_t i = 0; i < length; i += 2) {
uint16_t value = (data[i] << 8) | data[i + 1];
if(i < 5)
value = value / 10;
printf("Register %zu: %u \n", i / 2, value);
}

printf("\n");
});

modbus.onError([](esp32Modbus::Error error) {
printf("Modbus Error: 0x%02x\n", static_cast<uint8_t>(error));
});

// start Modbus
modbus.begin();
vTaskDelay(pdMS_TO_TICKS(1000)); // wait 1 sec to stabilise

while (true) {
modbus.readHoldingRegisters(0x01, 0x0000, 5); // slave address: 0x01
vTaskDelay(pdMS_TO_TICKS(1000));
}
}

extern "C" void app_main(void)
{
xTaskCreate(modbusTask, "modbusTask", 8192, NULL, 5, NULL);

while (true) {
std::cout << "In the while\n" << std::endl;
vTaskDelay(pdMS_TO_TICKS(2000));
}

}]]>
anybody had implement Modbus ?
I'm having hard time to get mine working.
I'm using esp32ModbusRTU library.

here is my code;

esp32ModbusRTU modbus(&Serial1, -1); 


void modbusTask(void *pvParameters) {
  Serial1.begin(4800, SERIAL_8N1, RX, TX); 
  printf("Serial1 initialized for Modbus\n");
  vTaskDelay(pdMS_TO_TICKS(1000)); 

    // callbacks  Modbus
    modbus.onData([](uint8_t serverAddress, esp32Modbus::FunctionCode fc, uint8_t* data, size_t length) {
        printf("Modbus Response Received - Server ID: 0x%02x, Function Code: 0x%02x, Length: %u\n", serverAddress, fc, length);
        for (size_t i = 0; i < length; ++i) {
            printf("%02x ", data[i]);
        }
        printf("\n");
    });

    modbus.onError([](esp32Modbus::Error error) {
        printf("Modbus Error: 0x%02x\n", static_cast<uint8_t>(error));
    });

   
    modbus.begin();
  vTaskDelay(pdMS_TO_TICKS(1000)); 

   
    while (true) {
        modbus.readHoldingRegisters(0x01, 0x0000, 4); 
        //vTaskDelay(pdMS_TO_TICKS(1000)); 
    }
}

extern "C" void app_main(void)
{
  vTaskDelay(6000 / portTICK_PERIOD_MS);
  printf("Hello world!\n");
 
    xTaskCreate(modbusTask, "modbusTask", 8192, NULL, 5, NULL);

    while (true) {
        std::cout << "In the while\n" << std::endl;
        //vTaskDelay(pdMS_TO_TICKS(1000));
    }

}

...
#include <esp32ModbusRTU.h>
#include "driver/uart.h"

// Declaration Modbus
esp32ModbusRTU modbus(&Serial1, 10); // 10 is arbitary GPIO because don't use RTS pin


void modbusTask(void *pvParameters) {
// Configurer la communication UART pour Modbus
Serial1.begin(4800, SERIAL_8N1, RX, TX); // Initialise Serial1
printf("Serial1 initialized for Modbus\n");
vTaskDelay(pdMS_TO_TICKS(1000)); // stabilisation time

// Configurer les callbacks de Modbus
modbus.onData([](uint8_t serverAddress, esp32Modbus::FunctionCode fc, uint8_t* data, size_t length) {

printf("Modbus Response Received - Server ID: 0x%02x, Function Code: 0x%02x, Length: %u\n", serverAddress, fc, length);

if (length % 2 != 0) {
printf("Invalid data length\n");
return;
}

for (size_t i = 0; i < length; i += 2) {
uint16_t value = (data[i] << 8) | data[i + 1];
if(i < 5)
value = value / 10;
printf("Register %zu: %u \n", i / 2, value);
}

printf("\n");
});

modbus.onError([](esp32Modbus::Error error) {
printf("Modbus Error: 0x%02x\n", static_cast<uint8_t>(error));
});

// start Modbus
modbus.begin();
vTaskDelay(pdMS_TO_TICKS(1000)); // wait 1 sec to stabilise

while (true) {
modbus.readHoldingRegisters(0x01, 0x0000, 5); // slave address: 0x01
vTaskDelay(pdMS_TO_TICKS(1000));
}
}

extern "C" void app_main(void)
{
xTaskCreate(modbusTask, "modbusTask", 8192, NULL, 5, NULL);

while (true) {
std::cout << "In the while\n" << std::endl;
vTaskDelay(pdMS_TO_TICKS(2000));
}

}]]>