[op25-dev] Recent changes

'William Becks' wa8wg@centurytel.net [op25-dev] op25-dev at yahoogroups.com
Tue Dec 19 04:18:52 UTC 2017


Matt.

 

I don’t think this works with Graham’s op25 (rx.py) fork having  tried a number of configurations (combinations) but not able to decode conventional P25 non-trunked IMBE.  Perhaps Graham or Max can elaborate if this functionality is still supported.   

 

Thanks again!

 

Bill, WA8WG

  

 

From: op25-dev at yahoogroups.com [mailto:op25-dev at yahoogroups.com] 
Sent: Monday, December 18, 2017 5:54 PM
To: op25-dev at yahoogroups.com
Subject: Re: [op25-dev] Recent changes

 

  

Hi Bill,

 

trunk.csv isn't required for conventional. Here's a few exmaple commands I have used with my USRPs (via UHD) and airspy:-

 

../rx.py -S 2500000 -o 50000 -q 2 -f 434075000 --args 'uhd' -D fsk4 -P fft --gains 'PGA:10'

 

../rx.py -S 1000000 -o 50000 -q 39 -f 434075000 --args 'uhd' --gains 'PGA:40'

 

../rx.py -S 2500000 -o 50000 -q 2 -f 438187500 --args 'airspy' -D fsk4 -P fft --gains 'MIX:5'

 

 /rx.py -S 1000000 -o 50000 -q 2 -f 438187500 --args 'uhd' -D fsk4 -P fft --gains 'PGA:30'

 

Cheers,
Matt

 

 

 

 

 

On 19 December 2017 at 09:06, 'William Becks' wa8wg at centurytel.net [op25-dev] <op25-dev at yahoogroups.com> wrote:

  

OK.  How does one setup the rx.py command line and/or trunk.tsv file if required to monitor conventional traffic?  Can you please post example configuration?

 

Thank you,

 

Bill, WA8WG

 

 

From: op25-dev at yahoogroups.com [mailto:op25-dev at yahoogroups.com] 
Sent: Monday, December 18, 2017 2:43 PM
To: op25-dev at yahoogroups.com
Subject: Re: [op25-dev] Recent changes

 

  

rx.py can already monitor conventional traffic. In fact this feature was there before trunking was.

 

On Tue, 19 Dec 2017 at 06:55, 'William Becks' wa8wg at centurytel.net [op25-dev] <op25-dev at yahoogroups.com> wrote:

  

Graham,

 

Thank you so much for your efforts in the continuing development of op25.  Especially for the recent coding changes allowing for FQDN --wireshark-host command line entry.  The addition of the --nocrypt function was very innovative and solved an issue in my area where some talkgroups use a mix of clear, and encrypted transmissions that were previously impossible to reject without also filtering the clear voice transmissions as well..  

 

I am personally very grateful for the work that you and Max have done to improve the code.  If I could wish for one  new feature, it would be to incorporate code allowing rx.py to monitor conventional IMBE non-trunked transmissions.   Such a feature would be great for monitoring small non-trunked systems in addition to providing a great resource to monitor and analyze amateur P25 transmissions from MMDVM and similar devices.

 

Keep up the good work and best of holiday greetings!

 

Bill, WA8WG

 

 

From: op25-dev at yahoogroups.com [mailto:op25-dev at yahoogroups.com] 
Sent: Saturday, December 16, 2017 7:08 PM
To: op25-dev at yahoogroups.com
Subject: [op25-dev] Recent changes

 

  

For my version of op25 I've just pushed a change to support using hostnames/fully qualified domain names (or straight IP addresses) in the --wireshark-host command line parameter (-W).

Earlier changes include the addition of the source radio id (where available) to the terminal screen, as well as indication of when encryption is active (only applies when using --nocrypt command line option).

 

 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20171218/951c7565/attachment.html>


More information about the op25-dev mailing list