[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/.

iain macdonnell - N6ML n6ml@dseven.org [op25-dev] op25-dev at yahoogroups.com
Tue Nov 27 00:35:00 UTC 2018


On Mon, Nov 26, 2018 at 4:15 PM 'Trunk Tracker'
trunktracker at tampabay.rr.com [op25-dev] <op25-dev at yahoogroups.com>
wrote:
> For the command line options, the readme file doesn't seem to give you examples or lists of values of what to actually type.  For example, the -N 'LNA:15,MIX:15,IF:15' syntax was something I searched for and found in a RadioReference forum.  One of my screenshots below shows "built-in source types:" with what looks like a list of things that can be entered with the --args command.  But it doesn't list 'airspymini' as one of the options and I wonder if it should?

I think if you just make up something bogus, it'll be ignored.

Please paste the contents of stderr.2 after each attempt.


> And how about this question.  How come we use an "e6" after the frequency -f 769.28125e6?

Frequency is given in Hz. "e6" means "x 10^6".

    ~iain


> From: wllmbecks at gmail.com [mailto:wllmbecks at gmail.com]
> Sent: Sunday, November 25, 2018 10:28 PM
> To: op25-dev at yahoogroups.com
> Cc: trunktracker at tampabay.rr.com
> Subject: FW: [op25-dev] Re: Beginner's Guide To Setting Up OP25 From Scratch
>
>
>
> OK.   You’re making good progress.     The last screen capture below is blank so I can’t see what it flipped to.
>
>
>
> I appears that you are attempting to decode Hillsborough County (P25) but may not have specified the correct control channel frequency according to
>
> the listing for Hillsborough County on radioreference.com.    You might need to try 770.33125 or 769.80625 instead of 769.28125.
>
>
>
> The following rx.py command line will work without a trunk.tsv file and will decode the system provided you specify the correct (active) control channel.
>
>
>
> ./rx.py --args 'airspy' -S 3000000 -N 'LNA:15,MIX:15,IF:15' -f 769.28125e6 -t -q 0 -V -U 2> stderr.2
>
>
>
> The 2> stderr.2 will send error messages and other status to a logfile and will prevent garbage from appearing on your terminal screen.
>
> This same logfile will also be very helpful if things still don’t work to diagnose the problem.
>
>
>
> When you have the correct control channel frequency, your terminal screen should look something like my screen
>
> capture shown below except that it will display your systems NAC, WACN, SYSID, and frequency.
>
>
>
> When op25 is working the tsbks (Trunk Signaling Blocks) value will constantly increment except when
>
> voice traffic is present, and will then resume as soon as the system goes idle again.   Other data will
>
> be displayed indicating the voice trunk frequency and talkgroup ID when there is traffic present.
>
>
>
> Bill, WA8WG
>
>
>
>
>
> From: op25-dev at yahoogroups.com <op25-dev at yahoogroups.com>
> Sent: Sunday, November 25, 2018 6:17 PM
> To: op25-dev at yahoogroups.com
> Subject: RE: [op25-dev] Re: Beginner's Guide To Setting Up OP25 From Scratch
>
>
>
>
>
> Well, thanks.  I tried re-booting and un-plugged both Airspys and plugged only 1 of 'em back in.  Then I was able to see it in VMWare and connect it via the following menu option:
>
>
>
>
>
> Then I ran lsusb and got the following (so now it's showing up):
>
>
>
>
>
> When I run dmesg, I get a very long list of stuff, but here's what I found at the end:
>
>
>
>
>
> But now I still get a similar error when running a command line of ./rx.py --args 'airspy' -N 'LNA:10,MIX:10,IF:10' -S 3000000 -f 769.28125e6 -o 25000 :
>
>
>
>
>
> My device is actually an Airspy Mini, so I wonder if that has something to do with it.  So as a complete shot in the dark, I tried changing it to 'airspymini' and leaving everything else the same:
>
>
>
> ./rx..py --args 'airspymini' -N 'LNA:10,MIX:10,IF:10' -S 3000000 -f 769.28125e6 -o 25000.
>
>
>
> Here's what I get now instead of the error:
>
>
>
>
>
> No idea what all this is, but I noticed if I then grab the window edge and re-adjust the size of the terminal window, the screen suddenly flips to this:
>
>
>
>
>
> So does this mean the software program, OP25, is running now?
>
>
>
> trunktracker at tampabay.rr.com
>
>
>
> From: wllmbecks at gmail.com [mailto:wllmbecks at gmail.com]
> Sent: Sunday, November 25, 2018 8:00 AM
> To: op25-dev at yahoogroups.com
> Cc: trunktracker at tampabay.rr.com
> Subject: RE: [op25-dev] Re: Beginner's Guide To Setting Up OP25 From Scratch
>
>
>
> Trunktracker
>
>
>
> Here are a couple of steps to insure that your Airspy device is available to your Ubuntu VM.
>
>
>
>
>
> Remove one of the Airspy devices.  You do not need two devices in rx.py.
> Set /verify that the remaining Airspy device is virtualized in your VMware settings menu for the Ubuntu VM.
> Start the Ubuntu VM then execute lsusb from the command line.  It should return somethings like the lines below if your Airspy devices has been virtualized.
>
>
>
> op25 at op25-VirtualBox:~$ lsusb
>
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>
> Bus 001 Device 003: ID 1d50:60a1 OpenMoko, Inc.       ß This is the Airspy device
>
> Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>
>
> Now execute dmesg from the command line.   The terminal output should have lines similar to these.
>
>
>
> 5.911019] airspy 1-2:1.0: Board ID: 00
>
> [    5.911024] airspy 1-2:1.0: Firmware version: AirSpy NOS v1.0.0-rc10-0-g946184a 2016-09-19
>
> [    5.914976] airspy 1-2:1.0: Registered as swradio0
>
> [    5.914980] airspy 1-2:1.0: SDR API is still slightly experimental and functionality changes may follow
>
>
>
> Your VM must be able to see the Airspy before proceeding to debug your rx..py command line and trunk.tsv files..
>
> My Airspy is the R2 and has different sampling rates than the Mini.    You must specify the correct sample rate on
>
> the rx.py command line that is supported by the Mini.
>
>
>
> Bill, WA8WG
>
>
>
>
>
>
>
> Well, I've gotten a little further but am stuck on this part.  I've got 2 Airspy Minis plugged in and if I run the following:
>
>
>
> ./rx.py --args 'airspy' -N 'LNA:10,MIX:10,IF:10' -S 2400000 -f 769.28125e6 -o 25000
>
>
>
> I get a lot of errors (screenshot):
>
>
>
>
>
> So is there any way to trouble shoot all of this?  Thanks.
>
>
>
> trunktracker at tampabay.rr.com
>
>
>
> From: Trunk Tracker [mailto:trunktracker at tampabay.rr.com]
> Sent: Saturday, November 24, 2018 5:13 PM
> To: 'op25-dev at yahoogroups.com'
> Subject: RE: [op25-dev] Re: Beginner's Guide To Setting Up OP25 From Scratch
>
>
>
> Thanks for the dummies link.  Just what I need!  It looks like there's another step to install something called GNUPLOT:
>
>
>
> sudo apt-get install gnuplot-x11
>
>
>
> trunktracker at tampabay.rr.com
>
>
>
> From: op25-dev at yahoogroups.com [mailto:op25-dev at yahoogroups.com]
> Sent: Friday, November 23, 2018 10:48 PM
> To: op25-dev at yahoogroups.com
> Subject: [op25-dev] Re: Beginner's Guide To Setting Up OP25 From Scratch
>
>
>
>
>
> As mentioned before this is likely the most recent how-to:
>
>
>
> https://www.hagensieker.com/wordpress/2018/07/17/op25-for-dummies/
>
>
>
> A year ago I wrote this, when it was just starting to be a thing to install OP25 on a Raspberry Pi:
>
>
>
> http://kb9mwr.blogspot.com/2017/07/listening-to-local-700-mhz-simulcast.html
>
>
>
> While I don't have any desire to run op25 on Windows, unfortunately I can see a good how-to on that sort of thing being desirable to many.
>
>
>
> I am a ham and I like to tinker, not just be a end user.  So I don't see anyone using this on Windows really contributing anything back to the community.  I really urge people to dig into things deeper than skin level, you never know, you just might learn something.  But that is just me.
>
>
>
>
>
>
>
>
>
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20181126/4f19535f/attachment.htm>


More information about the op25-dev mailing list