@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

@ryanastiefes Dear Ryan,
I have used PID Control Laboratory at www.pidlab.com.

0_1571646428904_pidlab-pi-controller.png

Hope this helps.

Best regards
Jaroslav

Hi Tomas,

I tried your proposal, but unfortunately it did not work.
At the end I decided to simply re-image the SD card and start from scratch. Installed the most recent Rexygen test version and now, all is working fine.
Thanks for your support.

Best regards,
Peter

Hi Guenther,

the official release version is still 2.50.9 for now. However we are not far from public release of 2.50.10 and the pre-release version is available in above mentioned post.

Kind regards
Tomas

@reitinge

Již jsem problém vyřešil, problém byl v tom, že jsem napájel pouze Raspberry přes micro-usb, nikoliv Monarco HAT.

Vše funguje tak, jak má.

@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.

@cechurat Hi Tomas,

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

Cheers,
Mike

Hi Tomas,

Thank you for your help. I understand how it works now, what you provided is where i wasn't sure what to do. It makes sense to me now.

Cheers

Mike

Hello Martijn,
this will save the total number of run-minutes to database everytime the RUN input drops to OFF (FALSE):
0_1576604316928_rexygen-hour-meter-database.png

See example 0404-01 and Database connection driver manual for details.

Hope it helps.

Jaroslav

I created a "ProwlPushMessage" block (SubSystem) where all properties can be set easily.
Implemented the conversion from a "space" character towards "%20" in order to get the correct code for the message.

So this system is ready to be used, only fill in your own APIkey and press the button to send a message to your iPhone.
Please find the project attached.
prowl_exec.mdl
prowl_task.mdl
998b3e55-a136-4055-9b09-ccfa7f38c786-image.png

This is how it looks.
4db243ab-c0d8-4f5d-b534-74a12ac6b81e-image.png

@cechurat Thank you Tomas,

It works perfectly now. I really like this method, good to learn new things.

Cheers

Mike

Hi Toni,
FilterIdMask can be used for filtering messages from more devices. In your case, there is only one device, so you can set FilterIdMask as 0xfff. For message decomposing, use the INTSM blocks (www.rexygen.com/doc/ENGLISH/MANUALS/BRef/INTSM.html). The basic example of using INTSM block can be found in this thread: https://forum.rexygen.com/topic/174/reading-and-writing-4-byte-floating-point-from-modbus?_=1609251284153
For decomposing a byte value into bits can be used block BDOCT(www.rexygen.com/doc/ENGLISH/MANUALS/BRef/BDOCT.html).

Cheers,
Jan

Hi Kris,

one more thing - did you try to use ARS function block? https://www.rexygen.com/doc/ENGLISH/MANUALS/BRef/ARS.html

It might help you.

Kind Regards,
Tomas

@cechurat said in Use of the 'MTM__SlaveStation_Connected' signal.:

Status shows time to next reconnect in ms

@fabio
add poznámka: Je to vidět z výše zmíněného obrázku. Jakmile mezi DOUT a GND připojíte odpor a DOUT bude mít hodnotu OFF, vznikne napěťový dělič. Podle připojeného odporu dopočtete napětí, které bude mezi DOUT a GND. Nicméně procházející proud bude stále pravděpodobně nedostatečný. DOUT je prostě dělaný tak, aby se spínal s externím napětím.

Buď si za 12V předřaďte odpor tak, aby Vám vycházelo požadované napětí (5V) , nebo použijte externí zdroj 5V nebo sežeňte 12V ventilátor. Výpočty a konečnou volbu nechám na Vás.

S pozdravem,
Reitinger

@apollo I am glad that it is working.

@gerritjan1 I've observed that you are currently using the flags MTM__readBlock_ReadEnable and MT__writeBlock2_WriteEnable. However, in a previous post, you mentioned flags named MTM__readBlock1 and MTM__writeBlock1. It is important to ensure that the flag names correlate properly. Therefore, for MTM__readBlock1, the corresponding enabling flag should be MTM__readBlock1_ReadEnable, and for MTM__writeBlock1, the enabling flag should be MTM__writeBlock1_WriteEnable.

@MikeyH Hi Mike,

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

Cheers,
Tomas

@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

Hello @sadilekivan ,
this issue was caused by unknown bug in the hashing algorithm during the HMI build process. This will be fixed in next version of our software. Thank you for the bug report.

Best regards
Ondrej