Date   

Re: Analog_Bridge and Received USRP packet of wrong size

SP2ONG Waldek
 

Ok when I have comment outt  57 - 60 now 

M: 2019-07-07 16:06:42.939 PTT on
W: 2019-07-07 16:07:36.781 Received USRP packet of wrong size
D: 2019-07-07 16:07:36.802 cpu_time_used = 53863, minTxTime = 2000, pttTime = 3442474491, end = 3442528354
M: 2019-07-07 16:07:36.802 PTT off (keyed for 53863 ms)

no warning before "PTT on" message but still after  PTT on


Re: Analog_Bridge and Received USRP packet of wrong size

Steve N4IRS
 

In lines 57 through 60 it looks like you are trying to assert a PTT. It is not needed, the sending of audio with the PTT flag on will assert PTT. Try commenting out 57 through 60.

On 7/7/19 8:20 AM, Waldek SP2ONG wrote:
Hi Steve,

We use MB / AB with an attached script to play information emcom every hour, if the file info.wav exists in the directory. Generally everything works, but in the Analog_Bridge log I saw the information "Received USRP packet of wrong size". I would like to know the reason for this message and eliminate this problem.

I: 2019-07-07 08:14:31.913 Starting USRP --> Analog_Bridge (encoder) -> TLV thread
W: 2019-07-07 08:15:00.949 Received USRP packet of wrong size
M: 2019-07-07 08:15:00.949 PTT on
W: 2019-07-07 08:15:41.680 Received USRP packet of wrong size
D: 2019-07-07 08:15:41.708 cpu_time_used = 40759, minTxTime = 2000, pttTime = 1562487300949, end = 1562487341708
M: 2019-07-07 08:15:41.708 PTT off (keyed for 40759 ms)

73 Waldek


Analog_Bridge and Received USRP packet of wrong size

SP2ONG Waldek
 

Hi Steve,

We use MB / AB with an attached script to play information emcom every hour, if the file info.wav exists in the directory. Generally everything works, but in the Analog_Bridge log I saw the information "Received USRP packet of wrong size". I would like to know the reason for this message and eliminate this problem.

I: 2019-07-07 08:14:31.913 Starting USRP --> Analog_Bridge (encoder) -> TLV thread
W: 2019-07-07 08:15:00.949 Received USRP packet of wrong size
M: 2019-07-07 08:15:00.949 PTT on
W: 2019-07-07 08:15:41.680 Received USRP packet of wrong size
D: 2019-07-07 08:15:41.708 cpu_time_used = 40759, minTxTime = 2000, pttTime = 1562487300949, end = 1562487341708
M: 2019-07-07 08:15:41.708 PTT off (keyed for 40759 ms)

73 Waldek


Re: MMDVM_Bridge and HBLink3 missing CALL END

david bencini ik5xmk
 

Hi Steve and all,

for completeness of information ( MMDVM_Bridge/DOC/DMRplus_startup_options.md ), the line Options= in DMR+ for startup also accepts the configuration for SLOT 2 in this way:

Options=StartRef=4013;RelinkTime=15;UserLink=1;TS1_1=262;TS1_2=1;TS1_3=20;TS1_4=110;TS1_5=270;TS2_1=2241;TS2_2=22251;TS2_3=;TS2_4=;TS2_5=;

Thank you all for your wonderful work.
73, David IK5XMK (sysop of IT-MLINK DMRPlus Network)


Re: HBlink3 DMR server to Motorola repeater

Steve N4IRS
 

On 7/3/19 9:29 PM, area51now via Groups.Io wrote:
Thank you for the quick reply what would be the appropriate group to talk about this, DVswitch openbridge? just looking for a little direction on getting this running.

Thank you

Bob
KB6LED


Re: HBlink3 DMR server to Motorola repeater

area51now@...
 

Thank you for the quick reply what would be the appropriate group to talk about this, DVswitch openbridge? just looking for a little direction on getting this running.

Thank you

Bob
KB6LED


Re: HBlink3 DMR server to Motorola repeater

Steve N4IRS
 

You should ask your question in the HBlink subgroup. That being said, you will need HB_Bridge and IPSC_Bridge from here. <https://github.com/n0mjs710/HBlink/tree/HB_Bridge> and here <https://github.com/n0mjs710/DMRlink/tree/IPSC_Bridge> Your flow diagram will look like this:

SLR5700 <-> IPSC_Bridge <-> HB_Bridge <-> HBlink3

73, Steve N4IRS

On 7/3/19 9:02 PM, area51now via Groups.Io wrote:
HI all I am not sure I am in the right spot to ask but ill try. I have successfully have the HBlink3 for DMR up and running and I can access via my MMVM hotspot to Branmister and TGIF I would like to
be able to point my Motorola SLR5700 repeater and access it but I have been unable to get them talking to each other,  has anyone done this type of set up?

Thanks

Bob


HBlink3 DMR server to Motorola repeater

area51now@...
 

HI all I am not sure I am in the right spot to ask but ill try. I have successfully have the HBlink3 for DMR up and running and I can access via my MMVM hotspot to Branmister and TGIF I would like to
be able to point my Motorola SLR5700 repeater and access it but I have been unable to get them talking to each other,  has anyone done this type of set up?

Thanks

Bob


Re: Two YSF Reflectors

Steve N4IRS
 

[System Fusion Network]

On 7/2/2019 2:57 PM, David wrote:
Thanks Steve.

You skipped a question...

The example MMDVM_Bridge.ini on github has no sections titled "[YSF]".  Are they to be added as in your example in this thread?


Re: Two YSF Reflectors

David - AK2L
 

Thanks Steve.

You skipped a question...

The example MMDVM_Bridge.ini on github has no sections titled "[YSF]".  Are they to be added as in your example in this thread?


Re: Two YSF Reflectors

Steve N4IRS
 



On 7/2/2019 2:39 PM, David wrote:
Where do the port numbers -- 42000/42001 -- go?
In the [System Fusion Network] stanza of each MMDVM_Bridge.ini

The example MMDVM_Bridge.ini on github has no sections titled "[YSF]".  Are they to be added as in your example in this thread?

You mentioned a flow diagram of:
YSFReflector_1 <-> MMDVM_Bridge_1 <-> MMDVM_Bridge_2 <-> YSFReflector_2

And you wrote "The crossover will be done in the respective DVSwitch.ini".  How does DVSwitch relate to the flow diagram?
DVSwitch.ini controls the port numbers each copy of MMDVM_Bridge uses to communicate with the other copy of MMDVM_Bridge
It relates here
MMDVM_Bridge_1 <-> MMDVM_Bridge_2
                                      ^



Can the two instances of MMDVM_Bridge reside on one reflector, or is each reflector getting its own copy?
Everything can be on one host.


Re: Two YSF Reflectors

David - AK2L
 

Where do the port numbers -- 42000/42001 -- go?

The example MMDVM_Bridge.ini on github has no sections titled "[YSF]".  Are they to be added as in your example in this thread?

You mentioned a flow diagram of:
YSFReflector_1 <-> MMDVM_Bridge_1 <-> MMDVM_Bridge_2 <-> YSFReflector_2

And you wrote "The crossover will be done in the respective DVSwitch.ini".  How does DVSwitch relate to the flow diagram?

Can the two instances of MMDVM_Bridge reside on one reflector, or is each reflector getting its own copy?


Re: MMDVM_Bridge and HBLink3 missing CALL END

Heiko DL1BZ
 

I certify too, now all is ok with the CALL_END problem. Great work guys !

73 Heiko, DL1BZ


Re: Two YSF Reflectors

Steve N4IRS
 

In MMDVM_Bridge.ini

On 7/2/19 1:48 AM, David wrote:
I just configured two (local) YSF reflectors for testing.

One is at 192.168.1.109, port 42000 and the other is at 192.168.1.112, port 42001.  (The ports are different so I could move the test outside of the firewall at some point.)

Where do I specify the reflectors' IP addresses and ports?

Thanks.

David


Re: Two YSF Reflectors

David - AK2L
 

I just configured two (local) YSF reflectors for testing.

One is at 192.168.1.109, port 42000 and the other is at 192.168.1.112, port 42001.  (The ports are different so I could move the test outside of the firewall at some point.)

Where do I specify the reflectors' IP addresses and ports?

Thanks.

David


Re: Audio_Bridge Levels

Dan K2IE
 

Just what I needed, thank you.


Re: MMDVM_Bridge and HBLink3 missing CALL END

Steve N4IRS
 

Good to hear. I am planning to push the updates for AB and MD to the apt repository Wednesday afternoon. Mike is working on a tweak now and I am updating scripts and config files. It looks like we have good BM, HB3, and DMR+ connectivity.

73, Steve N4IRS

On 7/1/2019 4:04 PM, Waldek SP2ONG wrote:
Steve

I watched the evening traffic coming from YSF reflector and did not see any lost CALL END

Good job Steve


Re: MMDVM_Bridge and HBLink3 missing CALL END

SP2ONG Waldek
 

Steve

I watched the evening traffic coming from YSF reflector and did not see any lost CALL END

Good job Steve


Re: MMDVM_Bridge and HBLink3 missing CALL END

SP2ONG Waldek
 

Steve

Thank you very much for the information, I updated MMDVM_Bridge and I will be watching traffic from the YSF reflector

73 Waldek


Re: MMDVM_Bridge and HBLink3 missing CALL END

Steve N4IRS
 

Waldek,
I have pushed a update to github that should solve the call end issue. Please test and report.

73, Steve N4IRS

On 6/27/2019 6:25 AM, Waldek SP2ONG wrote:
Another example of CALL END which did not appear in HBlink

D: 2019-06-27 10:09:40.604 V/D Mode 2 Data, DT1
D: 2019-06-27 10:09:40.604 0000:  15 22 61 5F 28 03 22 00 00 00                      *."a_(."...*
D: 2019-06-27 10:09:40.604 YSF Network Data Received
D: 2019-06-27 10:09:40.604 0000:  59 53 46 44 53 52 30 44 4D 52 20 20 20 20 53 51    *YSFDSR0DMR    SQ*
D: 2019-06-27 10:09:40.604 0010:  37 4F 56 50 20 20 20 20 41 4C 4C 20 20 20 20 20    *7OVP    ALL     *
D: 2019-06-27 10:09:40.604 0020:  20 20 3F D4 71 C9 63 4D F2 9D 38 78 41 70 C1 FF    *  ?.q.cM..8xAp..*
D: 2019-06-27 10:09:40.604 0030:  01 B8 83 B2 82 96 BD C1 F3 00 F7 37 CC 1C 23 AA    *...........7..#.*
D: 2019-06-27 10:09:40.604 0040:  D8 F3 F8 FF F4 15 53 11 8D 74 DF 23 63 C0 17 60    *......S..t.#c..`*
D: 2019-06-27 10:09:40.604 0050:  7F 1C 88 B7 A5 E0 40 76 9A 26 FF 9E B9 A8 5A BA    *......@v.&....Z.*
D: 2019-06-27 10:09:40.604 0060:  46 92 10 14 BE 05 AC 2C D3 7C 71 12 9C 75 75 A8    *F......,.|q..uu.*
D: 2019-06-27 10:09:40.604 0070:  F7 7F B8 11 10 F2 C6 5F 3F 0E 3E E8 89 B9 95 8F    *......._?.>.....*
D: 2019-06-27 10:09:40.604 0080:  3D EF 0E 84 25 1E 49 94 64 25 B4 D6 36 57 0E 02    *=...%.I.d%..6W..*
D: 2019-06-27 10:09:40.604 0090:  81 B7 13 73 F6 0D FB D5 89 01 93                   *...s.......*
D: 2019-06-27 10:09:40.604 Network Transmitted
D: 2019-06-27 10:09:40.604 0000:  44 4D 52 44 69 27 C8 50 00 00 69 00 03 F9 66 81    *DMRDi'.P..i...f.*
D: 2019-06-27 10:09:40.604 0010:  AC 19 A2 69 AC AA 40 20 00 44 40 80 80 AC AA 40    *...i..@ .D@....@*
D: 2019-06-27 10:09:40.604 0020:  20 01 30 90 50 C0 69 10 44 40 80 80 AC AA 40 20    * .0.P.i.D@....@ *
D: 2019-06-27 10:09:40.604 0030:  00 44 40 80 80 00 00                               *.D@....*
D: 2019-06-27 10:09:40.605 Network Transmitted
D: 2019-06-27 10:09:40.605 0000:  44 4D 52 44 6A 27 C8 50 00 00 69 00 03 F9 66 82    *DMRDj'.P..i...f.*
D: 2019-06-27 10:09:40.605 0010:  AC 19 A2 69 AC AA 40 20 00 44 40 80 80 AC AA 40    *...i..@ .D@....@*
D: 2019-06-27 10:09:40.605 0020:  20 01 70 50 F0 00 07 40 44 40 80 80 AC AA 40 20    * .pP...@D@....@ *
D: 2019-06-27 10:09:40.605 0030:  00 44 40 80 80 00 00                               *.D@....*
M: 2019-06-27 10:09:40.605 YSF, received network end of transmission, 52.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-06-27 10:09:40.610 DMR, TX state = OFF, DMR frame count was 875 frames
D: 2019-06-27 10:09:40.610 Network Transmitted
D: 2019-06-27 10:09:40.610 0000:  44 4D 52 44 6B 27 C8 50 00 00 69 00 03 F9 66 A2    *DMRDk'.P..i...f.*
D: 2019-06-27 10:09:40.610 0010:  AC 19 A2 69 02 40 0F 8A 02 40 3E 10 59 60 00 20    *...i.@...@>.Y`. *
D: 2019-06-27 10:09:40.610 0020:  84 AD 5D 7F 77 FD 75 79 64 4C 0B 20 24 10 1E 20    *..].w.uydL. $.. *
D: 2019-06-27 10:09:40.610 0030:  5F 41 E5 01 6C 00 00                               *_A..l..*

5741 - 5760 of 10078