@martin_triska said in 1-wire sensor and modbus sensor:
in this case, you have to tie the wires manually ON THE SENSOR. According to the photo, you have to connect dark-green and light-brown wires together ON THE PCB
Yes, that did the trick!
Thanks for the education and superb support here Martin. Really enjoy using your products.
You are absolutely correct sir!
Thanks a lot for your help - now it works like a charm. I've used Neuron's RS485 for communication with xS11 and separate USB dongle with CH340C chip (a bargain really, $2.7 from CZ shop) for communication with PRO1 energy meter through the same Node-RED setup getting data from /dev/ttyUSB0.
It's a pity that I cannot edit my previous post ^^ - feel free to edit it with a big warning that you cannot combine multiple processes on one serial (which is absolutely logical, but for us: HW newbies not obvious).
thanks for your information.
I have connected a 4 wire cable very close to the three wire sensor and connected the data line to 2 wires in order to use the hub. At the moment it works.
Hello @juntiedt,
this sensor comes in the 3 wire connection + shielding. You can connect it to the 1-Wire hub, ideally as a last sensor. Please consult the 1-Wire hub pinout https://kb.unipi.technology/en:automation:02-glossary:1wire-hidden
@wavoigt We have tested HMI terminals from weintek like this one https://www.unipi.technology/weintek-mt8051ip-p198?categoryId=29 via Modbus RTU (RS485). Works well but the SW setup is a bit complicated.
Mervis has recently gained BACnet server support so you can connect higher verions of Weintek displays which support BACnet with Neuron or Axon via BACnet/IP
Alternatively Mervis has a web based HMI so you can also use this with any web browser while on the same IP network.
@kalophain if 1wire sensor is loaded to the channel, it's ID is stored in the non-volatile memory and so it should be restored upon boot of the gateway. Since the memory is tested on every piece, the probability that it no ok is really low.
The DIP switch is used for firmware change and has no affect to the store/load of the sensors.
Please make sure that:
the baudreate in Neuron and GW is the same [image: 0_1569339863243_GW_pic2.png]
check that the addresses stored in the GW and loaded from the neuron are the same [image: 0_1569339910879_GW_pic.png]
upload the latest FW 1.24 to the GW
loadand save the sensor to the channel multiple times
Dobrý den @beny44,
náš 1-Wire hub je pasivní zařízení, které spolu s našimi 4 vodičovými čidly napomáhá vytvoření správné 1-Wire sběrnice - tedy serializované a bez odboček.
Pokud se rozhodnete zapojovat čidla vlastní, pak použijte schéma pro aktivní napájení, ne parazitní. Odpor ve výše uvedeném schematu vynechejte.
Hello @qcomp we don't have direct experience with these devices, but it is quite simple to connect them to our PLCs through Digital Inputs. I recommend looking into our Counters functionality which can give you more precise results during high water consumption periods. The process is the same as measuring electricity consumption through S0 output of energy meters - 1 pulse equals to some defined amout of energy / water .
As you can see on the very last photo, we used TacoSetter Tronic
http://www.taconova.com/en/products/pv/hydronic-balancing/1/tacosetter-tronic/13/
Output temperature 0,5-3,5V
Output volume flow 0,5-3,5V
In theory it should work the same as any other extension we have, though we cannot guarantee it, since some devices deviate from the standard protocol in one way or another. Either way you will need to create a custom ModBus map, whether you are using Evok, Mervis or something else.
@dickesc Not sure, they are also using I2C and some microcontroller. You would have to check their documentation and ours documentation if there is no conflict with GPIOs, I2C, SPI,...
Hello @viestivelho,
1Wire has only one data pin from its design, and that is pin 7 on the master = the UniPi. Besides that we use another wire, pin 6, to serialize the bus as much as possible to maximize the reliability. That pin is wired only in the temperature sensors and HUBs which we provide.