OP25 -v option debug levels

k7dq

Member
Premium Subscriber
Joined
Dec 22, 2016
Messages
12
Location
Clinton, Ut
Looking for a definition of each of the debug levels that the -v option has for multi_rx.py. (boatload version).
I how used both -v 1. and -v 5. I see that -v 5 will show the attempts at getting control channel frequencies and also the different frequencies and talk groups as they are active. (also recently add_patch and expire patches information)
are there other debug levels (2 through 4 and 6 through 10 or more). I think I read somewhere about 10 but can't find that listing or that thread.
if there a listing somewhere in the code, perhaps just point me to the correct modules.
Thanks.
 

boatbod

Member
Joined
Mar 3, 2007
Messages
3,409
Location
Talbot Co, MD
Looking for a definition of each of the debug levels that the -v option has for multi_rx.py. (boatload version).
I how used both -v 1. and -v 5. I see that -v 5 will show the attempts at getting control channel frequencies and also the different frequencies and talk groups as they are active. (also recently add_patch and expire patches information)
are there other debug levels (2 through 4 and 6 through 10 or more). I think I read somewhere about 10 but can't find that listing or that thread.
if there a listing somewhere in the code, perhaps just point me to the correct modules.
Thanks.
Logging is additive, so selecting a higher level gets you all that came before, up to whatever level is selected. It's not a perfect world, and I really wish the logging were bitmap based, so you could turn on/off specific subsystems, but that would be a big re-write effort.

-v 0 : disable logging except for critical error messages
-v 1 : bare minimum logging, useful to see call activity
-v 5 : shows internal tgid activity (grants, updates, patches, holds)
-v 9 : shows xMBE codewords
-v 10 : shows P25 messages
-v 11 : shows message decode, internal processing (currently this is the most verbose level)
 
Top