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/.
scancaster at scancaster.net scancaster at scancaster.netBefore I go down a hole and end in a dead end.... I have some questions on using the -L option for "logging." Logging in my universe means logging the audio to Dictaphone/tape/disk/CD/what ever physical media... NOT the -v option, thats a log, not logging! :) ;) So after reading about 30 different files on this -L option, it appers that it will act as A LOGGING RECORDER and RECORD the audio to disk... Great! What I am after is to record UNKNOWN GROUPS for analysis for ID purposes.... My question(s) are what options are used with this for: rx.py trunk.tsv whitelist.tsv blacklist.tsv ie: rx.py example ./rx.py --args 'rtl' -N 'LNA:47' -S 2400000 -f 8xx.xxxxe6 -o 25000 -q 72 -L 4 -v 10 -T trunk.tsv -V -2 -U -O loop0 -M mysystem.json -l http:192.168.0.26:8080 -x 3 2>> stderr.2 trunk.tsv then REQUIRES a "center frequency" for the system... 8xx.xxxx based on the channels of the system... I've determined this for this system, and it will just fit the way this is setup. This will then RECORD the various groups that are NOT BLACKLISTED to disk as WAV's from what I understand... Correct???? Ie: OP25 tunes to a group, it records it. Anything that is exlusive of each other on this -L option with other optons for rx.py???? Any thing I am missing in this????? Goal is simple to log any group I've not blacklisted as known user/use.. Thanks.