https://www.kincony.com/forum/ Tue, 27 Oct 2026 09:14:51 +0000 MyBB https://www.kincony.com/forum/showthread.php?tid=9913 Mon, 26 Oct 2026 14:46:44 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9913
  KinCony 3-Wire-PT100-Wiring-Diagram.png (Size: 1.34 MB / Downloads: 11)

• Connect the two wires from the same end of the sensing element to the two “+” terminals, one wire to each terminal.
  
• Connect the remaining wire to the “−” terminal.
  
• No external power supply is required for the sensor.
  

The diagram uses two red wires and one white wire as an example. Follow your sensor’s wiring instructions to identify the correct wires.]]>
  KinCony 3-Wire-PT100-Wiring-Diagram.png (Size: 1.34 MB / Downloads: 11)

• Connect the two wires from the same end of the sensing element to the two “+” terminals, one wire to each terminal.
  
• Connect the remaining wire to the “−” terminal.
  
• No external power supply is required for the sensor.
  

The diagram uses two red wires and one white wire as an example. Follow your sensor’s wiring instructions to identify the correct wires.]]> https://www.kincony.com/forum/showthread.php?tid=9912 Mon, 26 Oct 2026 14:45:26 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9912
  KinCony-RS485-Multidrop-Sensor-Wiring.png (Size: 1.39 MB / Downloads: 14)
Connect multiple Modbus RTU devices to a single RS485 port, with KCS v3 acting as the master to poll and read each device.
The example includes a temperature sensor, a humidity sensor, and an energy meter, with Modbus addresses 1, 2, and 3, respectively. The diagram shows the A/B bus, termination resistors at both ends, and requirements such as unique device addresses and matching serial communication settings.]]>
  KinCony-RS485-Multidrop-Sensor-Wiring.png (Size: 1.39 MB / Downloads: 14)
Connect multiple Modbus RTU devices to a single RS485 port, with KCS v3 acting as the master to poll and read each device.
The example includes a temperature sensor, a humidity sensor, and an energy meter, with Modbus addresses 1, 2, and 3, respectively. The diagram shows the A/B bus, termination resistors at both ends, and requirements such as unique device addresses and matching serial communication settings.]]> https://www.kincony.com/forum/showthread.php?tid=9911 Mon, 26 Oct 2026 14:44:09 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9911
  KinCony-UART-Wiring-to-G1-4G.png (Size: 1.34 MB / Downloads: 13)

• Controller TXD → G1 RXD
  
• Controller RXD ← G1 TXD
  
• GND → Common ground
  
• G1 requires an external power supply, a SIM card, and a 4G antenna.
  

With compatible firmware, the controller can send and receive SMS messages and dial phone calls. Select available GPIO pins that support UART operation.]]>
  KinCony-UART-Wiring-to-G1-4G.png (Size: 1.34 MB / Downloads: 13)

• Controller TXD → G1 RXD
  
• Controller RXD ← G1 TXD
  
• GND → Common ground
  
• G1 requires an external power supply, a SIM card, and a 4G antenna.
  

With compatible firmware, the controller can send and receive SMS messages and dial phone calls. Select available GPIO pins that support UART operation.]]> https://www.kincony.com/forum/showthread.php?tid=9910 Mon, 26 Oct 2026 14:42:30 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9910
  KinCony-1-wire-sensor-wiring-diagram.png (Size: 1.48 MB / Downloads: 15) ]]>
  KinCony-1-wire-sensor-wiring-diagram.png (Size: 1.48 MB / Downloads: 15) ]]> https://www.kincony.com/forum/showthread.php?tid=9909 Mon, 26 Oct 2026 14:40:12 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9909
  KinCony-Wiegand-GPIO-Wiring-Guide.png (Size: 1.32 MB / Downloads: 9)

• D0 → GPIO A
  
• D1 → GPIO B
  
• GND → GND
  

GPIO A and GPIO B are placeholder names. Select available GPIO pins according to your controller model.]]>
  KinCony-Wiegand-GPIO-Wiring-Guide.png (Size: 1.32 MB / Downloads: 9)

• D0 → GPIO A
  
• D1 → GPIO B
  
• GND → GND
  

GPIO A and GPIO B are placeholder names. Select available GPIO pins according to your controller model.]]> https://www.kincony.com/forum/showthread.php?tid=9908 Mon, 26 Oct 2026 14:38:29 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9908
  KinCony-0–10 V-lighting-control-wiring.png (Size: 1.4 MB / Downloads: 9)

• 12 V LED driver → 12 V LED strip
  
• 24 V LED driver → 24 V LED strip
  
• AC dimmer with a 0–10 V input → Dimmable AC 220 V lamp
  

DAC/AO provides only the dimming signal. The load is powered by an external power supply and driver. For AC dimming, use a dedicated dimming SSR; a standard ON/OFF SSR is not suitable. Follow the driver’s manual for the exact terminal connections.]]>
  KinCony-0–10 V-lighting-control-wiring.png (Size: 1.4 MB / Downloads: 9)

• 12 V LED driver → 12 V LED strip
  
• 24 V LED driver → 24 V LED strip
  
• AC dimmer with a 0–10 V input → Dimmable AC 220 V lamp
  

DAC/AO provides only the dimming signal. The load is powered by an external power supply and driver. For AC dimming, use a dedicated dimming SSR; a standard ON/OFF SSR is not suitable. Follow the driver’s manual for the exact terminal connections.]]> https://www.kincony.com/forum/showthread.php?tid=9907 Mon, 26 Oct 2026 14:37:01 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9907
  KinCony-Analog-Input-Wiring-Guide.png (Size: 1.35 MB / Downloads: 7)

• 0–5 V / 0–10 V: Connect the sensor OUT to AI1. Connect the sensor and controller to a common GND.
  
• 2-wire 4–20 mA: Power supply positive → Transmitter +; Transmitter − → AI1; Controller GND → Power supply negative.
  

Before use, configure the input range and jumper settings according to your controller model. The 4–20 mA wiring example applies to passive current inputs with an onboard sampling resistor.]]>
  KinCony-Analog-Input-Wiring-Guide.png (Size: 1.35 MB / Downloads: 7)

• 0–5 V / 0–10 V: Connect the sensor OUT to AI1. Connect the sensor and controller to a common GND.
  
• 2-wire 4–20 mA: Power supply positive → Transmitter +; Transmitter − → AI1; Controller GND → Power supply negative.
  

Before use, configure the input range and jumper settings according to your controller model. The 4–20 mA wiring example applies to passive current inputs with an onboard sampling resistor.]]> https://www.kincony.com/forum/showthread.php?tid=9906 Mon, 26 Oct 2026 14:35:06 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9906
  KinCony-dry-contact-wiring-diagram.png (Size: 1.2 MB / Downloads: 10)

• DI1 connected to GND: TRUE
  
• DI1 disconnected from GND: FALSE
  

You can connect a volt-free switch, push button, or relay dry contact.]]>
  KinCony-dry-contact-wiring-diagram.png (Size: 1.2 MB / Downloads: 10)

• DI1 connected to GND: TRUE
  
• DI1 disconnected from GND: FALSE
  

You can connect a volt-free switch, push button, or relay dry contact.]]> https://www.kincony.com/forum/showthread.php?tid=9905 Mon, 26 Oct 2026 14:33:07 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9905
  KinCony-Bidirectional-Input-Wiring.png (Size: 1.28 MB / Downloads: 10)

• COM connected to GND: The switch connects +12/24 V to DI1.
  
• COM connected to +12/24 V: The switch connects GND to DI1.
  

In both configurations, DI1 becomes active (TRUE) when the switch is closed. This applies to controllers with bidirectional optocouplers and 12/24 V DC digital inputs.]]>
  KinCony-Bidirectional-Input-Wiring.png (Size: 1.28 MB / Downloads: 10)

• COM connected to GND: The switch connects +12/24 V to DI1.
  
• COM connected to +12/24 V: The switch connects GND to DI1.
  

In both configurations, DI1 becomes active (TRUE) when the switch is closed. This applies to controllers with bidirectional optocouplers and 12/24 V DC digital inputs.]]> https://www.kincony.com/forum/showthread.php?tid=9904 Mon, 26 Oct 2026 14:29:32 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9904
  KinCony-220VAC-lamp-wiring.png (Size: 1.24 MB / Downloads: 8)

• L (Live) → Fuse → COM
  
• NO → Lamp → N (Neutral)
  
• NC: Leave unconnected
  

The lamp turns ON when the relay is energized and OFF when the relay is de-energized. For actual wiring, follow the terminal markings on your controller.]]>
  KinCony-220VAC-lamp-wiring.png (Size: 1.24 MB / Downloads: 8)

• L (Live) → Fuse → COM
  
• NO → Lamp → N (Neutral)
  
• NC: Leave unconnected
  

The lamp turns ON when the relay is energized and OFF when the relay is de-energized. For actual wiring, follow the terminal markings on your controller.]]> https://www.kincony.com/forum/showthread.php?tid=9903 Mon, 26 Oct 2026 05:59:27 +0800 Saif Kitany]]> https://www.kincony.com/forum/showthread.php?tid=9903 I want to make a condition by kcs v3 like this :

If the relays 2,4,6,……..,32 in H32B are on, then turn on relay2 in A8v3.

I made a custom protocol 3 like this:

Realy-status-255,170,170,170,170

The router is: TCP Client.

In the IFTTT Condition, i put this:

If “custom protol 3”, Then DO2 ON.

But it didn’t work!!

Is there something i need to correct?]]> I want to make a condition by kcs v3 like this :

If the relays 2,4,6,……..,32 in H32B are on, then turn on relay2 in A8v3.

I made a custom protocol 3 like this:

Realy-status-255,170,170,170,170

The router is: TCP Client.

In the IFTTT Condition, i put this:

If “custom protol 3”, Then DO2 ON.

But it didn’t work!!

Is there something i need to correct?]]> https://www.kincony.com/forum/showthread.php?tid=9902 Mon, 26 Oct 2026 03:22:53 +0800 maczrool]]> https://www.kincony.com/forum/showthread.php?tid=9902 Initially, the board was caught in a continuous USB resetting loop. I resolved the USB dropping issue by ensuring the file row checkbox in the downloader program was properly selected. However, even though the USB connection now holds steady while plugged in, the firmware still completely fails to execute when the board is restarted. The board remains totally unresponsive on the network.

What Works (Hardware Verification):

The physical board hardware is completely healthy. When I flash a clean, standalone image compiled natively via the Arduino framework (bypassing the ESP-IDF KCS binary image), the board boots up perfectly fine, initializes its local interfaces, and connects to the local network switch cleanly. This confirms the physical hardware is fine, but the factory KCS file layout is failing to execute on this specific board variant.

Technical Analysis:

Because the KCS binary provided on the forum is an Application-only image, it is missing the necessary low-level bootloader and partition tables required to initialize the advanced memory/PSRAM boundaries of the ESP32-S3 chip from a completely erased state. When flashed alone to 0x0, the chip hangs silently on boot.

My Request:

I bought this KinCony hardware specifically to use the native KCS web interface and its dropdown IFTTT configuration features.
Please provide the complete factory multi-file partition zip package for this specific board variant. I need the matching:
1. bootloader.bin (compiled for address 0x0)
2. partition-table.bin (compiled for address 0x8000)
3. ota_data_initial.bin (compiled for address 0xd000)
This will allow me to properly offset the main KCS application binary to 0x10000 so the ESP32-S3 can initialize its memory lanes on startup and boot into the KCS platform safely.

Thanks for any suggestions and assistance.]]> Initially, the board was caught in a continuous USB resetting loop. I resolved the USB dropping issue by ensuring the file row checkbox in the downloader program was properly selected. However, even though the USB connection now holds steady while plugged in, the firmware still completely fails to execute when the board is restarted. The board remains totally unresponsive on the network.

What Works (Hardware Verification):

The physical board hardware is completely healthy. When I flash a clean, standalone image compiled natively via the Arduino framework (bypassing the ESP-IDF KCS binary image), the board boots up perfectly fine, initializes its local interfaces, and connects to the local network switch cleanly. This confirms the physical hardware is fine, but the factory KCS file layout is failing to execute on this specific board variant.

Technical Analysis:

Because the KCS binary provided on the forum is an Application-only image, it is missing the necessary low-level bootloader and partition tables required to initialize the advanced memory/PSRAM boundaries of the ESP32-S3 chip from a completely erased state. When flashed alone to 0x0, the chip hangs silently on boot.

My Request:

I bought this KinCony hardware specifically to use the native KCS web interface and its dropdown IFTTT configuration features.
Please provide the complete factory multi-file partition zip package for this specific board variant. I need the matching:
1. bootloader.bin (compiled for address 0x0)
2. partition-table.bin (compiled for address 0x8000)
3. ota_data_initial.bin (compiled for address 0xd000)
This will allow me to properly offset the main KCS application binary to 0x10000 so the ESP32-S3 can initialize its memory lanes on startup and boot into the KCS platform safely.

Thanks for any suggestions and assistance.]]> https://www.kincony.com/forum/showthread.php?tid=9901 Mon, 26 Oct 2026 02:13:08 +0800 osis]]> https://www.kincony.com/forum/showthread.php?tid=9901 https://www.kincony.com/forum/showthread.php?tid=9899 Sun, 25 Oct 2026 09:29:46 +0800 admin]]> https://www.kincony.com/forum/showthread.php?tid=9899
  drv8262.pdf (Size: 2.79 MB / Downloads: 8) ]]>
  drv8262.pdf (Size: 2.79 MB / Downloads: 8) ]]> https://www.kincony.com/forum/showthread.php?tid=9898 Fri, 23 Oct 2026 18:31:05 +0800 ThomasJS]]> https://www.kincony.com/forum/showthread.php?tid=9898
I'm interested in buying the N30, but I see multiple issues on this forum about the current direction detection.

I came accross this one on the forum:
https://www.kincony.com/forum/attachment.php?aid=9375

This one is on the webshop: (i guess this is the wrong one?)
https://www.kincony.com/forum/attachment.php?aid=8460

This one on ESPHOME: (also older one?)
https://devices.esphome.io/devices/kincony-n30/

Which N30 ESPHome configuration correctly expose signed, bidirectional active power for each BL0910 CT channel?
Which is the most recent ESPHOME config?]]>
I'm interested in buying the N30, but I see multiple issues on this forum about the current direction detection.

I came accross this one on the forum:
https://www.kincony.com/forum/attachment.php?aid=9375

This one is on the webshop: (i guess this is the wrong one?)
https://www.kincony.com/forum/attachment.php?aid=8460

This one on ESPHOME: (also older one?)
https://devices.esphome.io/devices/kincony-n30/

Which N30 ESPHome configuration correctly expose signed, bidirectional active power for each BL0910 CT channel?
Which is the most recent ESPHOME config?]]>