[op25-dev] OP25 setup once built [1 Attachment]

John Ackermann N8UR jra@febo.com [op25-dev] op25-dev at yahoogroups.com
Fri Jun 9 16:57:31 UTC 2017


As you suggested, I deleted the "-T trunk.tsv" and set the frequency to 
the control channel.  Now I'm seeing lots of decodes on the "traffic" 
tab.  Woot woot!

Next step is to get the trunk.tsv file sussed...

Thanks much for the suggestions.

On 06/09/2017 11:37 AM, ikj1234i at yahoo.com [op25-dev] wrote:
> ok the console window indicates you're receiving on a NAC of 0x343 
> whereas the traffic tab shows a NAC of 0x25A.  (with respect to these 
> two NACs, your trunk.tsv is totally daft).  This is certainly one 
> problem.  At the stage you're at you should forego the trunk TSV and use 
> manual mode until the trunk CC is properly acquired.
> 
> Separately the datascope indicates a very strong LSM signal (i.e., not 
> C4FM), so you'll need to use the constellation tab for normal ops.  If 
> you stay on the datascope tab it will (incorrectly) use the C4FM demod, 
> this is a legacy of scope.py.   Based on that constellation any attempt 
> to use C4FM will fail miserably, it's pretty nasty and a really good 
> example of why C4FM demods won't work well on LSM.
> 
>   One other thing is that your datacscope tab isn't centered vertically, 
> it suggests the tuning is slightly below where it should be tuned.  This 
> can be adjusted using the -q pa rameter and fine tuned using the slider...
> 
> Max
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20170609/fa13d3b1/attachment.html>


More information about the op25-dev mailing list