Hi Yannick,

Please look in the datasheet that can be downloaded from the CODESYS store along with the software. In there are instructions for accessing channels in groups 2 and 3. Basically you created channels as you would in a standard codesys modbus device (although all registers and coils are identified by name. You then map these into your application. There are a number of utility function blocks in the library that may be helpful.

Group 1 is the same across all Neuron devices, so I created the drivers to automatically create channels and map the data into an automatically created function block. If users find this helpful then I could do the same for the other groups. I would be interested to hear if users find this automated mapping helpful, or if they prefer to map the channels used themselves.

regards David

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

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

Version 1.0.2.0 is now available for download in the CODESYS store, this is only a bug fix release fixing a minor defact and updating to later versions of CODESYS and Unipian. The new version is built on CODESYS 3.5.14.0 and is supported on version 1.9 of Unipian. Please see the datasheet in the store for details.

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

With the release of a new version of Unipian (V1.9) and also the release of CODESYS 3.5.14.0 I have had to temporarily remove UniPi Neuron for CODESYS from the CODESYS store. I aim to release a new version by 17/1/19, I will post progress here.
Please accept my apologies for any inconvenience, I am working to provide a solution as soon as possible.

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 Oliver,

I’m going to need more detail to be able to help?

What does your configuration look like?
What exactly is the error message and where do you see it?

How is the physical device connected and configured?

Is anything sent from the port?

Are there any further device diagnostics?

Unfortunately with all serial communications, including modbus, just one configuration error or wiring error on the master or slave will mean the communications doesn’t work. The process to solve this is really to carefully check every step.

If I was debugging your system, I would first extract as much detail on the error as possible to see if that helps.

Try answering these questions.

Does the master send a modbus request?
Is it at the right baud rate, parity etc?
Does the slave see the request?
Do it’s comms settings match?

Is the UID correct?
...

Hi Oliver,

You need a modbus com device for each port you wish to use. Then under those a modbus master device, and then a modbus slave for each slave connected to that port.

The modbus com port needs to be set to com 1 for the first port, 2 for the second..,

So if your slave devices operate with the same serial port settings you could use different modbus addresses for each and connect them to the same port, or put one on each port.