The same way that you cannot usually have more than 32 devices on a single RS485 bus. The more devices you have the harder it is for the transceiver to drive the line in order to transmit the data. This is usually solved by divining the line into two segments connected by a line coupler.
Having more than one KNX power supply is a standard solution for longer lines.
01.10.2023, 08:53 (This post was last modified: 01.10.2023, 09:05 by Hoang Hien.)
Hello, I am also experiencing the above error, checked the knx bus status, but Logic Machine still cannot communicate with other knx devices, or if it does, it communicates unstable. what should I do
(01.10.2023, 08:53)Hoang Hien Wrote: Hello, I am also experiencing the above error, checked the knx bus status, but Logic Machine still cannot communicate with other knx devices, or if it does, it communicates unstable. what should I do
10.10.2023, 06:47 (This post was last modified: 10.10.2023, 06:54 by Hoang Hien.)
(01.10.2023, 16:25)CristianAgata Wrote:
(01.10.2023, 08:53)Hoang Hien Wrote: Hello, I am also experiencing the above error, checked the knx bus status, but Logic Machine still cannot communicate with other knx devices, or if it does, it communicates unstable. what should I do
KNX/TP: Transmitter Error (send 0 receive 1)
Hi,
What about the bus load?
BR Cristian
I have checked the bus status, and here are the results
(10.10.2023, 06:47)Hoang Hien Wrote:
(01.10.2023, 16:25)CristianAgata Wrote:
(01.10.2023, 08:53)Hoang Hien Wrote: Hello, I am also experiencing the above error, checked the knx bus status, but Logic Machine still cannot communicate with other knx devices, or if it does, it communicates unstable. what should I do
KNX/TP: Transmitter Error (send 0 receive 1)
Hi,
What about the bus load?
BR Cristian
I have checked the bus status, and here are the results,
At first I thought the wrong flag on the ETS was causing the bus to have to continuously update its status, but after fixing it, the bus was no longer clogged due to the constant status updates. After a week this happened again
This usually happen when you have suddenly a lot of telegrams on a bus. it could be a script which sends to a lot of groups at once or some global command and loads of statuses is sent. KNX statistics shows only average so such spike is not visible well there.
(10.10.2023, 09:26)Daniel Wrote: This usually happen when you have suddenly a lot of telegrams on a bus. it could be a script which sends to a lot of groups at once or some global command and loads of statuses is sent. KNX statistics shows only average so such spike is not visible well there.
Is there any other possible cause for this error? Is there anything else I should check?