As you can see on the very last photo, we used TacoSetter Tronic http://www.taconova.com/en/products/pv/hydronic-balancing/1/tacosetter-tronic/13/ Output temperature 0,5-3,5V Output volume flow 0,5-3,5V

@tomas_hora I'm not sure that made any difference. I have to do some more testing, (For some reason the IDE has been crashing on me a lot when I try to do certain things like delete outputs or function blocks.) but what I think is happening is that the correct logic is being uploaded to the PLC, but the "debug" output (e.g. when using manual mode switches) loses track of things after the update. Exiting and restarting the Mervis IDE, it seems to come back again.

@msoenen That is because Mervis is not able to use SSL/TSL connections to the SMTP servers. As Google describes here https://support.google.com/a/answer/176600?hl=en you have to use aspmx.l.google.com server in order to be able to send the email using an unencrypted connection but using this server you can only send the mail to Gmail/Gsuite users.

@msoenen The status should be CONNECTED in the PROXY field. If you see disabled, then the configuration is not done properly. Anyway, Mervis requires the port 6677 to be allowed for outgoing connection in order to make the proxy work.

@martin-trojan I just encountered the same error: "there is not declared any retval output for function 'testfunction'. FBD functions have to have retval explicitly declared" After some experimentation, I just created a bool output on the right side called "retval". It's set to "False" by default but it seems happy with True also. Not sure how this is used in FBD, but it might be needed in ST scripts to determine if there were errors encountered while the block tried to execute. (e.g. if it returns > 0 then stop) etc. Perhaps one of the unipi team can comment on what it is for? Anyway - it seems to build without errors now.

Hello @PR-Reger, Generally speaking that is always the safer approach, if possible. Regards, Tomas

Hi @PhilesG! That's good to hear, though a bit concerning that it doesn't work with all flash drives. I'm not sure what we can do about that, but we'll have a look at it again. The size limit in the web interface is unfortunately inserted quite deep into the system; essentially it's the amount of memory-mapped drive space that is reserved for holding the file sent over the network. Which is also why the flash drive method works, as the file is instead stored on the drive. At any rate - glad you managed to get it to work!

@tomas_hora hello, I found a solution to turn a digital setter into push-Button I put a flip-flop that reset after 2 seconds the variable on which points the digital setter HMI https://www.dropbox.com/s/dvf4toi76z35kxw/Capture d'écran 2019-01-10 09.56.36.png?dl=0

@robl ok it works, but I was forced to delete the old variables and replace them in the program it is a pity that there is no table with troublechoottings in which could look during malfunction but without the system does not default

Hello, No noise. No light. No luck. Only the green led turned on. So I suppose I have to contact support. Thanks for your help and quick answers !

Sorry for the confusion. UniPi had removed the UniPian image and so I removed UniPi Neuron for CODESYS from the CODESYS store. I have since been working with UniPi and a new Image for UniPian was released today. The UniPian image will work with CODESYS 3.5.12.x and the release UniPi Neuron for CODESYS. 3S have also released a new Version of CODESYS which requires a rebuild and retest of UniPi Neuron for CODESYS before the product can be re-enabled in the CODESYS store. I anticipate that this will be released by 17/1/19. I will post here when the new version is available.

@dnevin The outputs are assigned as for any IO device in CODESYS. Please check the CODESYS help for how to map IO. There is also a UniPi Neuron library included in the package which makes it easier to handle the data types which span more than one register. Please see the help for the library in CODESYS.

Hi Ludwigj, I'm sorry to say but there was a compatibility issue with the version of UniPian that you are using. If you use the version referenced in the datasheet then you should see no problem. UniPi have released a new Version of UniPian V1.9 today that I believe resolves the issue. regards David

Hi @Martin-Trojan, This is just one possible solution, but you can use a custom ST FunctionBlock with this code (use the name "DigitalMemoryMultiplexer" if you do use it): FUNCTION_BLOCK DigitalMemoryMultiplexer (* EXTENDS //base type IMPLEMENTS //interface type list *) VAR previous_inp_1: BOOL; previous_inp_2: BOOL; previous_outp: BOOL; END_VAR VAR_INPUT inp1: BOOL; inp2: BOOL; END_VAR VAR_OUTPUT outp: BOOL; END_VAR INIT previous_inp_1 := inp1; previous_inp_2 := inp2; previous_outp := inp1; END_INIT IF inp1 <> previous_inp_1 THEN outp := inp1; previous_inp_1 := inp1; ELSIF inp2 <> previous_inp_2 THEN outp := inp2; previous_inp_2 := inp2; ELSE outp := previous_outp; END_IF; previous_outp := outp; END_FUNCTION_BLOCK And connect it like this: The DO_2_01 is set as DirectSwitch Trigger and the WEB_LIGHT_BUTTON is tied to a HMI Digital Setter. Whenever you are using DirectSwitch remember to set the Debounce value on the DI sufficiently high for your input device. Again, there are many other options for doing this, including using two HMI elements on top of each other (Digital Indicator and Digital Setter). Here is the project file, for reference: https://www.mediafire.com/file/1o8kq9iici2qc8g/ForumProject.7z/file