OP25 OP25 - Empty Voice channels

[MTL_Emergencies]

It's weird because when playing it back I get the frequencies I've been talking about... They seem to appear at around TSBK 1300 when syncing to TG 60061 or 50001/50002.

 

[boatbod]

Sorry for slow response... been down with a stomach bug the entire weekend. Will catch up as soon as I can.

 

[boatbod]

I downloaded the capture and replayed it. This is what I ended with:


I'll look at the two logs next and comment on those later if I find anything useful.

 

[boatbod]

When voice channel frequencies are identified and added to the working list (i.e. what you see on the terminal) you get a log level 5 message containing the keyword "new freq". Curiously, my replay log has only 3 of these, which is consistent with the terminal screenshot. The OPs has 57!!

grep "new freq" stderr-play.2
04/02/24 18:14:55.967330 [tk_play] new freq=770.756250
04/02/24 18:14:57.079768 [tk_play] new freq=772.006250
04/02/24 18:15:25.269377 [tk_play] new freq=772.256250

vs

grep "new freq" stderr.4 
03/31/24 17:39:19.477574 [SERAM] new freq=770.756250
03/31/24 17:39:20.525587 [SERAM] new freq=772.006250
03/31/24 17:39:51.707712 [SERAM] new freq=772.256250
03/31/24 17:40:31.029814 [SERAM] new freq=771.606250
03/31/24 17:40:31.029863 [SERAM] new freq=769.006250
03/31/24 17:40:31.164008 [SERAM] new freq=771.631250
03/31/24 17:40:31.164372 [SERAM] new freq=771.656250
03/31/24 17:40:31.298506 [SERAM] new freq=771.681250
03/31/24 17:40:31.298892 [SERAM] new freq=771.706250
03/31/24 17:40:31.421836 [SERAM] new freq=771.743750
03/31/24 17:40:31.422229 [SERAM] new freq=771.756250
03/31/24 17:40:31.556281 [SERAM] new freq=771.781250
03/31/24 17:40:31.556660 [SERAM] new freq=771.806250
03/31/24 17:40:31.814957 [SERAM] new freq=771.893750
03/31/24 17:40:32.083009 [SERAM] new freq=772.043750
03/31/24 17:40:33.260202 [SERAM] new freq=769.293750
03/31/24 17:40:33.528198 [SERAM] new freq=769.443750
03/31/24 17:40:34.309466 [SERAM] new freq=769.743750
03/31/24 17:40:34.705414 [SERAM] new freq=769.893750
03/31/24 17:40:34.967808 [SERAM] new freq=770.043750
03/31/24 17:40:36.157402 [SERAM] new freq=770.531250
03/31/24 17:40:36.271031 [SERAM] new freq=770.556250
03/31/24 17:40:36.282956 [SERAM] new freq=770.581250
03/31/24 17:40:36.416922 [SERAM] new freq=770.606250
03/31/24 17:40:36.418046 [SERAM] new freq=770.643750
03/31/24 17:40:37.068626 [SERAM] new freq=770.881250
03/31/24 17:40:37.069541 [SERAM] new freq=770.906250
03/31/24 17:40:37.203257 [SERAM] new freq=770.943750
03/31/24 17:40:37.204205 [SERAM] new freq=770.956250
03/31/24 17:40:37.586054 [SERAM] new freq=771.093750
03/31/24 17:40:37.588127 [SERAM] new freq=771.106250
03/31/24 17:40:37.714157 [SERAM] new freq=771.156250
03/31/24 17:40:37.719170 [SERAM] new freq=771.181250
03/31/24 17:40:37.848705 [SERAM] new freq=771.243750
03/31/24 17:40:38.639831 [SERAM] new freq=771.543750
03/31/24 17:40:39.025563 [SERAM] new freq=771.693750
03/31/24 17:40:39.293834 [SERAM] new freq=771.843750
03/31/24 17:40:40.078068 [SERAM] new freq=772.143750
03/31/24 17:40:43.616137 [SERAM] new freq=770.431250
03/31/24 17:40:44.401392 [SERAM] new freq=770.731250
03/31/24 17:40:48.990188 [SERAM] new freq=769.481250
03/31/24 17:40:49.385807 [SERAM] new freq=769.631250
03/31/24 17:40:50.168361 [SERAM] new freq=769.931250
03/31/24 17:40:50.430758 [SERAM] new freq=770.081250
03/31/24 17:40:50.824497 [SERAM] new freq=770.231250
03/31/24 17:40:51.882096 [SERAM] new freq=770.681250
03/31/24 17:40:52.275997 [SERAM] new freq=770.831250
03/31/24 17:40:53.055445 [SERAM] new freq=771.131250
03/31/24 17:40:53.318640 [SERAM] new freq=771.281250
03/31/24 17:40:59.086553 [SERAM] new freq=770.481250
03/31/24 17:40:59.477421 [SERAM] new freq=770.631250
03/31/24 17:41:00.143455 [SERAM] new freq=770.931250
03/31/24 17:41:00.529156 [SERAM] new freq=771.081250
03/31/24 17:41:00.918963 [SERAM] new freq=771.231250
03/31/24 17:41:01.578691 [SERAM] new freq=771.531250
03/31/24 17:41:02.369476 [SERAM] new freq=771.831250
03/31/24 17:41:03.025976 [SERAM] new freq=772.131250

 

[MTL_Emergencies]

That's strange. Here is another transfer: https://we.tl/t-UogYRRfArt . I included my whitelist file, the tgid file (tags), sh file, json file and log (stderr.4). The frequencies start to appear at around 3000 tsbks. With all of these file you should be able to recreate the environment. I was able to replay the capture and observe the said frequencies.

 

[boatbod]

I've played around a bit more (set up tg priorities and whitelists to match yours) and can categorically say that you are not running the same version of tk_p25.py as I am.

My decode log following voice update for tg=50002:

04/02/24 20:38:23.712103 [0] MAC_ACTIVE: mco=1/02(0x42), len=9, mco=2/35(0xb5), len=5, mco=0/00(0x00), len=3, rs_errs=1
04/02/24 20:38:23.720316 [tk_play] set tgid=60181, srcaddr=None, svcopts=None
04/02/24 20:38:23.720399 [tk_play] VF ts ph2: tgid: 60181, freq: 770.756250, slot: 1
04/02/24 20:38:23.720443 [0] tsbk(0x02) grp_v_ch_grant_up: ch1: 770.756250 ga1: 60181 ch2: 770.756250 ga2: 60181

Your decode log of the same sequence:

03/31/24 17:40:31.027079 [0] MAC_ACTIVE: mco=1/02(0x42), len=9, mco=2/35(0xb5), len=5, mco=0/00(0x00), len=3, rs_errs=1
03/31/24 17:40:31.028166 [SERAM] set tgid=60181, srcaddr=0
03/31/24 17:40:31.028217 [SERAM] VF ts ph2: tgid: 60181, freq: 770.756250, slot: 1
03/31/24 17:40:31.028235 [0] tsbk(0x02) grp_v_ch_grant_up: ch1: 770.756250 ga1: 60181 ch2: 770.756250 ga2: 60181

Notice how your log doesn't include "svcopts=None" at the end of the second line? This extra logging message was pushed to git around Feb 18. Shortly after I also pushed a fix for a bug in TDMA message decode parsing, and it is this latter fix that you are missing, which I believe is causing the erroneous frequencies to show up in your terminal.

I suggest you might try cloning and building a freshly pulled op25 repo to see if that fixes your problem. The code you are running now has either been modified or otherwise got into a state that git is not updating properly. Let me know what happens when you do that.

 

[MTL_Emergencies]

I removed OP25 and reinstalled it and it worked! Weird because I did rebuild it before using the rebuild.sh script and it didn't append the changes...

 

[lwvmobile]

I removed OP25 and reinstalled it and it worked! Weird because I did rebuild it before using the rebuild.sh script and it didn't append the changes...

Yeah, but if you still had your custom source code in place, the rebuild.sh script isn't going to clear those out for you, it'll just pull new updates. It may in fact, leave an error if you have uncommitted changes, staged changes, or committed changes that conflict with new code being pulled in, so most likely, it didn't pull new code and also just rebuilt what you already had changed.

 

[boatbod]

I removed OP25 and reinstalled it and it worked! Weird because I did rebuild it before using the rebuild.sh script and it didn't append the changes...

Glad to hear it's working now.
If you're going to locally modify version-controlled files, you're better off forking your own copy of the repo and committing your changes once you're happy with then. That way you can pull upstream changes and merge them in a controlled manner.