Date   

Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Cort N0MJS <n0mjs@...>
 


On Jan 2, 2019, at 3:42 PM, Jason Johnston <kc5hwb@...> wrote:

Just for the heck of it, I tried uninstalling python-dev, python-pip and python-twisted, then rebooted and installed everything again.  Upon running the "pip" commands below:
pip install bitstring
pip install bitarray

I get these errors:
root@josephus:~# pip install bitstring
Requirement already satisfied (use --upgrade to upgrade): bitstring in /usr/local/lib/python2.7/dist-packages

Not an error, it only says that bitstring, current version, is already installed. uninstalling python-dev, python-pip and python-twisted will not uninstall bitstring.
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
This is not your OS telling you to upgrade pip. This is a shameful advertisement on pip’s part telling you to upgrade it.
root@josephus:~# pip install bitarray
Requirement already satisfied (use --upgrade to upgrade): bitarray in /usr/local/lib/python2.7/dist-packages
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Same as the above module.
If I am going to reinstall the OS, which I have no problem with, then what is to prevent this error next time?  What am I missing here?
I'm gonna really come off like an ass, so get ready to get mad at me. For real - you’re about to get mad.

I can’t really answer your questions. I don’t feel like I’m competent to support your OS distribution or python. The problems you’ve been having aren’t with my software itself. They’ve all been with OS stuff and the python install. These issues would be better handled on a python forum. I use python as a tool – I don’t pretend to be an expert on it’s internals, or the installation of 3rd party modules. Now the only thing I’ll say to redeem my asshole-ishness here is that the README.md with hblink is very clear – it expects the user to have familiarity with unix/linux and python. And exactly what I meant by that is that anyone wanting to use HBlink, as it stands, is going to need to be able to handle basic level unix system configuration/administration and be familiar with python – which includes things like using pip, reading a python module “requirements.txt” file, etc.

There, I said it. I don’t feel good about me right now either…. but there it is. If there’s anyone on the list that feels like they have a really good handle on fixing broken python installs, would you please contact Jason off-list and try to help him with this?



--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: HBLink and HBLink3

Cort N0MJS <n0mjs@...>
 

HBlink has to do a little more calculation of things than DMRlink does. In the respective confbridge applications (renamed just bridge.py in hblink3), hblink has to calculate the complete LC and the embedded LC pieces for each new stream. It turns out that’s not too big of a deal. DMRlink and HBlink should be pretty close in how much resources they “hog”. There are some other things I want to fix – like depending on a unique stream ID to tell one call stream from another… that will reduce processing time, and as it turns out, statistically, the chances of two identical stream IDs on the same slot at the same time is….. a lot lower than the likelihood I’ll get killed by someone drink driving tomorrow night.

Here’s the bad news. K0USY Group has chosen (it’s not me, it’s actually a group) to pull our Motorola XPR series repeaters out of service and sell them. We’re replacing them with Motorola MTR2000s and MMDVM. We’re going to be going 100% MMDVM on our own network. This has the dubious result of eliminating my testbed for Motorola IPSC. I’m actually supportive of that because it best serves K0USY Group’s goals.

At this point it’s uncertain whether or not I’ll have the time to migrate DMRlink to Python3. DMRlink may end up being sunset and only bug-fixes in the future. I live in two worlds – the Kansas DMR network in the US, and these projects. My own radio network has decided that MMDVM is the way of the future, and is moving that way. It will have the effect of moving me with it to a great degree.

Nothing is final – nothing ever is. But the one thing we learned on KS-DMR since beginning operations in 2010 is that IPSC was great for what it was intended for. Within that scope, it’s hands-down far better than HomeBrew. But, the majority of what we (KS-DMR, probably others too) do with Ham radio is outside the intended scope of IPSC, and HomeBrew makes a better platform for what we do as hams. I’ve decided that, elegant as it is, the “simulated multicast” over unicast networking methodology of IPSC is simply too complicated to troubleshoot with more than a few repeaters and a number of random internet connections.

Likewise, IPSC is inefficient run as a one-repeater, one-bridge per “IPSC system”… you know like the c-Bridge guys do who talk about “one repeater per manager”. IPSC’s glory is wasted when you use it that way, and HomeBrew actually becomes  much better protocol.

I guess this turned into a bit of a rant about ham radio DMR – and I most assuredly will be really pissing someone off with it. I do not intend to abandon DMRlink, but the writing is kinda on the wall…. IPSC just isn’t the right protocol to build wide-area networks with lots of repeaters.

On Jan 2, 2019, at 4:20 PM, Peter M0NWI <peter-martin@...> wrote:

All sounds interesting!! 

Will DMRlink get the Python3 hurry up as some stage?  Although I have to say, even on my meagre VM With ~10 Moto repeaters, IPSC bridge to a few MMDVM on HBlink, I’ve never noticed any performance issues!! 

Is HBLink more of a performance hog that IPSC?

Regards
Peter

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: 02 January 2019 22:12:38
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] HBLink and HBLink3
 
HBlink 3 is non-functional at this point. It will not work. It is on GitHub because I use GitHub to sync multiple computers I do development on.

Once HBlink3 is completed and has parity with HBlink, HBlink will be depreciated and all new development will be with HBlink3. The 3 means it runs on Python3. There are a number of advantages to moving to Python3 – which wasn’t possible when I began the project. Once I have everything working, the next move will be to pull twisted out from underneath it and replace it with a combination of asyncio and uvloop. This should bring network performance close to that of a compiled machine code program.

A bit of a deeper dive for those who are interested. A few weeks ago we did some heavy duty performance measurement on the K0USY KS-DMR network – where we run my tools in production. We wanted to know how far this thing will scale with modest resources. What we ended up finding out is that the network calls through twisted are the most costly in terms of time. Twisted is a GREAT module, don’t get me wrong. But we really don’t use it the way it was intended. We use fairly low-level pieces, of which there are much faster options in Python3. How much faster? Two orders of magnitude.

That’s the roadmap as of now – get HBlink3 working, then migrate to different underlying network modules.

On Jan 2, 2019, at 3:43 PM, Kim-Benjamin Lütkemeier via Groups.Io <kbluetkemeier@...> wrote:

Hello,
the HBlink and HBlink3 has the same status?

You add some functions on booth version or you only support HBLink3 now?

Good Job
Do1KBL

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: HBLink and HBLink3

Peter M0NWI
 

All sounds interesting!! 

Will DMRlink get the Python3 hurry up as some stage?  Although I have to say, even on my meagre VM With ~10 Moto repeaters, IPSC bridge to a few MMDVM on HBlink, I’ve never noticed any performance issues!! 

Is HBLink more of a performance hog that IPSC?

Regards
Peter


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: 02 January 2019 22:12:38
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] HBLink and HBLink3
 
HBlink 3 is non-functional at this point. It will not work. It is on GitHub because I use GitHub to sync multiple computers I do development on.

Once HBlink3 is completed and has parity with HBlink, HBlink will be depreciated and all new development will be with HBlink3. The 3 means it runs on Python3. There are a number of advantages to moving to Python3 – which wasn’t possible when I began the project. Once I have everything working, the next move will be to pull twisted out from underneath it and replace it with a combination of asyncio and uvloop. This should bring network performance close to that of a compiled machine code program.

A bit of a deeper dive for those who are interested. A few weeks ago we did some heavy duty performance measurement on the K0USY KS-DMR network – where we run my tools in production. We wanted to know how far this thing will scale with modest resources. What we ended up finding out is that the network calls through twisted are the most costly in terms of time. Twisted is a GREAT module, don’t get me wrong. But we really don’t use it the way it was intended. We use fairly low-level pieces, of which there are much faster options in Python3. How much faster? Two orders of magnitude.

That’s the roadmap as of now – get HBlink3 working, then migrate to different underlying network modules.

On Jan 2, 2019, at 3:43 PM, Kim-Benjamin Lütkemeier via Groups.Io <kbluetkemeier@...> wrote:

Hello,
the HBlink and HBlink3 has the same status?

You add some functions on booth version or you only support HBLink3 now?

Good Job
Do1KBL

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: HBLink and HBLink3

Cort N0MJS <n0mjs@...>
 

HBlink 3 is non-functional at this point. It will not work. It is on GitHub because I use GitHub to sync multiple computers I do development on.

Once HBlink3 is completed and has parity with HBlink, HBlink will be depreciated and all new development will be with HBlink3. The 3 means it runs on Python3. There are a number of advantages to moving to Python3 – which wasn’t possible when I began the project. Once I have everything working, the next move will be to pull twisted out from underneath it and replace it with a combination of asyncio and uvloop. This should bring network performance close to that of a compiled machine code program.

A bit of a deeper dive for those who are interested. A few weeks ago we did some heavy duty performance measurement on the K0USY KS-DMR network – where we run my tools in production. We wanted to know how far this thing will scale with modest resources. What we ended up finding out is that the network calls through twisted are the most costly in terms of time. Twisted is a GREAT module, don’t get me wrong. But we really don’t use it the way it was intended. We use fairly low-level pieces, of which there are much faster options in Python3. How much faster? Two orders of magnitude.

That’s the roadmap as of now – get HBlink3 working, then migrate to different underlying network modules.

On Jan 2, 2019, at 3:43 PM, Kim-Benjamin Lütkemeier via Groups.Io <kbluetkemeier@...> wrote:

Hello,
the HBlink and HBlink3 has the same status?

You add some functions on booth version or you only support HBLink3 now?

Good Job
Do1KBL

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






P25Reflector-Dashboard

Michael KD5DFB
 

Hello everyone,

I am having issues with my P25Reflector-Dashboard. I am using the one from https://github.com/N4IRS/MMDVM-Install/tree/master/P25/P25Reflector-Dashboard.

The problem I am having is, it will never show any stations in the "Currently Transmitting". I can refresh the page while transmitting and it will show the station in the "Last Heard List" and "All Heard List"

The dashboard is http://p25.kd5dfb.net/

Thanks,

Michael KD5DFB


HBLink and HBLink3

Kim-Benjamin Lütkemeier
 

Hello,
the HBlink and HBlink3 has the same status?

You add some functions on booth version or you only support HBLink3 now?

Good Job
Do1KBL


Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Jason Johnston
 

Just for the heck of it, I tried uninstalling python-dev, python-pip and python-twisted, then rebooted and installed everything again.  Upon running the "pip" commands below:
pip install bitstring
pip install bitarray

I get these errors:


root@josephus:~# pip install bitstring
Requirement already satisfied (use --upgrade to upgrade): bitstring in /usr/local/lib/python2.7/dist-packages
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
root@josephus:~# pip install bitarray
Requirement already satisfied (use --upgrade to upgrade): bitarray in /usr/local/lib/python2.7/dist-packages
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
If I am going to reinstall the OS, which I have no problem with, then what is to prevent this error next time?  What am I missing here?


C-Bridge to P25 Reflector Bridge

Michael KD5DFB
 

Happy New Year Everyone!

Looking for some guidance on my C-Bridge to P25 Reflector bridge.

I had a working instance running on a RPi and moving it to my cloud based server. It was setup with the following modules

cbridge<-->IPSC_Bridge<-->Analog_Bridge_DMR<-->Analog_Bridge_P25<-->MMDVM_Bridge<-->P25Gateway<-->P25Reflector

My question is, using IPSC_bridge it passes all the TS and TG to the analog bridge. How can I can I limit it to TS 2 and TG 8207?

Would I use confbridge.py and define it in the confbridge_rules? I know when using IPSC-bridge, I define the ports to connect to analog_bridge.

Any help would be greatly appreciated!

Michael KD5DFB




Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Jason Johnston
 

That's fine with me, I will start over.

Where, in the install steps that you list, should the dependencies and dmr_utils be installed?


Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Cort N0MJS <n0mjs@...>
 

It’s all python. Outside of shell scripts, the variation of Linux won’t matter. I wrote it all on MacOS and run it in production on Debian, raspbian and Ubuntu.

Nothing should be limiting in any way on any Unix-like os.


On Jan 2, 2019, at 2:53 PM, Steve N4IRS <szingman@...> wrote:

I can't tell you what OS flavor to use. I just don't trust your python environment.  All I can tell you is I run Mint on my desktop and pure Debian on my servers. YMMV


On 1/2/2019 3:49 PM, Jason Johnston wrote:
This is a fresh start from the software itself, but not the OS.  Is that what you are referring to?

I am running this on Ubuntu 16.04 LTS.  Is there any reason this wouldn't work?  In reading online forums, facebook groups, etc - and talking with several people who are using their own DMRlink/HBlink server, I get mixed opinions about whether Ubuntu will work or not.  It is a Debian based OS, but different enough that some say it won't work, even though it works on Raspian, which is much more watered-down than what I am running.

If I am going to start fresh all over again, what OS do you recommend I start with?  It can be anything, I don't care, I just want to know what works best.


Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Steve N4IRS
 

I can't tell you what OS flavor to use. I just don't trust your python environment.  All I can tell you is I run Mint on my desktop and pure Debian on my servers. YMMV


On 1/2/2019 3:49 PM, Jason Johnston wrote:
This is a fresh start from the software itself, but not the OS.  Is that what you are referring to?

I am running this on Ubuntu 16.04 LTS.  Is there any reason this wouldn't work?  In reading online forums, facebook groups, etc - and talking with several people who are using their own DMRlink/HBlink server, I get mixed opinions about whether Ubuntu will work or not.  It is a Debian based OS, but different enough that some say it won't work, even though it works on Raspian, which is much more watered-down than what I am running.

If I am going to start fresh all over again, what OS do you recommend I start with?  It can be anything, I don't care, I just want to know what works best.


Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Jason Johnston
 

Here is the result of that command, running with SUDO

jape@josephus:/opt/dmrlink/HBlink$ sudo pip show dme_utils
The directory '/home/jape/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

Steve, in your reply #2727, there is nothing about installing dmr_utils or dependencies.  If I am going to start over with a new OS, where do these steps fall in the process?


Re: P25<-->DMR issue "Still"

Ian Tulley
 

Thanks Steve, will give that a try soon.

------------------
Regards
Ian (VK2HK)




On 3 Jan 2019, at 7:51 am, Steve N4IRS <szingman@...> wrote:

Set the USRP audio settings in BOTH ini files to:
aslAudio = AUDIO_USE_GAIN
agcGain = 1.0
dmrAudio = AUDIO_USE_GAIN
dmrGain = 1.0

From there you can go up to 1.5,2,etc or down .9,.8,etc.


On 1/2/2019 3:46 PM, Ian Tulley wrote:
Hi Steve, if I do systemctl status md380-emu it shows it as running, if I TX from the P25 radio, I get very broken audio out of the DMR, if I TX from the DMR Radio I just get very harsh hash from the P25 Radio, that was with the USRP Audio settings as per default. I am assuming I will need to adjust those on both of the Analog_Bridge ini files ??

I have not done any as yet this morning, but will be looking at it hopefully in the next hour.

------------------
Regards
Ian (VK2HK)




On 2 Jan 2019, at 9:36 pm, Steve N4IRS <szingman@...> wrote:

So,
it sounds like P25 is working all the way to Analog_Bridge. It also sounds like you have a problem with Analog_Bridge for DMR.
Are you using the emulator?
Is the emulator running?

Steve

On 1/2/19 2:40 AM, Ian Tulley wrote:
Hi Steve, OK here is what I have been able to achieve, P25Gateway runs fine, I can then start MMDVM_Bridge and it connects to the BM Master successfully, I can TX on both the P25 radio and the DMR radio on different repeaters and see my calls come up on the screen output. I then start up Analog_Bridge_P25.ini and do the same test and again can see myself coming up on the screen output but no audio between them. Now when I startup Analog_Bridge_DMR.ini and do the same test I can see myself come up on the screen output then I get the following error, only on that Stanza, "Emulator Timed out on Decode" or "Emulator Timed out on Encode" depending on the direction of the data and still no audio in either direction, but I can get the DMR repeater to TX "sometimes" when PTT from the P25 radio but no audio.
I'm not sure where to look for this one, please remember this is on a server in the cloud so there are no USB Dongles connected, I'm only using the software decoder.

Regards
Ian (VK2HK)





Re: P25<-->DMR issue "Still"

Steve N4IRS
 

Set the USRP audio settings in BOTH ini files to:
aslAudio = AUDIO_USE_GAIN
agcGain = 1.0
dmrAudio = AUDIO_USE_GAIN
dmrGain = 1.0

From there you can go up to 1.5,2,etc or down .9,.8,etc.


On 1/2/2019 3:46 PM, Ian Tulley wrote:
Hi Steve, if I do systemctl status md380-emu it shows it as running, if I TX from the P25 radio, I get very broken audio out of the DMR, if I TX from the DMR Radio I just get very harsh hash from the P25 Radio, that was with the USRP Audio settings as per default. I am assuming I will need to adjust those on both of the Analog_Bridge ini files ??

I have not done any as yet this morning, but will be looking at it hopefully in the next hour.

------------------
Regards
Ian (VK2HK)




On 2 Jan 2019, at 9:36 pm, Steve N4IRS <szingman@...> wrote:

So,
it sounds like P25 is working all the way to Analog_Bridge. It also sounds like you have a problem with Analog_Bridge for DMR.
Are you using the emulator?
Is the emulator running?

Steve

On 1/2/19 2:40 AM, Ian Tulley wrote:
Hi Steve, OK here is what I have been able to achieve, P25Gateway runs fine, I can then start MMDVM_Bridge and it connects to the BM Master successfully, I can TX on both the P25 radio and the DMR radio on different repeaters and see my calls come up on the screen output. I then start up Analog_Bridge_P25.ini and do the same test and again can see myself coming up on the screen output but no audio between them. Now when I startup Analog_Bridge_DMR.ini and do the same test I can see myself come up on the screen output then I get the following error, only on that Stanza, "Emulator Timed out on Decode" or "Emulator Timed out on Encode" depending on the direction of the data and still no audio in either direction, but I can get the DMR repeater to TX "sometimes" when PTT from the P25 radio but no audio.
I'm not sure where to look for this one, please remember this is on a server in the cloud so there are no USB Dongles connected, I'm only using the software decoder.

Regards
Ian (VK2HK)




Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Jason Johnston
 

This is a fresh start from the software itself, but not the OS.  Is that what you are referring to?

I am running this on Ubuntu 16.04 LTS.  Is there any reason this wouldn't work?  In reading online forums, facebook groups, etc - and talking with several people who are using their own DMRlink/HBlink server, I get mixed opinions about whether Ubuntu will work or not.  It is a Debian based OS, but different enough that some say it won't work, even though it works on Raspian, which is much more watered-down than what I am running.

If I am going to start fresh all over again, what OS do you recommend I start with?  It can be anything, I don't care, I just want to know what works best.


Re: P25<-->DMR issue "Still"

Ian Tulley
 

Hi Steve, if I do systemctl status md380-emu it shows it as running, if I TX from the P25 radio, I get very broken audio out of the DMR, if I TX from the DMR Radio I just get very harsh hash from the P25 Radio, that was with the USRP Audio settings as per default. I am assuming I will need to adjust those on both of the Analog_Bridge ini files ??

I have not done any as yet this morning, but will be looking at it hopefully in the next hour.

------------------
Regards
Ian (VK2HK)




On 2 Jan 2019, at 9:36 pm, Steve N4IRS <szingman@...> wrote:

So,
it sounds like P25 is working all the way to Analog_Bridge. It also sounds like you have a problem with Analog_Bridge for DMR.
Are you using the emulator?
Is the emulator running?

Steve

On 1/2/19 2:40 AM, Ian Tulley wrote:
Hi Steve, OK here is what I have been able to achieve, P25Gateway runs fine, I can then start MMDVM_Bridge and it connects to the BM Master successfully, I can TX on both the P25 radio and the DMR radio on different repeaters and see my calls come up on the screen output. I then start up Analog_Bridge_P25.ini and do the same test and again can see myself coming up on the screen output but no audio between them. Now when I startup Analog_Bridge_DMR.ini and do the same test I can see myself come up on the screen output then I get the following error, only on that Stanza, "Emulator Timed out on Decode" or "Emulator Timed out on Encode" depending on the direction of the data and still no audio in either direction, but I can get the DMR repeater to TX "sometimes" when PTT from the P25 radio but no audio.
I'm not sure where to look for this one, please remember this is on a server in the cloud so there are no USB Dongles connected, I'm only using the software decoder.

Regards
Ian (VK2HK)



Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Steve N4IRS
 

OK,
I'm confused here is my result

root@orangepipc:~# pip show dmr_utils
Name: dmr-utils
Version: 0.1.19
Summary: ETSI DMR (Digital Mobile Radio) Tier II Utilities
Home-page: https://github.com/n0mjs710/dmr_utils
Author: Cortney T. Buffington, N0MJS
Author-email: n0mjs@...
License: GPLv3
Location: /usr/local/lib/python2.7/dist-packages
Requires: bitstring, bitarray

I'm out of answers. Best I can tell you at this point is to start fresh. At least that is what I would do.

Steve

On 1/2/2019 3:41 PM, Jason Johnston wrote:
My MMDVM hotspot is connecting to my server via the HBlink.cfg file.  I show it is connected now.  I am running both the hotspot and the HBlink server here on my home network, so I just have it connecting to an internal IP, but it seems to be working.

Here is the cmd you asked for:

jape@josephus:/opt/dmrlink/HBlink$ pip show dmr_utils
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
 


Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Jason Johnston
 

My MMDVM hotspot is connecting to my server via the HBlink.cfg file.  I show it is connected now.  I am running both the hotspot and the HBlink server here on my home network, so I just have it connecting to an internal IP, but it seems to be working.

Here is the cmd you asked for:

jape@josephus:/opt/dmrlink/HBlink$ pip show dmr_utils
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
 


Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Steve N4IRS
 

What is the result of:
pip show dmr_utils


On 1/2/2019 3:23 PM, Jason Johnston wrote:
OK got that done, trying to run the dmrlink.py in the foreground, getting this message below - it doesn't appear to be connecting to the cbridge yet.  I haven't tried the hblink connection yet.

jape@josephus:/opt/dmrlink/DMRlink$ sudo python dmrlink.py
Traceback (most recent call last):
  File "dmrlink.py", line 1098, in <module>
    peer_ids, subscriber_ids, talkgroup_ids, local_ids = build_aliases(CONFIG, logger)
  File "dmrlink.py", line 116, in build_aliases
    peer_ids = mk_id_dict(_config['ALIASES']['PATH'], _config['ALIASES']['PEER_FILE'])
  File "/usr/local/lib/python2.7/dist-packages/dmr_utils/utils.py", line 107, in mk_id_dict
    dict[int(row[0])] = (row[1])
ValueError: invalid literal for int() with base 10: 'Repeater ID'


Re: Setting up DMRLink <-> KBLink #best_practices #dmrlink #hblink

Jason Johnston
 

OK got that done, trying to run the dmrlink.py in the foreground, getting this message below - it doesn't appear to be connecting to the cbridge yet.  I haven't tried the hblink connection yet.

jape@josephus:/opt/dmrlink/DMRlink$ sudo python dmrlink.py
Traceback (most recent call last):
  File "dmrlink.py", line 1098, in <module>
    peer_ids, subscriber_ids, talkgroup_ids, local_ids = build_aliases(CONFIG, logger)
  File "dmrlink.py", line 116, in build_aliases
    peer_ids = mk_id_dict(_config['ALIASES']['PATH'], _config['ALIASES']['PEER_FILE'])
  File "/usr/local/lib/python2.7/dist-packages/dmr_utils/utils.py", line 107, in mk_id_dict
    dict[int(row[0])] = (row[1])
ValueError: invalid literal for int() with base 10: 'Repeater ID'

7261 - 7280 of 9925