• To anyone looking to acquire commercial radio programming software:

    Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.

    If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.

    To obtain Motorola software see the Sticky in the Motorola forum.

    The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.

    For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).

    This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.

P25 simulcast multipath interference

Status
Not open for further replies.

taysml

Member
Joined
May 1, 2012
Messages
9
Location
Last 22 engineering years in Moneta, Va .First 20
P25 Simulcast Multipath Interference

Gee I can't stay out of this thread. bailey2, here's my 2 cents.....

When you say "LSM" I'm going to assume that you mean linear simulcast in general, which, according to the P25 standards, also includes WCQPSK.

See my point 2 of post 09-05-2015, 11:39 AM for the reason that simulcast is used.

Simulcast systems have existed for several years, even long before the existence of linear simulcast. So a simulcast system doesn't have to be linear, and in fact there are still many older fielded systems that use FM transmissions from the towers such as P25 Phase 1 C4FM and proprietary modulations that the manufacturers used even before that. See my point 5 of post 09-05-2015, 11:39 AM for the reason why linear simulcast is usually used these days instead of C4FM simulcast.

For some cases, you are right about not needing as many TX sites with linear simulcast ..... but not necessarily always. Better delay spread tolerance afforded by linear simulcast sometimes means that the transmit sites can be placed further apart and thus reduce the quantity needed for a bounded coverage area such as a city limit However, the ability to spread the sites further can be counteracted by a customer's inbuilding coverage requirements, which tends to force the sites closer together to enable achieving the requisite signal level impinging on the buildings (in a large area) from the transmit sites. Cities, in particular, usually have quite onerous requirements for so-called "general" coverage in buildings, often requiring penetration of a 30 dB or greater assumed building loss and achieve a requisite voice quality inside the building (so-called DAQ rating).

I personally know of no customer, standards or Industry Forum bodies that I ever been involved with that wanted linear simulcast for enhanced security from scanners. If properly designed, scanners should work fine with linear simulcast even for severe delay spread conditions. Security needs drive customers towards added encryption of the digital signal, which commercial scanners won't be able to decode.

By the way, I'm very surprised that your scanner doesn't decode voice when you use a Yagi for the geometry that you describe . When between two sites, your Yagi antenna should offer enough angular resolution to capture one of the sites and attenuate the other. Off the top of my head, the following possibilities come to mind.... 1) your Yagi's directional pattern is being corrupted if you're attempting to use it near physical obstructions such as indoors, 2) there are actually more than two sites in the system (usually the case), you have near-equal signal levels from at least two that your Yagi can't separate, and the overlapping signals are from sites with large differences in path length to your scanner 3) The system is encrypting everything (not likely) so your scanner can't decode it . Good luck.
 

MTS2000des

5B2_BEE00 Czar
Joined
Jul 12, 2008
Messages
6,115
Location
Cobb County, GA Stadium Crime Zone
If properly designed, scanners should work fine with linear simulcast even for severe delay spread conditions.

This should be made a sticky. There is no "simulcast distortion". It is the failure of the receiver designer to implement the correct design for the modulation of the carrier desired.

To date, not ONE commercially available consumer scanner can actually do a consistent, reasonable job of handling CQPSK-LSM. Let me know when one hit the market, for real.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,059
Sorry, but simulcast distortion is a fact of physics. Two signals not in phase will affect each other on any receiver.

You may be right about the scanner designs, but that is not proof that the interference does not exist.
 

MTS2000des

5B2_BEE00 Czar
Joined
Jul 12, 2008
Messages
6,115
Location
Cobb County, GA Stadium Crime Zone
Sorry, but simulcast distortion is a fact of physics. Two signals not in phase will affect each other on any receiver.

Whatever. Those of us who operate and maintain systems don't see it that way. We deal with delay spread and if a system is setup according to manufacturer's specification and optimized properly, there is no "distortion" coming out of any of our users' subscriber radios.

Turdy consumer crap scanners do not matter to those of us who maintain and operate the system or the actual users. What does is proper performance. So the topic of this thread is about these garbage pail scanners that have to have a PERFECT spoon fed signal to work at all. That's a design fault of the receiver not a problem with the network, simulcast, launch times, delay spread, et al.

You may be right about the scanner designs, but that is not proof that the interference does not exist.

Again, I know I am right about the scanner designs. They suck plain and simple.

As far as this interference, it does not happen on a properly designed, optimized and configured simulcast system within the designed coverage area with subscriber radios that are properly programmed, tuned and aligned by a competent technician to the vendors' specifications, so what proof do you have that it exists other than your experience as a scanner hobbyist using consumer gear that you already agree with me is crap?
 

dgmaley

Member
Joined
Dec 26, 2012
Messages
103
Location
Marion,Iowa
Here is what I've been told by one of the design engineers about P25 system receiver design. Conventional police scanner are still using an analog receiver and just route audio, from the discriminator to a DSP to do all the decoding. Any error correction is done in the DSP only.
Professional transceivers use a true digital receiver, where true I and Q data is fed to a DSP where it can control the receivers bit error rate first. Any multi path is nulled out.
As long as scanner designers use a FM discriminator, there will be no way to eliminate multi path errors in software.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,059
Whatever. Those of us who operate and maintain systems don't see it that way. We deal with delay spread and if a system is setup according to manufacturer's specification and optimized properly, there is no "distortion" coming out of any of our users' subscriber radios.

Well, those of us who operate and maintain systems know that interference can and will occur no matter how well you think you've designed a system that uses more than one transmitter in simulcast operation. All you need is more than one signal out of phase and distortion of the pattern WILL occur. More than one radio signal arriving at any given point will only be perfectly in phase about 1/360th of the time. The other 359/360th, they will be out of phase and distortion of the signal results. Again, this is basic Radio 101 physics. Anyone who claims otherwise has zero credibility. Most hams even know this. You cannot design a system to be perfectly in phase everywhere. It's a physical impossibility no matter how much delay you put on the transmitter. The on exception is when the transmitters are perfectly lined up so the separation changes by exactly the same amount. In the real world, the towers are never put in a straight line with coverage only off the ends. They are put where coverage is needed, and the rate of change relative to each tower does not change exactly the same. Granted delays can help minimize gross errors, but never will eliminate all errors.

That was funny about distortion not coming from the subscriber radios, as the subscriber radios don't simulcast. They only have one transmitter. Again, Radio 101.
 

MTS2000des

5B2_BEE00 Czar
Joined
Jul 12, 2008
Messages
6,115
Location
Cobb County, GA Stadium Crime Zone
Well, those of us who operate and maintain systems know that interference can and will occur no matter how well you think you've designed a system that uses more than one transmitter in simulcast operation. All you need is more than one signal out of phase and distortion of the pattern WILL occur.

Mr. Engineer, if your system is optimized, any "distortion" won't be an issue so long as the BER stays below the manufacturer threshold. Your users don't care and neither should you so long as the BER is within the tolerances throughout the coverage area.

Who gives a rats behind, in a simulcast environment, nothing will be exactly 100 percent perfect. The key is balancing the desired coverage vs. cost.

No one but scanner enthusiasts have problems receiving our systems and this isn't because our systems are malfunctioning, which is what this thread is all about.

My users don't experience issues because:

1)-System is optimized by the STs and our team to be within the specified engineering design
2)-Coverage is balanced throughout the guaranteed footprint with the guaranteed 8dB of in building coverage using an approved portable radio with standard 1/2 wave whip at waist level.
3)-Subscriber radios are maintained properly, all PMed and tuned to manufacturers specifications, and properly programmed to our system as specified.

This is the case with the hundreds of P25 simulcast systems across the USA from multiple vendors. What exactly is your point? If you are having issues with YOUR system with actual SUBSCRIBER radios and not some scanner nerd crying because his turdy scanner can't hear it, should you not be on the horn with your vendor asking for help?
 

im800mhz

Member
Joined
Dec 19, 2002
Messages
349
Location
WA
For those following along and not understanding, here's what you can take away.

1. Simulcast is the art of controlling the inherent distortion and interference. Done right, it works well.

2. Scanners suck. That's why P25 radios cost more.

3. Systems are not designed for the hobbyist benefit.
 

KA1RBI

Member
Joined
Aug 15, 2008
Messages
799
Location
Portage Escarpment
"LSM is compatible with a QPSK demodulator as defined in the Project 25 - FDMA Common Air Interface Standard, (TIA.102-BAAA-A)." ........

In this post and following post(s) it is necessary to take a detour before returning to the subject of FM demodulators. The above citation, and the use of terms such as "compatible" and "interoperable" need to be placed into the proper context. Without this, a correct understanding of these issues is not possible.

... that statement should raise some eyebrows with both the TIA P25 Standards interoperability folks ... interoperability (of great importance to the P25 standards folks) of the Air Interface...

That amusing portrait depicts a process that is naively unaware of the actual state of play in Project 25. Nothing could be further from the truth. In this post we will explore one way (of the four already mentioned) that the real world works. To do so, this post will be confined to publicly available documents from the major players in industry and government.

In part II of this series we'll take a look at the same issue (1 of 4) from a different perspective; to include an OP25 code patch to enable anyone competent in the arts to verify for himself (to any level of detail desired) what's really happening behind the scenes. That post will inspect the half-rate counterpart of the vocoder we look at in this post.

Here for illustrative purposes we will examine the "Enhanced AMBE+2 Full-Rate 7,200 bps" vocoder to help us to a more accurate definition of "compatible".

http://dps.mo.gov/dir/programs/intercomm/docs/Project25.pdf
Project 25 radios operating on MOSWIN must utilize, at a minimum, the IMBE (Baseline) P25 vocoder. However, agencies should strive to utilize the Project 25 Enhanced Full Rate Vocoder (AMBE + 2) as it is available on newer radios from multiple manufacturers and outperforms in all scenarios any previous full or half rate vocoder in areas of noise suppression and voice clarity. The AMBE + 2 vocoder is the preferred Project 25 vocoder for use in the MOSWIN network...

http://www.efjohnson.com/resources/dyn/files/171947z8ebcbe0c/_fn/Vocoder_09_09.pdf
In every test ... the Enhanced Full-Rate (AMBE+2) Vocoder outperformed all other vocoders, including the “baseline” IMBE Vocoder

DVSI Products USB-3000™
The enhanced full-rate AMBE+2™ vocoder is fully compatible with the older IMBE™ vocoder that was used in the APCO Project 25 Phase 1

DVSI Evaluation Results
DVSI developed an Enhanced (AMBE+2) P25 vocoder ... available in a 7200 bps Enhanced full-rate vocoder configuration which is fully interoperable with the existing P25 full-rate vocoder standard (TIA-102BABA).

Conclusion so far: The two full-rate vocoders are therefore, officially, "compatible" and "interoperable" with each other in precisely the same way that LSM is, officially, "compatible" with the BAAA-A CQPSK demodulator (see above).

To be continued...
 

taysml

Member
Joined
May 1, 2012
Messages
9
Location
Last 22 engineering years in Moneta, Va .First 20
P25 Simulcast Multipath Development

That amusing portrait depicts a process that is naively unaware of the actual state of play in Project 25. Nothing could be further from the truth. In this post we will explore one way (of the four already mentioned) that the real world works.

KA1RBI, perhaps I misunderstand your statement, but if you're implying that I naively misunderstand Project 25 or the players/process involved, I can assure you that, having been personally involved in the P25 standards meetings and development, I do. And gosh, if I understand your verbiage correctly, I wish that I could have met you before my last 22 years in LMR engineering design and solving customer field issues so that you could have taught me beforehand about what to expect in the "real world".
 

jackj

Member
Joined
Jul 19, 2007
Messages
1,548
Location
NW Ohio
At last

Mr. Engineer, if your system is optimized, any "distortion" won't be an issue so long as the BER stays below the manufacturer threshold. Your users don't care and neither should you so long as the BER is within the tolerances throughout the coverage area.
snip

Something I can understand and agree with 100%. I believe that statement will also hold true for "for crap" scanners.
 

mancow

Member
Database Admin
Joined
Feb 19, 2003
Messages
6,908
Location
N.E. Kansas
Whatever they did with the X36HP series definitely improved things over any of the others so far.
 

jcardani

Member
Premium Subscriber
Joined
Jan 16, 2002
Messages
1,393
Location
Orlando, FL
Hi All,

With all of the knowledge on this forum on how to correct this problem with the scanners, why not contact Uniden or Whistler and offer a solution? Or patent it just like Greg Knox and Terry Brennan did with Smartnet and EDACS. I worked with both of these guys years ago testing their products pre trunking scanners. I am sure that one of the manufacturers would pay for the information.
 

MTS2000des

5B2_BEE00 Czar
Joined
Jul 12, 2008
Messages
6,115
Location
Cobb County, GA Stadium Crime Zone
Hi All,

With all of the knowledge on this forum on how to correct this problem with the scanners, why not contact Uniden or Whistler and offer a solution?

One would think that the dozens of threads on this very forum which are read by supposed representatives of those companies that they would have already addressed that.

But it is clear they are not interested in doing anything but crank out new versions of the same old, same old.

Or patent it just like Greg Knox and Terry Brennan did with Smartnet and EDACS. I worked with both of these guys years ago testing their products pre trunking scanners. I am sure that one of the manufacturers would pay for the information.

Because there really isn't any "magic bullet" or exclusive technology to patent. And besides, those who design such hardware these days are getting paid big bucks or have long retired.

The consumer scanner manufacturers are all doing their R&D overseas where labor is cheaper and just buying crap already made for other applications, throwing it together, and slapping their name on it.
 

KA1RBI

Member
Joined
Aug 15, 2008
Messages
799
Location
Portage Escarpment
In previous posts I've mentioned OP25. Before going further, a few remarks about it since not everyone may be fully familiar with the OP25 project, which exists "to bring together folks that are interested in implementing APCO P25 using a software-defined radio ... that is available under the GNU Public License".

As a major OP25 code contributor (including the PI/4 DQPSK demodulator work), I might naturally be considered (by reasonable people) to be biased on the subject. Therefore I'll rely on publicly sourced quotes from others (and one PM I couldn't resist). As always I should be most grateful to anyone for bringing to my attention any errors or omissions...

Max

Hi Max! ... Some day there will be people that finally have that "Ah-hah" moment like I did, when they realize how well OP25 actually works. There isn't any of that silly virtual audio patching and 4 different apps to accomplish one task. None of which can demodulate LSM, so thank you for that!

Max - works great on WVSIRN Ohio co Simulcast (West Virginia statewide system, monitoring a simulcast site). Historically my PSR-500/800, PRO-197, and BCD436HP|BCD536HP cannot decode this site from my location.

Scanner manufacturers should study how OP25 decodes P25 CQPSK LSM signals and incorporate it into the next generation of scanners ... People should thank Max for developing and implementing this method in OP25!

Just wanted to say that OP25 is working great! Handling CQPSK with an SDR is quite a feat of software and mathematical gymnastics; hats off and many thanks to the developers.

... first off, my 436HP still struggles with simulcast issues at times (it's much better than previous scanners though), whereas OP25 might add a squeak or two to the audio, but other than that it keeps right on going. The other thing that's a really big plus for me is the ability to log activity on multiple talkgroups at once (although I confess I haven't gotten that far with my installation yet - still having too much fun just running it like a scanner).

It could be you are hearing an LSM simulcast site, and receiving strong signals from several simulcast cells. If that's the case, the only solution (other than an agency-issued radio) is OP-25.

(relayed via PM)
Dude you was so right, the decode is just awesome. Almost hate to say it but appears to be better than Uniden and GRE decode.

This is the Christmas present I've been praying for since the rtl-sdr dongles came out what a year or two ago.

Just unbelievable how clear it is, no more guessing what they're saying.

Ok i'M AT A LOSE OF WORDS, SO TILL TONIGHT. OOPS caps.

digital voice Archives - rtl-sdr.com
Over on YouTube user jdlucas78 has uploaded a video showing a P25 LSM modulated digital voice signal being decoded by the Osmocom OP25 software for Linux. Although DSD and DSD+ can decode P25 voice, it seems that the Osmocom OP25 software is better at decoding P25 signals ...
 

tlefkowitz

Member
Premium Subscriber
Joined
Apr 11, 2013
Messages
50
p25

Hi All

Many of you helped to get my OP25 working here in Tucson on the PCWIN system. Very impressive use of an SDR-RTL dongle.

Can I intrude and ask a noob question...how does Simulcast work? I live closest to Simulcast N signal in Tucson. Does Simulcast N give me access to all talkgroups in PCWIN, regardless of being closest to Simulcast N?

Thanks in advance
Todd
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,059
Simulcast simply transmits the same data on the same frequencies from multiple locations. If the entire system is simulcast, you will hear all TGs on all sites.
 

ElroyJetson

Getting tired of all the stupidity.
Premium Subscriber
Joined
Sep 8, 2002
Messages
3,977
Location
Somewhere between the Scylla and Charybdis
To expand on that overly simple explanation, a simulcast system consists of cells which contain multiple transmitter sites.

Each transmitter site is configured IDENTICALLY to all the others in the same cell.

They are nothing less than completely duplicated sites. Right down to the data, modulation, and exact transmitter frequencies.

Any given transmitter transmits on the same frequency as its counterparts at other sites to within a frequency tolerance of 1 Hz.

All modulation settings are very closely matched. Voice, high speed data, and low speed data. Audio equalization is matched.

Timing of voice and data is carefully adjusted to be as simultaneous as possible.

The end result is that each site in the simulcast cell is transmitting substantially identical signals that
tend to reinforce each other rather than cancel each other out as you move from the coverage of one site to another.

The range between sites is described as "capture" area or "non-capture" area, which refers to the "capture effect" characteristic of FM and related modulation formats.

The capture effect is simply this: If one signal is 20 dB stronger than another signal on the same frequency, the stronger signal "captures" the receiver and no trace of the weaker signal will be heard.

Thus, as you move through the simulcast cell, in areas where one transmitter site has a 20 dB signal strength advantage (or more) over the other sites, then you are in the capture area.

When you are an an area where there is less than 20 dB of signal strength difference between the signals from multiple towers, then you are in the non-capture area. This is where signals will interfere and compete with each other UNLESS the signals are well matched. This is where the payoff comes from for a simulcast system.

In the non-capture areas, a properly implemented simulcast system's signals will reinforce each other. The user may notice little or even no signal degradation as he moves out of the coverage range of one site within the simulcast cell and into the coverage range of another.
 
Status
Not open for further replies.
Top