HS: visu OK, but iETS not

[domoticom]

Hello,

I have a strange problem, maybe someone here can help.
HS3 with latest f/w is on LAN, and on KNX via USB (Gira), Visu works fine (read/write), so connection between HS & KNX seems OK.
There's only one TP line, and no linecoupler.

When I conect ETS4 to the KNX net via iETS (HS), the connection seesm ok. I can open the busmonitor, and read/write GA's. i.e. i switch a light, and get responce from aktor.

But when I try to read info from a KNX device, or try to program one (that already has a physical address), it doens't work. Below some telegrams regarding this action. It looks like communicatin is extremely slow, and finaly it gives up. (not sure if that's what actualy is happening)

I already tried to change the address of the iETS connection to a different value (1.1.240 (free) instead of the default 15.15.255)

This setup worked before. Only thing that was changed is added al the tasters and some other devices to the KNX net.
Tasters are now programmed directly vua USB and work fine, three devices are not yet programmed with physical address (ArcusEDS gas/water en electricity meters). Maybe those unprogrammed devices couse a address conflict ??

Hope someone has an idea

Thanx.

[domoticom]

nobody ?

[Martin J.]

if you still have the problem or maby someone else will have. I think you first have to assign a physical adress to the device directly connected to the ETS. Then you can use it via iETS connected to the homeserver.

The problem is that the native adress is 15.15.255, like you can find as well in your log, this does not work.

[MatthiasS]

My idea: power supply of KNX not sufficient

[Martin J.]

My idea: power supply of KNX not sufficient

As well possible. Anyway I had the same problem and solved it in the described way.

Regards

Martin