Neuron - Addressing GPIO from C++
@Boy-Lenssen The fastest is definitely only the TCP Modbus since more SW between your calls and the HW causes more delays. The TCP Modbus server can handle easily thousand of requests per seconds. Evok does not scan that fast (by default twice per second but can be re-configured).
If you disable the mervis system (sharkrt + configtool) on the MervisOS, than there is nothing else I am aware of that will try to write to the card. So everything except Mervis shoudl be read-only, but I cannot guarantee there is no chance of corruption.
There is no ready solution for easy shutdown (except standard linux features like cronjob).
@tomas_hora I fired up the system with the december 6th version of Mervis software image (https://files.unipi.technology/index.php/s/zTmrEbQEvifNd6W?path=%2FSoftware%2FMervis).
what is the login for it? I have the Neuron connected to my screen and only get to the login.
http://192.168.1.102/rest/all (where I checked it's IP address via my router) does not return anything. It gives a 404 in the browser and wget -qO- http://192.168.1.102/rest/all does nothing. http://192.168.1.102 shows a page with a login button, so the server is running.
- The mervis services are still running, thus also its web interface on port 80 where you see the page with login. See the port of evok in /etc/evok.conf
Btw. I suggest you to disable the sharkrt and configtool services first or even get started with a clean raspbian (lite) so you do not get confused by some of tuneups that are implemented in the MervisOS.
@tomas_hora so it is normal not to have access to the REST api? I thought this was available on the Mervis image.
I just wanted to get some basics to try out, that is why I took the Mervis img
@Boy-Lenssen The mervis image does not contain the newest version of evok that supports Neurons (since it is not needed). That is only available on github as above
@tomas_hora ok, going to try it on Jessie Lite...
I am completely confused about the software that is available atm. Can you do a summary on what is what?
I see Mervis had TCP modbus, but no REST API, which seems to be part of EVOK?
I wanted to try out someting using the REST API, but on Mervis, there is only modbus?
Do I see it correctly, and Mervis contains Modbus as it uses it to communicate itself? And is EVOK a collection of UniPi API possibilities?
Edit: in meanwhile, I have installed EVOK without any issues on a Jessie Lite img and could address the REST API. The Pi I had it installed on was not the one in the UniPi. I have to use some pliers to get the SD-card out of the UniPi to replace it ;) will do that tomorrow, enough for today ;)
Edit the next morning :) : I think I understand now. EVOK is something that is in development with API's and (in future?) control the UniPi via some UI, like Mervis
Mervis is an off-the-shelve solution that already existed and works with the UniPi...
@Boy-Lenssen :) You got it all right. Evok and the TCP Modbus server are opensourse solutions for people who want to do their own implementation.
Mervis makes UniPi all in one PLC system including scada, HMI designer and database.
@tomas_hora Ok, I made the mistake by following the readme instead of getting the current branch :p
I restarted this morning, get -qO- http://192.168.1.16/rest/all does not show anything. I selected option 2 (Neuron) during setup, so all should be ok.
Can you tell me how to read / write via rest (or another way?)...how do I know what the ports are called? Also I see no web interface when going to http://192.168.1.16
What am I doing wrong?
Edit: OK! Adding port nr 8088 to the command makes it work! wget -qO- http://192.168.1.16:8088/rest/relay/2_14 --post-data='value=0' now changes the value! \o/ thanks!
Edit2: websocket via Python script is also working perfectly! But as you said TCP Modbus is faster, I might go with that one...
@tomas_hora I got it working with Modbus, websockets and REST, very cool!
You advised to use Modbus because of the speed. To see changes on the input, I need to poll the port. Do websockets push any changes so polling is not necessary?
When should I use registers to change a value, and when should I use coils?
@Boy-Lenssen Great :) Yep, the websocket automatically notifies all clients about a change of state at DI. However by default it does only twice a second so check your config.
If you want to set only a single for example relay then use coils. If you want to set multiple relays at once, use registers. But be aware that by using registers, you set all the relays mapped to the registers, so you can accidentally set relay to a different state (eg. if the state of relay changes from a different place in your app between the read and write to register).
@tomas_hora Ok, coils it is :p
ok, notification is perfect! It is not a problem if it takes half a second, would be nice if i could set it down to 5 times a second, but as you mention here, that is possible :)
I think I'm going to go with websockets then!
@tomas_hora I changed the config of
50, as I really need to know when an input has changed for a split second. This way it checks every 20ms and that seems to be working ok. Are there any caveats when setting the frequency so high?
@Boy-Lenssen You should be OK.