pokeys57e vs OW-server

[tkn]

Been reading up on 1-wire extensions and the problems people were having with Loxones suggested wiring. Basically to not use the same Cat 7 wire for lighting, correct?

Then a couple of people still had problems with Loxone's 1-wire extension and I saw two suggestions: pokeys57e and the OW-server.

One complaint about the pokeys57e is apparently it needs to be polled a lot? Is that true for the OW-server? Is there a "best in class" solution here for 1-wire items?

[Duncan]

its not so much about not sharing the cat7 used for switch wiring, its about using the correct wiring for 1-wire:
use screened cat5/6/7 (doesnt matter which)
use a single strand of rj45 starting at the extension and going direct from sensor to sensor, not back and forwards.
keep side branches as short as possible
try not to use connectors for the side branches to sensors - solder if possible
dont use the same cable for anything else
connect the screen to the 0v of the 1-wire bus

if you were to use a pokeys, you can poll around once per 5 to 10 minutes for temperature sensors - it wouldnt need to be any quicker

for more details regarding correct 1-wire wiring see
https://www.maximintegrated.com/en/app-notes/index.mvp/id/148

[Andrew B]

The OW-SERVER is also polled using http. The 1-wire network is read continuously but the whole cycle through all the devices take time that depends on the number of devices and how they are arranged and whether there are errors on the bus. The read from the OW-SERVER is independant and can be at whatever rate you want. I have two of them and read one at one second and the other at two second intervals. This is probably excessive but it also doesn’t hurt anything, and I like to get updates as soon as they’re available.

I’m quite happy with the OW-SERVERs I have. Haven’t used the other device.

[tkn]

Hmmm... so the Loxone miniserver still has to poll the OW-Server.

In this older thread, https://groups.google.com/d/msg/loxone-english/sh9MxIApGJQ/VdVlJOLuDAAJ, someone suggests using an Elexol IO board that can then push UDP requests through. I'll ping Yannick to see if he followed through. Plus the Elexol board has 72 IOs, so should be nicely configurable for a lot of stuff.

EDIT - So they did solve this, and this seems like the superior solution. https://groups.google.com/d/msg/loxone-english/fBz1w4Jexdo/60B_eNJuAgAJ

[Andrew Brownsword]

For 1-wire sensor updates.  It’s not a significant load, and the latency is irrelevant.  For switch I/O latency is a big deal.  Sensor network, it’s not.

On Apr 9, 2018, at 6:19 PM, tkn <ta...@nagpal.info> wrote:

Hmmm... so the Loxone miniserver still has to poll the OW-Server.

In this older thread, https://groups.google.com/d/msg/loxone-english/sh9MxIApGJQ/VdVlJOLuDAAJ, someone suggests using an Elexol IO board that can then push UDP requests through. I'll ping Yannick to see if he followed through. Plus the Elexol board has 72 IOs, so should be nicely configurable for a lot of stuff.

On Monday, April 9, 2018 at 5:27:21 PM UTC-7, Andrew B wrote:

The OW-SERVER is also polled using http.  The 1-wire network is read continuously but the whole cycle through all the devices take time that depends on the number of devices and how they are arranged and whether there are errors on the bus.  The read from the OW-SERVER is independant and can be at whatever rate you want.  I have two of them and read one at one second and the other at two second intervals.  This is probably excessive but it also doesn’t hurt anything, and I like to get updates as soon as they’re available.

I’m quite happy with the OW-SERVERs I have.  Haven’t used the other device.

--
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/uaFf-yL7hL4/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/9c5c5929-e244-45bd-ba13-7bc3e0975a2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.