REXYGEN Community Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Login

    Announcement of a new pre-release Version 3

    Development tools
    beta studio
    2
    17
    1.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      MikeyH @cechurat
      last edited by

      @cechurat Thanks Tomas,

      I have done that, what would cause this error?
      aec7a4b0-e17e-46a5-82a4-4fc36a1d3672-image.png

      Cheers

      Mike

      cechuratC 1 Reply Last reply Reply Quote 0
      • cechuratC
        cechurat @MikeyH
        last edited by

        @mikeyh Hi Mike,

        This error can be caused by several issues:

        • RexCore is not running on the target device - try to reboot the device and reconnect.
        • RexCore is running on a different port (you need to change it manually via rexcore.cfg file)

        Let me know if it helped.

        Cheers, Tomas

        M 1 Reply Last reply Reply Quote 0
        • M
          MikeyH @cechurat
          last edited by

          @cechurat Hi Tomas,

          All sorted now. Not sure what happened. Rebooted it a few times and suddenly I could connect.

          Cheers

          Mike

          1 Reply Last reply Reply Quote 0
          • M
            MikeyH
            last edited by

            Just looking at the DWM, Does REXYGEN now have it's own database? Is that linked to the Archives or a sperate thing?

            Right now I use Influx as a database, can I replace that with this?

            Cheers

            Mike

            cechuratC 1 Reply Last reply Reply Quote 0
            • M
              MikeyH
              last edited by MikeyH

              Has how the way Modbus arrays work changed in V3?

              I can no longer seem to get arrays to work. Read a large group of registers, then use passive items to read from the array.

              I see the new option of array in the item setup, but I keep getting a naming issue.
              a0ddba2d-94fd-455b-889c-eae102d09c76-image.png
              b4980b87-1c03-4881-82f1-5433c181c995-image.png

              Cheers

              Mike

              cechuratC 1 Reply Last reply Reply Quote 0
              • cechuratC
                cechurat @MikeyH
                last edited by

                @mikeyh said in Announcement of a new pre-release Version 3:

                Just looking at the DWM, Does REXYGEN now have it's own database? Is that linked to the Archives or a separate thing?

                Right now I use Influx as a database, can I replace that with this?

                Cheers

                Mike

                Hi Mike,
                I wouldn't call it a database but there is an archive subsystem (which was there also in version 2.XX). There were not many differences in this between versions 2 and 3. However, improvements were made in the display of archived values (so far there was just the command line utility called RexArc to export the data from the archive to CSV/JSON).

                It can be an option for the Influx DB, however, it depends on how you further process the data.

                Cheers, Tomas

                M 1 Reply Last reply Reply Quote 0
                • cechuratC
                  cechurat @MikeyH
                  last edited by

                  @mikeyh said in Announcement of a new pre-release Version 3:

                  Has how the way Modbus arrays work changed in V3?

                  I can no longer seem to get arrays to work. Read a large group of registers, then use passive items to read from the array.

                  I see the new option of array in the item setup, but I keep getting a naming issue.
                  a0ddba2d-94fd-455b-889c-eae102d09c76-image.png
                  b4980b87-1c03-4881-82f1-5433c181c995-image.png

                  Cheers

                  Mike

                  Hi Mike,

                  you are right - the flag "As array" is new. The documentation says: As Array (V) – The values are transmitted to the REXYGEN algorithm in the form of an array. If multiple values are involved, a From block is utilized to connect the array signal from the driver, along with one or more VTOR blocks.

                  The use case behind this is that you will read a large group of registers, sign it as "As array" and within the task you use just one From flag and decompose it manually.

                  Another approach is to decompose the group of registers by passive items and use From / INQUAD / INOCT / INHEXD blocks in your task.

                  What naming issue are you getting?

                  Cheers,
                  Tomas

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    MikeyH @cechurat
                    last edited by

                    @cechurat Ok, that makes sense. Do you have an example of that?

                    The naming error I get seems to be from naming the bock and item/array the same, for example. But only when using the array setting.

                    The other thing I get now is the below older way of doing it, passive. No longer works. I get no data from the driver. Even though the registers are ok. If I call SrG on it's own it works. But when SrG is passive and the array is used I get no data.

                    63ba61d7-92d9-40f6-8b6e-e6eece3c8be4-image.png
                    e1e3679f-2ff3-415c-b1fa-287fb0c44fda-image.png

                    cechuratC 1 Reply Last reply Reply Quote 0
                    • M
                      MikeyH @cechurat
                      last edited by

                      @cechurat Ok, makes sense.

                      Thank you

                      1 Reply Last reply Reply Quote 0
                      • cechuratC
                        cechurat @MikeyH
                        last edited by

                        @mikeyh said in Announcement of a new pre-release Version 3:

                        @cechurat Ok, that makes sense. Do you have an example of that?

                        The naming error I get seems to be from naming the bock and item/array the same, for example. But only when using the array setting.

                        The other thing I get now is the below older way of doing it, passive. No longer works. I get no data from the driver. Even though the registers are ok. If I call SrG on it's own it works. But when SrG is passive and the array is used I get no data.

                        63ba61d7-92d9-40f6-8b6e-e6eece3c8be4-image.png
                        e1e3679f-2ff3-415c-b1fa-287fb0c44fda-image.png

                        Hi Mike,

                        does this error with Modbus persists? Can you provide more details, please? E.g. error messages or Rexygen System log?

                        Cheers, Tomas

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          MikeyH @cechurat
                          last edited by MikeyH

                          @cechurat Hi Tomas,

                          The naming issue seems to of gone. What I still get though when using the "passive" register method is this.
                          68fc0941-a43f-4163-9784-76023fba03fc-image.png
                          7f49dbeb-9cd0-46bc-9c53-6f0659aa81f4-image.png
                          4a8ea19d-e271-4376-b6e1-f56074d5214a-image.png
                          93a3acb4-85f0-41d4-9f1c-ecbaf0e1586f-image.png
                          If I don't use the "passive" method and call SrG on it's own, it works fine. Are my "passive" settings not correct?

                          Cheers

                          Mike

                          cechuratC 1 Reply Last reply Reply Quote 0
                          • cechuratC
                            cechurat @MikeyH
                            last edited by

                            @mikeyh Hi Mike,

                            According to the screenshots provided, I would suspect that the Response timeout parameter in MBDrv is too short - did you try to enlarge it?

                            I also use passive tag in my projects and don't face any issues when the communication parameters are correctly set.

                            One more question: What is the RS485 Baudrate set in the Monarco Driver?

                            Kind regards
                            Tomas

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post

                            This is a community forum for REXYGEN users and fans. Detailed information can be found at REXYGEN homepage.

                            There is also an outdated REXYGEN community forum.

                            Powered by NodeBB.