[op25-dev] Beginner's Guide To Setting Up OP25 From Scratch

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/op25-dev@lists.osmocom.org/.

wllmbecks@gmail.com [op25-dev] op25-dev at yahoogroups.com
Thu Nov 29 00:50:40 UTC 2018


Your logfile reports that op25 does not see your Airspy device.     This may be as a result of a virtualization problem with your Ubuntu VM.     Run another lsusb and see if the Airspy device still

shows up or not.    If it does, then I would be suspect that the airspy library did not initiate properly during the installation phase.  BTW,  you don’t need the -2 in your rx.py command line because your county is running a Phase-I system.  Of course, that is not the issue at this point in time.       

 

I am willing to help you over the phone if you want some help and want to install TeamViewer on your PC so that I can access your VM remotely to take a look at a few things.

 

Bill

 

 

 

From: op25-dev at yahoogroups.com <op25-dev at yahoogroups.com> 
Sent: Wednesday, November 28, 2018 5:43 PM
To: op25-dev at yahoogroups.com
Subject: RE: [op25-dev] Re: Beginner's Guide To Setting Up OP25 From Scratch,

  

Well, it's a busy workweek, so I've been slow to reply back.  But thanks for all the suggestions.  The control channel changed today, so I cleared out everything in stderr.2 first and then ran this:

 

../rx.py --args 'airspy' -S 3000000 -N 'LNA:15,MIX:15,IF:15' -f 769.80625e6 -t -q 0 -2 -w -U 2> stderr.2

 

and got this:

 



 

Then I looked in stderr.2 and found this:

 

..

 

But if I do the same thing with 'airspymini' instead, I get this:

 



 

And stderr.2 has all this in it:

 

gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.11

built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp 

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

[INFO] Using format CF32.

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Using two-stage decimator for speed=3000000, decim=30/4 if1=100000 if2=25000

Project 25 IMBE Encoder/Decoder Fixed-Point implementation

Developed by Pavel Yazev E-mail: pyazev at gmail.com <mailto:pyazev at gmail.com> 

Version 1.0 (c) Copyright 2009

This program comes with ABSOLUTELY NO WARRANTY.

This is free software, and you are welcome to redistribute it

under certain conditions; see the file ``LICENSE'' for details.

op25_audio::open_socket(): enabled udp host(127.0.0.1), wireshark(23456), audio(23456)

p25_frame_assembler_impl: do_imbe[1], do_output[0], do_audio_output[1], do_phase2_tdma[1], do_nocrypt[0]

audio device: default

 

RtApiAlsa::getDeviceInfo: snd_pcm_open error for device (hw:0,0), Device or resource busy.

 

 

RtApiAlsa: dump hardware params just after device open:

 

ACCESS:  MMAP_INTERLEAVED RW_INTERLEAVED

FORMAT:  U8 S16_LE

SUBFORMAT:  STD

SAMPLE_BITS: [8 16]

FRAME_BITS: [8 32]

CHANNELS: [1 2]

RATE: [4000 48000]

PERIOD_TIME: (333 16384000]

PERIOD_SIZE: [16 65536]

PERIOD_BYTES: [64 131072]

PERIODS: [1 1024]

BUFFER_TIME: (333 16384000]

BUFFER_SIZE: [16 65536]

BUFFER_BYTES: [64 65536]

TICK_TIME: ALL

 

RtApiAlsa: dump hardware params after installation:

 

ACCESS:  RW_INTERLEAVED

FORMAT:  S16_LE

SUBFORMAT:  STD

SAMPLE_BITS: 16

FRAME_BITS: 16

CHANNELS: 1

RATE: 48000

PERIOD_TIME: (42666 42667)

PERIOD_SIZE: 2048

PERIOD_BYTES: 4096

PERIODS: 4

BUFFER_TIME: (170666 170667)

BUFFER_SIZE: 8192

BUFFER_BYTES: 16384

TICK_TIME: 0

 

RtApiAlsa: dump software params after installation:

 

tstamp_mode: NONE

tstamp_type: MONOTONIC

period_step: 1

avail_min: 2048

start_threshold: 2048

stop_threshold: -1

silence_threshold: 0

silence_size: 4611686018427387904

boundary: 4611686018427387904

 

trunktracker at tampabay.rr.com <mailto:trunktracker at tampabay.rr.com> 

 

From: wllmbecks at gmail.com <mailto:wllmbecks at gmail.com>  [mailto:wllmbecks at gmail.com] 
Sent: Tuesday, November 27, 2018 3:57 PM
To: op25-dev at yahoogroups.com <mailto:op25-dev at yahoogroups.com> 
Cc: trunktracker at tampabay.rr.com <mailto:trunktracker at tampabay.rr.com> 
Subject: RE: [op25-dev] Re: Beginner's Guide To Setting Up OP25 From Scratch

 

Trunktracker,

 

>From what I can fine the Airspy Mini gets configured the same as the Airspy R2 with

the exception being the sample rate differences.

 

I further assume from an earlier posting that your installed the op25/boatbod version that

supports starting rx.py without a trunk.tsv file using just the -t option.   This was a handy

feature that allows you to discover the P25 system’s NAC, SID, and other information needed to properly

construct your trunk.tsv file.    

 

As has already been suggested, do post your stderr.2 logfile..   OP25 will create and write to the logfile

(stderr.2) each time you execute the  rx.py command line with the 2> stderr..2 option specified.  The

Information contained in that logfile should prove useful to diagnose what is happening.

 

Bill, WA8WG

 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20181128/2e34242a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 44985 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20181128/2e34242a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 94740 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20181128/2e34242a/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 29811 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20181128/2e34242a/attachment-0002.png>


More information about the op25-dev mailing list