Author Topic: commands execution and *.rds files  (Read 139 times)

kamlay

  • Newbie
  • *
  • Posts: 5
commands execution and *.rds files
« on: April 18, 2020, 01:09:03 pm »
I made an experimental stand out of a low-power transmitter, an broadcast processor, and P132 RDS encoder. I control the real broadcast signal via P275 and RDS Spy. In General everything seems to work fine.

But it seems that commands from the Text Conditions don't work in this version. The executed command lines are visible in Recent Events, but no reactions in the RDS air. For example, I use the commands: RT1=, RT2=, PTY=, PTYN=, RTPRUN=, RT1EN=, RT2EN=.
Also the question, are files for Task Sheduler  in *.rds format from the previous version of Magic RDS supported by this version?

Thanks,

BR,
Gennady

Jan

  • Hero Member
  • *****
  • Posts: 586
Re: commands execution and *.rds files
« Reply #1 on: April 18, 2020, 02:01:55 pm »
The philosophy is a bit different from version 3. Especially due to support of multiple connections the scheduler's task line for sending a command to the encoder must look like this:

Code: [Select]
send connection:"*" command:"RT1=New RT text here"
Instead of the *, you may specify a list of connection names. The command is automatically translated to correct protocol (ASCII, UECP, MRDS1322 binary).

The *.rds files are no longer supported. And are no longer required. The configuration is saved in XML-based *.rdsx files. For the task scheduler, the list of commands will be published.

Jan

  • Hero Member
  • *****
  • Posts: 586
Re: commands execution and *.rds files
« Reply #2 on: April 19, 2020, 10:16:18 am »
Well, it has been already done in version 4.0.1.

There is a well known example from Magic RDS 3, now written directly to the Tasks box:

Code: [Select]
set Radiotext.Src1Enabled:"0"
set Radiotext.Src2Enabled:"1"

This switches the external text source for Radiotext from Source 1 to Source 2.

To change a RDS content value (without update of the encoder):

Code: [Select]
set connection:"Connection Name" DataSet1.PS:"NEW PS"
To change Group Sequence of UECP or READBEST encoder:

Code: [Select]
send connection:"DEMO" command:"GS=0A,0A,0A,2A,3A,0A,0A,0A,2A,11A"
The same but with address, site, DSN:

Code: [Select]
send connection:"DEMO" command:"GS=0A,0A,0A,2A,3A,0A,0A,0A,2A,11A" site:"6" adr:"1" dsn:"2"
... etc.

For complete list of commands and properties click on appropriate button next to the Tasks box. The same code may be entered in Tools - Execute Script.

Some more commands and options will be added in future.

kamlay

  • Newbie
  • *
  • Posts: 5
Re: commands execution and *.rds files
« Reply #3 on: April 19, 2020, 03:24:26 pm »
Thanks Jan!

What format is the date and time set in?
I tried this format:
event days:"1234567" times:"16:21"
Scheduler does not triggering. Test button sends a command correctly.

------

To clarify, in the course of experiments, it turned out that the sheduler does not work if there are two or more date/time lines in the field. If one line is used, it works fine! I will change the question, how can I specify two or more switching times in one line?

I entered the information like this:
event days:"1234567" times:"14:59"
event days:"1234567" times:"19:59"


Experimentally I found that multiple sheduling times need to specify using the semicolon: event days:"1234567" times:"12:54;19:00"

Jan

  • Hero Member
  • *****
  • Posts: 586
Re: commands execution and *.rds files
« Reply #4 on: April 21, 2020, 05:47:50 pm »
There was a bug which made troubles when specify more than one event.

Some examples which are applicable now:

Code: [Select]
event days:"12345" months:"01,02,03" times:"06:00,18:00"
event daysOfMonth:"01" years:"2020" times:"12:00"
event minutesOfHour:"15,45"
event dates:"01.01.2021" times:"00:00"
etc.

The times or minutesOfHour parameter is obligatory.