Hi Martin, do you have any suggestions on how to resolve. I tried disabling node-red to see if that worked but no success. Am open to suggestions on what to try. If I have some extra time I will try a fresh SD card with the setup you verified for Stefan (specified vanilla neuron OS, install evok, and use the same evok.conf) to see if that will work.

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

Keeping it with my weekly tradition: https://blog.mhemeryck.com/2021-07-13/home_automation_cabinet This one might be a bit more interesting in that it gives some more details on the actual wiring I did.

Hello @HVAC-Arthus First, I recommend downloading and installing the latest Mervis IDE and Mervis OS available here: https://kb.unipi.technology/en:files:software Then open the project in a new IDE and save to convert the project to the new version. Before converting to the new version, we recommend that you always create a project archive with a suitable name. If you use the RaspberryPi 4 computing module for Unipi 1.1 / Lite, this should also solve your problem, as support for these computing modules was added only in the last version. With my RaspberryPi 4 and Mervis v2.4.0 your project works.

Hi @Csevi, in short - the 1-Wire hub is passive device, which helps with the "linearization" of the star topology. You can find complete information about 1-Wire here: https://kb.unipi.technology/en:automation:02-glossary:1wire-hidden Best regards, Martin

Hello @daminou53 , we have released the Patron kernel (more precisly the "Zulu" kernel - Zulu is the codename for the SBC). Here's the repository: https://git.unipi.technology/UniPi/zulu-linux. Here are the config files: https://git.unipi.technology/UniPi/zulu-linux/-/tree/zulu_5.4.70/arch/arm64/configs Best regards, Martin

Hello @CKB, it is LM358 for amplification of the analog output.

Hello @DAWaller, can you please describe your application in more detail? Websocket connection is provided by Evok software. Node-RED uses this type of connection to communicate with the I/Os. Do you see the connection outages from Node-RED running on the same unit? What displays the Node-RED debug console?

Hi Sabina, The best way to communicate between SW Mervis and third party devices is to implement the Modbus protocol on these devices. Subsequent operation and modifications are simpler and faster. Another great advantage is that this protocol basically allows you to operate multiple slave devices on one serial line. In this case, Openport is a functional block that takes care of opening the port, ie its reservation within the system. In the input string (def) for FB io.openport it is necessary to enter for UART port 1: "def: = 'serial: 1: 9600,8, N, 1';". I also enclose a tested code example in ST for Unipi 1.1.

ok, thx for feedback

@Martin-Kudláček Do you maybe know how i can check current speed of I2C, which is set over device tree overlays?

Hello @pavel_nadr, we have released a new version of MervisIDE, which fixes the problem. Please, follow the information in this news: https://kb.unipi.technology/en:00-start?redirect=1#new_mervis_ide_os_v240_released

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

Hello @HPC, since Modbus doesn't know anything about data types, it is up to both the master and slave to come up with an exchange format. The registers are 16bit, but the ASCII is only 8bit. The data has to be aligned somehow, or maybe two consecutive characters can be stored into one register? Either way, the goal will be to iterate through the string and convert every item of the string array to byte. Best regards, Martin

Thx for explanation!

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

Hello, I just followed what you told me yesterday, but that doesn't change anything. In my .csv file, the values ​​that I save its data every second and not every tenth of a second ... For the use that I make of it, it is absolutely necessary that I can obtain more values ​​per second. PICOUL Mathurin