Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by Jan on August 17, 2026, 07:52:06 am »
Yes, now, in the case of XML or JSON sources, each element is processed separately, as this better reflects the logic of working with these text sources. Therefore, text replacement is no longer applied to the resulting text composed of elements according to the template.

The proposed workaround will no longer work. We will find a better solution for your specific needs.
22
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by nuno on August 16, 2026, 11:40:06 pm »
Quote from: Jan on August 16, 2022, 08:45:15 pm
  • Using the Output template, encapsulate the 'link' element into any unique substring.
    For example, if %1% is title and %2% is link:
    %1%<<%2%>>
  • Use the Text Replacing to test if the substring contains the keyword
    Change %REGEXP%<<.*programs.*>> to %GOTONEXT%
  • Remove the substring from final text
    Change %REGEXP%<<.*>> to (nothing)

Alternatively you may apply JavaScript to the same Output template, if further filtering or conditions are required.

Hi!
This is not working anymore on new versions!
How can I do this now?

Thanks
23
RDS Spy / Re: Request for lager font of PI code in RDSSpy
« Last post by SWL Tobias on August 14, 2026, 01:34:01 pm »
I fully agree, the important PI Code is displayed a bit small.

Therefore I have added a bigger separate display here, as attached.

Sorry, adding an attachment was not possible (?)

I also enjoy the signal history view (bottom curve) and a realtime AF list in the captoin of theBasic RDS decoder.

Finally, you may notice the SpectrumLab window, displaying the 'analog' view of the 57 kHz RDS traces. It gives an idea, before decoding is possible, whether there is an RDS signal and about its level above noise.
I wish some such signal indicator (not to replace the useful BER) would also be implemented into RDSspy directly.

Thanks and best regards
SWL Tobias, Bavaria
24
RDS Spy / Re: Request to change non-decoded PS Characters from '-' to '▪'
« Last post by SWL Tobias on August 14, 2026, 12:57:14 pm »
Sorry, posted before making my point...

Thanks for the great freeware RDSspy, a really superb tool for FM DX!

Since '-' is used in regular PS names, I'd suggest to change the non-decoded charcter to something not usually appearing in PS tags, e.g. the small centered 'dot', as entered via Alt+0183 (NumPad) in Windows. This allows clear distinguishing received from non-received characters.

Thank you!

Best regsrds
SWL Tobias, Bavaria
25
RDS Spy / Request to change non-decoded PS Characters from '-' to '▪'
« Last post by SWL Tobias on August 14, 2026, 12:51:08 pm »
Dear RDSspy developer
26
Bug Reports / Re: CR / 0x0D termination in Readbest
« Last post by Jan on August 05, 2026, 11:13:27 am »
The settings related to UECP only take effect when UECP is the preferred communication protocol. You have all these settings in one place.
Unlike our hardware products, the READBEST is a UECP-based RDS encoder. Without enabling the UECP ('Encapsulate all Outgoing Data to UECP') some functions may not be available.
Any changes to the text settings will only take effect after sending a new message.

For loading data to external UECP encoder, you should use the Generic UECP model rather than the DEMO Encoder.
27
Bug Reports / Re: CR / 0x0D termination in Readbest
« Last post by chbroadcast on August 05, 2026, 11:05:08 am »
Hello,

I have tried the latest version now. I see the new additional toggles, but they don't seem to do anything in Readbest.
With them enabled, the RT still gets padded up to 64 chars with spaces.
Am I forgetting something?
28
P132, P164, P232(U) and P332 RDS Encoders / Re: Factory reset P332
« Last post by Jan on August 03, 2026, 02:04:21 pm »
If the network configuration changes (e.g. subnet address) and the device's IP address has been set to a fixed value, it is natural that the device will appear unavailable for TCP connections or web management. The same can happen if you do not know the previous configuration of the device.

The procedure for setting the correct network parameters is always the same and was described in detail in the pdf manual (p132com.pdf). The P332 encoder was equipped with a serial port for local management, so you will need a serial connection and proceed according to the manual, section "2.2.1 Establishing a First Communication with the RDS Encoder". In this way, you can set network parameters, enable/disable TCP ports, enable/disable web management, etc. The RDS content itself is not affected. It is unnecessary to use port scanning or other low level network utilities.

Unlike our current models, the P332 was not equipped with Ethernet defaults button nor device discovery feature. In some cases, the described serial connection is therefore the only way to configure network parameters and make the device accessible over the network.
29
P132, P164, P232(U) and P332 RDS Encoders / Factory reset P332
« Last post by Rade on August 03, 2026, 01:44:14 pm »

I am having a network access problem with my PIRA 332 RDS encoder after changing the network configuration.

The device is reachable on the network at IP address **10.50.0.5**, and it responds at the Ethernet level (ARP), but I cannot access the web interface or connect with the PIRA control application.

I performed a port scan and found that all tested TCP ports are filtered (no response), including port **7020**, which I believe should be used for communication with the application. The web interface is also not accessible on the expected ports.

For example, Nmap reports that all scanned ports are in the **filtered** state with **no response**.

The device appears to be alive on the network, but it does not accept TCP connections.

Could you please advise:

* Is there a default web server port for the PIRA 332?
* Is it possible that I accidentally disabled the TCP server or web interface?
* Is there a procedure to reset only the network settings without affecting the RDS configuration?
* Is there a hardware reset, serial recovery procedure, or a way to restore the network configuration?

I am also planning to connect a PC directly to the encoder with a static IP address to eliminate any network infrastructure issues.

Any guidance would be greatly appreciated.

Thank you for your support.
30
Configuration Options and Possibilities / Re: Omnia SST
« Last post by juglaresdelrock on August 02, 2026, 12:54:59 am »
Hello, I solved it with the Omnia 9/XE and with MagicRDS 4.1, it's now a matter of configuration.
Pages: 1 2 [3] 4 5 ... 10