@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

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

@cechurat hi there, would you happen to have an example of how to configure & deploy this?

@Jan-Reitinger Thanks for explanation! I promise I will study the documentation in more details next time. However, still I have some remarks here.

Regarding SAT documentation:
"The maximal rate at which the active limits may vary is given by time constants tp (positive slope) and tn (negative slope)."
This statement is ambigous for me.
If we say maximal rate of the signal is affected by some parameter rate_max, then from technical point of view, higher
rate_max means higher allowable rate (1st derivative), thus indicating being close to immediate changes of the signal.
So if rate_max reaches infinity, immediate changes are allowed.

Then we should say the maximal rate at which the active limits may vary is given by INVERSE OF time constants tp,
and rate_max = 1/tp, meaning that the meaning of logic in choice of parameters tp and tn is actually inverse.

This is actually declared in the documentation of RLIM block as the steepest rise per second, and should be also repeated for for documentation of SAT to keep documentation consistent.

I tried series connection of CNR and RLIM, and changing CNR on the fly. If tp=0.1, then maximal slope is 10, and the new value of CNR is
reached in 0.1s, following linear ramp signal. This is OK, and similar functionality works for SAT block.

Also, reading "time constants tp and tn" may indicate presence of some dynamics like first-order system 1/(tp*s+1) or 1/(tn*s+1), because this technical term is ususally used
when talking about dynamic systems. It would be much better to simply use "parameters tp and tn" instead to make things clear.

@Jan-Reitinger I am thankful that you made this clear !

@cechurat Hi Tomas,

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

Cheers,
Mike

Hi Tomas,

Thank you for your quick and precise response -- this is precisely what I was looking for.

@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 Nice. Just one small remark: There's no need to use a two-dimensional input here—even formally. You can define a system with a one-dimensional input, a certain number of states, and possibly a different number of outputs. Instead of using u(t)=[sin(2πt);0] you can simply write u=u1=sin(2πt).

@carvin Hi carvin,

thanks for your feedback. I would suggest to use the SRTF function block with some certain subsystem (e.g. "sybsystem_slow") within your fast task.

Would that solve your issue?

Cheers,
Tomas

Hi Carvin,

Thanks for the question. With all the provided information I don't see anything suspicious. Please, can you share the whole project (mdl files at minimum) just to see all other information and configuration which are not visible from the screenshot?

Just be aware that arrays and vectors in REXYGEN are connected by references so the flow of "information" is different from ordinary "wire" flow where the wire starts somewhere and goes somewhere else. Contrary reference contains the same data in every instance.

Kind regards,
Tomas

@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