@tradlost.se Basically yes, but since I do not know much about your board it is hard to tell.

@cvdd https://github.com/UniPiTechnology/neuron_tcp_modbus_overlay is only for Neurons and will not work for the UniPi 1. For UniPi 1 there is only Evok as API from us. But if you need Modbus and do not want to use the HTTP REST api, websocket or JSON RPC, then take a look at someone implementing Modbus for UniPi 1

@ubee Thanks for the tip! I will take a look at it.

@Merv,

I have the same problem. It doesn't help to change the log level in the service file. It still continues dumping info about every read attempt which is annoying. I guess the "I" in the log indicates log level is Info. And it remains I whatever level you set.

Try reinstalling the Modbus server as described here: https://github.com/UniPiTechnology/neuron_tcp_modbus_overlay

@HarishKumar
The evok itself is not designed to handle the logic of your application. That's why we call it API.

It is using Tornado which means the server itself runs in one loop so you need to have all the program behavior ready before it is called mainLoop.start(). So if you run an infinite loop anywhere in evok, you stop everything else (reading, setting, all APIs, ...).

So I suggest using that APIs, it is much more easier to implement and you have the same functionality. But if you would REALLY want to do it in evok, you would have to prepare your program in a function, all tasks that would take more time would have to be decorated as coroutines and the call has to be yielded in order not to stop the main loop. The logic behind this is a little bit complicated to describe in one post :)

@tomas_hora Awesome! When I have time again for this project, I'll try it!

@tomas_hora

BTW, I absolute love Neuron! <3 I'll put it everywhere.

Having a simple REST API is a bless.

Thank you for all your hard work that goes into UniPi!

@zeus I will think about it how to make it possible, Thanks for the tip: https://github.com/UniPiTechnology/evok/issues/11

@fipsi72 You can place evok behind a proxy of course...

@Juergen Relay 1 does not exists. Check the web interface of evok for correct identification. The correct identification is eg. 2_1

@Kitaps IC stands for Integrated Circuit. What code?

@Boy-Lenssen You should be OK.

Thanks for the report. I will take a look at it :) https://github.com/UniPiTechnology/evok/issues/10

@Merv Thanks a lot for the info!

@HarishKumar It's ok. That's why the forum is here. If you visit the web interface of evok, you will see the numbers of IO of the Neuron you are using.

In general it is numbered as X_Y where X is the number of group (1-3 depending on S/M/L model) and Y is the number of the Di/Ro/...

So for example you would address DI1.4 as a string 1_4 with device type di.

I have a Raspberry Pi 3 running Jessie with fresh installation of Evok. I am also using Python 3.4. I received the error, "TypeError: 'NoneType' object is not subscriptable." The workaround Tomas referred to on Nov 25, 2016, worked, but I first had to install jsonrpclib-pelix, a version of jsonrpclib updated for Python 3. The standard jsonrpclib does not work with Python 3.

Thansk a lot. Could you create a pull request or a bug report on github?

hi Tomas,

sorry for my recent post!
I have solved the problem!
I had to delete the cache of my chrom browser and now it works!

have a nice Weekend