OP25 A request about similar NACs and a question about the -l http terminal

[noamlivne]

First of all, thank you very much Boatbod and Max.
I am revisiting OP25 (Boatbod's fork) after more than 2 years that I did not touch it and it works great again.
I newly installed it on a Windows 10 laptop that runs Ubuntu 20.04 on a Virtual Machine Player. I used the ./install.sh and it was excellent!

I see that I still cannot set up a .tsv file that contains multiple control channels with the same NACs.

At the example below only Service 3 will be used. Services 1 and 2 will be ignored.
Service1 865.4 0 0x345 C4FM groups.tsv blocked.tsv
Service2 860.1234 0 0 C4FM groups.tsv blocked.tsv
Service3 862.5678 0 0 C4FM groups.tsv blocked.tsv

It does not work even if I set all the NACs to 0 (because all of them are the same 0), or even if I set one real NAC such as 0x345 and NAC 0.
I wonder if you can find a solution for that?

And a not so important question: how can I view the -l terminal window that works great in the Virtual Machine's browser, in the browser of the Host (Windows 10)?
So I can view the http terminal at 127.0.0.1:808 for example in the Ubuntu's Firefox, but if I enter that address in the Windows machine I get nothing.
This is of course not related to OP25, but maybe someone knows.

Thank you,
Noam

 

[KA1RBI]

If it is simply a single system with multiple control channels you can specify the control channel frequencies as a comma-separated list in the trunking TSV. Otherwise I'm not clear what you're trying to accomplish with this setup - please provide more details as to the reason for wanting multiple entries. Agreed, using the NAC to differentiate systems was not the best choice in the original design.

To access the http port from outside the VM requires assistance from the VM software. In the "kvm" virtualizer it's a matter of adding a line such as
-net user,hostfwd=tcp::8080-:8080
to the command line parameters. Other VM software probably has its own method for forwarding ports.

To open the port on the linux vm side you may also need to specify "-l http:0.0.0.0:8080" (instead of 127.0.0.1) to enable connections from other than localhost. This may not (or may) be needed if you're simply doing port-forwarding as mentioned above....

Max

 

[noamlivne]

Thank you very much for your reply and tip about the KVM.

Agreed, using the NAC to differentiate systems was not the best choice in the original design.

Yep, that is indeed what I meant. I need to use the same NACs to differentiate systems.

See attached trunk.tsv file as an example. (sorry about the .zip file, I could not upload .tsv).
Only the last P25 System5 will be heard.

My main goal is to listen to those different P25 systems one after the other.
Had they have different NACs, I would have been able to listen to each P25 System, and they would have changed every minute or so (if there is no activity, I think) - which is exactly what I need. Moving through systems automatically.
This could have been the best way for me - to listen "automatically" to different systems one after the other.

Of course I can listen "manually" to one P25 System, get bored, issue another ./rx.py command with a different system. Get bored. Issue another ./rx.py command and listen to another system...

Unfortunately, all my P25 Systems have the same NAC so I cannot give all of them 0x345 or 0 NAC because they are "duplicated".

I wonder if it it would be possible to change this mechanism that NACs cannot be the same?

Thank you,
Noam

 

[boatbod]

Suggest you try using multi_rx.py and the cfg.json method of defining P25 trunking systems. You should be able to define multiple system and each will be able to have the same (or different) NAC because the new code keys on the system name which is user-defined rather than the nac value.

Note that you'll need to dedicate one RTL to each P25 system, or have a wide-band SDR that can receive the whole system bandwidfth and share this between your receiver channels.

 

[noamlivne]

Thank you, Boatbod, for the tip.
Nonetheless, I hope that one day duplicate NACs (or no NACs at all) will be allowed.
Thanks,
Noam

 

[boatbod]

Thank you, Boatbod, for the tip.
Nonetheless, I hope that one day duplicate NACs (or no NACs at all) will be allowed.
Thanks,
Noam

No, that's never going to happen with rx.py version because it has for practically all purposes been superseded by multi_rx.py.

 

[noamlivne]

Understood.
Thank you very much.