@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
@georgedumitru I think the best documentation is this thread here on the forum. Byte array reading from communication is also discussed there.
Another helpful tool is definitely the example located at C:\Program Files\REX Controls\REXYGEN 2.50.12.14711\Examples\0203_Function_Blocks_REXLANG.
@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
@georgedumitru
Hello George,
It's challenging to give advice remotely when I can't see what's happening. The data might be in a different format than expected. Could you use Trace() to print the contents of the buffer and share it here?
Hi Mike,
I know that @RexPeter use it on his setups with REXYGEN - maybe he can share some experiences with that.
Kind Regards,
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
@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
Hi Mike,
I recommend checking out the examples in the 0401_Modbus_RTU folder or take a look at the 0121-10_Monarco_HAT_Modbus_RTU_ADAM-4024 and 0121-11_Monarco_HAT_Modbus_RTU_Loopback_USB examples. These are all provided in REXLANG. Hopefully, these examples will provide some assistance.
Cheers,
Jan
@mikeyh
Hello Mike,
Yes, it's possible to use both RS485 for RTU on the Monarco and the USB on the RPi for RTU simultaneously. Check out the illustrative example "0121-11_Monarco_HAT_Modbus_RTU_Loopback_USB." This example features two distinct Modbus drivers: one for /dev/ttyAMA0 (Monarco HAT) and another for /dev/ttyUSB0.
Cheers,
Jan
@georgedumitru Hi,
When we refer to a 28-bit number, does this imply that the number is transmitted within 4 bytes? If that's the case, and the number is in floating-point format, you should use double buf2double(buf[,endian]) REXLANG function.
