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/.
John Ackermann N8UR jra@febo.com [op25-dev] op25-dev at yahoogroups.comI have an image file with a working OP-25 "max" branch Raspberry Pi 3 system available if anyone wants to try it (just copy to an SD card and boot). I'm in a low-bandwidth location now, but will be back home late next week. Ping me if you want to grab it. Johm On Aug 29, 2017, 1:19 PM, at 1:19 PM, "James K4JK k4jk.james at gmail.com [op25-dev]" <op25-dev at yahoogroups.com> wrote: >Thanks for the reply. It sounds like using scope.py from the main >branch is >the best bet at this point. > >I've been thinking about building a mini desktop with Ubuntu 14.04 for >use >specifically with OP25, so I think I will finally bite the bullet and >do >so. I don't think the main branch liked my Debian 8 installation when I >tried to compile. > >When using scope.py do I need to do the same thing as far as turning >off >audio decoding for use with wireshark? Would this be what I want for >example? > >./scope.py --args 'rtl' -N 'LNA:30' -f <freq> -S 1000000 -q 1 -v 10 >-w -W >224.0.0.1 -T file.tsv > > > >Thanks again > > > >On Tue, Aug 29, 2017 at 12:31 PM, gnorbury at bondcar.com [op25-dev] < >op25-dev at yahoogroups.com> wrote: > >> >> >> You'll definitely want to turn off all audio decoding (-2 and -V) >when >> using wireshark, otherwise the audio stream will pollute the P25 data >being >> sent over UDP. Beyond that it's unclear to me whether wireshark >works >> properly with the rx.py version of the op25 codebase. I don't >believe it's >> been tested to any degree. >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20170829/c682b2ca/attachment.htm>