• Connecting/communicating with a Modbus device

    6
    0 Votes
    6 Posts
    5k Views
    D
    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? ...
  • RTC - UniPian - Codesys

    4
    0 Votes
    4 Posts
    3k Views
    O
    Sharing the way I solved it, feel free to comment. [image: 0_1526107594620_clock.PNG]
  • Understanding the Modbus Registers Maps

    3
    0 Votes
    3 Posts
    3k Views
    O
    Thank you again for the extensive answer!! It is clear for me (atm ;) )
  • UniPI Analog Input

    2
    0 Votes
    2 Posts
    2k Views
    D
    I must have missed this post somehow. The most likely cause is that the variable that the channel is mapped to has been optimised out because it is otherwise unused.
  • using Modbus overlay in Codesys

    13
    0 Votes
    13 Posts
    9k Views
    D
    @tom84 The mA problem is an issue with older hardware. UniPi Neuron for CODESYS will be updated to resolve the issue at the next service release. Please note the issue does not occur on current Neurons. No Neuron products shipped since the release of UniPi Neuron for CODESYS will see this problem.
  • Adding Group 2 and 3 - Neuron L503

    3
    0 Votes
    3 Posts
    2k Views
    O
    Thanks David, I've got it figured out!
  • Reading digital input from switch

    4
    0 Votes
    4 Posts
    3k Views
    O
    Thank you for the clarification, this is exactly what I did... but I must have missed something, now it works :) I don't think it is needed to add the other channels already, seems easy enough.
  • Multiple Modbus Read Registers Access by an Array of Elements

    2
    0 Votes
    2 Posts
    2k Views
    D
    @mikeardy Consider this as an alternative. I've created 500 holding registers [image: 0_1524082533025_img1.png] In my program (it could be ina GVL) I have created an addary of 250 UDINT. [image: 0_1524082629032_img2.png] Then I was able to map all of the registers in one go [image: 0_1524082699632_img3.png] For generic CODESYS questions I suggest trying https://forum.codesys.com/, for many generic CODESYS questions there will already be an answer posted.
  • Configure Neuron S103x as Modbus Slave

    5
    0 Votes
    5 Posts
    3k Views
    M
    Thank you. I will try.
  • Neuron S103 and fast input (or counter)

    5
    0 Votes
    5 Posts
    3k Views
    M
    thank you
  • UniPi and Codesys 3.5 (library references issue)

    3
    0 Votes
    3 Posts
    3k Views
    D
    Thank you for posting the resolution, I am sure others will find this helpful. Please note that this is expected behaviour when using any CODESYS project with different versions of the devices to the ones the project was developed with. The template project that is part of CODESYS for UniPi was developed with a particular version of CODESYS, yet will work with many different versions just by updating the device as shown. The project and package are only updated if there is an enhancement or a bug fix. Once you have created a project, if you wish to update to a new version of CODESYS for Raspberry Pi, or CODESYS for UniPi you would need to update any changed devices in the same way. I hope that helps explain why the step is required.
  • Acces Group 2 and 3 at Neuron L503

    3
    0 Votes
    3 Posts
    2k Views
    Yannick SteinY
    Thank you very Mutch, thats what I'm looking for. Now if´ve got it.
  • UniPi Neuron and Variable Retain, WiFi, Bluetooth

    2
    0 Votes
    2 Posts
    2k Views
    D
    Hi Mike, This has been an on-going topic for CODESYS on the Raspberry Pi. The Raspberry Pi does not have non-volatile RAM, and so the built in PERSISTENT and RETAIN variables within IEC61131 do not function. The neatest solution I have seen is discussed in this forum posthttps://forum.codesys.com/viewtopic.php?t=5722 where 3S have provided some sample code that can write retain variables to a file on demand and then restore at power up. Be careful about writing too frequently to the SDCard as you increase the chance of file system corruption if the power is interrupted whilst writing. Regarding wifi, CODESYS relays on the underlying Raspbian configuration. So yes you can enable WiFi and it will work. There is a discussion on how to do this on the UniPi forum https://forum.unipi.technology/topic/438/wifi-instead-nic-mervis the process is the same. I have no experience of using Bluetooth with CODESYS. I suggest contacting 3S or using the CODESYS forum. regards David
  • CODESYS on UniPi Neuron installing issues... help please!

    6
    0 Votes
    6 Posts
    4k Views
    M
    Many Thanks!
  • UNIPI V1.1 Lite

    4
    0 Votes
    4 Posts
    3k Views
    D
    @DavidCozens I just stumbled across this old thread. I can confirm that CODESYS for UniPi does work on the UniPi Lite, just ignore the parameters for IO that is not fitted.
  • unipi 1.1 + pi3 and 1Wire DS18B20 bus problem

    Moved
    12
    0 Votes
    12 Posts
    9k Views
    D
    @lefrank01 thank you for sharing your tips. I have also had this reported once or twice and on each occasion starting from a clean install of Raspbian, installing CODESYS for Raspberry Pi and then running the script that ships with CODESYS for UniPi has resolved users problems.
  • UNIPI V1.1 analog output problem

    3
    0 Votes
    3 Posts
    2k Views
    D
    I have seen this issue reported a couple of times. On each occasion it was resolved by a clean install of Raspbian, followed by an install of CODESYS for Raspberry Pi and running the install script that installed as part of CODESYS for UniPi (See the data sheet for install instructions).
  • Why

    3
    0 Votes
    3 Posts
    3k Views
    D
    Support for the EMO-R8 is underway and will be available later this year.
  • Help about UNIPI v1.1 on codesys

    4
    0 Votes
    4 Posts
    4k Views
    D
    @Alverman Development for supporting the EMO-R8 is now underway and will be available later this year
  • Does UniPi support CODESYS?

    3
    0 Votes
    3 Posts
    3k Views
    H
    Thank you :-)