Recent Posts

Pages: 1 ... 5 6 [7] 8 9 10
61
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.
62
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.
63
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.
64
Configuration Options and Possibilities / Re: Omnia SST
« Last post by BruceWayne05 on August 02, 2026, 12:18:21 am »
Well, this information is good, but it’s not for Omnia SST, they solution it’s for Omnia 9E. Can be possible connect MagicRDS with Omnia SST, I tried a Generic UECP connection, in Magic RDS it says “Connected” also in Omnia; but the RDS rt with music are not showing yet, just the custom SST Generator
65
FM Transmitters, RF Amplifiers / Re: Pira CZ 5W PLL FM Transmitter - PCB
« Last post by ELIO on July 30, 2026, 07:35:33 pm »
hola

colega me podría ayudar con los archivo Gerber del trasmisor ?
66
FM Transmitters, RF Amplifiers / Re: Pira CZ 5W PLL FM Transmitter - PCB
« Last post by ELIO on July 22, 2026, 02:54:46 pm »
Hola
colegas

tendrás el archivo Gerber de la cara serigrafia de los componente ?


saludos espero su respuesta
67
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on July 19, 2026, 12:31:34 am »
Version 4.3.0

http://pira.cz/rds/magicrds/MagicRDS_Setup.exe

General:
  • New connection kind: Hybrid Radio
  • New model: Simple HTTP for sending text data using GET or POST method
  • Internal channel - sendhttp command now accepts further parameters, incl. GET/POST method selection
  • Read button sometimes unexpectedly set the Program to 1
  • Read All button sometimes did not read EON
  • Internal timing is now derived from a system timer that is independent of local real time
  • The way individual Connection threads communicate with main thread has been redesigned. This sometimes led to unexpected connection problems.
  • UECP RT: user can configure the UECP parameter Number of transmissions, default is "indefinite"
  • UECP RT: CR character is placed immediately behind the text rather than the segment end
  • UECP RT: an option added for filling the rest of the text by spaces
  • Demo encoder: Short RT option did not work
  • If the Serial/USB port could not be opened, the program kept repeating the error message
  • UDP connection: "Opened" status was indicated even though the UDP port was occupied by another application
  • UDP connection: changing the UDP port was sometimes not possible without the application restart
  • UDP virtual port: bidirectional communication allowed
  • UDP virtual port: local port and remote port are now configurable independently
  • Sometimes, the AF method B was not correctly cleared in the form when switching between Connections
  • MRDS1322/MicroRDS: a RT time setting was displayed in the form which is not applicable to this model
  • Magic RDS Installator: the installation folder can be changed as usual (2026-08-12)

External text sources:
  • Maximum number of text sources increased from 32 to 64
  • Text Replacing: XML/JSON elements are now processed separately. The Output template is no longer processed.
  • XML/JSON Find element: an error message is shown if the file cannot be read
  • Default name of a new Source includes a number which now always corresponds to the Source ID (i.e. "Source 3", ID: 3). The same applies to the Output.
  • Text Output Setup: The Add Selected button unintentionally added also non-source items.
  • A connection can be added to the Output destinations using drag and drop

Radiotext Plus, Dynamic Label Plus (RT+/DL+):
  • The behavior of the Item Toggle and Item Running bits has been unified across all models
  • DL+: added option to send unused elements as a group of zeros or to skip them completely
  • XML/JSON: the Text Processing Presets sometimes did not work as expected, corrupting the RT+ information
  • MRDS1322/MicroRDS: the RT+ indicator was displayed even though the RT+ encoder was disabled in Extensions
  • PIRA32: if RT+ running bit needs to the cleared, the application sends RTPRUN=2 command
  • PIRA32: RTP= command contained incorrect seventh byte
  • XCMD capable encoders: the dest parameter is always set to 3 to allow keeping RT+ running bit even if a plain text is being displayed
  • DAB AVT model sometimes did not send <inactive/> element when the RT+ running bit needed to be turned off
  • As the RT+ becomes essential, the RT+ software encoder in Extensions is now enabled by default for most encoders which do not support RT+ directly

Please report any bugs or ambiguities.
68
Bug Reports / Re: Buggy Group Sequence in Readbest
« Last post by Jan on July 18, 2026, 12:28:24 pm »
This is not a bug, but rather a feature of current implementation in Windows. The reason is that the encoder's emulator is a separate application and it is not synchronized with the Signal Tool as using the Signal Tool is optional. The time base of the emulator is thus derived using the Windows API timer which is not accurate. Given the intended demonstration use, this does not affect the functionality and keeps the sources tiny. This is the reason why the implementation is marked as experimental. We plan to synchronize the emulator with the built-in Signal Tool (i.e. with the sound card oscillator), but it won't be right away.
69
Bug Reports / Buggy Group Sequence in Readbest
« Last post by chbroadcast on July 18, 2026, 11:50:36 am »
Hello,
I have noticed that sometimes groups get sent out 2 times in Readbest.
This is the group sequence I have set: 0A, 14A, 2A, 3A, 0A, 2A, 0A, 12A, 0A, 2A, 0A, 10A, 0A, 2A, 0A, 14A, 0A, 2A, 0A, 1A, 0A, 2A

You can see in the screenshot, that groups get randomly duplicated, even though its not set like that in the sequence.
The contents of these duplicated groups are also always the exact same.
Im using Magic RDS version 4.2.9.
70
P275 FM Analyzer / Re: Unable to install on Win 11
« Last post by Jan on July 12, 2026, 09:41:10 am »
You don't mention which version of the P275 FM Analyzer you have, so I'll answer in general.

We're not aware of any compatibility issues with Windows 11. We use Windows 11 ourselves and all of our USB products communicate in the same way. The driver is included with Windows as standard, or Windows installs it itself. There is no need to install the driver manually.

The virtual COM port is only present while the analyzer is connected and powered on. This is normal Windows behavior, regardless of the Windows version. (Windows remembers the previously assigned COM port number, but it is only available while the device is connected.)

Could you please check the following?
  • Is the analyzer powered on when you connect it? Windows only creates the COM port while the device is connected and powered. In other words, is the power from the USB cable working? If not, the USB cable or port on the PC is faulty.
  • Does anything new appear in Windows Device Manager after connecting the analyzer? Please check both Ports (COM & LPT) and Universal Serial Bus controllers. If you see an Unknown device or a device with a yellow exclamation mark, please let us know.
  • Please try a different USB cable or a cable supplied with the device (if this is that case).
  • If possible, also try a different USB port (preferably directly on the laptop, not through a USB hub).
  • If you have another Windows PC available, please check whether the analyzer is detected there.

If nothing at all changes in Device Manager when the analyzer is connected or disconnected, Windows is not detecting the USB device at all. In that case the problem may be the USB cable, USB port, or a hardware issue.
Pages: 1 ... 5 6 [7] 8 9 10