Weinzierl 570 multi IO KNX

Hidde Beumer

unread,

Dec 23, 2019, 5:26:22 PM12/23/19

to Loxone English

Hopefully you can help me.

I have a Weinzierl 570 multi IO KNX device, I want to transfer the 24V Digital inputs and 24V Digital outputs from my loxone extensions to this device.

However, the loxone extension seems to use + 24V and the weinzierl -24V ... for door contacts this is no problem, but for the (EPV) motion detection and for the 24V NIKO PIR this seems a problem ... anyone experience with this? or maybe tips?

Cheers,

Hidde

Rob_in

unread,

Dec 25, 2019, 3:23:23 AM12/25/19

to Loxone English

Hi,

DC is all just relative, so when you say it's it's zero and minus 24v (rather than zero and plus 24v) sounds like you've just got the polarity reversed (by mistake?).

Robin

P.S. That looks like a pretty good value module - just over 6E per I/O (albeit probably requiring a coupling relay for any heavy output loads).

Hidde Beumer

unread,

Dec 25, 2019, 8:51:08 AM12/25/19

to Rob_in, Loxone English

It looks really neat indeed. I’ll report back when I get it working. It’s for 24V only... but I will have some wago relais connected to it for 16A 230V loads.

The thing I don’t quite understand is that for Loxone digital inputs I need to insert 4.7k Ohm pull-up resistors for the EpV PIR and also for the Niko PIR. Not sure if I need to remove these for the Weinzierl.

Hidde

--
You received this message because you are subscribed to a topic in the Google Groups "Loxone English" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/loxone-english/Y8SYEBPpico/unsubscribe.
To unsubscribe from this group and all its topics, send an email to loxone-englis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/loxone-english/516bc540-e690-4f5b-ac09-ae146e13dcee%40googlegroups.com.

Duncan

unread,

Dec 26, 2019, 8:51:34 AM12/26/19

to Loxone English

if you use it for outputs, the thing you are operating eg a relay must be connected to +24v and the output itself is open drain, i.e. it becomes the 0v of the output

it looks like the inputs have a pullup resistor built in so its likely that an input needs to be switched to 0v rather than 24v to trigger it

Capture.JPG

Hidde Beumer

unread,

Jan 15, 2020, 2:35:35 PM1/15/20

to Loxone English

Reporting back about my experience. I have to say that this device is a great piece of equipment. Raally nice to have a small LCD and buttons to test things, without having to update through ETS and/or Loxone. you can simply use the buttons to test inputs/outputs and see the reqults directly in the wiring closet. The other nice thing is that it has a USB interface which allows ETS to program the device (As well as other devices on the bus), this helps me to hedge my loxone bets even more.

I migrated all my 24V digital inputs and 24V digital outputs from the loxone environment over to the Weinzierl, no issues so far.

In general I have everything now on KNX with the exception of my wall switches (Loxone touch, tree) and analogue inputs/outputs. The only issue I have is that it seems to sometimes take a few seconds before an input from the touch switches is converted into a relay switching on the KNX side. any ideas if/how to speed this up?

Cheers,

Hidde

Rob_in

unread,

Jan 15, 2020, 2:46:29 PM1/15/20

to Loxone English

That sounds sweet... aside from the delay!

To check what's causing the delay, you can open up your Loxone KNX bus monitor and check if the delay is between pressing the touch switch and KNX datagram transmitted from Loxone (ie, it's in Loxone) or between the KNX transmission and the relay actuating (ie. it's in the KNX Multi IO device). At least that will narrow down the search for a solution.

Robin

On Wednesday, 15 January 2020 20:35:35 UTC+1, Hidde Beumer wrote:

Reporting back about my experience....

Hidde Beumer

unread,

Jan 15, 2020, 3:09:22 PM1/15/20

to Loxone English

I'll check that. the delay is not int he multi-IO, since it's not playing a role at all in this scenario, could it be that the KNX bus is somewhat busy/chatty...?

Hidde

Op woensdag 15 januari 2020 20:46:29 UTC+1 schreef Rob_in:

leo no

unread,

Jan 15, 2020, 4:43:18 PM1/15/20

to Hidde Beumer, Loxone English

I have experience the same, but I noticed that in one knx In triggered with a loxone wired input there are 0,30 to 0,45 seconds, but in another input on the same knx device triggered again with a loxone in it works instanly, I don’t know the reason, so don’t bothers me at all, but is what it is.

Enviado desde mi iPad

El 15 ene 2020, a las 21:09, Hidde Beumer <hidde....@gmail.com> escribió:

--
You received this message because you are subscribed to the Google Groups "Loxone English" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loxone-englis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/loxone-english/418c685f-0318-4e26-9c3e-85ba8b0c143f%40googlegroups.com.

Rob_in

unread,

Jan 16, 2020, 3:26:22 AM1/16/20

to Loxone English

The ETS5 bus monitor page shows the bus utilisation level at the bottom, so you could watch that while running some tests and see if it is a factor.

Hidde Beumer

unread,

Jan 16, 2020, 5:38:54 AM1/16/20

to Loxone English

interesting, I'll check that out... yesterday I've ensured that for the KNX outputs I'm no longer sending the messages repetitively. This seems to have solved the issue. When I looked at the KNX monitor it looked like Loxone pops a timer every x-seconds and then repeats all of the messages to KNX (which then looks like a spike of messages on KNX), not very smart. instead they should smoothen things out more. Lesson for me is that I should only repeat those messages which I feel need repeating, the rest not.