I think I will stop using Mervis as main IDE as it only works with the image you provide. I think a better approach would be having a runtime that can be installed in an existing SD with upgrading features, this approach makes each update very hard expecially if you have to work with lot Unipi devices at same time... I would have to reinstall the image in each device each time an update comes out than reinstall all other softwares I need

Ok thx !

ok. In which directory should I look for the evok software?

Thank you Tomas, it was very helpful. Now it working. I only switch off parity on external modules and communication started :-)

hi tomas,

the new version (2.05a) seems to be fixed regarding that strange message.

thx for helping,
wbr,tja...

@Vesa-Kauppinen No, you have to use converter. @Vesa-Kauppinen I have seen this one http://www.a2s.pl/en/mbus10-rs485-p-7941.html but have not tried it... It should not be expensive and it can handle up to 10 units on the bus.

I'd rather send it directly, it's only in source code on git and compiling it is not trivial.

You should have the link in your messages now.

@Eanna
You can use the relays to send a pulse out, or the analog output

@nash_78 Does not seems to be related to the previous topic. It seems you are using UniPi 1 guide instead of UniPi Neuron - https://store.codesys.com/unipi-neuron-for-codesys-sl.html

@dsurname it's now a bit offtopic from the thread description, so please start a new topic which will better describe your issues. At first, you do not need to worry about the RUN led. If you try to read a DI, the behavior of RUN led will change.

/dev/ttyAMA0 is the UART of RPi, not the RS485 of Neuron. If you want to access the RS485, you need to install UniPi drivers (currently is part of in Evok https://github.com/UniPiTechnology/evok, in future, there will be Debian packages). Once installed, the RS485 ports are will be available for example at /dev/extcomm/0/0

Hi @martijn-hemeryck,
We changed the repository's name to unipi-python-lighting and it resides here: https://git.unipi.technology/UniPi/unipi-python-lighting

@sennevds

My notes:

reading of inputs: works reasonably well right now. I did create my own implementation (based on golang) that basically just polls the states of the switches continuously and pushes out any change as an MQTT event -- processed directly by home assistant. The polling implementation works on the background and eats about 5-10% CPU (still tolerable, might still be improved), switch behavior feels instantaneous for me. writing outputs: my implementation is also able to again translate incoming MQTT events into toggle outputs. Here, you don't need to poll directly (the MQTT handler itself is able to deal with that). Alternatively, you could look into home assistant modbus, to send a modbus command directly from home assistant. My implementation completely sidesteps the whole modbus translation phase, so if you'd be using it for reading, writing would make sense as well. pushing out DALI commands: I did receive my axons S605 not that long ago, been fiddling with it, see https://forum.unipi.technology/topic/966/dali-interface-integration-in-python-dali . I have the feeling support for this product is still in its infancy, as well as the python-dali library it depends on. If I would have some more low-level documentation on it, I would very much like to take the development on this to a higher level!

If you'd like more input on how to use the unipitt binaries, and you feel a bit tech-savvy yourself, I'd be happy to help you set it up. That way, I can improve the project to make it more robust a portable for other interested users.

@martin-kudláček said in Another home automation project:

our din rail mounted relay - and connect it to DO or RO. Awkward, but it works.

In most of my projects i use external relays to extend the life of embedded hardware relays, so it's not that awkward. I use mostly relays with coil voltage 230 V AC with UniPi 1.1 but now with the shared COM port and neuron power suply, i'll go with coil voltage 24 V DC.

Hello @phil, @StevenHendrickx
to login to the MervisOS command line via SSH, you need to enable the SSH first. This behaviour changed in the image 1.7, where the SSH is disabled by default as a security measure. In older images, the SSH was enabled.

To enable the SSH, you need to create file named "ssh.txt" in the partition called "boot" on your SD card. This is the same process as with Raspbian. You cannot enable the SSH once the UniPi is running. You need to take out the SD card, put it in your PC a create the file there.

The default username is "unipi" and password is "unipi.technology". To switch to the "root" user, run sudo bash.

Is this description sufficient or do you need to clarify it a bit more?

Best regards,
Martin

Hi @Martin-Trojan,

This is just one possible solution, but you can use a custom ST FunctionBlock with this code (use the name "DigitalMemoryMultiplexer" if you do use it):

FUNCTION_BLOCK DigitalMemoryMultiplexer (* EXTENDS //base type IMPLEMENTS //interface type list *) VAR previous_inp_1: BOOL; previous_inp_2: BOOL; previous_outp: BOOL; END_VAR VAR_INPUT inp1: BOOL; inp2: BOOL; END_VAR VAR_OUTPUT outp: BOOL; END_VAR INIT previous_inp_1 := inp1; previous_inp_2 := inp2; previous_outp := inp1; END_INIT IF inp1 <> previous_inp_1 THEN outp := inp1; previous_inp_1 := inp1; ELSIF inp2 <> previous_inp_2 THEN outp := inp2; previous_inp_2 := inp2; ELSE outp := previous_outp; END_IF; previous_outp := outp; END_FUNCTION_BLOCK

And connect it like this:
alt text

The DO_2_01 is set as DirectSwitch Trigger and the WEB_LIGHT_BUTTON is tied to a HMI Digital Setter. Whenever you are using DirectSwitch remember to set the Debounce value on the DI sufficiently high for your input device.

Again, there are many other options for doing this, including using two HMI elements on top of each other (Digital Indicator and Digital Setter).

Here is the project file, for reference: https://www.mediafire.com/file/1o8kq9iici2qc8g/ForumProject.7z/file

@martin-kudláček Okay, thanks. After posting yesterday I managed to figure out the communication errors I was getting, so preventing the NaNs from messing up the chart is less of an issue now.

Vše vyřešeno pomocí Weintek cMT-SVR-100. Vyčítám data do své SQL databáze. Problém s časovou značkou vyřešen pomocí vlastní značky v SQL databázi.
Chápu, že jiní by to dali lépe a levněji, ale bohužel já programovat neumím.

@tomas_hora
hello, I found a solution to turn a digital setter into push-Button
I put a flip-flop that reset after 2 seconds the variable on which points the digital setter HMI
https://www.dropbox.com/s/dvf4toi76z35kxw/Capture d'écran 2019-01-10 09.56.36.png?dl=0

Hello @Raph7454, all of the IO on the Unipi work the same as other CODESYS devices. Use the device tab to map the IO into your application. The data sheet provides guidance on each device. The package also installs a new application template so that in one step you can create a new UniPi application with all devices installed ( you will just need to add the expansion module).
Regarding how to download, login etc. CODESYS for UniPi is adding device drivers to CODESYS for raspberry pi. There is a large active forum of users on the CODESYS forums. I suggest that for general CODESYS questions you will find answers to most of your questions already posted there.
I

@tomkling Thank you for your information. I also figured out 502 is used on debugging. So it is important.