Topics created by MikeyH

@cechurat Hi Tomas,

Yeah I see, thank you.

Cheers,
Mike

@MikeyH Hi Mike,

This is related to the communication timeout - inspect data length with respect to baudrate and timeouts.

All REXYGEN error codes here in Docs: https://www.rexygen.com/doc/ENGLISH/MANUALS/BRef/BRef_ENGap3.html#x488-487000C

Cheers,
Tomas

@MikeyH Hi Mike,

This error is triggered when something is preventing Studio from writing to the Project location. Do you have all related folders available for read and write?

If the issue persists, can you share a minimal project with us? Thanks

Cheers, Tomas

sorry, I've just worked it out using the Bitwise demultiplexer

f8e2817e-be2b-4795-8b4f-ac8a5581218b-image.png

@cechurat Hi Tomas,

I will try and record this this week, sorry for the delay.

Cheers,
Mike

@cechurat Hi Tomas,

That worked thank you, I used apt-get which didn't seem to update the REX stuff.

Thank you
Mike

@Jan-Reitinger Hi Jan,

Awesome thank you. I'll give it a try this week and let you know.

Cheers,
Mike

@Jan-Reitinger Hi Jan,

All sorted, thank you.

Cheers,
Mike

@cechurat Hi Tomas,

No problem, and thank you for your help as always.

Cheers,
Mike

@MikeyH Hi Mike,

thanks for the report. It seems that the Archive viewer in Diagnostics is limited to the 16 signals.

I have prepared a Python script for converting the Archive timezone - find it attached.

How to use the script:

export the REXYGEN archive using the RexArc command line utility. For details execute command RexArc --help put the exported file in the same directory as the Python conversion script run the conversion script using the following command: python archive_timezone_converter.py input.csv output.csv offset

Parameters meaning:

input.csv - original file exported using RexArc output.csv - output file offset - The timezone offset to apply (in hours).

Script file: archive_timezone_converter.py

Let me know if it helps.

Cheers, Tomas

@MikeyH Hi Mike,

you are right - this is new in v3. The parameter SigNames is passed to the TRND block and can be read in Watch Mode in REXYGEN Studio (just double-click the TRND block) - see the signal annotation in the right part of a window.
It is also read by HMI component TRND which displays the information directly to the HMI (you can override the information by editing the HMI component parameters).

Cheers,
Tomas

@MikeyH Hi Mike,

Code "-102" stands for Timeout - see Doc: https://www.rexygen.com/doc/ENGLISH/MANUALS/BRef/BRef_ENGap3.html#x360-359000C

How often do you write the values?

PS: In version 3 we have introduced native support for the PostgreSQL database. Have a look at the documentation if you find it useful: https://download.rexcontrols.cz/partner/testing/rexygen/doc/3.0.0.15811/ENGLISH/MANUALS/PqDrv/PqDrv_ENG.html

Cheers,
Tomas

@MikeyH Hi Mike,

I'm glad it works for you 😉

For the "variable decimal point" I would use blocks MUL and CNDR. CNDR configure so it reflects the changing of the gain according to the value.

You will probably find many other solutions which will lead you to the desired behaviour (e.g. SSW for switching gain according to the value)

Hope it helps.

Cheers,
Tomas

@MikeyH Hi Mike,

Please, make sure to tick the "GenerateRexHMI" parameter as well.

Cheers,
Tomas

@cechurat Hi Thomas,

Thanks for the replay.

I'm about to get some pi 5's to run REXYGEN on, so that's good to know. I won't be fitting Monarco HATs to these so no issue there.

But will be getting one once you release the updated design etc

Cheers,
Mike

@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