methodsilikon.blogg.se

Loxone miniserver knx
Loxone miniserver knx












loxone miniserver knx
  1. LOXONE MINISERVER KNX FULL
  2. LOXONE MINISERVER KNX CODE
  3. LOXONE MINISERVER KNX SERIES
  4. LOXONE MINISERVER KNX MAC
loxone miniserver knx

Since all my I/O is already via Elexol (thus UDP) and a TCP-based 1-wire box, I can control it all from any Ethernet device. Mine has 4 CPU 1GHz ARM cores w/ floating point hardware, a GPU (that can be used for calculations… machine learning, here I come.), 2GB of RAM, 2 SD card slots (which can be >4GB), and draws only a few watts.

LOXONE MINISERVER KNX FULL

It can run a full blown Linux or Android OS, supports the full set of development tools including the latest C++ compilers, debuggers, and so forth. Arguably, I’m already past that point, and I haven’t even implemented my custom HVAC logic yet! As a result, I’m pressing into service a single board ARM machine I’ve had on my shelf for a couple of years ( ).

LOXONE MINISERVER KNX CODE

Yeah, hindsight, right? As I mentioned earlier, I’ve decided that (in hindsight) the amount of custom code I want is beyond what the Loxone picoC environment is really good for.

loxone miniserver knx

The Loxone has a lot of nice features and I don't want to abandon it, but if worst came to worst I'm a lot better off than building a purely locked in vendor solution. I could easily replace the Loxone with any other microcontroller board (Raspberry Pi, Wandboard, etc). And that brings up another advantage of taking the picoC + Ethernet route. This is important considering how flakey the miniserver can be while you're debugging picoC code (not to mention Loxone doesn't provide a compiler nor debugger!!!).

LOXONE MINISERVER KNX MAC

And with the picoC I can develop and debug C code on my Mac without disturbing the Loxone (and the household!) while doing development, then port the C to the Loxone with a lot less fuss. The elegance and scalability of an Ethernet-based solution is really nice. On the control side the IO controllers now have a total of 24 outputs that can drive relays, and 80 inputs from wall switches. Those will be used for more precise processes, whereas the 1-wire network is fine for things that can wait up to a couple of minutes for a reading. I'm going to use these for 8 thermistors (and 5x voltage dividers to reduce 24v -> 5v) that I can read faster and more reliably than my 1-wire sensor network. so I now have 8 analog-to-digital inputs (10 bit precision) working, and (if I needed them) a pair of DACs. I've just gotten the code for the latter working (it talks SPI so its a bit different), and it is working very well. The second IO24 has 2 of the 8-way darlington transistor breakout boards (to control pumps & valve & fan relays), and 1 Elexol Analog I/O breakout board. I'm also now building up a new board for my mechanical room with a second IO24 (so now I'll have 1xIO72 and 2xIO24). I have actually moved all my UDP code into picoC because I discovered that there is a Loxone bug at the moment if you try to do some work via the virtual UDP function blocks and some via picoC. If you want 8 independent relays that can be in any state, then you need to do something to compute the 8-bit value (like I did). Your solution of sending Hx09 works fine if you only want those 2 relays on at a time. Use google chrome to translate from germanīrian, I didn't see your post until now. However, the cheapest is probably the pokeys57e, a 55 input/output ethernet board for 60 euros

LOXONE MINISERVER KNX SERIES

If you just need a few extra inputs for almost nothing, and these are in the same location such as a single switch location, you can use a resistor ladder or zenner diode ladder to create a series of voltages at the switch end from the 24v feed, and use an analog input connected to a state block, with the blocks output connected to a binary decoder - each input switch connects a different voltage to the input, and the state block works out which input is triggered based on a range of voltages - eg 1st input is 1v, and the state block has the first positive outpu Using 1-wire chips that replicate the presence/absence of an i-button Transfer some of your inputs to knx using knx switches or the abb concentrator (both expensive, but knx switches look pretty) Pi or arduino with i/o board and ethernet/virtual inputs to loxone miniserver There are a number of different ways of achieving this, some more complex than others














Loxone miniserver knx