@c0fec0de E/N stands for the parity as Even or None. In your case there might be a small bug in the firmware so the meaning might be switched. So Up can be None and Down can be Even. The same is for the speed settings.
You should set both to different addresses and then set 19.2/9.6 DOWN (On) and E/N UP(off) restart it (power cycle) and you should be able to communicate using 19200 without parity.
Make a new HMI project, select a new image and then try to get a analog indicator from your MDI project into your image.
You have to make a connection (mostly default connection) in the properties to a so called shark image file (.exs) from your (perfect running) Mervis IDE project with software version 220.127.116.11674. At the moment that you click 'retrieve' to get a list off all parameters in the MDI you will get this error.
At this moment is is not possible to make a HMI project with HMI version 0.9.16.715 from a MDI project with version 18.104.22.168674
@wizro_pl Ok, sorry now I understand. You can use any of the comparsion functions (taken from the help): GT > decreasing sequence, GE >= Monotonous decreasing sequence, EQ = Equality ,LE <= Monotonous increasing sequence, LT < Increasing sequence, NE <> Inequality
Writing your own function blocks is taken as a advanced function so the user actually know what is doing. But actually the only thing that is simple mode doing is that it automatically generates variable, which you can do also by right click on the device using the autogen.
Of course Mervis changes that. You have to choose which is the default access to the IOs. It is not a good idea to control output from two points without letting know each other about the change. But if you really want to, you can set the variable to be written only on change (right click on the device on the modbus channel and make custom).
I was finally able to get back to working on it. I was able to get the AO board working, for some reason the address I was trying was not working. I change the DIP switches and entered the address in Mervis and good to go.
I do not have any experience with DMX but it looks like a simple protocol similar to RS485. Do you have any experience running DMX right on the RS485? Or you could get for example a Modbus RTU (on RS-485) to DMX converter which is pretty easy in Mervis. You would just need to map the registers to a variables in your project.
I have one 1-wire temp -meter and 2 external I2C relay-cards (emorelay-boven and emorelay-beneden).
These relay-cards and the unipi card are supplied by separate adapters, so the grounds are not coupled.
Can this have influence on the speed?
if in the program 2 relays are switched at the same time (each relay on a separate relay card), i can see that they are switched one after the other. at least 0.5 sec after each other.
I would be nice if all relays could be switched in 100ms.
I use the older mervis runtime (version 2.5) on a Rasberry Pi B+, is the last runtime faster or is there no difference is speeds.
there has been some work already done on such thing. However it has never been finished and there is also no documentation for it so I recommend using the function blocks (like PID, delays etc) that are already included in Mervis.