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.

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.

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.

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.

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.

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

ok, thx:)

Okay, thanks!

As promised, here is the feedback.
The problem has definitely been solved.
Many thanks for the help

Kind regards
Stefan

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

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.

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

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.

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

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

Thx for explanation!