@gninaus Hi Guenther,

the fix is available in our daily build repository: https://download.rexcontrols.cz/partner/daily/

Feel free to test it and report back.

Kind Regards,
Tomas

@mtomek Hello,
I'm really sorry—I somehow overlooked the fact that you were posting in this old thread. The "Warning 1 1" indicates that the buffer for serial communication between the Master and Slave devices is full:

#define WARNING_SERIAL 1 #define WARNING_SERIAL_BUFFER_FULL 1

Have you added any new data communication or changed the communication speed recently? I’d also like to point out that REXduino is a third-party project, and we don’t have direct control over it. I found the explanation for the warning directly in the source code here:
https://github.com/jaroslavs/REXduino/blob/master/REXduino_slave/REXduino_slave.ino

Cheers,
Jan

Hi @stepan-ozana,

The delay you're observing in Windows is likely due to process prioritization and interruption handling, which are less efficient and harder to control compared to a Linux-based system like Debian or Raspberry Pi OS. In Linux, you have better control over how processes are scheduled and managed, allowing the system to run more smoothly and minimizing the BUSY signal duration. Windows, on the other hand, tends to introduce more overhead when executing external processes, even if the script itself does nothing, due to the way it handles process management at the system level.

Additionally, our systems on Raspberry Pi use a real-time kernel, which further improves the timing and responsiveness of processes. That's why we recommend running time-critical processes on Debian-based systems.

Cheers,
Jan

@Jan-Reitinger Hi Jan,

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

Cheers,
Mike

@Jan-Reitinger Hi Ja, thank you very much, I'll give it a try one of these days. When I have some results I'll post the outcome here.

@stepan-ozana Thanks for sharing your solution! Unfortunately, I don't have the required toolboxes to run the script on my computer. However, the code is well-documented and well-organized, which should make it easy for anyone with the necessary Matlab toolboxes to use it without any issues.

'modbus' requires one of the following: Industrial Communication Toolbox MATLAB Coder Support Package for NVIDIA Jetson and NVIDIA DRIVE Platforms Error in example_ModbusTcpIP_Comm_RpiToPC (line 9) m = modbus('tcpip', IP_ADDR,MODBUS_PORT) %establish communication with the server (client)

Cheers,
Jan

@stepan-ozana
Thank you for confirmation. I will update the example. Unfortunately, quite large changes occur across Matlab versions, and there are situations where a script from older versions stops working in newer ones.

Cheers,
Jan

@cechurat

Hello Tomas,

After read and read again the first lines of the procedures,
Unfortunately, I cannot arrive to register my component.

If we take your "procedure note", in the exemple 0301-12,

I would like to register my gauge,
In first step I select my circle and needle as group of component.

An error flag appear with this message :

Issue flag.png

Does it mean I need a background square for my component ?

In the procedure, at line 11, "check external file and close the dialog with ok
Does it mean in group animation window : Ticking "import content of the group from external file"

If yes, I have some troubles with "import content", meaning for me we not export the selection, but rather the reverse.

I tried to redesign the component on a blank page with a square as a background with the circle and the needle, and repeat the procedure.
And tick external file square.

In the procedure, at line 15, "open the extenal file and had some content"

When we tick this case and close the group box by ok, it register the component automaticly ?

But where ?

I try have a standalone component which could use on any independant project.

Does I need to apply rather the procedure for a custom button explained at the top of the forum ?

Can you help me

Thanks

@stepan-ozana Thanks for sharing your solution with the community!

Good luck with your project.

Tomas

@Jan-Reitinger Hi Jan,

All sorted, thank you.

Cheers,
Mike

@Jan-Reitinger

Hello Jan,

Thanks for your help in my project.

I will see this tutorial, in case of the therm of the project, which is not again finish.

I have lot of work before.

@TourneurHello,
Thank you for sharing the details of your progress and providing such comprehensive information. Taking small steps is indeed the best approach and the most reliable way to achieve your goals. If you encounter any further issues, please do not hesitate to reach out.

A note in the documentation: "If you want to replace the WeBuDi interface with the Rexygen HMI designer interface, just delete the index.hmi.js and save the HMI as index.hmi.svg" is mentioned because the visualization was created using WeBuDi in the above steps. If you didn't follow this process for WeBuDi, this note is not relevant to you.

Keep up the great work, and we're here to help whenever you need it!

Cheers,
Jan

@BailP Hello,
yes, there are REXYGEN packages (version 3) for Bookworm. Details are described here.

Cheers,
Jan

@cechurat Hi Tomas,

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

Cheers,
Mike

Hi Phil,

A colleague has already responded to your query via support. To ensure we have all the information, I’m adding some additional questions here on the forum as well. We need more details from you:

Has the problem been present since the beginning, or did something change? What has changed? Did the LEDs work well before? What REXYGEN project are you using? Can you try running the "0121-09 Monarco HAT Demo Example" and see if you can trigger the LEDs? What does the system log say?

Best regards,
Jan

@Jan-Reitinger Thank you so much for efficient help. Now it works exactly as I wish.

@Jan-Reitinger Thank you so much for efficient help. So far I have used Inport and Outport blocks for working with subsystems. Now I am able to use them to exchange data between tasks.

@Tourneur

Hello,

All my apologies for this very late replying, and status of my advancement.

Unfortunately, I left completely the idea of using simulation without real target connected.

I tryed to compare the use of Rexygen with Profilab Expert, which is for me a really, and really compfortable software.
Particularly, when you are not familiary with all the complexity of programming environnement.

But yes, now, I see it's completly different, and I must re-see all my vision of Rexygen.

I finally decided to use a real target, and follow the tutorial in the documentation.

I arrived to put in place an interactive comunication with the target and my ethernet devices.

You understand lot of thing when system running, for example, i won't understood the machine interface is a web page.

Now I could, thing a little bit deeper in the working of the rexstudio.
Particularly, with Nextape, for a particular project.
I will put my question in HMI topic.

Have a good end day