Recent Posts

Pages: [1] 2 3 ... 10
1
What is the simplest way to combine multiple text sources into a single line?

Yes, sometimes it is better to present information on a single line (or within a single Radiotext message) rather than displaying it sequentially. This is particularly relevant for very short messages or data values, ensuring that the final text does not exceed any applicable length limits.

Follow these steps:

  • Note the ID of all text sources you want to merge into one line.
  • Add a new source, source type Internal channel
  • Locate the N/A text field and write a template for the final text.
    To insert a text source, use the tag %SOURCExTEXT% where x is the source ID
  • Finally, put the new source into the output sequence.

See the pictures for example.
2
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on Yesterday at 03:33:53 pm »
Version 4.3.5

https://magicrds.com/download/MagicRDS_Setup.exe

External text sources:
  • File reading has been moved out of the main thread and now occurs asynchronously. This prevents occasional sluggish responsiveness, such as when reading from a busy network drive.
  • XML/JSON: N/A text fixed
  • If the N/A text is filled in and the appropriate conditions are met, the N/A text is always used, even if JS is enabled.
3
This peak is not present in your previous image.

It is likely to be a fault in the PC power supply unit. These older devices were relatively sensitive to the quality of the power supply. In the devices we manufacture today, the power supply is handled differently, and a dedicated voltage regulator is always used.

You do not mention the origin of the device. We do not have your email in our database. It is also possible that the previous owner handed it over to you in a damaged condition. The only way to determine this is to test it on another PC.
4
Another question: I’ve noticed a signal appearing on the FFT at 27 kHz on virtually every station I tune into. It seems the equipment is picking up this information and displaying it incorrectly—it’s impossible for every station on the dial to have the exact same issue.
I am using the device connected to a computer, with an external antenna attached.
I’ve taken care to ensure there are no noise sources near the equipment; is there any way to resolve this? How should I proceed?
5
You can find the relevant setting for the margin in the menu Options - Preferences - General.

Regarding your other question: Yes, the FCC once introduced the parameter "percentage modulation," which is still in use today. The FCC's concept of "percentage modulation" provides a convenient way to define and evaluate regulatory modulation limits. It does not establish a physical unit of frequency deviation, nor does it require measuring instruments to display frequency deviation in percentages instead of kHz.

Frequency deviation remains a physical quantity expressed in kHz, while percentage modulation is simply a derived, dimensionless value referenced to a specified frequency deviation (75 kHz in USA).

Since the P275 also provides advanced frequency deviation analysis, including deviation histograms, it is important to retain kHz as the fundamental unit of measurement throughout the instrument and the software. Replacing kHz with percentages would, for example, result in histograms x-axis expressed in percentages. While mathematically valid, this would be unnecessarily confusing and counterintuitive.

The FM Scope supports % in the FM deviation bar, you may toggle the unit by clicking on its scale.
6
That puts my mind at ease!

Regarding other observations, is it possible to display the measurements as a percentage rather than as a deviation value?

Another detail: would it be possible to extend the deviation error margin—currently at 5 kHz—to 7.5 kHz or 10 kHz? In my country, an error margin of up to 7.5 kHz is permitted (within a total of 82.5 kHz at 110%) for stations that use RDS.
7
I have carefully examined the image you attached, but I do not see any problem. Although your device is an older model, that is not a factor in this case. The device includes a simple indicator for detecting unwanted AM modulation; however, this indicator only functions within a specific input voltage range (roughly 40 to 80 dBuV). It operated in the same way in the old firmware version. Therefore, your concern that the firmware update caused an issue is unfounded.

The official recommendation issued by the authorities for the minimum input voltage when measuring frequency deviation is 60 dBuV. In your case, you are nearly 30 dB below this recommendation.
8
Pira P275 FM Analyzer Firmware: 2.2F R3 (Issue with AM noise analysis and measurement)

After updating to the latest firmware (2.2F R3), the device no longer displays the AM noise level in the FM SCOPE V 1.7.8 software.

The system worked perfectly with the previous firmware version (2.1a R3).

What steps should I take to resolve this?

The signal level when acquiring data is 5/5.

Additionally, in my country, local regulations require modulation measurements to be expressed as a percentage—covering the pilot signal, RDS, and total modulation—rather than in frequency deviation (kHz). Could this conversion feature be added in a future firmware update? Furthermore, could support for the extended FM bands used in the Americas be included—specifically the 76–108 MHz range (used in South America), in addition to the standard 87–108 MHz range (used in North America)?

I look forward to a resolution!
9
Feature Requests / Re: need to send via HTTP POST (not HTTP GET)
« Last post by Jan on November 09, 2026, 09:48:36 pm »
Thank you for the nice description of your case.

You didn't make any mistake. However, it won't work for you because the file path contains a space; this requires extra quotation marks, which must also be escaped. The correct line is as follows:

Code: [Select]
cmd """C:\Program Files (x86)\Magic RDS 4\DTS\wxxxdts.bat"""
I am fully aware that this is not very intuitive. Although it might seem that the program could add the quotation marks automatically, this is unfortunately not possible because there is no reliable way to determine where the file path ends and the command-line parameters begin. Any attempt to guess could break otherwise valid commands.

Therefore, if a file path contains spaces, it must be enclosed in double quotation marks. This applies to both the executable file and any file paths passed as parameters.

For example:

cmd """C:\Program Files\MyApp\program.exe"" ""C:\My Documents\data.txt"""

This ensures that commands are passed to Windows without modification, preserving full flexibility and compatibility with Windows command-line syntax.

I should also point out that, in Windows, folders located under Program Files are not intended for storing working files; in fact, doing so is often impossible due to a lack of the necessary permissions.
10
Feature Requests / Re: need to send via HTTP POST (not HTTP GET)
« Last post by broybal on November 09, 2026, 08:55:43 pm »
Sorry if this is an old thread.

I'm attempting to also execute a batch file that I've written from an internal channel to deliver a JSON payload via HTTP Post to dts.

Here's my internal channel data distribution settings:
Quote
saveto file:"C:\Program Files (x86)\Magic RDS 4\DTS\wxxxpost.json"
cmd "C:\Program Files (x86)\Magic RDS 4\DTS\wxxxdts.bat"

The JSON file creation works flawlessly, and the batch file posts the JSON file correctly which I can verify when run manually through windows, but I cannot seem to get Magic RDS 4 to execute the batch file even though it's logged in recent events:
Quote
26-11-09 14:50:16; Executed cmd /C runcmd.bat C:\Program Files (x86)\Magic RDS 4\DTS\wxxxdts.bat

Anybody have any advice?
Pages: [1] 2 3 ... 10