Dear Jan.
Thank you for the information. We used to do the RT1 part earlier (just by using RT2 instead since we are using RT1 for song information), but some of the shows wants more information given than just one message.
Just to clarify what we are looking for if you have any other ideas on how we could do this.
They are looking for something like (by a 0,5min switching interval from RT1 to RT2):
Radiotext1 - Song information
Radiotext2 - Message #1 (Normally information about the radio station - name, contact ++)
Radiotext1 - Song information
Radiotext2 - Message #2 (Normally information about the show - name ++)
Radiotext1 - Song information
Radiotext2 - Message #3 (Some information to the listeners)
+++
And then all over again (depending on how many Messages they want - but normally this is 2-5).
We are updating the Message1 to 99 today by making and running a .rds file using the following method:
1. Type all the texts on the raspberry pi that they wants in the rotation
2. The raspberry pi sends the information to the MagicRDS computer by using MQTT protocol.
3. The MagicRDS computer stores the information from the Raspberry PI to a file
4. The Raspberry PI runs a command on the MagicRDS machine : magicrds.exe messagefile.rds
We would like to simplify this operation if its possible by sending the information directly to MagicRDS instead of having to store it to a file, and then have MagicRDS read the file (As this will give us more control of what is given to the software as it fails sometimes if the file is not stored/closed before we run the update command. We have a small "wait" command of 0,5 sec before the command runs as this takes care of 95% of the faults - but would like to have the rate to 100% as some of the users are not technical and does not understand what to do if it fails - even if this is just pressign the same button on the touchpanel again).
Thanks in advance