Announcement of a new pre-release Version 3
-
Is this beta version backwards compatible? If I use the new studio do I have to update old programs and the Monarco HAT run time as well?
Also is there any beta documentation/manuals for the new studio?
Cheers
Mike
-
@mikeyh Hi Mike,
Thank you for your question. As a rule of thumb, we recommend using the same version of REXYGEN Development tools and RexCore running on your target device. Please, update the runtime as well.
@Studio Documentation: Basic documentation for the new Studio is part of the installation - just open the TrayMon and select "Documentation" -> "REXYGEN Studio - User Guide".
In the meantime, we are working on documentation for many enhancements integrated into the Studio. We will keep you posted.
Kind Regards,
Tomas -
-
@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
-
@cechurat Hi Tomas,
All sorted now. Not sure what happened. Rebooted it a few times and suddenly I could connect.
Cheers
Mike
-
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
-
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.
Cheers
Mike
-
@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
-
@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.
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 -
@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.
-
@cechurat Ok, makes sense.
Thank you
-
@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.
Hi Mike,
does this error with Modbus persists? Can you provide more details, please? E.g. error messages or Rexygen System log?
Cheers, Tomas
-
@cechurat Hi Tomas,
The naming issue seems to of gone. What I still get though when using the "passive" register method is this.
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
-
@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
