@andmo Yep, the text file contains an example of ST code which parses communication with a custom RS485 ASCII protocol.

@andmo Check the custom serial protocol in Example project in our download section for Mervis

Hello,

please check the description. The block will be documented in the next release of Mervis. Please note that this block still needs testing and is not recommended for project deployment (we cannot guarantee it work 100%).

Description
!! Without time setting, the block is down!!
The block is used to control the blinds either with the up/down command or with the percentage of position and rotation. For the proper functionality of the block, it is necessary to define times of the variables.
The STOP button works by pressing both command buttons at the same time.
perc_rot is inactive when leaving the top position for a period of rotation_time.
calib_time it is the time that serves to calibrate the position. Calibration runs from the angle of the direction to the starting position at the top (0%). Ideally, set it up slightly longer than the full rollout time.
rotation_time is the transition time between the minimum and the maximum of the blinds opening. For the proper functionality of the block, it is important to correctly set this value together with rolling_time.
time_delay is the protection period that is triggered by the falling edge of the command up (down), During which the command down (up) is blocked. (Does not apply to the STOP button)

Inputs
Input Type Description Default value
calib_time TIME The time that calibration is running (relay up is switched ON). 0s
cmd_down BOOL Command to scroll down. FALSE
cmd_up BOOL Command to scroll up. FALSE
hold_time TIME The time it takes to hold the button to automatically roll up/down. 2s
perc_pos USINT Setting the position of the blinds in percent. 0%
perc_rot USINT Setting the position of the blinds in percent. 0%
re_calib BOOL Rissing edge of the signal will start the calibration. FALSE
rolling_time TIME Time distance of limits positions (0-100%). 2min
rotation_time TIME Time distance of limits rotations (0-100%). 0s
time_delay TIME Protective time for changing the scrolling direction. 500ms

Outputs
Output Type Description
relay_down BOOL Relay down is switched ON.
relay_up BOOL Relay up is switched ON.

@jelle the levels can be different if you configure the jumpers to use different power supply, if you are using the onboard 12, then the GNDs are on the same level

@mdturnerphys Unfortunately no. But for example, you will need to create a Server channel on one side (A) select port different than 502 and map your variables to holding/input registers/coils so you can read and write to them from the other (B) side. You can map the variables to Units for example 0-10 (if you need more, just map it as you wish). On the other side just create a custom device on Modbus TCP channel (B), set the IP address and port of the (A). Then on (B) create a read group with starting register 0 and 10 number of registers and map the variables from (A) to data points (create datapoint by right click, assign read group...). Check F1 help of Mervis for 'Modbus' there is a nice explanation. You can also check eg. the Inepro example project from our downloads section.

@jelle You have to enable internal pull-up resistor for the GPIOs and set them as inputs

@joe160781 Discussed in email communication

@mdturnerphys Hopefully the next release will be published within a few weeks in the meantime, you can create Modbus TCP connection between those two units

@nash_78 Does not seems to be related to the previous topic. It seems you are using UniPi 1 guide instead of UniPi Neuron - https://store.codesys.com/unipi-neuron-for-codesys-sl.html

@roberts_lando Right now Evok supports only broadcast message to one of the DALI compatible channels to set the intensity of the lights (on/off/50%...). We do definitely want to implement more functionality (like addressing, scenes,...) in the future, but a little push from our customers is needed :)