[op25-dev] A couple Q's - RID Aliases? CC Data

op25 at zellners.com op25 at zellners.com
Mon Feb 25 15:35:36 UTC 2019


Quoting Graham Norbury <gnorbury at bondcar.com>:

> Sorry, RID alias is not there yet.
> Biggest issue on curses terminal (i.e. non-http) is the lack of  
> space for the RID String.
>

Just as FYI and comment on this... while it would be nice, great etc.  
if the various interfaces displayed the RID data ie: ncurses and/or  
the http....

If its possible to ADD that to the metatag process thats where I am  
more interested in it.. the display be it http/ncurses is really not  
used 99.999999999999999% of the time... its dumped to a screen  
session, dettached, and hopefully forgotten about... right now for  
testing/setup that may not be the case, but thats the goal... same  
with the http... that might change if there was more data in either  
ala sdtrunk showing the events...even at -v 10 the log which I keep in  
a tail screen doesn't log the various events that others do.. now that  
may be where the wireshark interface was meant to deal with that and  
not op25 itself... I am talking about IDEN UP, RSSI info (http does  
grab this), affiliations, failed registrations etc... All that seems  
to just be ignored from that CC stream in -v10...again that may be the  
intention and again it was expected to pass this to wireshark, that  
seems to be a dead end now????...


So tl;dr, if you can get RID's to the tag data and even if it doesn't  
show on the interface that would be great... that wouldn't need an y  
space on the interfaces be it http or ncurses....  Add it to the tag  
interface shouldn't be wasted effort.. and when space, time what not  
it can be added to the interfaces when time, space etc. permit.

ie:

  TGID ..... RID: MayberryPD1

etc....

Which gets me back to the another part of this...

Is there something that outlines the various ways that the threads are  
started, interaction with that CC data... again I have personal use  
cases I'd like to explore, but don't have a reference starting point  
to go from where all this interaction is... rx.py seems to call  
various things as threads to deal with things... ie: tags.....





More information about the op25-dev mailing list