Date   

locked Re: HBLINK ECHO-PARROT and DudeSTAR #parrot #closed #hblink #echo #dudestar

Heitor Mercaldi
 
Edited

Yes it is, but its not the point. The point is that the DudeStar crashes the ECHO service in HBlink3.


locked Re: HBLINK ECHO-PARROT and DudeSTAR #parrot #closed #hblink #echo #dudestar

Randy AA6RH
 

I thought BM Parrot was 9990, not 9999

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) ūüėĀ


locked Re: HBLINK ECHO-PARROT and DudeSTAR #parrot #closed #hblink #echo #dudestar

Heitor Mercaldi
 
Edited

At the " Call log window"

 

 ## TX (1) - from radio (ID:1000007)
13:02:43 VOICE START SYS: MASTER-1 SRC: 724216401; 724216401 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 13:02:48 VOICE END SYS: MASTER-1 SRC: 724216401; 724216401 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 Time: 5s 13:02:50 VOICE START SYS: ECHOTEST SRC: 9999 ; 9999 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 13:02:57 VOICE START SYS: ECHOTEST SRC: 9999 ; 9999 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 13:03:02 VOICE END SYS: ECHOTEST SRC: 9999 ; 9999 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 Time: 5s ## TX (2) - from Radio (ID:1000007)
13:03:13 VOICE START SYS: MASTER-1 SRC: 724216401; 724216401 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 13:03:20 VOICE END SYS: MASTER-1 SRC: 724216401; 724216401 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 Time: 6s 13:03:22 VOICE START SYS: ECHOTEST SRC: 9999 ; 9999 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 13:03:28 VOICE END SYS: ECHOTEST SRC: 9999 ; 9999 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 Time: 6s ## TX (3) - from DudeStar (ID: 7242164) 
13:03:37 VOICE START SYS: MASTER-1 SRC: 724216410; 724216410 TS: 2 TGID: 9999 Papagaio SUB: 7242164 ; 7242164 13:03:48 VOICE END SYS: MASTER-1 SRC: 724216410; 724216410 TS: 2 TGID: 9999 Papagaio SUB: 7242164 ; 7242164 Time: 6s ## TX (4) - from radio
13:04:16 VOICE START SYS: MASTER-1 SRC: 724216401; 724216401 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 13:04:22 VOICE END SYS: MASTER-1 SRC: 724216401; 724216401 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 Time: 5s 13:04:24 VOICE START SYS: ECHOTEST SRC: 9999 ; 9999 TS: 2 TGID: 9999 Papagaio SUB: 7242164 ; 7242164 -----------------------------> DudeStar audio ECHO 13:04:30 VOICE START SYS: ECHOTEST SRC: 9999 ; 9999 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 ------------------> Radio audio ECHO 13:04:35 VOICE END SYS: ECHOTEST SRC: 9999 ; 9999 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 Time: 5s


locked Re: HBLINK ECHO-PARROT and DudeSTAR #parrot #closed #hblink #echo #dudestar

Heitor Mercaldi
 

from parrot.log

# TX (1) - from radio (ID:1000007)
INFO 2021-03-17 13:02:43,529 (PARROT) *START RECORDING* STREAM ID: 2539034976 SUB: 1000007 (1000007) REPEATER: 9999 (9999) TGID 9999 (9999), TS 2
INFO 2021-03-17 13:02:48,746 (PARROT) *END   RECORDING* STREAM ID: 2539034976
# ECHO (1) from radio TX
INFO 2021-03-17 13:02:50,748 (PARROT) *START  PLAYBACK* STREAM ID: 2539034976 SUB: 1000007 (1000007) REPEATER: 9999 (9999) TGID 9999 (9999), TS 2, Duration: 5.217082977294922
INFO 2021-03-17 13:03:02,272 (PARROT) *END    PLAYBACK* STREAM ID: 2539034976
# ECHO (1) playback END

# TX (2) - from Radio (ID:1000007)
INFO 2021-03-17 13:03:13,947 (PARROT) *START RECORDING* STREAM ID: 2358276375 SUB: 1000007 (1000007) REPEATER: 9999 (9999) TGID 9999 (9999), TS 2
INFO 2021-03-17 13:03:20,251 (PARROT) *END   RECORDING* STREAM ID: 2358276375
# ECHO (2) from radio TX
INFO 2021-03-17 13:03:22,253 (PARROT) *START  PLAYBACK* STREAM ID: 2358276375 SUB: 1000007 (1000007) REPEATER: 9999 (9999) TGID 9999 (9999), TS 2, Duration: 6.303557872772217
INFO 2021-03-17 13:03:28,407 (PARROT) *END    PLAYBACK* STREAM ID: 2358276375

# TX (3) - from DudeStar (ID: 7242164) 
INFO 2021-03-17 13:03:37,227 (PARROT) *START RECORDING* STREAM ID: 4198236160 SUB: 7242164 (7242164) REPEATER: 9999 (9999) TGID 9999 (9999), TS 2
# NO *END RECORDING for this TX 

# TX (4) - from radio
INFO 2021-03-17 13:04:16,520 (PARROT) *START RECORDING* STREAM ID: 3887657222 SUB: 1000007 (1000007) REPEATER: 9999 (9999) TGID 9999 (9999), TS 2
INFO 2021-03-17 13:04:22,108 (PARROT) *END   RECORDING* STREAM ID: 3887657222
# END RECORDING is OK now

# ECHO STREAM ID shows only the last Record, but the listened audio comming with last 2 records concatenated like a FIFO.
INFO 2021-03-17 13:04:24,110 (PARROT) *START  PLAYBACK* STREAM ID: 3887657222 SUB: 1000007 (1000007) REPEATER: 9999 (9999) TGID 9999 (9999), TS 2, Duration: 5.58738112449646
INFO 2021-03-17 13:04:35,813 (PARROT) *END    PLAYBACK* STREAM ID: 3887657222



locked Re: HBLINK ECHO-PARROT and DudeSTAR #parrot #closed #hblink #echo #dudestar

Corey Dean N3FE
 

What do you logs show you?

 


On 2021-03-17 11:44, Heitor Mercaldi wrote:

Hello,

I have sucessfully configured a HBlink3 private server ( http://vps29637.publiccloud.com.br) with PARROT just for learning purposes.
I use just 2 TGs:  13 for Local and 9999 for ECHO - parrot.
This week i was testing the PC version of DroidStar (DudeStar) connected my server and realize that i can use it at my local TG 13, however its doesn't work at PARROT 9999.
Other tests shows that the same issue happens in any HBlink or FreeDMR servers.
Additionally i get the following behavior in my server: 
1) TX from RADIO to 9999 -> Everything works fine and all nodes (repeaters, hotspots, DudeStar) receive the transmision and ECHO return;
2) TX from DudeStar to 9999 -> Everyone receive the transmision but no return, additionaly the PARROT call shows a TX time of a hundreds seconds;
3) TX from Radio to 9999 after DudeStar tx to same TG - > Everyone receives the radio TX and the ECHO returns to all connected nodes  with the last 2 transmissions like a FIFO.

Anyone could explain me this behavior ?


locked HBLINK ECHO-PARROT and DudeSTAR #parrot #closed #hblink #echo #dudestar

Heitor Mercaldi
 

Hello,

I have sucessfully configured a HBlink3 private server ( http://vps29637.publiccloud.com.br) with PARROT just for learning purposes.
I use just 2 TGs:  13 for Local and 9999 for ECHO - parrot.
This week i was testing the PC version of DroidStar (DudeStar) connected my server and realize that i can use it at my local TG 13, however its doesn't work at PARROT 9999.
Other tests shows that the same issue happens in any HBlink or FreeDMR servers.
Additionally i get the following behavior in my server: 
1) TX from RADIO to 9999 -> Everything works fine and all nodes (repeaters, hotspots, DudeStar) receive the transmision and ECHO return;
2) TX from DudeStar to 9999 -> Everyone receive the transmision but no return, additionaly the PARROT call shows a TX time of a hundreds seconds;
3) TX from Radio to 9999 after DudeStar tx to same TG - > Everyone receives the radio TX and the ECHO returns to all connected nodes  with the last 2 transmissions like a FIFO.

Anyone could explain me this behavior ?


Re: HBMon Connected/TX/RX/Lost - Red color

Eddie Lim 9W2LWK
 

Hi Randy,

I check on the python code actually i can turn the highlighted to green since all works fine
but nevertheless, i will upgrade to the latest version from sp2ong but i still like the old web interface :)

Thanks for the help anyway


Re: XLX <> HBlink3 Help #hblink

GB7NR Support
 

Hi Jason. We have done something similar with FreeSTAR except instead of using XLX interlink we have used DMR peers to accomplish the same thing with one less link in the chain. HBLink is a very power compilation of software and you will be able to accomplish all you need with HBLink. 

Shane 
M0VUB




On 13 Mar 2021, at 17:08, J M <jason@...> wrote:

ÔĽŅSo I feel somewhat foolish now... I was trying to use hblink.py rather than bridge.py. Now I think I just have to mess with rules.py. I see the traffic on both sides now.


Re: XLX <> HBlink3 Help #hblink

Jason McCormick N8EI
 

So I feel somewhat foolish now... I was trying to use hblink.py rather than bridge.py. Now I think I just have to mess with rules.py. I see the traffic on both sides now.


XLX <> HBlink3 Help #hblink

Jason McCormick N8EI
 

Hello all,

I am trying to accomplish linking together xlxd, hblink3, and BrandMeister DMR (via OpenBridge). In the longer term, I want to use hblink3 as the hub for other DMR networks and maybe P25. But for now, what I am trying to build is shown on the attached diagram. I have XLX working fine (for a long while) between D-STAR and YSF. The system is using ambed to transcode. All traffic is on Module A. When trying to add in the hblink3 part, I see the system connect to xlxd properly. However whenever there is traffic on xlxd, I can see with tcpdump the packets going from xlxd into hblink3 but hblink3 seems to completely ignore them. I have logging setup at debug level but all I ever see are the housekeeping tasks. I'm not finding anything describing this in the group.io search. Any thoughts or help would be appreciated. Or any different ways of doing this that might work better.

INFO 2021-03-13 11:00:01,675 (XLX330) Sending login request to master 44.70.49.128:62030
DEBUG 2021-03-13 11:00:01,677 (GLOBAL) XLXPEER instance created: XLX330, <__main__.HBSYSTEM object at 0xb57a9970>
INFO 2021-03-13 11:00:01,678 (XLX330) Repeater Login ACK Received with 32bit ID: 3997777929
INFO 2021-03-13 11:00:01,679 (XLX330) Repeater Authentication Accepted
INFO 2021-03-13 11:00:01,679 (XLX330) Repeater Configuration Sent
INFO 2021-03-13 11:00:01,680 (XLX330) Repeater Configuration Accepted
INFO 2021-03-13 11:00:01,680 (XLX330) Connection to Master Completed
INFO 2021-03-13 11:00:01,681 (XLX330) Sending XLX Module request
DEBUG 2021-03-13 11:00:06,677 (MEGALINK-MASTER) Master maintenance loop started
DEBUG 2021-03-13 11:00:06,678 (XLX330) Peer maintenance loop started
DEBUG 2021-03-13 11:00:06,679 (XLX330) RPTPING Sent to Master. Total Sent: 0, Total Missed: 0, Currently Outstanding: 0
DEBUG 2021-03-13 11:00:06,679 (XLX330) MSTPONG Received. Pongs Since Connected: 1
DEBUG 2021-03-13 11:00:11,680 (MEGALINK-MASTER) Master maintenance loop started
DEBUG 2021-03-13 11:00:11,681 (XLX330) Peer maintenance loop started
DEBUG 2021-03-13 11:00:11,681 (XLX330) RPTPING Sent to Master. Total Sent: 1, Total Missed: 0, Currently Outstanding: 0
DEBUG 2021-03-13 11:00:11,682 (XLX330) MSTPONG Received. Pongs Since Connected: 2

Here are what I think would be the relevant sections from hblink.cfg and rules.py.

hblink.cfg (partial)

[BM3103]
MODE: OPENBRIDGE
ENABLED: True
IP: 44.70.49.129
PORT: 62035
NETWORK_ID: 317561150
PASSPHRASE: >>REDACTED<<
TARGET_IP: 74.91.118.251
TARGET_PORT: 62035
BOTH_SLOTS: True
USE_ACL: True
SUB_ACL: PERMIT:ALL
TGID_ACL: PERMIT:ALL


[MEGALINK-MASTER]
MODE: MASTER
ENABLED: True
REPEAT: True
MAX_PEERS: 10
EXPORT_AMBE: False
IP: 44.70.49.129
PORT: 54000
PASSPHRASE: passw0rd
GROUP_HANGTIME: 5
USE_ACL: True
REG_ACL: DENY:1
SUB_ACL: DENY:1
TGID_TS1_ACL: PERMIT:ALL
TGID_TS2_ACL: PERMIT:ALL


[XLX330]
MODE: XLXPEER
ENABLED: True
LOOSE: True
EXPORT_AMBE: False
IP: 44.70.49.129
PORT: 54002
MASTER_IP: 44.70.49.128
MASTER_PORT: 62030
PASSPHRASE: passw0rd
CALLSIGN: WW8TF
RADIO_ID: 3175611
RX_FREQ: 221000000
TX_FREQ: 221000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
LATITUDE: 41.05749
LONGITUDE: -081.68424
HEIGHT: 0
LOCATION: Norton, OH
DESCRIPTION: Megalink XLX330
URL: ww8tf.club
SOFTWARE_ID: 20170620
PACKAGE_ID: MMDVM_HBlink
GROUP_HANGTIME: 5
XLXMODULE: 4001
USE_ACL: True
SUB_ACL: DENY:1
TGID_TS1_ACL: PERMIT:ALL
TGID_TS2_ACL: PERMIT:ALL

rules.py:

BRIDGES = {
    'Megalink 330': [
        { 'SYSTEM': 'MEGALINK-MASTER', 'TS': 2, 'TGID': 9, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',
                'ON': [], 'OFF': [], 'RESET': [] },
        { 'SYSTEM': 'XLX330', 'TS': 2, 'TGID': 9, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',
                'ON': [], 'OFF': [], 'RESET': [] },
        { 'SYSTEM': 'BM3103', 'TS': 1, 'TGID': 311070, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',
                'ON': [], 'OFF': [], 'RESET': [] },
    ]
}


Re: #hblink DMR GPS to APRS Application, initial release #hblink

Alister Chapman
 

Hi Eric.

I have no entries in user_settings.txt, but the Anytones almost always get decoded correctly with any ID/Callsign. But the other radios are getting the -1 block countdown even if I use the same ID’s as the 878.

I had a working install based on a build from on 10th January. Then I pulled this version a couple of days ago but I didn’t try any versions between 10th of Jan and now.


Alister Chapman 

Cinematographer - DIT - Consultant
UK Mobile/Whatsapp +44 7711 152226


Facebook: Alister Chapman
Twitter: @stormguy



www.xdcam-user.com    1.5 million hits, 100,000 visits from over 45,000 unique visitors every month!  Film and Video production techniques, reviews and news.


















On 12 Mar 2021, at 20:59, Eric - KF7EEL <kf7eel@...> wrote:

This looks similar to a problem that has popped with 2 other servers. For some reason, if the radio sending a position doesn't have an entry in user_settings.txt, the block countdown will go negative and fail to decode. I am trying to figure out what is causing this. Let me know if you notice that only users with entries in user_setting.txt work. When was the last good working commit for you?

On Fri, Mar 12, 2021, 10:51 Alister Chapman <alister@...> wrote:
Hi Eric.

I’ve upgraded my gps-data installation to your latest build and decoding of messages from my Ailunce HD1 seems to be broken now. The system decodes messages from the Anytone 878most of the time (but not as reliably as previously) but not at all  from the Ailunce HD1 or MD-380UV (RT3S).

This is the Ailunce HD1:

INFO 2021-03-12 16:56:26,311 Header from G0NEF. DMR ID: 2343895
INFO 2021-03-12 16:56:26,311 b'00050395f723c3d7001bbd12'
INFO 2021-03-12 16:56:26,311 Blocks to follow: 0
INFO 2021-03-12 16:56:26,439 16:56:26 - 03/12/21
INFO 2021-03-12 16:56:26,439 Block #: -1
INFO 2021-03-12 16:56:26,440 Data block from G0NEF. DMR ID: 2343895
INFO 2021-03-12 16:56:26,440 b'500cd90ea802c08180451a26'
DEBUG 2021-03-12 16:56:29,341 (D-APRS) Peer maintenance loop started
DEBUG 2021-03-12 16:56:29,341 (D-APRS) RPTPING Sent to Master. Total Sent: 54, Total Missed: 0, Currently Outstanding: 0
DEBUG 2021-03-12 16:56:29,344 (D-APRS) MSTPONG Received. Pongs Since Connected: 55



And this is the Anytone 878:

DEBUG 2021-03-12 17:34:19,345 (D-APRS) MSTPONG Received. Pongs Since Connected: 509
INFO 2021-03-12 17:34:22,739 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:22,877 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:23,002 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:23,142 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,271 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,383 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,384 Header from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,384 b'02390395f723be288800a771'
INFO 2021-03-12 17:34:23,384 Blocks to follow: 8
INFO 2021-03-12 17:34:23,500 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,500 Block #: 7
INFO 2021-03-12 17:34:23,500 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,500 b'0001000000277e277e244750'
INFO 2021-03-12 17:34:23,504 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,504 Block #: 6
INFO 2021-03-12 17:34:23,504 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,505 b'524d432c3137333432322e30'
INFO 2021-03-12 17:34:23,512 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,512 Block #: 5
INFO 2021-03-12 17:34:23,512 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,513 b'30302c412c353132352e3130'
INFO 2021-03-12 17:34:23,516 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,516 Block #: 4
INFO 2021-03-12 17:34:23,517 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,517 b'30343937362c572c302e3030'
INFO 2021-03-12 17:34:23,517 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,518 Block #: 3
INFO 2021-03-12 17:34:23,518 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,518 b'3037372c4e2c30303034342e'
INFO 2021-03-12 17:34:23,520 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,520 Block #: 2
INFO 2021-03-12 17:34:23,520 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,520 b'2c3330332e37302c31323033'
INFO 2021-03-12 17:34:23,525 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,525 Block #: 1
INFO 2021-03-12 17:34:23,525 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,526 b'32312c2c2c412a36390d0a00'
INFO 2021-03-12 17:34:23,530 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,531 Block #: 0
INFO 2021-03-12 17:34:23,531 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,531 b'0000000000000000fff6e854'
INFO 2021-03-12 17:34:23,531 '~'~$GPRMC,173422.000,A,5125.1004976,W,0.00077,N,00044.,303.70,120321,,,A*69
T

INFO 2021-03-12 17:34:23,532 GPRMC location
INFO 2021-03-12 17:34:23,532 Latitude: 5125.1004976W Longitude: 0.00077N Direction: 303.7 Speed: 44.0

INFO 2021-03-12 17:34:23,541 G0NEF-15>APHBL3,TCPIP*:@173423h5125.10W/0.00077N[304/044/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 17:34:23,541 User comment: HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 17:34:23,541 User SSID: 15
INFO 2021-03-12 17:34:23,541 User icon: /[
DEBUG 2021-03-12 17:34:23,541 Parsing: G0NEF-15>APHBL3,TCPIP*:@173423h5125.10W/0.00077N[304/044/HBLink3 D-APRS - DMR ID: 2342440

BUT OFTEN IT FAILS WITH THE 878:

INFO 2021-03-12 18:47:01,349 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,349 Header from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,350 b'02390395f723be288800a771'
INFO 2021-03-12 18:47:01,350 Blocks to follow: 8
INFO 2021-03-12 18:47:01,471 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,471 Block #: 7
INFO 2021-03-12 18:47:01,471 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,471 b'0001000000277e277e244750'
INFO 2021-03-12 18:47:01,476 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,476 Block #: 6
INFO 2021-03-12 18:47:01,476 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,476 b'524d432c3138343730302e30'
INFO 2021-03-12 18:47:01,482 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,482 Block #: 5
INFO 2021-03-12 18:47:01,482 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,482 b'3833312c4e2c30303034342e'
INFO 2021-03-12 18:47:01,482 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,483 Block #: 4
INFO 2021-03-12 18:47:01,483 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,483 b'30302c412c353132352e3038'
INFO 2021-03-12 18:47:01,489 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,489 Block #: 3
INFO 2021-03-12 18:47:01,489 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,489 b'30383136392c572c302e3332'
INFO 2021-03-12 18:47:01,490 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,490 Block #: 2
INFO 2021-03-12 18:47:01,490 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,490 b'2c3238382e30342c31323033'
INFO 2021-03-12 18:47:01,494 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,494 Block #: 1
INFO 2021-03-12 18:47:01,494 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,494 b'32312c2c2c412a36420d0a00'
INFO 2021-03-12 18:47:01,505 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,506 Block #: 0
INFO 2021-03-12 18:47:01,506 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,506 b'0000000000000000163d0cce'
INFO 2021-03-12 18:47:01,506 '~'~$GPRMC,184700.0831,N,00044.00,A,5125.0808169,W,0.32,288.04,120321,,,A*6B
=


INFO 2021-03-12 18:47:01,507 GPRMC location
INFO 2021-03-12 18:47:01,507 Latitude: 00044.00A Longitude: 5125.0808169W Direction: 288.04 Speed: 0.32

INFO 2021-03-12 18:47:01,514 G0NEF-15>APHBL3,TCPIP*:@184701h00044.0A/5125.080W[288/000/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,514 User comment: HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,514 User SSID: 15
INFO 2021-03-12 18:47:01,514 User icon: /[
DEBUG 2021-03-12 18:47:01,514 Parsing: G0NEF-15>APHBL3,TCPIP*:@184701h00044.0A/5125.080W[288/000/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,515 Failed to parse packet. Packet may be deformed. Not uploaded.
INFO 2021-03-12 18:47:01,515 invalid format
INFO 2021-03-12 18:47:01,515 [<FrameSummary file gps_data.py, line 632 in dmrd_received>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/__init__.py, line 114 in parse>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/__init__.py, line 204 in _try_toparse_body>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/position.py, line 59 in parse_position>]
DEBUG 2021-03-12 18:47:05,280 (D-APRS) Peer maintenance loop started


Alister Chapman 

Cinematographer - DIT - Consultant
UK Mobile/Whatsapp +44 7711 152226


Facebook: Alister Chapman
Twitter: @stormguy



www.xdcam-user.com    1.5 million hits, 100,000 visits from over 45,000 unique visitors every month!  Film and Video production techniques, reviews and news.


















On 4 Mar 2021, at 20:37, Eric - KF7EEL <kf7eel@...> wrote:

I have made some big changes in the last update of the application.

You will need to compare the [GPS_DATA] section of gps_data-SAMPLE.cfg with your current configuration as there are MAJOR changes that could break your setup.

First, configuration of the web dashboard has moved ENTIRELY into gps_data,cfg, no more separate configuration in dashboard_settings.py. This helps make the configuration of the dashboard easier. To run the dashboard, you will need to execute: python3 dashboard.py -c path/to/gps_data.cfg

New feature:
There is a new script in folder aprs_receive called receive.py. This script will connect to an APRS feed and look for APRS messages to users who have settings saved in user_settings.txt. If a user is happy with the default settings, a command of @APRS will add an entry to user_settings.txt causing the APRS receive script to scan for APRS messages to that user. If the user has a custom icon, ssid, or comment, this command is not necessary. This script also handles APRS message acknowledgement. When a message is received, the script will write it to a file that can be viewed in the dashboard Mailbox. This was designed to give the gateway some sort of 2 way APRS messaging capability as the gateway doesn't send DMR SMS yet. Configuration of the APRS receive script is in gps_data.cfg. To execute it, run: python3 receive.py -c path/to/gps_data.cfg

Again, this update will require you to add to your current configuration. See gps_data-SAMPLE.cfg.





Re: #hblink DMR GPS to APRS Application, initial release #hblink

Eric - KF7EEL
 

This looks similar to a problem that has popped with 2 other servers. For some reason, if the radio sending a position doesn't have an entry in user_settings.txt, the block countdown will go negative and fail to decode. I am trying to figure out what is causing this. Let me know if you notice that only users with entries in user_setting.txt work. When was the last good working commit for you?


On Fri, Mar 12, 2021, 10:51 Alister Chapman <alister@...> wrote:
Hi Eric.

I’ve upgraded my gps-data installation to your latest build and decoding of messages from my Ailunce HD1 seems to be broken now. The system decodes messages from the Anytone 878most of the time (but not as reliably as previously) but not at all  from the Ailunce HD1 or MD-380UV (RT3S).

This is the Ailunce HD1:

INFO 2021-03-12 16:56:26,311 Header from G0NEF. DMR ID: 2343895
INFO 2021-03-12 16:56:26,311 b'00050395f723c3d7001bbd12'
INFO 2021-03-12 16:56:26,311 Blocks to follow: 0
INFO 2021-03-12 16:56:26,439 16:56:26 - 03/12/21
INFO 2021-03-12 16:56:26,439 Block #: -1
INFO 2021-03-12 16:56:26,440 Data block from G0NEF. DMR ID: 2343895
INFO 2021-03-12 16:56:26,440 b'500cd90ea802c08180451a26'
DEBUG 2021-03-12 16:56:29,341 (D-APRS) Peer maintenance loop started
DEBUG 2021-03-12 16:56:29,341 (D-APRS) RPTPING Sent to Master. Total Sent: 54, Total Missed: 0, Currently Outstanding: 0
DEBUG 2021-03-12 16:56:29,344 (D-APRS) MSTPONG Received. Pongs Since Connected: 55



And this is the Anytone 878:

DEBUG 2021-03-12 17:34:19,345 (D-APRS) MSTPONG Received. Pongs Since Connected: 509
INFO 2021-03-12 17:34:22,739 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:22,877 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:23,002 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:23,142 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,271 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,383 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,384 Header from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,384 b'02390395f723be288800a771'
INFO 2021-03-12 17:34:23,384 Blocks to follow: 8
INFO 2021-03-12 17:34:23,500 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,500 Block #: 7
INFO 2021-03-12 17:34:23,500 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,500 b'0001000000277e277e244750'
INFO 2021-03-12 17:34:23,504 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,504 Block #: 6
INFO 2021-03-12 17:34:23,504 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,505 b'524d432c3137333432322e30'
INFO 2021-03-12 17:34:23,512 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,512 Block #: 5
INFO 2021-03-12 17:34:23,512 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,513 b'30302c412c353132352e3130'
INFO 2021-03-12 17:34:23,516 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,516 Block #: 4
INFO 2021-03-12 17:34:23,517 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,517 b'30343937362c572c302e3030'
INFO 2021-03-12 17:34:23,517 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,518 Block #: 3
INFO 2021-03-12 17:34:23,518 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,518 b'3037372c4e2c30303034342e'
INFO 2021-03-12 17:34:23,520 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,520 Block #: 2
INFO 2021-03-12 17:34:23,520 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,520 b'2c3330332e37302c31323033'
INFO 2021-03-12 17:34:23,525 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,525 Block #: 1
INFO 2021-03-12 17:34:23,525 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,526 b'32312c2c2c412a36390d0a00'
INFO 2021-03-12 17:34:23,530 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,531 Block #: 0
INFO 2021-03-12 17:34:23,531 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,531 b'0000000000000000fff6e854'
INFO 2021-03-12 17:34:23,531 '~'~$GPRMC,173422.000,A,5125.1004976,W,0.00077,N,00044.,303.70,120321,,,A*69
T

INFO 2021-03-12 17:34:23,532 GPRMC location
INFO 2021-03-12 17:34:23,532 Latitude: 5125.1004976W Longitude: 0.00077N Direction: 303.7 Speed: 44.0

INFO 2021-03-12 17:34:23,541 G0NEF-15>APHBL3,TCPIP*:@173423h5125.10W/0.00077N[304/044/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 17:34:23,541 User comment: HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 17:34:23,541 User SSID: 15
INFO 2021-03-12 17:34:23,541 User icon: /[
DEBUG 2021-03-12 17:34:23,541 Parsing: G0NEF-15>APHBL3,TCPIP*:@173423h5125.10W/0.00077N[304/044/HBLink3 D-APRS - DMR ID: 2342440

BUT OFTEN IT FAILS WITH THE 878:

INFO 2021-03-12 18:47:01,349 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,349 Header from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,350 b'02390395f723be288800a771'
INFO 2021-03-12 18:47:01,350 Blocks to follow: 8
INFO 2021-03-12 18:47:01,471 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,471 Block #: 7
INFO 2021-03-12 18:47:01,471 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,471 b'0001000000277e277e244750'
INFO 2021-03-12 18:47:01,476 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,476 Block #: 6
INFO 2021-03-12 18:47:01,476 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,476 b'524d432c3138343730302e30'
INFO 2021-03-12 18:47:01,482 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,482 Block #: 5
INFO 2021-03-12 18:47:01,482 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,482 b'3833312c4e2c30303034342e'
INFO 2021-03-12 18:47:01,482 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,483 Block #: 4
INFO 2021-03-12 18:47:01,483 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,483 b'30302c412c353132352e3038'
INFO 2021-03-12 18:47:01,489 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,489 Block #: 3
INFO 2021-03-12 18:47:01,489 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,489 b'30383136392c572c302e3332'
INFO 2021-03-12 18:47:01,490 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,490 Block #: 2
INFO 2021-03-12 18:47:01,490 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,490 b'2c3238382e30342c31323033'
INFO 2021-03-12 18:47:01,494 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,494 Block #: 1
INFO 2021-03-12 18:47:01,494 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,494 b'32312c2c2c412a36420d0a00'
INFO 2021-03-12 18:47:01,505 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,506 Block #: 0
INFO 2021-03-12 18:47:01,506 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,506 b'0000000000000000163d0cce'
INFO 2021-03-12 18:47:01,506 '~'~$GPRMC,184700.0831,N,00044.00,A,5125.0808169,W,0.32,288.04,120321,,,A*6B
=


INFO 2021-03-12 18:47:01,507 GPRMC location
INFO 2021-03-12 18:47:01,507 Latitude: 00044.00A Longitude: 5125.0808169W Direction: 288.04 Speed: 0.32

INFO 2021-03-12 18:47:01,514 G0NEF-15>APHBL3,TCPIP*:@184701h00044.0A/5125.080W[288/000/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,514 User comment: HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,514 User SSID: 15
INFO 2021-03-12 18:47:01,514 User icon: /[
DEBUG 2021-03-12 18:47:01,514 Parsing: G0NEF-15>APHBL3,TCPIP*:@184701h00044.0A/5125.080W[288/000/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,515 Failed to parse packet. Packet may be deformed. Not uploaded.
INFO 2021-03-12 18:47:01,515 invalid format
INFO 2021-03-12 18:47:01,515 [<FrameSummary file gps_data.py, line 632 in dmrd_received>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/__init__.py, line 114 in parse>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/__init__.py, line 204 in _try_toparse_body>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/position.py, line 59 in parse_position>]
DEBUG 2021-03-12 18:47:05,280 (D-APRS) Peer maintenance loop started


Alister Chapman 

Cinematographer - DIT - Consultant
UK Mobile/Whatsapp +44 7711 152226


Facebook: Alister Chapman
Twitter: @stormguy



www.xdcam-user.com    1.5 million hits, 100,000 visits from over 45,000 unique visitors every month!  Film and Video production techniques, reviews and news.


















On 4 Mar 2021, at 20:37, Eric - KF7EEL <kf7eel@...> wrote:

I have made some big changes in the last update of the application.

You will need to compare the [GPS_DATA] section of gps_data-SAMPLE.cfg with your current configuration as there are MAJOR changes that could break your setup.

First, configuration of the web dashboard has moved ENTIRELY into gps_data,cfg, no more separate configuration in dashboard_settings.py. This helps make the configuration of the dashboard easier. To run the dashboard, you will need to execute: python3 dashboard.py -c path/to/gps_data.cfg

New feature:
There is a new script in folder aprs_receive called receive.py. This script will connect to an APRS feed and look for APRS messages to users who have settings saved in user_settings.txt. If a user is happy with the default settings, a command of @APRS will add an entry to user_settings.txt causing the APRS receive script to scan for APRS messages to that user. If the user has a custom icon, ssid, or comment, this command is not necessary. This script also handles APRS message acknowledgement. When a message is received, the script will write it to a file that can be viewed in the dashboard Mailbox. This was designed to give the gateway some sort of 2 way APRS messaging capability as the gateway doesn't send DMR SMS yet. Configuration of the APRS receive script is in gps_data.cfg. To execute it, run: python3 receive.py -c path/to/gps_data.cfg

Again, this update will require you to add to your current configuration. See gps_data-SAMPLE.cfg.


Re: #hblink DMR GPS to APRS Application, initial release #hblink

Alister Chapman
 

Hi Eric.

I’ve upgraded my gps-data installation to your latest build and decoding of messages from my Ailunce HD1 seems to be broken now. The system decodes messages from the Anytone 878most of the time (but not as reliably as previously) but not at all  from the Ailunce HD1 or MD-380UV (RT3S).

This is the Ailunce HD1:

INFO 2021-03-12 16:56:26,311 Header from G0NEF. DMR ID: 2343895
INFO 2021-03-12 16:56:26,311 b'00050395f723c3d7001bbd12'
INFO 2021-03-12 16:56:26,311 Blocks to follow: 0
INFO 2021-03-12 16:56:26,439 16:56:26 - 03/12/21
INFO 2021-03-12 16:56:26,439 Block #: -1
INFO 2021-03-12 16:56:26,440 Data block from G0NEF. DMR ID: 2343895
INFO 2021-03-12 16:56:26,440 b'500cd90ea802c08180451a26'
DEBUG 2021-03-12 16:56:29,341 (D-APRS) Peer maintenance loop started
DEBUG 2021-03-12 16:56:29,341 (D-APRS) RPTPING Sent to Master. Total Sent: 54, Total Missed: 0, Currently Outstanding: 0
DEBUG 2021-03-12 16:56:29,344 (D-APRS) MSTPONG Received. Pongs Since Connected: 55



And this is the Anytone 878:

DEBUG 2021-03-12 17:34:19,345 (D-APRS) MSTPONG Received. Pongs Since Connected: 509
INFO 2021-03-12 17:34:22,739 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:22,877 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:23,002 17:34:22 - 03/12/21
INFO 2021-03-12 17:34:23,142 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,271 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,383 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,384 Header from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,384 b'02390395f723be288800a771'
INFO 2021-03-12 17:34:23,384 Blocks to follow: 8
INFO 2021-03-12 17:34:23,500 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,500 Block #: 7
INFO 2021-03-12 17:34:23,500 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,500 b'0001000000277e277e244750'
INFO 2021-03-12 17:34:23,504 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,504 Block #: 6
INFO 2021-03-12 17:34:23,504 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,505 b'524d432c3137333432322e30'
INFO 2021-03-12 17:34:23,512 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,512 Block #: 5
INFO 2021-03-12 17:34:23,512 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,513 b'30302c412c353132352e3130'
INFO 2021-03-12 17:34:23,516 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,516 Block #: 4
INFO 2021-03-12 17:34:23,517 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,517 b'30343937362c572c302e3030'
INFO 2021-03-12 17:34:23,517 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,518 Block #: 3
INFO 2021-03-12 17:34:23,518 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,518 b'3037372c4e2c30303034342e'
INFO 2021-03-12 17:34:23,520 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,520 Block #: 2
INFO 2021-03-12 17:34:23,520 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,520 b'2c3330332e37302c31323033'
INFO 2021-03-12 17:34:23,525 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,525 Block #: 1
INFO 2021-03-12 17:34:23,525 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,526 b'32312c2c2c412a36390d0a00'
INFO 2021-03-12 17:34:23,530 17:34:23 - 03/12/21
INFO 2021-03-12 17:34:23,531 Block #: 0
INFO 2021-03-12 17:34:23,531 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 17:34:23,531 b'0000000000000000fff6e854'
INFO 2021-03-12 17:34:23,531 '~'~$GPRMC,173422.000,A,5125.1004976,W,0.00077,N,00044.,303.70,120321,,,A*69
T

INFO 2021-03-12 17:34:23,532 GPRMC location
INFO 2021-03-12 17:34:23,532 Latitude: 5125.1004976W Longitude: 0.00077N Direction: 303.7 Speed: 44.0

INFO 2021-03-12 17:34:23,541 G0NEF-15>APHBL3,TCPIP*:@173423h5125.10W/0.00077N[304/044/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 17:34:23,541 User comment: HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 17:34:23,541 User SSID: 15
INFO 2021-03-12 17:34:23,541 User icon: /[
DEBUG 2021-03-12 17:34:23,541 Parsing: G0NEF-15>APHBL3,TCPIP*:@173423h5125.10W/0.00077N[304/044/HBLink3 D-APRS - DMR ID: 2342440

BUT OFTEN IT FAILS WITH THE 878:

INFO 2021-03-12 18:47:01,349 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,349 Header from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,350 b'02390395f723be288800a771'
INFO 2021-03-12 18:47:01,350 Blocks to follow: 8
INFO 2021-03-12 18:47:01,471 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,471 Block #: 7
INFO 2021-03-12 18:47:01,471 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,471 b'0001000000277e277e244750'
INFO 2021-03-12 18:47:01,476 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,476 Block #: 6
INFO 2021-03-12 18:47:01,476 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,476 b'524d432c3138343730302e30'
INFO 2021-03-12 18:47:01,482 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,482 Block #: 5
INFO 2021-03-12 18:47:01,482 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,482 b'3833312c4e2c30303034342e'
INFO 2021-03-12 18:47:01,482 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,483 Block #: 4
INFO 2021-03-12 18:47:01,483 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,483 b'30302c412c353132352e3038'
INFO 2021-03-12 18:47:01,489 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,489 Block #: 3
INFO 2021-03-12 18:47:01,489 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,489 b'30383136392c572c302e3332'
INFO 2021-03-12 18:47:01,490 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,490 Block #: 2
INFO 2021-03-12 18:47:01,490 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,490 b'2c3238382e30342c31323033'
INFO 2021-03-12 18:47:01,494 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,494 Block #: 1
INFO 2021-03-12 18:47:01,494 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,494 b'32312c2c2c412a36420d0a00'
INFO 2021-03-12 18:47:01,505 18:47:01 - 03/12/21
INFO 2021-03-12 18:47:01,506 Block #: 0
INFO 2021-03-12 18:47:01,506 Data block from G0NEF. DMR ID: 2342440
INFO 2021-03-12 18:47:01,506 b'0000000000000000163d0cce'
INFO 2021-03-12 18:47:01,506 '~'~$GPRMC,184700.0831,N,00044.00,A,5125.0808169,W,0.32,288.04,120321,,,A*6B
=


INFO 2021-03-12 18:47:01,507 GPRMC location
INFO 2021-03-12 18:47:01,507 Latitude: 00044.00A Longitude: 5125.0808169W Direction: 288.04 Speed: 0.32

INFO 2021-03-12 18:47:01,514 G0NEF-15>APHBL3,TCPIP*:@184701h00044.0A/5125.080W[288/000/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,514 User comment: HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,514 User SSID: 15
INFO 2021-03-12 18:47:01,514 User icon: /[
DEBUG 2021-03-12 18:47:01,514 Parsing: G0NEF-15>APHBL3,TCPIP*:@184701h00044.0A/5125.080W[288/000/HBLink3 D-APRS - DMR ID: 2342440
INFO 2021-03-12 18:47:01,515 Failed to parse packet. Packet may be deformed. Not uploaded.
INFO 2021-03-12 18:47:01,515 invalid format
INFO 2021-03-12 18:47:01,515 [<FrameSummary file gps_data.py, line 632 in dmrd_received>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/__init__.py, line 114 in parse>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/__init__.py, line 204 in _try_toparse_body>, <FrameSummary file /usr/local/lib/python3.7/dist-packages/aprslib/parsing/position.py, line 59 in parse_position>]
DEBUG 2021-03-12 18:47:05,280 (D-APRS) Peer maintenance loop started


Alister Chapman 

Cinematographer - DIT - Consultant
UK Mobile/Whatsapp +44 7711 152226


Facebook: Alister Chapman
Twitter: @stormguy



www.xdcam-user.com    1.5 million hits, 100,000 visits from over 45,000 unique visitors every month!  Film and Video production techniques, reviews and news.


















On 4 Mar 2021, at 20:37, Eric - KF7EEL <kf7eel@...> wrote:

I have made some big changes in the last update of the application.

You will need to compare the [GPS_DATA] section of gps_data-SAMPLE.cfg with your current configuration as there are MAJOR changes that could break your setup.

First, configuration of the web dashboard has moved ENTIRELY into gps_data,cfg, no more separate configuration in dashboard_settings.py. This helps make the configuration of the dashboard easier. To run the dashboard, you will need to execute: python3 dashboard.py -c path/to/gps_data.cfg

New feature:
There is a new script in folder aprs_receive called receive.py. This script will connect to an APRS feed and look for APRS messages to users who have settings saved in user_settings.txt. If a user is happy with the default settings, a command of @APRS will add an entry to user_settings.txt causing the APRS receive script to scan for APRS messages to that user. If the user has a custom icon, ssid, or comment, this command is not necessary. This script also handles APRS message acknowledgement. When a message is received, the script will write it to a file that can be viewed in the dashboard Mailbox. This was designed to give the gateway some sort of 2 way APRS messaging capability as the gateway doesn't send DMR SMS yet. Configuration of the APRS receive script is in gps_data.cfg. To execute it, run: python3 receive.py -c path/to/gps_data.cfg

Again, this update will require you to add to your current configuration. See gps_data-SAMPLE.cfg.


Re: HBMon Connected/TX/RX/Lost - Red color

Randy AA6RH
 

I was referring to the version of HBlink before you updated it from the git repo. I'm wondering if you have that version somewhere.

Getting these properly identified as releases would help with some of this troubleshooting, to be honest.

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) ūüėĀ


Re: HBMon Connected/TX/RX/Lost - Red color

Eddie Lim 9W2LWK
 

Hi Randy,

I am using HBMon Version SP2ONG 2019-2020.
and the latest hblink3 , git-cloned from github

Eddie 9W2LWK


Re: HBMon Connected/TX/RX/Lost - Red color

Randy AA6RH
 

Thanks for letting me know. What "version" were you using previously, out of curiosity? We can look at a diff between versions if I can get that information. It may be lost to the cosmos at this point, however.

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) ūüėĀ


Re: HBMon Connected/TX/RX/Lost - Red color

Eddie Lim 9W2LWK
 

Nope, It is not a first setup
just recently updated to the latest HBLink binaries from the github

and yes it works, i will try the method you describe and i will update over here
Thanks anyway

73s
Eddie


Re: HBMon Connected/TX/RX/Lost - Red color

Randy AA6RH
 

Perhaps it's because the ID you're using for those points are already used elsewhere (for instance, OBP-1 is using ID 502006008, and then you have that also set up for BM-Malaysia-1)? Did it ever work, did something change, or is this a first-time setup?

I don't have a particularly cogent answer here, the monitor is a black box to me at the moment.

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) ūüėĀ


Re: HBMon Connected/TX/RX/Lost - Red color

area51now@...
 

Means your not connected to those BM servers


HBMon Connected/TX/RX/Lost - Red color

Eddie Lim 9W2LWK
 

Anyone knows what is this status mean in hbmon3 ?



As now i do not see any problem related to rules.cfg and everything seems fine
Just out of curiousity.

Best regards,
Eddie 9W2LWK

301 - 320 of 2790