Official EVOK API

• M

  Problem with running Evok on Unipi 1.1 + RPI4
  • marioverhaeg  

  5
  0
  Votes
  5
  Posts
  19
  Views

  M

  Hello @marioverhaeg, I have replied you on your email - please provide us with more info. Then, I copy the right solution to this topic.
• N

  EVOK shows no I/O - Neuron L513
  • Negropo  

  3
  0
  Votes
  3
  Posts
  17
  Views

  N

  Hello @marioverhaeg, here ist my evok.log with debug=on. Evertything seems fine, but it still won't work. I only see Analog Input & Output from 1.01. I also made a snapshot from my evok.conf And as I saw it on your post made an output from dpkg -l | egrep "raspberrypi|evok|unipi|python" Output dpkg Maybe @Martin-Kudláček could help me too? Kind regards Negropo
• T

  Sysfs interface support for extension modules (Pt.2)
  • tja  

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  Hi @tja, this is not planned, nor it makes sense from the architecture point of view. The SysFS endpoints are generated from the Unipi kernel module, which is aware of the HW it is running on, but not aware of any peripheral devices. The only way right now is the Evok, or you can directly poll the devices over ModbusRTU. We have some internal discussion from time to time about adding support for extensions to our ModbusTCP service. So far, no work has been done on that part. Best regards, Martin
• M

  Check date/time of last action on relays
  • mglowinski  

  3
  0
  Votes
  3
  Posts
  8
  Views

  M

  ok, thx:)
• J

  Measure current SCT013
  • Jell-IT  

  3
  0
  Votes
  3
  Posts
  7
  Views

  J

  Okay, thanks!
• S

  After installation of a xG18 extention I get a Server Error 500 for the Rest Json
  • Stoeffel  

  22
  0
  Votes
  22
  Posts
  154
  Views

  S

  As promised, here is the feedback. The problem has definitely been solved. Many thanks for the help Kind regards Stefan
• S

  How to handle Softwarecrash
  • sknobloch  

  2
  0
  Votes
  2
  Posts
  12
  Views

  

  Hello @sknobloch, if your program is some script or binary, you should use systemd for starting and keeping alive. This tutorial shows how to work with it: https://medium.com/@benmorel/creating-a-linux-service-with-systemd-611b5c8b91d6 Best regards, Martin
• S

  Watchdog settings via EVOK
  • smontosa  

  3
  0
  Votes
  3
  Posts
  11
  Views

  M

  Hello @smontosa, please try to download the current version 2.4.10. The issue should be fixed. Please note that watchdog settings (same as other parameters) are stored in RAM memory by default. To burn it into non-volatile memory (FLASH), use the appropriate coil 1003 or call the separate REST request on the same endpoint with parameter nv_save=1.
• K

  Broken dependencies during EVOK installation
  • khachvla  

  3
  0
  Votes
  3
  Posts
  14
  Views

  K

  @Martin-Kudláček After flashing the image everything works fine. Thank you
• M

  Is there a way to set relays to default state after RaspberryPi reboot?
  • mglowinski  

  2
  0
  Votes
  2
  Posts
  33
  Views

  M

  Hello @mglowinski, sorry, but this feature is not supported in Unipi 1.1 series products. Please consider buying Neuron/Patron series PLCs which can do it.
• M

  Unipi 1.1 watchdog?
  • Maxiba  

  2
  0
  Votes
  2
  Posts
  15
  Views

  M

  Hello, unfortunately, the Unipi 1.1 does not have a watchdog device. You can see all available devices/circuits in reply to the "all" GET request. Example (can be invoked from your web browser): http://<your_unit_IP>:8080/json/all
• M

  How to count impulses on digital input via EVOK API?
  • mglowinski  

  2
  0
  Votes
  2
  Posts
  14
  Views

  

  Hello @mglowinski, the Evok doesn't have such logic. If the DI doesn't support counters (which does not on Unipi 1.1), the Evok is not able to share this information. This has to be done in your software. Best regards, Martin
• M

  Recommended way of connecting analog sensor
  • mglowinski  

  3
  0
  Votes
  3
  Posts
  17
  Views

  M

  Thx for explanation!
• M

  How to control relay extension board via EVOK?
  • mglowinski  

  2
  0
  Votes
  2
  Posts
  15
  Views

  M

  To make extension relay module (EMO-R8) working with EVOK below steps needs to be done: Open /etc/evok.conf file Uncomment relays assigned to EMO-R8: Each this line begins with a character ; This character must be removed for all lines related to the configuration for EMO-R8: ; ;Example of 8xRelay extension module addon (EMO-R8) on address 0x21 ; [MCP_2] i2cbus = 1 address = 0x21 [RELAY_9] mcp = 2 pin = 7 [RELAY_10] mcp = 2 pin = 6 [RELAY_11] mcp = 2 pin = 5 [RELAY_12] mcp = 2 pin = 4 [RELAY_13] mcp = 2 pin = 3 [RELAY_14] mcp = 2 pin = 2 [RELAY_15] mcp = 2 pin = 1 [RELAY_16] mcp = 2 pin = 0 Save /etc/evok.conf file Restart evok
• A

  Modbus CRC errors, rs485 extensions on Neuron
  • Achilleas Kotsis  

  5
  0
  Votes
  5
  Posts
  18
  Views

  

  Hello @Achilleas-Kotsis, the issue is not with the unipi-kernel-module, but with the unipi-firmware 5.52. We have removed it from our repository and advise to downgrade to 5.50 (and flash it to the HW via /opt/unipi/tools/fwspi). We are working on the fix. Thank you again for reporting this issue and have a nice day, Martin
• M

  Reading and sending data using UART via EVOK API
  • mglowinski  

  9
  0
  Votes
  9
  Posts
  47
  Views

  M

  I made it work. I enabled Serial in RaspberryPi Setting and and used /dev/serial0 and it worked. Thx @martin_triska for help!
• M

  Accessing I2C devices via EVOK API
  • mglowinski  

  5
  0
  Votes
  5
  Posts
  19
  Views

  M

  @martin_triska, thx for a tip. Indeed it worked quite well:)
• M

  Curl works, Python http.client.request not fully
  • Maxiba  

  3
  0
  Votes
  3
  Posts
  23
  Views

  M

  Thank you for the answer! I am using the websocket API now, as this suits my requirements the most. Have a nice day!
• N

  Read 1wire temp sensor on Axon
  • netman  

  2
  0
  Votes
  2
  Posts
  14
  Views

  No one has replied

• B

  installation of Evok on actual raspian fails
  • burnscm  

  4
  0
  Votes
  4
  Posts
  13
  Views

  

  Hello @burnscm, thanks to you, we have discovered that the package unipi-kernel-modules v1.54 for Neuron has been incorrectly built. It is now fixed and new OpensourceOS image has been built. I recommend to download the said image (https://kb.unipi.technology/_media/files:software:os-images:neuron-opensource-os_image-20210105.0.zip) and do apt update && apt install -y evok. Thank you for understanding and have a nice day, Martin