Date   

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


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

Steve N4IRS
 

Everybody, take a breath.
I do not think this issue is ASL configuration issue. I'll be honest, we do not think the hang settings in MMDVM_Bridge.ini have any effect. The first thing I want to know is what are we triggering on BM? That SHOULD help us track down the cause.

Steve



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

Chris WB4ULK
 

Those of us who are having THIS specific problem would like to discuss THIS issue.

Please don’t muddy the thread.

Chris


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

Mike KB8JNM
 

OFF LIST

Steve,

He was using a normal node config with his dvswitch attachment.

I think he has changed it on my advise.

...mike/kb8jnm


On 7/2/2018 10:08 AM, Steve N4IRS wrote:
Chris,
You are correct. This is a issue with traffic from ASL -> DMR. As a test I have ASL 2600 connected to TG 3166 in transceive. I also have 2600 connected to 2135 (WAN) in RECEIVE only. I have none of the hang time values set in MMDVM_Bridge.ini. (so they are at default) I am using the suggest ASL node config. I am hoping to catch the issue with "blocked"
Analog_Bridge has a hang timer which is built to keep any transmission sent to DMR to a minimum of 2 seconds. I am listening to the analog for the "blocked" message. If you have a ASL node that is NOT bridged to DMR and can stand listening to the traffic, please connect to 2600 in transceive so that we get analog traffic from you. My hope is to trigger the message and work with the US BM admins to find the block and understand what is triggering it.

73, Steve N4IRS  

On 7/2/2018 9:49 AM, Chris WB4ULK via Groups.Io wrote:
The cw id has no bearing in this situation. Even if you did have the CW id set to run by accident, it wouldn’t ID every time the machine keyed up.

Chris



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

Mike KB8JNM
 

You are reading words I did not write.

This was a general statement in "avoidance of issues"

And I used it in example.

The announcement (if you read the earlier posts) is generated at/by BM.

Once a issue has been generated/flagged, you will continue to get that massage till ???

For sure till the issue has been resolved and probably a short while after.

Combine a normal 6 char cw id with a shortening of the timers and see what you get.

...mike/kb8jnm


On 7/2/2018 9:49 AM, Chris WB4ULK via Groups.Io wrote:
The cw id has no bearing in this situation. Even if you did have the CW id set to run by accident, it wouldn’t ID every time the machine keyed up.

Chris


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

Chris WB4ULK
 

Ok. I am going to connect 47484 to 2600. It will be connected to my local tg we use on the machine as well.

Chris


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

Steve N4IRS
 

Chris,
You are correct. This is a issue with traffic from ASL -> DMR. As a test I have ASL 2600 connected to TG 3166 in transceive. I also have 2600 connected to 2135 (WAN) in RECEIVE only. I have none of the hang time values set in MMDVM_Bridge.ini. (so they are at default) I am using the suggest ASL node config. I am hoping to catch the issue with "blocked"
Analog_Bridge has a hang timer which is built to keep any transmission sent to DMR to a minimum of 2 seconds. I am listening to the analog for the "blocked" message. If you have a ASL node that is NOT bridged to DMR and can stand listening to the traffic, please connect to 2600 in transceive so that we get analog traffic from you. My hope is to trigger the message and work with the US BM admins to find the block and understand what is triggering it.

73, Steve N4IRS  

On 7/2/2018 9:49 AM, Chris WB4ULK via Groups.Io wrote:
The cw id has no bearing in this situation. Even if you did have the CW id set to run by accident, it wouldn’t ID every time the machine keyed up.

Chris


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

Chris WB4ULK
 

The cw id has no bearing in this situation. Even if you did have the CW id set to run by accident, it wouldn’t ID every time the machine keyed up.

Chris

8141 - 8160 of 9882