KNXD problems

[MikeMelga]

Hi.

I am using knxd with my Weinzierl KNX BAOS 770 IP interface.
I am starting knxd with these parameters:

knxd -e 1.1.221 -E 1.1.222:10 -D -T -R -S -i -t 65535 --send-delay=70 -b ipt:192.168.0.20

Everything works but I have 2 problems:
- When I send several commands in a short period of time... it seems to become 'stuck' and takes a few seconds to resume sending
- I am unable to use ETS programming.

Is there anything I can do or change in my parameters to resolve these issues?

Thanks.

Regards,
Mike

[schuma]

Use the Version 12.x! This will solve your problems.

[MikeMelga]

Use the Version 12.x! This will solve your problems.

schuma,

Thanks! I'll try that.

[Smurf]

Unfortunately that won't solve everybody else's problems.

I hope to have a fixed version next week.

MikeMelga Is the ETS talking to knxd or directly to the Weinzierl interface? Can you (or anybody else with the problem) do a packet dump of the traffic at the interface? (This requires a very dumb 10-MBit-only network hub, a switch on which you can configure a port to do packet monitoring, or a Linux box with two bridged network interfaces with the Weinzierl the only device attached to one of them.)

[MikeMelga]

Unfortunately that won't solve everybody else's problems.

I hope to have a fixed version next week.

Does it mean that is it a knxd problem and not my parameters?

[MikeMelga]

Smurf,

Unfortunately I don't have any of those 3.
I will try to get an old hub and will get back to you if I do.
Thanks.

Edit: ETS is talking to knxd directly.

[Smurf]

You might get further if you use "-B single" in front if the "-b ipt:".

Does ETS work if you tell it to talk to the Weinzierl instead of knxd?

[MikeMelga]

You might get further if you use "-B single" in front if the "-b ipt:".

Does ETS work if you tell it to talk to the Weinzierl instead of knxd?

Yes, ETS works fine directly connected to the Weinzierl.

I managed to get some hubs. If you need any packet dumps...let me know.

[Smurf]

Ideally, I need a shortest-possible comparison between a "good" ETS task and one that doesn't work out, so that it's possible to see where knxd gets things wrong. The accompanying knxd log (captured with "-B log -DTRS -B log -b ipt:…") plus the ETS logs would also be helpful.

If you want to email them directly to me, the address is matthias@urlichs.de.

[MikeMelga]

Smurf,

Sorry. I've been away.
Will the knxd logs and the ETS log be enough or do you need extra info like the one Wireshark can provide?
What ETS task do you need? Is a simple query enough?

[Smurf]

Any scenarium that works (or not) depending on whether ETS talks to knxd or directly to the interface would be helpful. The shorter the better obviously.