Recent Posts

Pages: 1 [2] 3 4 ... 10
11
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?
12
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.
13
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.
14
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.
15
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!
16
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.
17
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?
18
P275 FM Analyzer / Re: P275E FM Monitor+ (audio logging)
« Last post by Jan on November 04, 2026, 09:30:37 pm »
Yes, it allows remote listening over network. It primarily serves to verify that the correct program is being broadcast. However, this player uses lossy audio compression and is not intended for permanent recording, as it shares transmission capacity with certain FM Scope measurement functions.
19
P275 FM Analyzer / Re: P275E FM Monitor+ (audio logging)
« Last post by zvykov on November 04, 2026, 09:18:35 pm »
Could you clarify one more point: does the built-in monitoring player receive the audio stream over the network, or does it work differently?
Is there perhaps a remote demo device available?
20
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on November 04, 2026, 09:55:21 am »
Version 4.3.4

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

The logic regarding the sequence of text sources has been adjusted:
  • The next source in the sequence is not loaded except at a regular interval, unless another source has been active in the meantime.
  • If the timer is exited while waiting for a source to load, the process will continue with the next source the next time, rather than starting over with the same one.
  • Reading of empty file is no longer considered to be an error, so the N/A text is processed as expected
  • Reading of empty file no longer starts immediate searching for a next source. This can be done by putting %GOTONEXT% into the N/A text field.

Lots of complex and confusing sentences, so to put it briefly: the behavior has been adjusted, particularly in cases where an empty file is read.
Pages: 1 [2] 3 4 ... 10