Re: Current status DMRlink, HBlink DVSwitch


david bencini ik5xmk
 

Hi Steve,

i'm making some tests, to dmr master server no problem to connect to, 
but on xlx side i've this error:

DEBUG 2017-10-02 06:13:39,719 Logging system started, anything from here on gets logged
INFO 2017-10-02 06:13:39,720 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2017-10-02 06:13:39,721 (REPEATER-1) Client maintenance loop started
INFO 2017-10-02 06:13:39,722 (REPEATER-1) Sending login request to master 185.203.118.66:55555
DEBUG 2017-10-02 06:13:39,722 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0x7fbf0433aab8>
DEBUG 2017-10-02 06:13:39,723 (REPEATER-2) Client maintenance loop started
INFO 2017-10-02 06:13:39,723 (REPEATER-2) Sending login request to master 5.249.151.111:62030
DEBUG 2017-10-02 06:13:39,723 CLIENT instance created: REPEATER-2, <__main__.HBSYSTEM instance at 0x7fbf040fb878>
INFO 2017-10-02 06:13:39,724 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 2225069
INFO 2017-10-02 06:13:39,725 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-10-02 06:13:39,725 (REPEATER-1) Repeater Configuration Sent
DEBUG 2017-10-02 06:13:39,726 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1
INFO 2017-10-02 06:13:39,727 (REPEATER-1) Repeater Configuration Accepted
INFO 2017-10-02 06:13:39,727 (REPEATER-1) Connection to Master Completed
INFO 2017-10-02 06:13:39,768 (REPEATER-2) Repeater Login ACK Received with 32bit ID: 1228258867
ERROR 2017-10-02 06:13:39,813 (REPEATER-2) Master ACK Contained wrong ID - Connection Reset
DEBUG 2017-10-02 06:13:44,725 (REPEATER-1) Client maintenance loop started
DEBUG 2017-10-02 06:13:44,726 (REPEATER-1) RPTPING Sent to Master. Pings Since Connected: 1
DEBUG 2017-10-02 06:13:44,726 (REPEATER-2) Client maintenance loop started
INFO 2017-10-02 06:13:44,726 (REPEATER-2) Sending login request to master 5.249.151.111:62030
INFO 2017-10-02 06:13:44,771 (REPEATER-2) Repeater Login ACK Received with 32bit ID: 1228258867
ERROR 2017-10-02 06:13:44,816 (REPEATER-2) Master ACK Contained wrong ID - Connection Reset
^CINFO 2017-10-02 06:13:45,300 SHUTDOWN: HBLINK IS TERMINATING WITH SIGNAL 2
INFO 2017-10-02 06:13:45,300 SHUTDOWN: DE-REGISTER SYSTEM: REPEATER-1
INFO 2017-10-02 06:13:45,301 (REPEATER-1) De-Registeration sent to Master: 185.203.118.66:55555
INFO 2017-10-02 06:13:45,301 SHUTDOWN: DE-REGISTER SYSTEM: REPEATER-2
INFO 2017-10-02 06:13:45,302 (REPEATER-2) De-Registeration sent to Master: 5.249.151.111:62030
INFO 2017-10-02 06:13:45,302 SHUTDOWN: ALL SYSTEM HANDLERS EXECUTED - STOPPING REACTOR

form xlx log:

root@superciuk:~# tail -f /var/log/messages
Oct  2 12:19:55 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:19:55 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:00 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:00 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:05 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:05 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:10 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:10 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:15 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:15 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:20 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:20 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72

I tried with some callsigns and ids, but i think there is a problem in the code linking to xlx...
can you help me ?

thank you

David






2017-09-29 11:39 GMT+02:00 Steve N4IRS <szingman@...>:

David,
Your next step is to make sure HBlink can login to the 2 servers.
I suggest you test each connection separately by disabling one of the clients.
Rename or copy hblink-SAMPLE.cfg to hblink.cfg.
Run hblink.py in the foreground and watch the console to verify valid login.
You can then reduce the log level by changing LOG_LEVEL: DEBUG to LOG_LEVEL: INFO

Once that works, enable both clients, run hblink.py  and watch the console for errors.
If everything looks good you can run hb_bridge_all.py and test for traffic passing between the 2 servers.

73, Steve N4IRS

 

On 09/29/2017 04:54 AM, david bencini ik5xmk wrote:
Hi Steve, i'm looking for hblink-SAMPLE.cfg to work with this software.

Can you help me to understand how to handle this link?

In practice hblink should be able to connect as mmdvm client to the XLX dstar reflector, so act in configuration in this way?

[REPEATER-1]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP:
PORT: 62030
MASTER_PORT: 62030
PASSPHRASE: homebrew
CALLSIGN: IK5XMK
RADIO_ID: 2225013
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
...

and then, on the other side, to DMR MASTER server as mmdvm client repeater:


[REPEATER-2]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP:
PORT: 55555
MASTER_PORT: 55555
PASSPHRASE: passw0rd
CALLSIGN: IK5XMK
RADIO_ID: 2225013
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
...

on [MASTER-1]
ENABLED: False

What else do you need to hblink to work?
Is this a way to think about a collector between the two networks? This is for the first step to try the link...

Thank you,
David

... must i to open a new topic for this?

2017-09-28 21:26 GMT+02:00 Steve N4IRS <szingman@...>:
David,
Since both "endpoints" speak HBR protocol (MMDVM) it might be as simple as using HBlink:
dmrmaster <---> HBlink <---> XLX.
The problem that you might run into that HBlink does omore checking of the source ID. That is where DMRGateway came in.
Cort or Mike may chime in will a more detailed answer. Since it's only software (did I really say that?) It's worth a try. Take it one side at a time and build into the middle.

Steve

On 9/28/2017 3:15 PM, david bencini ik5xmk wrote:
Thank you Steve. It can be a way to try. Good!

At the end (only me ?) i need a software that side A it connects an xlx module (like standard mmdvm repeater) and
side B it connects a dmrmaster server (like standard mmdvm repeater), so when i hit  a TG i can hear me on dstar and viceversa.
Transcoding is fully working on my xlx.
I think (wrong tinking?) that it is not difficult to bring a data flow from a system to other, with same homebrew protocol.

by the way, thank you and best 73 to you and to all guys on group

David IK5XMK

2017-09-28 20:59 GMT+02:00 Steve N4IRS <szingman@...>:
David,
I do not know of a way to connect DMR+, IPSC2 or DMRMaster to XLX. If, and it's a BIG if, IPSC2 can connect to IPSC_Bridge (DMRlink) it might go something like this:
IPSC2 <---> IPSC_Bridge <---> HB_Bridge <---> DMRGateway <---> XLX. I think I remember someone posting that he needed DMRGateway from G4KLX to connect HB_Bridge to XLX.
Sorry I could not be of more help.

73, Steve N4IRS

On 9/28/2017 2:50 PM, david bencini ik5xmk wrote:
Hi Steve, great work !! Thank you.

Please, where can i find informations/which software/configuration about linking my dmr server (dmrmaster.webandcloud.net or ipsc2.webandcloud.net
to my xlx dstar server (http://vpngrf.webandcloud.net/db/dashboard/index.php) that it has an hardware transcoder server (2 USB ThumbDV)  into? I need a dmr flow to put into my
dstar system so i can join my dstar/dmr repeaters in my region. Now i can link my mmdvm repeater directly to xlx via dmrmmdvm protocol, and it works
very well with good audio, but a lot of friends are on dmr servers and i need a "connector" from dmr world to dstar one :)

Thank you for any infos
73, David IK5XMK





Join main@DVSwitch.groups.io to automatically receive all group messages.