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/.
ikj1234i@yahoo.com [op25-dev] op25-dev at yahoogroups.comHi John we need to do a better job of documenting the process of initial acquisition of the system. The process itself could be made easier, as could 1,000 other things... Could you post the command line you're running, and if possible post a screen print of the 'datascope' and 'constellation' plots... The best approach usually has been to first get the control channel coming in well in manual tuning mode (i.e., no -T parameter), then (and only then) to try to get voice decode working. In rx.py the way you'll know when the CC is tuned correctly is the number in the upper-right corner of the page (TSBKs) should be increasing steadily. Assuming you have the correct CC frequency, the most common troubles tuning are: not using the proper PPM correction (-q parameter), failing to add an offset (I usually use -o 50000), incorrect RTL gain setting via the --gains (-N) parameter, incorrect use of FSK4 mode on an LSM P25 system (and vice-versa, using the CQPSK mode on a C4FM P25 system)... Tuning in the CQPSK mode is fussier than in FSK4 mode, and messages should get written to the stderr file in the event of a slight mistuning... Max -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20170702/2fcc3553/attachment.htm>