Recent Posts

Pages: 1 ... 5 6 [7] 8 9 10
61
Configuration Options and Possibilities / Re: RDS information to XML
« Last post by Jan on March 02, 2024, 04:20:19 pm »
What does it mean "receiving RDS information"? It is via the Virtual port? Or via the External text source? What is the "RDS information" source? Anyway, the Magic RDS 4 can save it to a XML file in all cases.
62
Configuration Options and Possibilities / RDS information to XML
« Last post by sj87 on March 02, 2024, 04:00:55 pm »
Hi. I would like to put RDS information in an XML file. All documentation I can find want to go the other way around.

I can get Magic RDS to receive RDS information. I cannot put this information into a file.

Can anyone help?

Thanks
63
P132, P164, P232(U) and P332 RDS Encoders / Re: Dollar Sign on P164
« Last post by Jan on February 27, 2024, 07:40:10 pm »
There's no such restriction in the P164 for the dollar sign. It can be showed, of course.

Sometimes the problem is that on common devices, the dollar sign ASCII code is 0x24, while in the original RDS code table the dollar sign has code 0xAB. The solution needs to identify the code table currently in use for the encoder's data input, so it depends on what software and what command do you use for loading the data to the encoder.

The PIRA-family encoders support two code tables on the communication interface: RDS (EBU Latin G0) and UTF-8.
The UTF-8 is used for X-Command, the EBU Latin G0 for other ASCII commands and for UECP.
For the UTF-8, the encoder converts 0x24 to 0xAB itself. For the EBU Latin G0 the conversion obviously needs to be made by the application which sends the data.

Many receivers however do not respect the difference so the dollar sign can never be showed properly on all receivers. You can send 0x24 or 0xAB but not both at the same position... No ultimate solution exists for the $ issue. Maybe it is better to type 'USD'.
64
P132, P164, P232(U) and P332 RDS Encoders / Re: P232u connecting to the Ethernet nextwork
« Last post by Jan on February 27, 2024, 07:29:56 pm »
You can use any serial to Ethernet adapter. There's no reason why not.
65
P132, P164, P232(U) and P332 RDS Encoders / Dollar Sign on P164
« Last post by Ziekel23 on February 27, 2024, 07:27:18 pm »
Is it possible to show a $ on the RT for the P164. We sell our RDS and many a time the client wants the text to have a $ in it. We have other RDS units that display the $ correctly but, on the stations with P164s the display shows an unusual character instead of the dollar sign.
66
P132, P164, P232(U) and P332 RDS Encoders / P232u connecting to the Ethernet nextwork
« Last post by Richard B on February 27, 2024, 06:48:18 pm »
Jan, I recently purchased the P232u encoder to replace our P132. I read on the documentation that the P232u serial port can be used to go serial to ethernet. I thought that I could just use a serial to ethernet adapter, but this proving to be not the case. Can you give me any directions on what I need to have to make this happen. Originally we were using the ethernet port on the P132 to connect to our network. Presently the encoder receives the information needed via the network and directly sends it to the transmitter at the tower.
67
Control Software / Re: Backup and Retore
« Last post by Richard B on February 27, 2024, 06:31:50 pm »
Thanks much Jan. :)
68
Thanks Jan. Works perfectly now!
69
Hi Rod, nice pictures showing the problem.

Since version 4.1.0 the user can create multiple text Outputs. Due to this, the script commands have been expanded, to distinguish between the Outputs. Complete reference can be found in extsrc.pdf, section 'Dynamic configuration of the External Text Sources'.

Your Output ID is 1, so in your case, correct commands would be

Code: [Select]
set Output1.SrcSequenceItem3Checked:"0"
set Output1.SrcSequenceItem4Checked:"0"
set Output1.SrcSequenceItem5Checked:"1"
etc.

For example, the SrcSequenceItem5 is the fifth item in the sequence, from the top of the box. It is not the ID:5 because you may insert each source several times to the output sequence and you can still control each item separately.

Also the workaround with the NAText is no longer required. If you create a Source as Internal channel type, then you can set the text content directly from the Task Scheduler

Code: [Select]
set Source6.InternalChannelText:"TOTAL FIRE BAN"

The 'Tasks' box contains a set of button presets where the commands mentioned above are included, so you don't need to remember them.
70
Hi Jan,

I have a 'PRIORITY message' text source (ID:6). It's an empty txt file. I'd like to turn it on/off via the task scheduler. 
The priority message text itself is stored in the 'N/A text' attribute of Text Source ID:6.
At the same time, when the 'PRIORITY message' is enabled, I'm looking to disable the less important ID3 & ID4 to increase ID6 visibility.
While the 'N/A text' attribute changes as expected, the text source ID6 and others don't enable/disable automatically as expected.
(The text source selection ticks don't change).

thanks, Rod
Pages: 1 ... 5 6 [7] 8 9 10