Date   

Re: Trying to set up Parrot

Steve N4IRS
 

Rob,
Since you already have confbridge running, I assume you have a rule for the TG you are going to assign to parrot. I think the parrot should be just a client. Try turning off the master and point the client at one of the masters in your confbridge. Think of it as a remote client. Also check your logging section and make sure the directory exists.

73, Steve N4IRS

On 07/03/2018 04:35 PM, rob297@... wrote:

[Edited Message Follows]

I am unable startup parrot.py.  New at this and have conference bridge already running.  Trying to run this in another directory seperate from main bridge.  Error below..  I know I am missing something but cant find it.  Please help.

INFO ID ALIAS MAPPER: 'peer_ids.csv' is current, not downloaded
INFO ID ALIAS MAPPER: 'subscriber_ids.csv' is current, not downloaded
INFO ID ALIAS MAPPER: peer_ids dictionary is available
INFO ID ALIAS MAPPER: subscriber_ids dictionary is available
INFO HBlink 'hb_parrot.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
Traceback (most recent call last):
  File "hb_parrot.py", line 226, in <module>
    systems[system] = parrot(system, CONFIG, logger)
  File "hb_parrot.py", line 59, in __init__
    HBSYSTEM.__init__(self, _name, _config, _logger)
TypeError: __init__() takes exactly 5 arguments (4 given)


hblink.cfg

[Master]
MODE: MASTER
ENABLED: True
REPEAT: True
EXPORT_AMBE: False  
IP: 127.0.0.1
PORT: 54010
PASSPHRASE: Passw0rd
GROUP_HANGTIME: 5

[Parrot]
MODE: CLIENT
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54025
MASTER_IP: 127.0.0.1
MASTER_PORT: 54010
PASSPHRASE: Passw0rd
CALLSIGN: XXXXXX
RADIO_ID: 314882403
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1
LATITUDE: 38.0000
LONGITUDE: -095.0000
HEIGHT: 75  
LOCATION: Houston,TX
DESCRIPTION: TARMA  
URL: www.rob297.com
SOFTWARE_ID: 20170620
PACKAGE_ID: MMDVM_HBlink
GROUP_HANGTIME: 5
OPTIONS:


Trying to set up Parrot

KB5PBM
 
Edited

I am unable startup parrot.py.  New at this and have conference bridge already running.  Trying to run this in another directory seperate from main bridge.  Error below..  I know I am missing something but cant find it.  Please help.

INFO ID ALIAS MAPPER: 'peer_ids.csv' is current, not downloaded
INFO ID ALIAS MAPPER: 'subscriber_ids.csv' is current, not downloaded
INFO ID ALIAS MAPPER: peer_ids dictionary is available
INFO ID ALIAS MAPPER: subscriber_ids dictionary is available
INFO HBlink 'hb_parrot.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
Traceback (most recent call last):
  File "hb_parrot.py", line 226, in <module>
    systems[system] = parrot(system, CONFIG, logger)
  File "hb_parrot.py", line 59, in __init__
    HBSYSTEM.__init__(self, _name, _config, _logger)
TypeError: __init__() takes exactly 5 arguments (4 given)


hblink.cfg

[Master]
MODE: MASTER
ENABLED: True
REPEAT: True
EXPORT_AMBE: False  
IP: 127.0.0.1
PORT: 54010
PASSPHRASE: Passw0rd
GROUP_HANGTIME: 5

[Parrot]
MODE: CLIENT
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54025
MASTER_IP: 127.0.0.1
MASTER_PORT: 54010
PASSPHRASE: Passw0rd
CALLSIGN: XXXXXX
RADIO_ID: 314882403
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1
LATITUDE: 38.0000
LONGITUDE: -095.0000
HEIGHT: 75  
LOCATION: Houston,TX
DESCRIPTION: TARMA  
URL: www.rob297.com
SOFTWARE_ID: 20170620
PACKAGE_ID: MMDVM_HBlink
GROUP_HANGTIME: 5
OPTIONS:


Re: Strange announcement after each keyup after about a day of running

Chris WB4ULK
 

I think that solved the issue. At least it did mine. It has been running just fine and endured very heavy traffic for about 4 hrs last night with all sorts of mixed modes.

Thanks Steve!

Chris


Re: Strange announcement after each keyup after about a day of running

Chris WB4ULK
 

That sounds great! I just looked at mine and the default was 500ms. lol
I just changed it to 2500ms and waiting for it to get registered with Allstar and give it a shot.

Again, THANKS!

Chris


Re: Strange announcement after each keyup after about a day of running

Steve N4IRS
 

Did some playing today. Thanks to everyone that helped. That strange announcement is the word "blocked" in English at a distorted level from BrandMeister.

The optional hang times in MMDVM_Bridge do nothing in this environment. That is why the default is to either set them to zero in MMDVM_Bridge.ini or leave out the tags altogether. They are a leftover and will disappear some day soon.

 In a ASL <-> DMR bridge, the value that is important is in Analog_Bridge.ini. In the [AMBE_AUDIO] stanza minTxTimeMS is the important value. As of now, the default as shipped is 2000 ms. This value is to guarantee that a analog to DMR signal is at least 2 seconds long. Why 2 seconds? There is a "loop detector" in BrandMeister (and only BrandMeister) that is supposed to automatically block a loop condition from a hot spot.

The loop detector looks for more then 4 short transmissions in a 60 second period. The loop detector define a short transmission as being 35 frames or less. This is about 2 seconds. As a safety measure please bump the value in Analog_Bridge.ini to 2500. I will push out a update to Analog_Bridge with the new default value and a minor update to MMDVM_Bridge that will report the number of frames sent.

73, Steve n4IRS


Re: Strange announcement after each keyup after about a day of running

Chris WB4ULK
 

She's back.


Re: Strange announcement after each keyup after about a day of running

Chris WB4ULK
 

Connected.


Re: Strange announcement after each keyup after about a day of running

Steve N4IRS
 

If you guys would reconnect to 2600 in transceive, the more noise the better. You will only go out on TG3166 and ASL 2600

On 7/2/2018 1:32 PM, Mike KB8JNM wrote:

I think the point I thought was obvious that perhaps is not that I was trying to make was that among any other activity you might be doing and telemetry issue could create that 'quick keying' block. And you are not likely to hear 'short telemetry' on the dmr side.

Perhaps I am dead wrong about that but I don't think so.

Perhaps everyone is missing that so I said it bluntly.


On 7/2/2018 1:02 PM, Kevin Halton wrote:
If you are getting the “blocked” message it takes approximately 60 minutes of no key ups to reset. 


On Jul 2, 2018, at 12:03 PM, Mike KB8JNM <groupio@...> wrote:

I think you need to wait some abount of time to be "UNFLAGGED"

If all is well.

Just my opinion.

...mike/kb8jnm


On 7/2/2018 11:32 AM, Chris WB4ULK via Groups.Io wrote:
I reconnected the Bridge node to my hub node. I keyed up over DMR no prob, but when I keyed up the analog side, she started her same ol' rigamarole. LOL




Re: Strange announcement after each keyup after about a day of running

Mike KB8JNM
 

I think the point I thought was obvious that perhaps is not that I was trying to make was that among any other activity you might be doing and telemetry issue could create that 'quick keying' block. And you are not likely to hear 'short telemetry' on the dmr side.

Perhaps I am dead wrong about that but I don't think so.

Perhaps everyone is missing that so I said it bluntly.


On 7/2/2018 1:02 PM, Kevin Halton wrote:
If you are getting the “blocked” message it takes approximately 60 minutes of no key ups to reset. 


On Jul 2, 2018, at 12:03 PM, Mike KB8JNM <groupio@...> wrote:

I think you need to wait some abount of time to be "UNFLAGGED"

If all is well.

Just my opinion.

...mike/kb8jnm


On 7/2/2018 11:32 AM, Chris WB4ULK via Groups.Io wrote:
I reconnected the Bridge node to my hub node. I keyed up over DMR no prob, but when I keyed up the analog side, she started her same ol' rigamarole. LOL



Re: Strange announcement after each keyup after about a day of running

Kevin Halton
 

If you are getting the “blocked” message it takes approximately 60 minutes of no key ups to reset. 


On Jul 2, 2018, at 12:03 PM, Mike KB8JNM <groupio@...> wrote:

I think you need to wait some abount of time to be "UNFLAGGED"

If all is well.

Just my opinion.

...mike/kb8jnm


On 7/2/2018 11:32 AM, Chris WB4ULK via Groups.Io wrote:
I reconnected the Bridge node to my hub node. I keyed up over DMR no prob, but when I keyed up the analog side, she started her same ol' rigamarole. LOL


Re: Strange announcement after each keyup after about a day of running

Chris WB4ULK
 

Interesting. I disconnected the bridge node from my hub node. Let it sit there for awhile, connected back up and it isn't doing it any more. The thing is, if it is my node being blocked by BM, won't it just get blocked again?

Chris


Re: HBmonitor setup/Debian Stretch x86_64

Stephen Brown - K1LNX
 

Understood, thanks Cort. I'll continue to follow development and re-visit it at a later time. 

73
Stephen
K1LNX

On Mon, Jul 2, 2018 at 11:51 AM, Cort N0MJS <n0mjs@...> wrote:
Answer for Stephen, but something I really want everyone to take note of:

(warning: you’re not going to like this)

I consider DMRmonitor and HBmonitor very poorly written, unstable, and they are, as they stand, completely unsupported. I have a lot of work to do on both of them, changes I will likely make, frequently, would render any kind of install guide useless.

I’m giving this warning because I also don’t want anyone in the community taking time to write a guide, or a scripted installer only to be frustrated with me next week because it’s broken. Please read and understand this – any effort you put in could be almost immediately broken.



I am not, and have no desire to be a web programmer. This is where I draw the line that others need to contribute to the project. I have a few ground rules for anyone looking to do the web application stuff for monitor software:

1) the overhead to the packet-processing modules needs to be absolutely minimal.
2) web sockets. It’s 2018, we really shouldn’t be long-polling, etc.

Anyone who wants to take on the job of making REAL web-based monitoring/stats systems is welcome to do so. Get with me offline about what you need the packet-processing applications to export and how.


On Jul 2, 2018, at 10:34 AM, Stephen Brown - K1LNX <k1lnx@...> wrote:

Hi guys, 
    Trying to setup HBmonitor (https://github.com/n0mjs710/HBmonitor) to play with, and while I think I've satisfied most of the dependencies through apt-get installing packages as needed, it still fails to start, it can not import select_autoescape from jinja2: 

root@roipsrv-d:/opt/HBmonitor# ./web_tables.py 
Traceback (most recent call last):
  File "./web_tables.py", line 47, in <module>
    from jinja2 import Environment, PackageLoader, select_autoescape
ImportError: cannot import name select_autoescape

I could continue beating on it, but didn't want to get into pip install hell. Is there a set of instructions to get this up and running under Debian 9 x86_64? 

tnx and 73
Stephen
K1LNX

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







Re: Strange announcement after each keyup after about a day of running

KB5PBM
 
Edited

I: 2018-07-02 16:11:20.567 DMR, Begin TX: src=3148824 rpt=3148824 dst=114814 slot=2 cc=1 metadata=3148824
M: 2018-07-02 16:11:22.621 DMR, TX state = OFF
M: 2018-07-02 16:11:25.912 DMR Slot 2, received network voice header from 114814 to KB5PBM
M: 2018-07-02 16:11:27.060 DMR Slot 2, received network end of voice transmission, 1.4 seconds, 0% packet loss, BER: 0.0%


We are using an talk group that is not assigned.  Works fine for a while and then start getting this announcement.  Its coming from brandmeister network.  It sounds like its saying blocked.


Re: Strange announcement after each keyup after about a day of running

Mike KB8JNM
 

I think you need to wait some abount of time to be "UNFLAGGED"

If all is well.

Just my opinion.

...mike/kb8jnm


On 7/2/2018 11:32 AM, Chris WB4ULK via Groups.Io wrote:
I reconnected the Bridge node to my hub node. I keyed up over DMR no prob, but when I keyed up the analog side, she started her same ol' rigamarole. LOL


Re: HBmonitor setup/Debian Stretch x86_64

Cort N0MJS <n0mjs@...>
 

Answer for Stephen, but something I really want everyone to take note of:

(warning: you’re not going to like this)

I consider DMRmonitor and HBmonitor very poorly written, unstable, and they are, as they stand, completely unsupported. I have a lot of work to do on both of them, changes I will likely make, frequently, would render any kind of install guide useless.

I’m giving this warning because I also don’t want anyone in the community taking time to write a guide, or a scripted installer only to be frustrated with me next week because it’s broken. Please read and understand this – any effort you put in could be almost immediately broken.



I am not, and have no desire to be a web programmer. This is where I draw the line that others need to contribute to the project. I have a few ground rules for anyone looking to do the web application stuff for monitor software:

1) the overhead to the packet-processing modules needs to be absolutely minimal.
2) web sockets. It’s 2018, we really shouldn’t be long-polling, etc.

Anyone who wants to take on the job of making REAL web-based monitoring/stats systems is welcome to do so. Get with me offline about what you need the packet-processing applications to export and how.

On Jul 2, 2018, at 10:34 AM, Stephen Brown - K1LNX <k1lnx@...> wrote:

Hi guys, 
    Trying to setup HBmonitor (https://github.com/n0mjs710/HBmonitor) to play with, and while I think I've satisfied most of the dependencies through apt-get installing packages as needed, it still fails to start, it can not import select_autoescape from jinja2: 

root@roipsrv-d:/opt/HBmonitor# ./web_tables.py 
Traceback (most recent call last):
  File "./web_tables.py", line 47, in <module>
    from jinja2 import Environment, PackageLoader, select_autoescape
ImportError: cannot import name select_autoescape

I could continue beating on it, but didn't want to get into pip install hell. Is there a set of instructions to get this up and running under Debian 9 x86_64? 

tnx and 73
Stephen
K1LNX

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






HBmonitor setup/Debian Stretch x86_64

Stephen Brown - K1LNX
 

Hi guys, 
    Trying to setup HBmonitor (https://github.com/n0mjs710/HBmonitor) to play with, and while I think I've satisfied most of the dependencies through apt-get installing packages as needed, it still fails to start, it can not import select_autoescape from jinja2: 

root@roipsrv-d:/opt/HBmonitor# ./web_tables.py 
Traceback (most recent call last):
  File "./web_tables.py", line 47, in <module>
    from jinja2 import Environment, PackageLoader, select_autoescape
ImportError: cannot import name select_autoescape

I could continue beating on it, but didn't want to get into pip install hell. Is there a set of instructions to get this up and running under Debian 9 x86_64? 

tnx and 73
Stephen
K1LNX


Re: Strange announcement after each keyup after about a day of running

Chris WB4ULK
 

I reconnected the Bridge node to my hub node. I keyed up over DMR no prob, but when I keyed up the analog side, she started her same ol' rigamarole. LOL


Re: Strange announcement after each keyup after about a day of running

Steve N4IRS
 

I did, I disconnected everyone to make sure it was 2600 that was blocked. Chasing it down now.

On 7/2/2018 11:28 AM, Chris WB4ULK via Groups.Io wrote:
Ha!
I finally dialed into your node and noticed I was disconnected.
I reconnected and there it was. Lol
Sorry about that, didn’t realize you must have observed it and disconnected me.

Chris


Re: Strange announcement after each keyup after about a day of running

Chris WB4ULK
 

Ha!
I finally dialed into your node and noticed I was disconnected.
I reconnected and there it was. Lol
Sorry about that, didn’t realize you must have observed it and disconnected me.

Chris


Re: Strange announcement after each keyup after about a day of running

Chris WB4ULK
 

Steve,
FYI, I did go in last night and correct my DMR ID info. I increased it with an SSID as advised and put my tg in my selfcare.

Chris

7841 - 7860 of 9589