Posts made by cechurat

@stepan-ozana Hi Stepan,

Thanks for the data file.

I can confirm that I'm able to run the project using ResCore on localhost. I'm also able to run your project in the Simulation mode invoked via Studio.

Please, try out the following: In the project folder (where all the mdl files and Python files are stored), create an empty folder simroot and try to run the simulation via Studio again. (This tells simulation mode to use the simroot folder as a root folder for RexCore)

You can also try to run the simulation from the command line:

1. Copy the compiled project myproject_exec.rex into folder C:\ProgramData\REX Controls\REX_<VERSION>\rexcore\ and rename it to exec.rex
2. Run command: "C:\Program Files\REX Controls\<REXYGEN_VERSION>\Bin\RexCore.com" -C <PATH>, where <PATH> is relative/absolut path to <PROJECT_FOLDER>\simroot\rexcore\rexcore.cfg file. This config file is already prepared for simulation. You can change its parameters if desired.

Please note that using RexCore.com instead of RexCore.exe keeps the process running in the command line along with all the System Log printouts, which could provide a clue as to what is preventing you from using the simulation mode.

Let me know if you have any progress on this.

Kind regards,
Tomas

@stepan-ozana Hi Stepan,

Thanks for sharing your experiences. Please, can you provide kanal2_od_000645.csv file? It is to be loaded in compile time in block CNA_uU.

Thanks.

Tomas

@stepan-ozana Hi Stepan,

Thank you for your advanced question.

The proposed solution can look like the following:

1. Run RexCore from the command line with specific simulation parameters:
   RexCore -z simulation.enabled=1

Simulation-related parameters (other parameters can be found at /rex/rexcore/rexcore.cfg.help):

simulation.enabled=1 // turns on simulation mode
simulation.tickmin=0 // minimum tick time in milliseconds (if calculations finish earlier, sleep is done; default 0, so no sleep is done)
simulation.steps // number of ticks after start, then the run stops
simulation.start // date and time before the start of the simulation; default 0, i.e. Rex epoch 1.1.2000 00:00:00

2. Load set of input parameters - use SILO/SILOS function block or STATELOAD/STATESAVE function block.
3. At the end of the simulation, you can store the results using the same FB as mentioned in 2. It is also possible to read the result values via the REST API. The RexCore will continue running after the specified tick count, but the blocks will no longer be executed.

If you have any additional questions, just let me know.

Regards,
Tomas

@MikeyH Hi Mike,

Thanks for the details. Currently, there is no direct support for such data representation.

For small-scale, I can imagine using the CNDR function block. You can also check the STEAM function block, but it appears the data you require is missing there.

There is also the possibility to use, e.g., Python or a C library if available.

Let me know your thoughts on this.

Regards,
Tomas

@MikeyH Hi Mike,

Thanks for your post. Please can you add more details about your intention? Are you looking for a solution to store or use such a dataset in your control algorithm? Or is the goal to visualise similar diagrams on the HMI screen?

Kind regards,
Tomas

@gninaus Hi Guenther,

DWM is not ready for Trixie yet. We are working on it. I will keep you posted when Trixie is supported.

Cheers,
Tomas

@MikeyH Hi Mike,

It's a duplicate of this one: https://forum.rexygen.com/post/1707 - check the project timing.

Cheers,
Tomas

@har Hi Har,

I'm sorry, but we are not able to debug third-party Python code for you.

If you made it work under plain Python, then you can send the data to REXYGEN using the REST API. Have a look at "0302-03 REST API Python Bash etc", which sends data to REXYGEN using Python.

Kind regards,
Tomas

@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 related to the timing issue of the Modbus Driver. It means that the Modbus Driver exceeded the allotted time 800x from the executive start for some reason. In your case, I would inspect the timing of the whole project and also the diagnostics of tasks related to the Modbus driver.

Without knowledge of your project, communication frame and timing, I'm not able to provide more details.

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

@har Hi har,

Thanks for the additional info. We are not able to provide free support on this since it's your custom Python script. The error is not related to the Rexygen ecosystem. It seems that the CPU dispatcher is being initialised multiple times.

Tomas

@har Yes, the issue is in initialisation of the Python Block. If you wait a second with the mouse on the message
it will show you more instead of "..." which might help you to find the issue easier.

Cheers,
Tomas

Hi har,

thanks for your question. Please, can you share System Log? There should be some error which is preventing RexCore from running.

Cheers, Tomas

Hi Phil,

Thanks for your question. Please, have a look at example "0305-01 Hour Meter" - it should do the job or point you in the right direction.

Let us know if it helped.

Cheers,
Tomas

Hi Phil,

Thanks for your question.

Yes, it is possible using AlarmsTable HMI component - see docs: https://www.rexygen.com/doc/ENGLISH/MANUALS/RexHMI/RexHMI_ENG.html#x1-180002.4.3

More about the REXYGEN Alarm feature can be found here: https://www.rexygen.com/doc/ENGLISH/MANUALS/BRef/ALARMS.html#x8-70002

To create a banner, you can use the Dialog feature, which is part of the Group Animation settings.

Let me know if I can be of any assistance.

Cheers,
Tomas

@MikeyH Hi Mike,

Thanks for reporting this. This is really weird. Please, can you record and share your screen? E.g. using online tool https://gifcap.dev/

Kind regards,
Tomas

@MikeyH Hi Mike!

Do you use the same versions of Development tools and REXYGEN Runtime?

The TRND not providing any data seems to be disabled - is it active in the running project?

The error message about parsing the output can be omitted - the extension returns something which throws this error. It won't affect the behaviour of the HMI. We will try to fix it. Can you share your source files with us?

Kind regards,
Tomas

@bech Hi John,

There is the exec counter feature built into the REXYGEN diagnostics. And it is accessible via special signals. The example you are looking for is "0001 Special Signals", and the parameter is excnt.

Thanks for your comment. We are working on better interconnection between the Function block documentation and the Example library. For now, you can use search input within the Examples library to help you find the right example.

Let me know if it helped.

Kind Regards,
Tomas

@MikeyH Hi Mike,

The version you have is correct. The issue is in running the HMI Designer without proper initialization. Try to run the Designer via REXYGEN TrayMon (see the screenshot)

The thing is that you need to tell the Designer which REXYGEN version is valid. The reason for this is that one Designer version is shared among all REXYGEN versions, so you don't have to install all Designer things every time you install a new REXYGEN version. If you run Designer without this connection, it won't work. Running the Designer via TrayMon should solve this.

Kind regards,
Tomas