Weinzierl USB not working

[iain]

Hi all,

Just wondering if anyone has ever got a Weinzierl USB connection working - I've been trying for days to get knxd working from a pi4 with no luck and from what I can find searching around it's a problem other people are seeing. I've got a 312 and a 570 I/O which both come up as the same thing (0e77:0104) which is in the rules file already.

Tried several pi's with the same result.

If someone out there has got one of these working I'll stick at it and find what I'm doing wrong, or if someone out there ha any clues as to how to get this working please let me know.

I haven't attached any details but if anyone is interested I can add logs of what's going wrong.

I'm installing knxd on the pi with apt, and the pi was running the latest 32 bit raspbian, now I'm trying with an older version. Once again if anyone's interested I can be more specific but I'm away from my computer right now

[iain]

Some more info now I'm back at my computer:

I've just changed to an older raspbian image in case that helps, now its running raspbian buster 2021-01-11 (full), but previously I was using bullseye lite 32 bit 2022-01-28

On this buster pi knxd is installed as root by apt - knxd/oldstable,now 0.14.30-1 armhf [installed]
Bluetooth is disabled in /boot/config.txt with dtoverlay=disable-bt, and I've tried diosabling anything else I could find people trying just to see if it helps, but I'm assuming being usb none of this matters.

I'm no linux expert so I might be missing something obvious but it looks like the apt install creates the knxd user,  I tried messing around adding that to the knxd group, adding pi user to knxd group, etc. As I'm running it as root I don't think that is the issue either but I'm not sure.

So with that set up and starting knxd as root (sudo su -) with:

knxd -p /run/knxd/knxd.pid -e 1.1.220 -E 1.1.221:9 -DTRS -i --listen-local=/tmp/knx -f9 -t1023 -B log -b ipt:[ip address of a knx ip interface]

works great, but

knxd -p /run/knxd/knxd.pid -e 1.1.220 -E 1.1.221:9 -DTRS -i --listen-local=/tmp/knx -f9 -t1023 -B log -b usb:

looks happy at first, but doesn't seem to be connected to the bus:

root@raspberrypi:~# knxd -p /run/knxd/knxd.pid -e 1.1.220 -E 1.1.221:9 -DTRS -i --listen-local=/tmp/knx -f9 -t1023 -B log -b usb:
Layer 0 [17:log/C.usb         0.000] State setup
Layer 1 [19:C.usb/usbL        0.017] Detect
Layer 1 [19:C.usb/usbL        0.017] Using 1:3:1:0:0 (1:129)
Layer 1 [19:C.usb/usbL        0.032] Detect
Layer 1 [19:C.usb/usbL        0.032] Using 1:3:1:0:0 (1:129)
Layer 3 [15:C.usb/Conn        0.032] registerLink: 15:C.usb
Layer 3 [15:C.usb/Conn        0.032] Start: cfg:C.usb
Layer 5 [15:C.usb/Conn        0.032] down => >up
Layer 5 [15:C.usb/Conn        0.033] Starting
Layer 0 [17:log/C.usb         0.033] State start
Layer 1 [19:C.usb/usbL        0.033] Open
Layer 1 [19:C.usb/usbL        0.044] Claimed
Layer 1 [19:C.usb/usbL        0.044] Opened
Layer 0 [16:C.usb/USBdr       0.044] starting send_Local
Layer 0 [19:C.usb/usbL        0.044] SendUSB(064): 01 13 09 00 08 00 01 0F 01 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Layer 0 [19:C.usb/usbL        0.044] StartSend 12f0ca8
Layer 4 [15:C.usb/Conn        0.044] >up
Layer 4 [15:C.usb/Conn        0.046] is >up
Layer 0 [16:C.usb/USBdr       0.048] send_Local done
Layer 0 [19:C.usb/usbL        0.050] RecvUSB(064): 01 13 0B 00 08 00 03 0F 02 00 00 01 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Layer 2 [16:C.usb/USBdr       0.050] recv_Data(064): 01 13 0B 00 08 00 03 0F 02 00 00 01 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Layer 1 [16:C.usb/USBdr       0.051] Using EMI version 3
Layer 2 [18:C.usb/Conv        0.051] send_Init 3
Layer 0 [18:C.usb/Conv        0.052] starting send_Local
Layer 0 [19:C.usb/usbL        0.052] SendUSB(064): 01 13 0A 00 08 00 02 0F 03 00 00 05 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Layer 0 [19:C.usb/usbL        0.053] StartSend 12e46f8
Layer 0 [18:C.usb/Conv        0.055] send_Local done
Layer 2 [23:C.usb/CEMI        0.055] OpenL2
Layer 0 [17:log/C.usb         0.056] State started
Layer 5 [15:C.usb/Conn        0.056] >up => up
Layer 4 [15:C.usb/Conn        0.057] up
Layer 5 [15:C.usb/Conn        0.057] Started

If I try to send something with

knxtool off ip:localhost 1/1/11

it shuts it down:

Layer 6 [15:C.usb/Conn         106.998] sending, send_more clear
Layer 0 [17:log/C.usb          106.998] Send L_Data low from 1.1.221 to 1/1/11 hops: 05 T_DATA_XXX_REQ A_GroupValue_Write (small) 00
E00000059: [23:C.usb] EMI_common: send while waiting (-1228150576)
Layer 6 [15:C.usb/Conn         107.015] still waiting
E00000055: [15:C.usb] Driver timed out trying to send (C.usb)
Layer 5 [15:C.usb/Conn         117.008] up => down/error
Layer 4 [15:C.usb/Conn         117.008] up/error
Layer 5 [15:C.usb/Conn         117.008] Stopping
Layer 0 [17:log/C.usb          117.008] State stop
Layer 2 [23:C.usb/CEMI         117.008] CloseL2
Layer 0 [17:log/C.usb          117.008] State stopped
Layer 5 [15:C.usb/Conn         117.008] up/error => down
Layer 4 [15:C.usb/Conn         117.008] down/error
Layer 4 [15:C.usb/Conn         117.008] is down
F00000105: [15:C.usb] Link down, terminating
Layer 4 [15:C.usb/Conn         117.008] Stopping
Layer 5 [15:C.usb/Conn         117.008] down/error => >down
Layer 4 [15:C.usb/Conn         117.008] down/error
Layer 4 [15:C.usb/Conn         117.009] is down
Layer 1 [19:C.usb/usbL         117.009] Close
W00000123: [19:C.usb] RecvError 3
Layer 1 [19:C.usb/usbL         117.010] Release

That's about as far as my limited brainpower has got me so far, I'll keep bashing my head against the keyboard and see what happens but if anyone has any pointers please let me know.

I'd love to get a different usb interface to try but after buying 2 duds I've blown my budget so I'm stuck with these

FYI they both work fine from ETS

[Norbert]

Hello

suggest to use an IP Interface like Weinzierl KNX IP Interface 731. Same price range as USB and with flexible benefits.

Have this device in use with ETS 5/6 and knxd, works perfect with Tasmota flashed devices too.

[iain]

Thanks for the reply, yes probably the best bet. I was hoping for a usb solution but there's no great benefit in that really. I've got a 732 and it works great.

I've spent so long trying to get this usb interface working I was just keen to succeed, it's in the udev rules so I thought it must work

[Matthias Urlichs]

On 19.02.22 02:06, iain wrote:
> I've spent so long trying to get this usb interface working I was just
> keen to succeed, it's in the udev rules so I thought it must work

It possibly did once. Unfortunately I don't have one of these, otherwise
I should be able to fix the problem.

These USB things tend to have quirks, and the fact that they mimic being
a Human Interface Device (in order to work w/o drivers @ stone-age
Windows) doesn't help. They're really designed for the electrician to
arrive, plug in their ETS-equipped laptop, reconfigure stuff, and go
away again; there are exceptions but in general their long-term
stability tends to be sub-optimal, to say the least.

You might have luck with grabbing the current deb branch and building
the current version yourself.

--
-- mit freundlichen Grüßen
--
-- Matthias Urlichs

[iain]

Hi Matthias,

Thanks for the reply and explanation, and thanks for all the great work - really appreciate it

I'll have a go with the latest build but you've shown me the problem with what I was trying to achieve - I was hoping for a usb link to make it more reliable and so things would still work with no network like in a low power situation, but I need to keep the knx bus alive anyway so whether its a usb or ip interface makes no difference. It sounds like I'm introducing more chances of failure with usb over using ip anyway.

Thanks again and keep up the good work

Cheers,

Iain

[Matthias Urlichs]

On 20.02.22 21:55, iain wrote:
> I need to keep the knx bus alive anyway so whether its a usb or ip
> interface makes no difference.

You could use a network dongle on the pi that talks directly to the
KNX/IP interface, bypassing your "normal" network switch.

Using the interface in tunnel mode is best for that.

Alternately you can use a TPUART-based serial interface. The one from
Busware at
https://shop.busware.de/product_info.php/cPath/1_34/products_id/59 is
reasonably good, if a bit expensive.