Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 10,170
» Latest member: tinyfishing2
» Forum threads: 4,262
» Forum posts: 21,118

Full Statistics

Online Users
There are currently 640 online users.
» 0 Member(s) | 620 Guest(s)
Amazonbot, Applebot, Baidu, Bing, Bytespider, Crawl, DataForSeoBot, Google, HeadlessChrome, PetalBot, bot

Latest Threads
KC868-A16 and Tuya
Forum: KC868-A series and Uair Smart Controller
Last Post: newdos
22 minutes ago
» Replies: 0
» Views: 2
N30 (KCS): energy counter...
Forum: N30
Last Post: dominique_manas@hotmail.com
24 minutes ago
» Replies: 0
» Views: 1
Bricked KC868-A16
Forum: KC868-A series and Uair Smart Controller
Last Post: newdos
30 minutes ago
» Replies: 6
» Views: 37
Current direction detecti...
Forum: N30
Last Post: dominique_manas@hotmail.com
1 hour ago
» Replies: 4
» Views: 419
KC868-A8 on Heat Pump for...
Forum: KC868-HxB series Smart Controller
Last Post: marktuan
5 hours ago
» Replies: 2
» Views: 617
B32M maximum voltage
Forum: DIY Project
Last Post: felixandrea
5 hours ago
» Replies: 5
» Views: 585
remember relay state
Forum: KC868-E16T
Last Post: admin
7 hours ago
» Replies: 7
» Views: 390
It looks like it's broken...
Forum: KinCony Server-Mini / Server-16 Raspberry Pi4 relay module
Last Post: admin
10-07-2026, 08:36 AM
» Replies: 5
» Views: 108
Bidirectional reading
Forum: N10
Last Post: admin
10-05-2026, 11:35 PM
» Replies: 1
» Views: 33
Update to latest esphome
Forum: KC868-A16
Last Post: admin
10-05-2026, 12:05 PM
» Replies: 6
» Views: 171

  how to install Pi OS to SD or SSD card test by Node Red
Posted by: admin - 05-24-2026, 01:54 AM - Forum: Pi5R32 - No Replies

1. Download Pi OS to your SD card or SSD by Raspberry Pi Imager tool.

2. In the Pi OS configuration graphical interface, enable I2C and serial port, and disable the serial monitor function.

3. By default, the /dev/ttyAMA0 serial port is enabled, but you need to edit the file to enable the /dev/ttyAMA2 serial port.

Run the command:
sudo nano /boot/firmware/config.txt
Add the following lines:

dtoverlay=uart2
dtoverlay=uart3
Save the file and exit.

The serial port mappings are as follows:

Code:
Serial Port    Device File    Physical Pins (Board)    BCM Pins (GPIO)
UART2    /dev/ttyAMA1    Pin 27 (TXD) / 28 (RXD)    GPIO 0 / 1
UART3    /dev/ttyAMA2    Pin 13 (TXD) / 14 (RXD)    GPIO 4 / 5
UART4    /dev/ttyAMA3    Pin 7 (TXD) / 21 (RXD)    GPIO 8 / 9
UART5    /dev/ttyAMA4    Pin 29 (TXD) / 30 (RXD)    GPIO 12 / 13

4. When you first open Node RED and import a Node flow, you will be automatically prompted to install the required plugins. Click "OK" to install all the plugins automatically.

   

here is node red flow use for import. 

.zip   flows.zip (Size: 5.98 KB / Downloads: 269)

Print this item

  how to install Pi OS to SD or SSD card test by Node Red
Posted by: admin - 05-24-2026, 01:54 AM - Forum: Pi5M32 - No Replies

1. Download Pi OS to your SD card or SSD by Raspberry Pi Imager tool.

2. In the Pi OS configuration graphical interface, enable I2C and serial port, and disable the serial monitor function.

3. By default, the /dev/ttyAMA0 serial port is enabled, but you need to edit the file to enable the /dev/ttyAMA2 serial port.

Run the command:
sudo nano /boot/firmware/config.txt
Add the following lines:

dtoverlay=uart2
dtoverlay=uart3
Save the file and exit.

The serial port mappings are as follows:

Code:
Serial Port    Device File    Physical Pins (Board)    BCM Pins (GPIO)
UART2    /dev/ttyAMA1    Pin 27 (TXD) / 28 (RXD)    GPIO 0 / 1
UART3    /dev/ttyAMA2    Pin 13 (TXD) / 14 (RXD)    GPIO 4 / 5
UART4    /dev/ttyAMA3    Pin 7 (TXD) / 21 (RXD)    GPIO 8 / 9
UART5    /dev/ttyAMA4    Pin 29 (TXD) / 30 (RXD)    GPIO 12 / 13

4. When you first open Node RED and import a Node flow, you will be automatically prompted to install the required plugins. Click "OK" to install all the plugins automatically.

   

here is node red flow use for import. 
.zip   flows.zip (Size: 5.98 KB / Downloads: 235)

Print this item

  Pi5R16 Raspberry Pi CM5 pin define
Posted by: admin - 05-24-2026, 01:48 AM - Forum: Pi5R16 - No Replies

   

RS232:  /dev/ttyAMA0

RS485:  /dev/ttyAMA2

Print this item

  Pi5R8 Raspberry Pi CM5 pin define
Posted by: admin - 05-24-2026, 01:48 AM - Forum: Pi5R8 - No Replies

   

RS232:  /dev/ttyAMA0

RS485:  /dev/ttyAMA2

Print this item

  Pi5M8 Raspberry Pi CM5 pin define
Posted by: admin - 05-24-2026, 01:48 AM - Forum: Pi5M8 - No Replies

   

RS232:  /dev/ttyAMA0

RS485:  /dev/ttyAMA2

Print this item

  Pi5M16 Raspberry Pi CM5 pin define
Posted by: admin - 05-24-2026, 01:48 AM - Forum: Pi5M16 - No Replies

   

RS232:  /dev/ttyAMA0

RS485:  /dev/ttyAMA2

Print this item

  Pi5R32 Raspberry Pi CM5 pin define
Posted by: admin - 05-24-2026, 01:48 AM - Forum: Pi5R32 - No Replies

   

RS232:  /dev/ttyAMA0

RS485:  /dev/ttyAMA2

Print this item

  Pi5M32 Raspberry Pi CM5 pin define
Posted by: admin - 05-24-2026, 01:48 AM - Forum: Pi5M32 - No Replies

   

RS232:  /dev/ttyAMA0

RS485:  /dev/ttyAMA2

Print this item

  problem with kc868 has v2
Posted by: Gianfranco Pepi - 05-21-2026, 09:56 PM - Forum: News - Replies (13)

Good morning, I also did some tests with the multimeter looking at your diagram and the board seems not to work, that is, the KC868 has v2. Using your tool to check and change the assignments of the inputs to the outputs, I don't know if it also shows the activation of the outputs, but every time I close and open the input, the RS485 adapter emits a signal and under the bar it shows me the last signal that arrived, so the inputs, so to speak, "work". Now I tried with the multimeter considering that I'm using only one 12 volt power supply for everything, so the grounds are equivalent! Here is the voltage between the +12 volts and the output, which according to your diagram should be negative, always remains at 6 volts without ever varying (I'm talking about an open circuit). I tried installing a classic relay that is powered by 12 volts and has a pilot input that can be set to receive either positive or negative inputs. Obviously, I set the input to negative and when I try to close the input, the result does n



Attached Files Thumbnail(s)
           
Print this item

  CRC Errors with ESP Home & N10203060_KU_V20_260324SP
Posted by: edalquist - 05-21-2026, 03:10 AM - Forum: N60 - Replies (3)

I updated the ARM firmware to N10203060_KU_V20_260324SP and then tried flashing the ESP Home config from https://www.kincony.com/forum/showthread.php?tid=9157

I'm now not getting any data and the following logs repeating over and over:

Code:
[20:07:41.184][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=100 count=68
[20:07:41.189][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=200 count=68
[20:07:41.189][W][modbus_controller:145]: Duplicate modbus command found: type=0x3 address=600 count=68
[20:07:41.412][W][modbus:063]: Stop waiting for response from 1 424ms after last send
[20:07:41.447][W][modbus:219]: CRC check failed 1ms after last send
[20:07:41.455][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 3ms after last send
[20:07:41.468][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:41.713][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:41.732][W][modbus:219]: CRC check failed 1ms after last send
[20:07:41.737][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:41.751][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:41.994][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:42.015][W][modbus:219]: CRC check failed 2ms after last send
[20:07:42.021][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 5ms after last send
[20:07:42.036][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 23ms after last send
[20:07:42.402][W][modbus:063]: Stop waiting for response from 1 389ms after last send
[20:07:42.423][W][modbus:219]: CRC check failed 1ms after last send
[20:07:42.429][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:42.443][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:42.684][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:42.705][W][modbus:219]: CRC check failed 1ms after last send
[20:07:42.710][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:42.726][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:42.969][W][modbus:063]: Stop waiting for response from 1 266ms after last send
[20:07:43.007][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.012][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 3ms after last send
[20:07:43.026][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.407][W][modbus:063]: Stop waiting for response from 1 401ms after last send
[20:07:43.426][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.432][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:43.445][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.690][W][modbus:063]: Stop waiting for response from 1 265ms after last send
[20:07:43.710][W][modbus:219]: CRC check failed 1ms after last send
[20:07:43.715][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:43.730][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:43.975][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:43.996][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.001][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:44.012][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:44.402][W][modbus:063]: Stop waiting for response from 1 411ms after last send
[20:07:44.422][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.428][W][modbus:417]: Clearing buffer of 5 bytes - parse failed 4ms after last send
[20:07:44.441][W][modbus:417]: Clearing buffer of 3 bytes - timeout after partial response 21ms after last send
[20:07:44.687][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:44.722][W][modbus:219]: CRC check failed 1ms after last send
[20:07:44.728][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 3ms after last send
[20:07:44.741][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:44.984][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.004][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.013][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.024][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.407][W][modbus:063]: Stop waiting for response from 1 403ms after last send
[20:07:45.425][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.430][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.444][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.687][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.718][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.718][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:45.727][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send
[20:07:45.971][W][modbus:063]: Stop waiting for response from 1 264ms after last send
[20:07:45.992][W][modbus:219]: CRC check failed 1ms after last send
[20:07:45.998][W][modbus:417]: Clearing buffer of 6 bytes - parse failed 4ms after last send
[20:07:46.011][W][modbus:417]: Clearing buffer of 2 bytes - timeout after partial response 21ms after last send


There are no other changes to the system, just completed that ARM firmware update and flashed the example ESP Home config

Print this item