@Martin-Kudláček Hi
After a long time of trying and many tutorials, I made it
to switch my relays on my Unipi 1.1, to read temperatures and everything with ModbusTCP and Nodered. When I see it now, it's very easy, thank you for the great board and the software.

Hello @FabioIT,
the development of Codesys support has been dropped altogether. The Codesys can be still used on Neuron via ModbusTCP. The Unipi 1.1 doesn't have IOs accessible via ModbusTCP, only scattered over I2C, GPIO and so on - nothing easily configurable.

Best regards,
Martin

The development and support of the Codesys plugins for Unipi products has been discontinued by the developer. Unfortunately, there's not much we can do about it. We asked them to release the package as Open Source... More info at https://kb.unipi.technology/en:sw:03-3rd-party:codesys#codesys_on_unipitechnology_products

It seems like the whole connection up to Codesys is fine. When I delete the UniPi_AI I2C module and instead of that insert the MCP3424, I do get data, but it doesn't seem correct. Even if I leave the Unipi AI module and then use the I2C_master.read(16#68, ADR(baReadBufferV), 4); command, it shows data in the buffers that varies when the input voltage is adjusted.. Does anyone have more info on the UniPi_AI I2C chip driver?

Hello I tried to do a clean all and now is working.

Hello @arc,
we actually don't use CODESYS at all nor we are able give a proper support. The packages have been created by @DavidCozens of COSOSO. Try contacting him.

Thank you for understanding,
Martin

Hello @sbr,
the IOs of the Neuron are not connected to the GPIOs. Instead, they are accessible via local ModbusTCP server (you can see the Modbus Registers Map)

Or better yet, check the official Neuron plugin for Codesys: https://store.codesys.com/unipi-neuron-for-codesys-sl.html?___store=en&___from_store=default

Best regards,
Martin

Hello @Raph7454, all of the IO on the Unipi work the same as other CODESYS devices. Use the device tab to map the IO into your application. The data sheet provides guidance on each device. The package also installs a new application template so that in one step you can create a new UniPi application with all devices installed ( you will just need to add the expansion module).
Regarding how to download, login etc. CODESYS for UniPi is adding device drivers to CODESYS for raspberry pi. There is a large active forum of users on the CODESYS forums. I suggest that for general CODESYS questions you will find answers to most of your questions already posted there.
I

A new version is now available in the store updated for CODESYS 3.5.14.0 and supported on a new version of Unipian.

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

@andré sorry to be so slow responding. Somehow I missed the post. There are instructions in the data sheet on how to use groups 2 and 3.

As a summary getting the IO to work with Group1 was fairly involved, and given that it is identical across all Neuron devices a function block instance is created and the mappings from registers is done automatically. For groups 2 and 3 you will need to map the IO using standard CODESYS features. To make this simpler, all of the Registers and Coils for these groups are named, there are also function blocks provided that will assist with converting between registers and larger data types.

Hi,

thank you. It is better now.

One more question about programing... how to retrive the temperatuer from sensor?
I can read few parameter except temperature value.

0_1534847503859_b61c7a7e-9188-4d40-8193-6aa2f4c6422a-slika.png

It looks that the issue I have is related to the /boot/config.txt file (dtoverlay=w1-gpio). Is this OK?

0_1534882451084_e3347d05-ec00-42fb-a0cb-14d96b8c33cd-image.png

Thank you in advance.

@OlivierP, what type of pH and EC sensors do you use? Would you recommend some?

Thanks in advance!

Hi..i am a new user here. As per my knowledge many times you would not use the power from the USB-UART converter. The target device will provide power to the UART. All you need to connect is Rx,Tx and Ground. The TTL signals come in different flavors. 5V, 3.3V and 1.7V being common. This is all the more reason why not to use the power from the UART adapter. Put 5V TTL on 1.7V TTL pins and something will fry. Use no power from the UART adapter.

percentage calculator

Hi @TriathletC!

You will need to use the UniPian image for CODESYS, but you will also need to buy the CODESYS for Neuron plugin.

For more information see the UniPi Neuron compatibility section on our CODESYS SW help section