Official EVOK API

• A

  unipi-kernel-modules-dkms 1.108 breaks the system on kernel 5.10.103-v7+
  • Achilleas Kotsis  

  2
  1
  Votes
  2
  Posts
  10
  Views

  K

  @Achilleas-Kotsis Thanks for your hints about downgrading. Worked for me, too. For reference the commands here: apt install unipi-kernel-modules=1.106.1.20220308~buster-1 I got the version by apt-cache policy unipi-kernel-modules. /KNEBB
• 

  Wrong device model in EVOK (Patron)
  • Vesa Kauppinen  

  2
  0
  Votes
  2
  Posts
  7
  Views

  M

  Hello @Vesa-Kauppinen, The 'dev' field describes an object type (similarly to di or relay) so the key has to be constant regardless of the PLC series. You are right, this can be a little bit confusing - it's a piece of history ;-). Now, we will add the new field of a family containing Patron/Neuron/Axon string. The 'dev' field fix is a breaking change of the existing API and will be subject to change within an upcoming new Major version.
• K

  EVOK a xS11 chyba
  • kratas  

  4
  0
  Votes
  4
  Posts
  59
  Views

  C

  Toto by mne také zajímalo. xS11 ovládat můžu, ale DirectSwitch rozjet nedokážu. Zkoušel jsem vyčíst status registru pomoci mbpoll, ale tam se mi nepodařilo získat smysluplná data.
• B

  Evok api and https protocol
  • Brzezinol  

  1
  0
  Votes
  1
  Posts
  14
  Views

  No one has replied

• N

  EVOK shows no I/O - Neuron L513
  • Negropo  

  6
  0
  Votes
  6
  Posts
  44
  Views

  N

  In the event monitor of FHEM I can see also the following message when I make a "get all": "2022.01.02 14:17:08 3: Neuron (NeuronL513) error decoding response: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 5830 (before "NaN, "circuit": "3_0...") at ./FHEM/00_Neuron.pm line 424." As I can see the error occurs on AI 3_01 or an other till AI 3_04.
• M

  Disturbed communication on I2C bus
  • mglowinski  

  4
  0
  Votes
  4
  Posts
  34
  Views

  M

  It is a problem related to power-supply. It was some voltage peaks while connecting anything to the same circuit as power-supply. I've a better one (Phoenix Contact) and it's working stable now. Topic closed.
• M

  This topic is deleted!
  • mglowinski  

  1
  0
  Votes
  1
  Posts
  12
  Views

  No one has replied

• M

  Problem with running Evok on Unipi 1.1 + RPI4
  • marioverhaeg  

  6
  0
  Votes
  6
  Posts
  29
  Views

  M

  The issue was caused by a combination of 64bit Linux kernel and bundled pigpio subsystem (used for peripheral access). After pigpio updating, Evok works on a 64bit platform properly. This change will be part of the next release.
• T

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

  2
  0
  Votes
  2
  Posts
  14
  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
  159
  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
  15
  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
  15
  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
  16
  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
  15
  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
  19
  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