Date   

Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the repeater
ID, which has several static TG's preconfigured. I'm transmitting
using my personal ID, on one of the static TG's (although if I were
using a different TG, wouldn't it bring it up as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N











Re: Bridging from MMDVM repeater to IPSC network

Rob WX1N
 

Ok, so it can tell what is connecting, similar to the Client/Package ID's? Is the difference in behavior between a DMRlink connection and a Motorola repeater connection specific to BM? What I'm getting at with that is, if I were to request and receive access to a c-Bridge, would it also behave differently for a DMRlink connection than it would for a Motorola repeater connection?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:05 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. This does not happen on a connection from a Motorola Repeater. It's all about how BM treats a DMRLink connection.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the repeater
ID, which has several static TG's preconfigured. I'm transmitting
using my personal ID, on one of the static TG's (although if I were
using a different TG, wouldn't it bring it up as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N












Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

The connection from DMRlink to BM is considered by BM as a SmartPTT connection. A c-Bridge treats the connection the same as a Motorola repeater. The SmartPTT issue is specific to BM ONLY.

On 6/23/2017 12:16 PM, Rob WX1N wrote:
Ok, so it can tell what is connecting, similar to the Client/Package ID's?  Is the difference in behavior between a DMRlink connection and a Motorola repeater connection specific to BM?  What I'm getting at with that is, if I were to request and receive access to a c-Bridge, would it also behave differently for a DMRlink connection than it would for a Motorola repeater connection?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:05 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. This does not happen on a connection from a Motorola Repeater. It's all about how BM treats a DMRLink connection.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324.  Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of 
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the repeater 
ID, which has several static TG's preconfigured.  I'm transmitting 
using my personal ID, on one of the static TG's (although if I were 
using a different TG, wouldn't it bring it up as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of 
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction.  I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink.  I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network.  I set it up as follows:  MMDVM set to connect to local instance of HBlink (successful).  HBlink configuration as a master to allow MMDVM to connect.  Run MMDVMHost, run HB_Bridge.py.  DMRlink configured as a peer to connect to the IPSC connection of 3102.  Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network.  I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N























Re: Bridging from MMDVM repeater to IPSC network

Rob WX1N
 

Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the repeater
ID, which has several static TG's preconfigured. I'm transmitting
using my personal ID, on one of the static TG's (although if I were
using a different TG, wouldn't it bring it up as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N












Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the repeater
ID, which has several static TG's preconfigured. I'm transmitting
using my personal ID, on one of the static TG's (although if I were
using a different TG, wouldn't it bring it up as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N














Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

Are you using a MMDVM repeater or hotspot for the testing?

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the repeater
ID, which has several static TG's preconfigured. I'm transmitting
using my personal ID, on one of the static TG's (although if I were
using a different TG, wouldn't it bring it up as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N














Re: Bridging from MMDVM repeater to IPSC network

Rob WX1N
 

Yes. Here's what I'm seeing in the IPSC_Bridge window. If this doesn't tell you anything, I don't want to take up any more of your time, this is a learning experience for me that doesn't contribute to the project development.

INFO DMRLink IPSC Bridge
INFO (SAMPLE_PEER) Registering with the Master: <redacted>
WARNING (SAMPLE_PEER) Registration response (we requested reg) from the Master: 3102, <redacted> (1 peers)
INFO (SAMPLE_PEER), No Peer List - Requesting One From the Master
INFO (SAMPLE_PEER) Begin AMBE encode STREAM ID: 2216044619 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID 313324 (313324), TS 1
INFO (SAMPLE_PEER) Begin AMBE encode STREAM ID: 1125825989 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID 313324 (313324), TS 1

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:23 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up as
a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N















Re: Bridging from MMDVM repeater to IPSC network

Rob WX1N
 

MMDVM repeater

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:25 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Are you using a MMDVM repeater or hotspot for the testing?

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up as
a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N















Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

Standby. Let me try it here.

On 6/23/2017 12:25 PM, Rob WX1N wrote:
Yes. Here's what I'm seeing in the IPSC_Bridge window. If this doesn't tell you anything, I don't want to take up any more of your time, this is a learning experience for me that doesn't contribute to the project development.

INFO DMRLink IPSC Bridge
INFO (SAMPLE_PEER) Registering with the Master: <redacted>
WARNING (SAMPLE_PEER) Registration response (we requested reg) from the Master: 3102, <redacted> (1 peers)
INFO (SAMPLE_PEER), No Peer List - Requesting One From the Master
INFO (SAMPLE_PEER) Begin AMBE encode STREAM ID: 2216044619 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID 313324 (313324), TS 1
INFO (SAMPLE_PEER) Begin AMBE encode STREAM ID: 1125825989 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID 313324 (313324), TS 1

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:23 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up as
a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N
















Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

Just in case, droy your dmrlink connection to 3102

On 6/23/2017 12:25 PM, Rob WX1N wrote:
Yes. Here's what I'm seeing in the IPSC_Bridge window. If this doesn't tell you anything, I don't want to take up any more of your time, this is a learning experience for me that doesn't contribute to the project development.

INFO DMRLink IPSC Bridge
INFO (SAMPLE_PEER) Registering with the Master: <redacted>
WARNING (SAMPLE_PEER) Registration response (we requested reg) from the Master: 3102, <redacted> (1 peers)
INFO (SAMPLE_PEER), No Peer List - Requesting One From the Master
INFO (SAMPLE_PEER) Begin AMBE encode STREAM ID: 2216044619 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID 313324 (313324), TS 1
INFO (SAMPLE_PEER) Begin AMBE encode STREAM ID: 1125825989 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID 313324 (313324), TS 1

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:23 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up as
a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N
















Re: Bridging from MMDVM repeater to IPSC network

Rob WX1N
 

Ok it's dropped

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:28 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Just in case, droy your dmrlink connection to 3102

On 6/23/2017 12:25 PM, Rob WX1N wrote:
Yes. Here's what I'm seeing in the IPSC_Bridge window. If this doesn't tell you anything, I don't want to take up any more of your time, this is a learning experience for me that doesn't contribute to the project development.

INFO DMRLink IPSC Bridge
INFO (SAMPLE_PEER) Registering with the Master: <redacted> WARNING
(SAMPLE_PEER) Registration response (we requested reg) from the
Master: 3102, <redacted> (1 peers) INFO (SAMPLE_PEER), No Peer List -
Requesting One From the Master INFO (SAMPLE_PEER) Begin AMBE encode
STREAM ID: 2216044619 SUB: WX1N (3133257) REPEATER: WX1NH (313323)
TGID 313324 (313324), TS 1 INFO (SAMPLE_PEER) Begin AMBE encode STREAM
ID: 1125825989 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID
313324 (313324), TS 1

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:23 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up
as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC
network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N

















Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

Your entry in dmrlink.cfg should look something like this:
[BM_3102]
ENABLED: True
RADIO_ID: 12345
IP:
PORT: 53102
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
GROUP_HANGTIME: 5
AUTH_ENABLED: False
AUTH_KEY:
MASTER_IP: 3102.repeater.net
MASTER_PORT: 55001

On 6/23/2017 12:29 PM, Rob WX1N wrote:
Ok it's dropped

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:28 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Just in case, droy your dmrlink connection to 3102

On 6/23/2017 12:25 PM, Rob WX1N wrote:
Yes. Here's what I'm seeing in the IPSC_Bridge window. If this doesn't tell you anything, I don't want to take up any more of your time, this is a learning experience for me that doesn't contribute to the project development.

INFO DMRLink IPSC Bridge
INFO (SAMPLE_PEER) Registering with the Master: <redacted> WARNING
(SAMPLE_PEER) Registration response (we requested reg) from the
Master: 3102, <redacted> (1 peers) INFO (SAMPLE_PEER), No Peer List -
Requesting One From the Master INFO (SAMPLE_PEER) Begin AMBE encode
STREAM ID: 2216044619 SUB: WX1N (3133257) REPEATER: WX1NH (313323)
TGID 313324 (313324), TS 1 INFO (SAMPLE_PEER) Begin AMBE encode STREAM
ID: 1125825989 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID
313324 (313324), TS 1

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:23 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up
as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC
network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N

















Re: Bridging from MMDVM repeater to IPSC network

Rob WX1N
 

Yup, looks the same:
[SAMPLE_PEER]
ENABLED: True
RADIO_ID: 313323
IP:
PORT: 50000
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
AUTH_ENABLED: False
AUTH_KEY:
MASTER_IP: 3102.repeater.net
MASTER_PORT: 55001
GROUP_HANGTIME: 5

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:32 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Your entry in dmrlink.cfg should look something like this:
[BM_3102]
ENABLED: True
RADIO_ID: 12345
IP:
PORT: 53102
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
GROUP_HANGTIME: 5
AUTH_ENABLED: False
AUTH_KEY:
MASTER_IP: 3102.repeater.net
MASTER_PORT: 55001


On 6/23/2017 12:29 PM, Rob WX1N wrote:
Ok it's dropped

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:28 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Just in case, droy your dmrlink connection to 3102

On 6/23/2017 12:25 PM, Rob WX1N wrote:
Yes. Here's what I'm seeing in the IPSC_Bridge window. If this doesn't tell you anything, I don't want to take up any more of your time, this is a learning experience for me that doesn't contribute to the project development.

INFO DMRLink IPSC Bridge
INFO (SAMPLE_PEER) Registering with the Master: <redacted> WARNING
(SAMPLE_PEER) Registration response (we requested reg) from the
Master: 3102, <redacted> (1 peers) INFO (SAMPLE_PEER), No Peer List -
Requesting One From the Master INFO (SAMPLE_PEER) Begin AMBE encode
STREAM ID: 2216044619 SUB: WX1N (3133257) REPEATER: WX1NH (313323)
TGID 313324 (313324), TS 1 INFO (SAMPLE_PEER) Begin AMBE encode
STREAM
ID: 1125825989 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID
313324 (313324), TS 1

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:23 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC
network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up
as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC
network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N


















Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

OK,
Standby

On 6/23/2017 12:34 PM, Rob WX1N wrote:
Yup, looks the same:
[SAMPLE_PEER]
ENABLED: True
RADIO_ID: 313323
IP:
PORT: 50000
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
AUTH_ENABLED: False
AUTH_KEY:
MASTER_IP: 3102.repeater.net
MASTER_PORT: 55001
GROUP_HANGTIME: 5

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:32 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Your entry in dmrlink.cfg should look something like this:
[BM_3102]
ENABLED: True
RADIO_ID: 12345
IP:
PORT: 53102
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
GROUP_HANGTIME: 5
AUTH_ENABLED: False
AUTH_KEY:
MASTER_IP: 3102.repeater.net
MASTER_PORT: 55001


On 6/23/2017 12:29 PM, Rob WX1N wrote:
Ok it's dropped

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:28 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Just in case, droy your dmrlink connection to 3102

On 6/23/2017 12:25 PM, Rob WX1N wrote:
Yes. Here's what I'm seeing in the IPSC_Bridge window. If this doesn't tell you anything, I don't want to take up any more of your time, this is a learning experience for me that doesn't contribute to the project development.

INFO DMRLink IPSC Bridge
INFO (SAMPLE_PEER) Registering with the Master: <redacted> WARNING
(SAMPLE_PEER) Registration response (we requested reg) from the
Master: 3102, <redacted> (1 peers) INFO (SAMPLE_PEER), No Peer List -
Requesting One From the Master INFO (SAMPLE_PEER) Begin AMBE encode
STREAM ID: 2216044619 SUB: WX1N (3133257) REPEATER: WX1NH (313323)
TGID 313324 (313324), TS 1 INFO (SAMPLE_PEER) Begin AMBE encode
STREAM
ID: 1125825989 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID
313324 (313324), TS 1

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:23 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC
network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up
as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC
network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N

















Re: Bridging from MMDVM repeater to IPSC network

Steve N4IRS
 

Are you listening to 313324?

On 6/23/2017 12:34 PM, Rob WX1N wrote:
Yup, looks the same:
[SAMPLE_PEER]
ENABLED: True
RADIO_ID: 313323
IP:
PORT: 50000
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
AUTH_ENABLED: False
AUTH_KEY:
MASTER_IP: 3102.repeater.net
MASTER_PORT: 55001
GROUP_HANGTIME: 5

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Friday, June 23, 2017 12:32 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Your entry in dmrlink.cfg should look something like this:
[BM_3102]
ENABLED: True
RADIO_ID: 12345
IP:
PORT: 53102
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: True
CON_APP: True
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
GROUP_HANGTIME: 5
AUTH_ENABLED: False
AUTH_KEY:
MASTER_IP: 3102.repeater.net
MASTER_PORT: 55001


On 6/23/2017 12:29 PM, Rob WX1N wrote:
Ok it's dropped

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:28 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Just in case, droy your dmrlink connection to 3102

On 6/23/2017 12:25 PM, Rob WX1N wrote:
Yes. Here's what I'm seeing in the IPSC_Bridge window. If this doesn't tell you anything, I don't want to take up any more of your time, this is a learning experience for me that doesn't contribute to the project development.

INFO DMRLink IPSC Bridge
INFO (SAMPLE_PEER) Registering with the Master: <redacted> WARNING
(SAMPLE_PEER) Registration response (we requested reg) from the
Master: 3102, <redacted> (1 peers) INFO (SAMPLE_PEER), No Peer List -
Requesting One From the Master INFO (SAMPLE_PEER) Begin AMBE encode
STREAM ID: 2216044619 SUB: WX1N (3133257) REPEATER: WX1NH (313323)
TGID 313324 (313324), TS 1 INFO (SAMPLE_PEER) Begin AMBE encode
STREAM
ID: 1125825989 SUB: WX1N (3133257) REPEATER: WX1NH (313323) TGID
313324 (313324), TS 1

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:23 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

Do I have the data right?
313324 : [ { "network" : 313323, "slot" : 1 } ],

On 6/23/2017 12:21 PM, Rob WX1N wrote:
Still doesn't seem to be going through, I don't see it on hose.repeater.net/313324, and I don't see anything coming through on our other repeater.

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:13 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC network

I have added Radio ID 313323 TS1 TG 313324 to bridge.json on BM server 3102.

On 6/23/2017 12:02 PM, Rob WX1N wrote:
Radio ID 313323, TS 1, TG 313324. Just to make sure I'm understanding this right - a valid IPSC connection to BM will pass absolutely nothing back and forth until it is preconfigured on the server end?

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 12:00 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC
network

Let me be a little more clear. The connection from DMRlink to BM is as you say considered by BM as a SmartPTT connection. For a BM SmartPTT connection, a BM admin (I am one) has to configure the bridge in BM. I will need the following:
Radio_ID: in dmrlink.cfg
The TS and TG you want to bridge.

This can NOT be configured from a self care account.

On 6/23/2017 11:58 AM, Rob WX1N wrote:
Steve,
In the DMR link configuration, I'm signing in to 3102 as the
repeater ID, which has several static TG's preconfigured. I'm
transmitting using my personal ID, on one of the static TG's
(although if I were using a different TG, wouldn't it bring it up
as a dynamic for a few
minutes?)

-----Original Message-----
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of
Steve N4IRS
Sent: Friday, June 23, 2017 11:55 AM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] Bridging from MMDVM repeater to IPSC
network

Rob,
Is 3102 setup to bridge the TG you are trying from the Radio ID you are presenting to BM?

On 6/23/2017 11:53 AM, Rob WX1N wrote:
Good morning,

I'm hoping for some basic info if one of you has the time to point me in the right direction. I know this is still a work in progress and I don't want to interfere with that, so if this isn't a quick answer, then please disregard.

I'm playing around with the new Bridge branches of HBlink and DMRlink. I wanted to see if I could successfully connect an MMDVM repeater to an IPSC network. I set it up as follows: MMDVM set to connect to local instance of HBlink (successful). HBlink configuration as a master to allow MMDVM to connect. Run MMDVMHost, run HB_Bridge.py. DMRlink configured as a peer to connect to the IPSC connection of 3102. Run IPSC_Bridge.py.
Results - MMDVM connects to HBlink and transmissions show in both HB_Bridge and IPSC_Bridge terminal windows, however, the transmissions don't seem to be making it through to the network. I think I am connected to 3102, as the repeater shows up in the 3102 status page (albeit as a SmartPTT network).

Does anyone have a guess as to where I'm going wrong?

Rob, WX1N

















Re: Analog_Bridge for the Raspberry Pi

Steve N4IRS
 
Edited

I have replaced Analog_Bridge in the Analog_Bridge repository on GitHub  Mike has uploaded the new version of the confidence test for DV3000 (AMBEtest4.py).
This new version of confidence test is significantly more complete. The number and complexity of the testing has improved and even more will be added.
Support for testing a remote AMBEserver has been added. DO NOT run on the same machine as AMBEserver. AMBEtest4.py -i 192.168..1.10
If your DV3000 FAILS the tests, you can be confident that Analog_Bridge will not work properly. If the DV3000 passes, you might have a shot.

The options are: vens
v == verbose test is normally silent.
e == stop on errors
n == use 460800 for baud rate (Newer DV3000u)
s == serial port
i == address of AMBEserver if that's what you are testing 

AMBEtest4.py -v -e -n -s /dev/ttyUSB0
AMBEtest4.py -v -e -i 192.168.1.1

What I am finding is that power is the MOST critical issue. To force errors, I am using a 1.35A power supply. Even adding a USB extension cable or thick cable affects results.
It LOOKS like the DV3000 resets when sent a frame to decode or encode if there is a problem. 
73, Steve N4IRS


AMBEtest4.py

Steve Siesel [K4KSA]
 

Steve,

 

Here is my results of a DV3000u in a RPi 3!

 

Thoughts?

Steve

K4KSA

 

 

root@DMRLink:/home/test/DV3000/Analog_Bridge# python AMBEtest4.py -n -s /dev/ttyUSB0

Setting serial port

Serial port parameters:

Port name:      /dev/ttyUSB0

Baudrate:       460800

Byte size:      8

Parity:         N

Stop bits:      1

Xon Xoff:       False

RTS/CTS:        False

DST/DTR:        False

*********************

Testing Reset DV3000

Test result: Success (6100010039)

Testing Get Product ID

Test result: Success (61000b0030414d4245333030305200)

Testing Get Version

Test result: Success (6100310031563132302e453130302e585858582e433130362e473531342e523030392e42303031303431312e433030323032303800)

Testing Set DSTAR Mode

Test result: Success (610002000a00)

Testing Reset DV3000

Test result: Success (6100010039)

Testing Set DMR Mode

Test result: Success (610002000a00)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ffff0001ffff000100000000000000000000ffff00000000000000000000000100000001000000000000ffff000000000000000000000001000000000000ffffffff000000000000000000000000000000000000000000000001000000000000ffff000000000001000000000000ffff00010001000000010000ffff00000000000000000000000000010000ffff0000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000ffff00010000ffff000000010000)

Testing Encode PCM

Test result: Success (61000b010148954be6500310b00777)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0001000000000001000000010000000000010000ffff0000ffff000000000000000000000000ffff00000000000000000000ffff00000000ffff0000000000000001000000010000ffff0001000000000000000000000000000000000000000100000000000000000000000000000000ffff0001ffff00000001000000010000000100000001ffffffff0000ffff0000ffff0001ffff00010000ffff0001ffff0001000000000000ffff0001ffff00000001ffff000000000000000000000000000000000000ffff0000ffff000100000000000100000001ffff0000000000000000ffff000000010000000000000000000100000000000000000000ffff000100000001000000000000ffff0000ffff00000000ffff0001ffff0000000000000001ffff0000000000000001ffff00000000ffff00000000000000000000)

Testing Encode PCM

Test result: Success (61000b010148a61ae1f1abaca4432b)

Testing Decode AMBE

Test result: Success (6101420200a00001ffff00000001ffff000000000000000000000001ffff00000000000000000000ffff0000000000000000ffff0001000000000000ffff000000000001ffff0000000000000001ffff0001ffff000000000000000000000001ffff000000000000000000000001ffff0000000000000000000100000000000000010001ffff00010000000000010001000000000000000000000001ffffffff0001ffff0000ffff0000000100000001ffff0001ffff00000000ffff0001ffff0001ffff0001000000000001ffff000100000000000000000001ffffffff0000000000010000000100010000000100000000000000010000ffffffffffff0001ffff0001ffff00000001ffff0001ffff0001ffff00000000ffff000100000001000000000001000000010000000100000000ffff0000ffffffff0000ffff00000000ffff0000)

Testing Encode PCM

Test result: Success (61000b010148fb836133dbbc308bb3)

Testing Decode AMBE

Test result: Success (6101420200a000010000ffff0000ffff000000010001000100000001ffff00000001ffff00010000ffff00000000ffffffff0001ffff00010000ffff0001ffff0001000100000001ffff000000000000000100000001ffff0001ffff00000000ffff0001ffff0001000000000000ffff0001ffff0000ffff00010000ffff0001ffff0001000000000000000000000000000100000000000000000000000100010000000000000000000000000000000000000001000000000000ffff0000ffff0001000000000001ffff000000000000000000000000000000000000ffff00000000ffff000000010000ffff000000010000000000000000ffffffffffff000000000000ffff0000000000000001ffff0001000000000001ffff00000000000000000000000000000001000000010000ffff0000000000000000000000000000000100000000)

Testing Encode PCM

Test result: Success (61000b010148dba06231d9b850abb3)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff000000000000000000000000ffff0001000000000000000000010000000000000000ffff00000000ffffffff0000000000000001ffff000000000001000100000001ffff0000000000000000ffff000000000000ffffffff00000000ffff000000000000000000000000000000000001000100000000000000000000000000000001000000010000ffff0000ffff000000000000000100000000ffff0000000000000000ffff00010000ffff000000000000ffff0000000000000000000000010000000000010000000000000000000000000000000000000000000000000000000000010000ffff0000000000000001ffff000000000001000000000000ffff00000000ffff00000000000100010001ffff00000001ffff000000000000ffff00000001ffff000000000001000000000001ffff00000001ffff0000)

Testing Encode PCM

Test result: Success (61000b010148a8c327379de4f08f3b)

Testing Decode AMBE

Test result: Success (6101420200a00000000000000000ffff000100000001000000000000000000000000000000000000ffff00000000000000000000000100000001000000000000ffff0000ffff0000ffff00000000ffff0000000100010000000000000000000100000000ffff0000000000000001ffff000000000000000000000000ffff000000000000000000000001000000000000ffff00000000ffff000000000000000000000000000000010001000000010000000100000000000000000000ffff0000ffff0000000000000001ffff000100000001000100000000ffff00000000000000000000ffff00000000ffff000000010000000100000000ffffffff0000000000000001ffff0000ffff00000001000000010000000000000000000000000001000000010000ffff000000000000ffff000000000001000000000001ffff0000000100000000)

Testing Encode PCM

Test result: Success (61000b010148bbc20517bfd0b0cb2f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000000000000ffff0001000000010000ffffffffffff000000010000ffffffff0000ffff0000000000000001000000000000000000000001000000010000000000000000000000000000ffff00000000000000000000000100000000000100000000ffff000000010000ffff00010000ffff0001ffff00000000000000000001ffffffff00000000000000010000000000000000ffff000000000000000000000001000000000000ffff0000000000000000ffff0001000000000000ffff00010001ffff0001000100000000ffff0000000000000000000000000000000100000000000000000000000000000000000000010000ffff0000ffff00010000ffff000000000000000100010000000000000001000000000000000000000000ffff000000000000000000000000000000000001ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014888f125379cd5d0ab6f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000100000001ffff000100000000000000000001ffff00000000ffff000100000000ffffffff0001ffff0000000000000000000000000000000000000000000100010000ffff00000000000000000000ffff000000010000ffff00000000ffff000000000001ffff00000000ffff000000000000000000000000000000010000000000000000000000000001000000000000000000000000ffff000000000000000100000000000100000001ffff0000000000000000ffff0000ffffffff00000000000000000001000000010000ffff00000000000000000000ffff00000000000000000000000000000000ffffffff0000ffff0000000000000001000000000001000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000010000ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014899e025359fe0b08f2b)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000ffff00000000ffffffff00000000000000010000ffff00010000ffff0000000000000000000100000000000100010000ffff000000000000000100000000ffff000000000000ffff00000000ffff00010000ffff0000000000000000000000000001ffff0000000000000000ffff00010001000000000000000000000001000000000000000000000000ffff00000000ffff0000000000010001ffff00000000ffff00000001ffffffff000000000000ffff0000000100000001000000000000ffff000100000000000000010001000000010000000000000000ffff0000000000000000000000000000000100000000ffff000000000000000100000001000000000000ffff00000000000000000000ffff000000000000000100010000ffff0001ffff0000000000000000000000000000ffff000000000000)

Testing Encode PCM

Test result: Success (61000b010148b543ad63cdd4a8033f)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff0001000000000000ffff0000000000010001ffff000000000000000000010000000100000000000100000000ffff00000001ffff0001000000000001ffff00000000000000000000000000010001000000000000000000000000000000000000000000000000ffffffff0000000000000000000000000000000000010000ffff00000001000000010000ffffffffffff0000ffff0000000100000000ffff0001000000000000000000000000ffff00000001000000000000000000000000000000000000000000000000ffff00000001ffff00000000000000000000000000000001000100000000ffff000000000001ffffffff0001ffff0000ffff000000010000000100010000000000000000000100010001000000000000000000000000000000010000ffff000000000000000000000000ffff00010000ffff)

Testing Encode PCM

Test result: Success (61000b01014886528d21a9f0fc032f)

root@DMRLink:/home/test/DV3000/Analog_Bridge#


Re: AMBEtest4.py

Steve N4IRS
 

Well,
At least it did not fail. As I said in the post, if it fails you have no chance. If it passes, you have a shot. It's worth a try.
So far I can cause a failure if I use a lower current power supply. With a 5V 1.35A PS powering a RPi2 I can get AMBEtest4 to fail. It's repeatable. I am going to bring up DIAL RC1 Analog_Bridge and HB_Bridge. The plan it to continue to expand the testing to try to find what is causing the failures. We want to get to a point where if the confidence test passes, Analog_Audio will work, every time. 

On 06/24/2017 04:25 PM, Steve Siesel [K4KSA] wrote:

Steve,

 

Here is my results of a DV3000u in a RPi 3!

 

Thoughts?

Steve

K4KSA

 

 

root@DMRLink:/home/test/DV3000/Analog_Bridge# python AMBEtest4.py -n -s /dev/ttyUSB0

Setting serial port

Serial port parameters:

Port name:      /dev/ttyUSB0

Baudrate:       460800

Byte size:      8

Parity:         N

Stop bits:      1

Xon Xoff:       False

RTS/CTS:        False

DST/DTR:        False

*********************

Testing Reset DV3000

Test result: Success (6100010039)

Testing Get Product ID

Test result: Success (61000b0030414d4245333030305200)

Testing Get Version

Test result: Success (6100310031563132302e453130302e585858582e433130362e473531342e523030392e42303031303431312e433030323032303800)

Testing Set DSTAR Mode

Test result: Success (610002000a00)

Testing Reset DV3000

Test result: Success (6100010039)

Testing Set DMR Mode

Test result: Success (610002000a00)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ffff0001ffff000100000000000000000000ffff00000000000000000000000100000001000000000000ffff000000000000000000000001000000000000ffffffff000000000000000000000000000000000000000000000001000000000000ffff000000000001000000000000ffff00010001000000010000ffff00000000000000000000000000010000ffff0000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000ffff00010000ffff000000010000)

Testing Encode PCM

Test result: Success (61000b010148954be6500310b00777)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0001000000000001000000010000000000010000ffff0000ffff000000000000000000000000ffff00000000000000000000ffff00000000ffff0000000000000001000000010000ffff0001000000000000000000000000000000000000000100000000000000000000000000000000ffff0001ffff00000001000000010000000100000001ffffffff0000ffff0000ffff0001ffff00010000ffff0001ffff0001000000000000ffff0001ffff00000001ffff000000000000000000000000000000000000ffff0000ffff000100000000000100000001ffff0000000000000000ffff000000010000000000000000000100000000000000000000ffff000100000001000000000000ffff0000ffff00000000ffff0001ffff0000000000000001ffff0000000000000001ffff00000000ffff00000000000000000000)

Testing Encode PCM

Test result: Success (61000b010148a61ae1f1abaca4432b)

Testing Decode AMBE

Test result: Success (6101420200a00001ffff00000001ffff000000000000000000000001ffff00000000000000000000ffff0000000000000000ffff0001000000000000ffff000000000001ffff0000000000000001ffff0001ffff000000000000000000000001ffff000000000000000000000001ffff0000000000000000000100000000000000010001ffff00010000000000010001000000000000000000000001ffffffff0001ffff0000ffff0000000100000001ffff0001ffff00000000ffff0001ffff0001ffff0001000000000001ffff000100000000000000000001ffffffff0000000000010000000100010000000100000000000000010000ffffffffffff0001ffff0001ffff00000001ffff0001ffff0001ffff00000000ffff000100000001000000000001000000010000000100000000ffff0000ffffffff0000ffff00000000ffff0000)

Testing Encode PCM

Test result: Success (61000b010148fb836133dbbc308bb3)

Testing Decode AMBE

Test result: Success (6101420200a000010000ffff0000ffff000000010001000100000001ffff00000001ffff00010000ffff00000000ffffffff0001ffff00010000ffff0001ffff0001000100000001ffff000000000000000100000001ffff0001ffff00000000ffff0001ffff0001000000000000ffff0001ffff0000ffff00010000ffff0001ffff0001000000000000000000000000000100000000000000000000000100010000000000000000000000000000000000000001000000000000ffff0000ffff0001000000000001ffff000000000000000000000000000000000000ffff00000000ffff000000010000ffff000000010000000000000000ffffffffffff000000000000ffff0000000000000001ffff0001000000000001ffff00000000000000000000000000000001000000010000ffff0000000000000000000000000000000100000000)

Testing Encode PCM

Test result: Success (61000b010148dba06231d9b850abb3)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff000000000000000000000000ffff0001000000000000000000010000000000000000ffff00000000ffffffff0000000000000001ffff000000000001000100000001ffff0000000000000000ffff000000000000ffffffff00000000ffff000000000000000000000000000000000001000100000000000000000000000000000001000000010000ffff0000ffff000000000000000100000000ffff0000000000000000ffff00010000ffff000000000000ffff0000000000000000000000010000000000010000000000000000000000000000000000000000000000000000000000010000ffff0000000000000001ffff000000000001000000000000ffff00000000ffff00000000000100010001ffff00000001ffff000000000000ffff00000001ffff000000000001000000000001ffff00000001ffff0000)

Testing Encode PCM

Test result: Success (61000b010148a8c327379de4f08f3b)

Testing Decode AMBE

Test result: Success (6101420200a00000000000000000ffff000100000001000000000000000000000000000000000000ffff00000000000000000000000100000001000000000000ffff0000ffff0000ffff00000000ffff0000000100010000000000000000000100000000ffff0000000000000001ffff000000000000000000000000ffff000000000000000000000001000000000000ffff00000000ffff000000000000000000000000000000010001000000010000000100000000000000000000ffff0000ffff0000000000000001ffff000100000001000100000000ffff00000000000000000000ffff00000000ffff000000010000000100000000ffffffff0000000000000001ffff0000ffff00000001000000010000000000000000000000000001000000010000ffff000000000000ffff000000000001000000000001ffff0000000100000000)

Testing Encode PCM

Test result: Success (61000b010148bbc20517bfd0b0cb2f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000000000000ffff0001000000010000ffffffffffff000000010000ffffffff0000ffff0000000000000001000000000000000000000001000000010000000000000000000000000000ffff00000000000000000000000100000000000100000000ffff000000010000ffff00010000ffff0001ffff00000000000000000001ffffffff00000000000000010000000000000000ffff000000000000000000000001000000000000ffff0000000000000000ffff0001000000000000ffff00010001ffff0001000100000000ffff0000000000000000000000000000000100000000000000000000000000000000000000010000ffff0000ffff00010000ffff000000000000000100010000000000000001000000000000000000000000ffff000000000000000000000000000000000001ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014888f125379cd5d0ab6f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000100000001ffff000100000000000000000001ffff00000000ffff000100000000ffffffff0001ffff0000000000000000000000000000000000000000000100010000ffff00000000000000000000ffff000000010000ffff00000000ffff000000000001ffff00000000ffff000000000000000000000000000000010000000000000000000000000001000000000000000000000000ffff000000000000000100000000000100000001ffff0000000000000000ffff0000ffffffff00000000000000000001000000010000ffff00000000000000000000ffff00000000000000000000000000000000ffffffff0000ffff0000000000000001000000000001000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000010000ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014899e025359fe0b08f2b)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000ffff00000000ffffffff00000000000000010000ffff00010000ffff0000000000000000000100000000000100010000ffff000000000000000100000000ffff000000000000ffff00000000ffff00010000ffff0000000000000000000000000001ffff0000000000000000ffff00010001000000000000000000000001000000000000000000000000ffff00000000ffff0000000000010001ffff00000000ffff00000001ffffffff000000000000ffff0000000100000001000000000000ffff000100000000000000010001000000010000000000000000ffff0000000000000000000000000000000100000000ffff000000000000000100000001000000000000ffff00000000000000000000ffff000000000000000100010000ffff0001ffff0000000000000000000000000000ffff000000000000)

Testing Encode PCM

Test result: Success (61000b010148b543ad63cdd4a8033f)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff0001000000000000ffff0000000000010001ffff000000000000000000010000000100000000000100000000ffff00000001ffff0001000000000001ffff00000000000000000000000000010001000000000000000000000000000000000000000000000000ffffffff0000000000000000000000000000000000010000ffff00000001000000010000ffffffffffff0000ffff0000000100000000ffff0001000000000000000000000000ffff00000001000000000000000000000000000000000000000000000000ffff00000001ffff00000000000000000000000000000001000100000000ffff000000000001ffffffff0001ffff0000ffff000000010000000100010000000000000000000100010001000000000000000000000000000000010000ffff000000000000000000000000ffff00010000ffff)

Testing Encode PCM

Test result: Success (61000b01014886528d21a9f0fc032f)

root@DMRLink:/home/test/DV3000/Analog_Bridge#



Re: AMBEtest4.py

Steve Siesel [K4KSA]
 

The power supply on the RPi3 is 5V 3A…..

Should I grab (git) the HB product next? Is that in the N4IRS Repository?

 

 

From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Saturday, June 24, 2017 4:35 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] AMBEtest4.py

 

Well,
At least it did not fail. As I said in the post, if it fails you have no chance. If it passes, you have a shot. It's worth a try.
So far I can cause a failure if I use a lower current power supply. With a 5V 1.35A PS powering a RPi2 I can get AMBEtest4 to fail. It's repeatable. I am going to bring up DIAL RC1 Analog_Bridge and HB_Bridge. The plan it to continue to expand the testing to try to find what is causing the failures. We want to get to a point where if the confidence test passes, Analog_Audio will work, every time. 

On 06/24/2017 04:25 PM, Steve Siesel [K4KSA] wrote:

Steve,

 

Here is my results of a DV3000u in a RPi 3!

 

Thoughts?

Steve

K4KSA

 

 

root@DMRLink:/home/test/DV3000/Analog_Bridge# python AMBEtest4.py -n -s /dev/ttyUSB0

Setting serial port

Serial port parameters:

Port name:      /dev/ttyUSB0

Baudrate:       460800

Byte size:      8

Parity:         N

Stop bits:      1

Xon Xoff:       False

RTS/CTS:        False

DST/DTR:        False

*********************

Testing Reset DV3000

Test result: Success (6100010039)

Testing Get Product ID

Test result: Success (61000b0030414d4245333030305200)

Testing Get Version

Test result: Success (6100310031563132302e453130302e585858582e433130362e473531342e523030392e42303031303431312e433030323032303800)

Testing Set DSTAR Mode

Test result: Success (610002000a00)

Testing Reset DV3000

Test result: Success (6100010039)

Testing Set DMR Mode

Test result: Success (610002000a00)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ffff0001ffff000100000000000000000000ffff00000000000000000000000100000001000000000000ffff000000000000000000000001000000000000ffffffff000000000000000000000000000000000000000000000001000000000000ffff000000000001000000000000ffff00010001000000010000ffff00000000000000000000000000010000ffff0000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000ffff00010000ffff000000010000)

Testing Encode PCM

Test result: Success (61000b010148954be6500310b00777)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0001000000000001000000010000000000010000ffff0000ffff000000000000000000000000ffff00000000000000000000ffff00000000ffff0000000000000001000000010000ffff0001000000000000000000000000000000000000000100000000000000000000000000000000ffff0001ffff00000001000000010000000100000001ffffffff0000ffff0000ffff0001ffff00010000ffff0001ffff0001000000000000ffff0001ffff00000001ffff000000000000000000000000000000000000ffff0000ffff000100000000000100000001ffff0000000000000000ffff000000010000000000000000000100000000000000000000ffff000100000001000000000000ffff0000ffff00000000ffff0001ffff0000000000000001ffff0000000000000001ffff00000000ffff00000000000000000000)

Testing Encode PCM

Test result: Success (61000b010148a61ae1f1abaca4432b)

Testing Decode AMBE

Test result: Success (6101420200a00001ffff00000001ffff000000000000000000000001ffff00000000000000000000ffff0000000000000000ffff0001000000000000ffff000000000001ffff0000000000000001ffff0001ffff000000000000000000000001ffff000000000000000000000001ffff0000000000000000000100000000000000010001ffff00010000000000010001000000000000000000000001ffffffff0001ffff0000ffff0000000100000001ffff0001ffff00000000ffff0001ffff0001ffff0001000000000001ffff000100000000000000000001ffffffff0000000000010000000100010000000100000000000000010000ffffffffffff0001ffff0001ffff00000001ffff0001ffff0001ffff00000000ffff000100000001000000000001000000010000000100000000ffff0000ffffffff0000ffff00000000ffff0000)

Testing Encode PCM

Test result: Success (61000b010148fb836133dbbc308bb3)

Testing Decode AMBE

Test result: Success (6101420200a000010000ffff0000ffff000000010001000100000001ffff00000001ffff00010000ffff00000000ffffffff0001ffff00010000ffff0001ffff0001000100000001ffff000000000000000100000001ffff0001ffff00000000ffff0001ffff0001000000000000ffff0001ffff0000ffff00010000ffff0001ffff0001000000000000000000000000000100000000000000000000000100010000000000000000000000000000000000000001000000000000ffff0000ffff0001000000000001ffff000000000000000000000000000000000000ffff00000000ffff000000010000ffff000000010000000000000000ffffffffffff000000000000ffff0000000000000001ffff0001000000000001ffff00000000000000000000000000000001000000010000ffff0000000000000000000000000000000100000000)

Testing Encode PCM

Test result: Success (61000b010148dba06231d9b850abb3)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff000000000000000000000000ffff0001000000000000000000010000000000000000ffff00000000ffffffff0000000000000001ffff000000000001000100000001ffff0000000000000000ffff000000000000ffffffff00000000ffff000000000000000000000000000000000001000100000000000000000000000000000001000000010000ffff0000ffff000000000000000100000000ffff0000000000000000ffff00010000ffff000000000000ffff0000000000000000000000010000000000010000000000000000000000000000000000000000000000000000000000010000ffff0000000000000001ffff000000000001000000000000ffff00000000ffff00000000000100010001ffff00000001ffff000000000000ffff00000001ffff000000000001000000000001ffff00000001ffff0000)

Testing Encode PCM

Test result: Success (61000b010148a8c327379de4f08f3b)

Testing Decode AMBE

Test result: Success (6101420200a00000000000000000ffff000100000001000000000000000000000000000000000000ffff00000000000000000000000100000001000000000000ffff0000ffff0000ffff00000000ffff0000000100010000000000000000000100000000ffff0000000000000001ffff000000000000000000000000ffff000000000000000000000001000000000000ffff00000000ffff000000000000000000000000000000010001000000010000000100000000000000000000ffff0000ffff0000000000000001ffff000100000001000100000000ffff00000000000000000000ffff00000000ffff000000010000000100000000ffffffff0000000000000001ffff0000ffff00000001000000010000000000000000000000000001000000010000ffff000000000000ffff000000000001000000000001ffff0000000100000000)

Testing Encode PCM

Test result: Success (61000b010148bbc20517bfd0b0cb2f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000000000000ffff0001000000010000ffffffffffff000000010000ffffffff0000ffff0000000000000001000000000000000000000001000000010000000000000000000000000000ffff00000000000000000000000100000000000100000000ffff000000010000ffff00010000ffff0001ffff00000000000000000001ffffffff00000000000000010000000000000000ffff000000000000000000000001000000000000ffff0000000000000000ffff0001000000000000ffff00010001ffff0001000100000000ffff0000000000000000000000000000000100000000000000000000000000000000000000010000ffff0000ffff00010000ffff000000000000000100010000000000000001000000000000000000000000ffff000000000000000000000000000000000001ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014888f125379cd5d0ab6f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000100000001ffff000100000000000000000001ffff00000000ffff000100000000ffffffff0001ffff0000000000000000000000000000000000000000000100010000ffff00000000000000000000ffff000000010000ffff00000000ffff000000000001ffff00000000ffff000000000000000000000000000000010000000000000000000000000001000000000000000000000000ffff000000000000000100000000000100000001ffff0000000000000000ffff0000ffffffff00000000000000000001000000010000ffff00000000000000000000ffff00000000000000000000000000000000ffffffff0000ffff0000000000000001000000000001000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000010000ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014899e025359fe0b08f2b)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000ffff00000000ffffffff00000000000000010000ffff00010000ffff0000000000000000000100000000000100010000ffff000000000000000100000000ffff000000000000ffff00000000ffff00010000ffff0000000000000000000000000001ffff0000000000000000ffff00010001000000000000000000000001000000000000000000000000ffff00000000ffff0000000000010001ffff00000000ffff00000001ffffffff000000000000ffff0000000100000001000000000000ffff000100000000000000010001000000010000000000000000ffff0000000000000000000000000000000100000000ffff000000000000000100000001000000000000ffff00000000000000000000ffff000000000000000100010000ffff0001ffff0000000000000000000000000000ffff000000000000)

Testing Encode PCM

Test result: Success (61000b010148b543ad63cdd4a8033f)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff0001000000000000ffff0000000000010001ffff000000000000000000010000000100000000000100000000ffff00000001ffff0001000000000001ffff00000000000000000000000000010001000000000000000000000000000000000000000000000000ffffffff0000000000000000000000000000000000010000ffff00000001000000010000ffffffffffff0000ffff0000000100000000ffff0001000000000000000000000000ffff00000001000000000000000000000000000000000000000000000000ffff00000001ffff00000000000000000000000000000001000100000000ffff000000000001ffffffff0001ffff0000ffff000000010000000100010000000000000000000100010001000000000000000000000000000000010000ffff000000000000000000000000ffff00010000ffff)

Testing Encode PCM

Test result: Success (61000b01014886528d21a9f0fc032f)

root@DMRLink:/home/test/DV3000/Analog_Bridge#

 


Re: AMBEtest4.py

Steve N4IRS
 

On 06/24/2017 04:39 PM, Steve Siesel [K4KSA] wrote:

The power supply on the RPi3 is 5V 3A…..

Should I grab (git) the HB product next? Is that in the N4IRS Repository?

 

 

From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Saturday, June 24, 2017 4:35 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] AMBEtest4.py

 

Well,
At least it did not fail. As I said in the post, if it fails you have no chance. If it passes, you have a shot. It's worth a try.
So far I can cause a failure if I use a lower current power supply. With a 5V 1.35A PS powering a RPi2 I can get AMBEtest4 to fail. It's repeatable. I am going to bring up DIAL RC1 Analog_Bridge and HB_Bridge. The plan it to continue to expand the testing to try to find what is causing the failures. We want to get to a point where if the confidence test passes, Analog_Audio will work, every time. 

On 06/24/2017 04:25 PM, Steve Siesel [K4KSA] wrote:

Steve,

 

Here is my results of a DV3000u in a RPi 3!

 

Thoughts?

Steve

K4KSA

 

 

root@DMRLink:/home/test/DV3000/Analog_Bridge# python AMBEtest4.py -n -s /dev/ttyUSB0

Setting serial port

Serial port parameters:

Port name:      /dev/ttyUSB0

Baudrate:       460800

Byte size:      8

Parity:         N

Stop bits:      1

Xon Xoff:       False

RTS/CTS:        False

DST/DTR:        False

*********************

Testing Reset DV3000

Test result: Success (6100010039)

Testing Get Product ID

Test result: Success (61000b0030414d4245333030305200)

Testing Get Version

Test result: Success (6100310031563132302e453130302e585858582e433130362e473531342e523030392e42303031303431312e433030323032303800)

Testing Set DSTAR Mode

Test result: Success (610002000a00)

Testing Reset DV3000

Test result: Success (6100010039)

Testing Set DMR Mode

Test result: Success (610002000a00)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ffff0001ffff000100000000000000000000ffff00000000000000000000000100000001000000000000ffff000000000000000000000001000000000000ffffffff000000000000000000000000000000000000000000000001000000000000ffff000000000001000000000000ffff00010001000000010000ffff00000000000000000000000000010000ffff0000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000ffff00010000ffff000000010000)

Testing Encode PCM

Test result: Success (61000b010148954be6500310b00777)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0001000000000001000000010000000000010000ffff0000ffff000000000000000000000000ffff00000000000000000000ffff00000000ffff0000000000000001000000010000ffff0001000000000000000000000000000000000000000100000000000000000000000000000000ffff0001ffff00000001000000010000000100000001ffffffff0000ffff0000ffff0001ffff00010000ffff0001ffff0001000000000000ffff0001ffff00000001ffff000000000000000000000000000000000000ffff0000ffff000100000000000100000001ffff0000000000000000ffff000000010000000000000000000100000000000000000000ffff000100000001000000000000ffff0000ffff00000000ffff0001ffff0000000000000001ffff0000000000000001ffff00000000ffff00000000000000000000)

Testing Encode PCM

Test result: Success (61000b010148a61ae1f1abaca4432b)

Testing Decode AMBE

Test result: Success (6101420200a00001ffff00000001ffff000000000000000000000001ffff00000000000000000000ffff0000000000000000ffff0001000000000000ffff000000000001ffff0000000000000001ffff0001ffff000000000000000000000001ffff000000000000000000000001ffff0000000000000000000100000000000000010001ffff00010000000000010001000000000000000000000001ffffffff0001ffff0000ffff0000000100000001ffff0001ffff00000000ffff0001ffff0001ffff0001000000000001ffff000100000000000000000001ffffffff0000000000010000000100010000000100000000000000010000ffffffffffff0001ffff0001ffff00000001ffff0001ffff0001ffff00000000ffff000100000001000000000001000000010000000100000000ffff0000ffffffff0000ffff00000000ffff0000)

Testing Encode PCM

Test result: Success (61000b010148fb836133dbbc308bb3)

Testing Decode AMBE

Test result: Success (6101420200a000010000ffff0000ffff000000010001000100000001ffff00000001ffff00010000ffff00000000ffffffff0001ffff00010000ffff0001ffff0001000100000001ffff000000000000000100000001ffff0001ffff00000000ffff0001ffff0001000000000000ffff0001ffff0000ffff00010000ffff0001ffff0001000000000000000000000000000100000000000000000000000100010000000000000000000000000000000000000001000000000000ffff0000ffff0001000000000001ffff000000000000000000000000000000000000ffff00000000ffff000000010000ffff000000010000000000000000ffffffffffff000000000000ffff0000000000000001ffff0001000000000001ffff00000000000000000000000000000001000000010000ffff0000000000000000000000000000000100000000)

Testing Encode PCM

Test result: Success (61000b010148dba06231d9b850abb3)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff000000000000000000000000ffff0001000000000000000000010000000000000000ffff00000000ffffffff0000000000000001ffff000000000001000100000001ffff0000000000000000ffff000000000000ffffffff00000000ffff000000000000000000000000000000000001000100000000000000000000000000000001000000010000ffff0000ffff000000000000000100000000ffff0000000000000000ffff00010000ffff000000000000ffff0000000000000000000000010000000000010000000000000000000000000000000000000000000000000000000000010000ffff0000000000000001ffff000000000001000000000000ffff00000000ffff00000000000100010001ffff00000001ffff000000000000ffff00000001ffff000000000001000000000001ffff00000001ffff0000)

Testing Encode PCM

Test result: Success (61000b010148a8c327379de4f08f3b)

Testing Decode AMBE

Test result: Success (6101420200a00000000000000000ffff000100000001000000000000000000000000000000000000ffff00000000000000000000000100000001000000000000ffff0000ffff0000ffff00000000ffff0000000100010000000000000000000100000000ffff0000000000000001ffff000000000000000000000000ffff000000000000000000000001000000000000ffff00000000ffff000000000000000000000000000000010001000000010000000100000000000000000000ffff0000ffff0000000000000001ffff000100000001000100000000ffff00000000000000000000ffff00000000ffff000000010000000100000000ffffffff0000000000000001ffff0000ffff00000001000000010000000000000000000000000001000000010000ffff000000000000ffff000000000001000000000001ffff0000000100000000)

Testing Encode PCM

Test result: Success (61000b010148bbc20517bfd0b0cb2f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000000000000ffff0001000000010000ffffffffffff000000010000ffffffff0000ffff0000000000000001000000000000000000000001000000010000000000000000000000000000ffff00000000000000000000000100000000000100000000ffff000000010000ffff00010000ffff0001ffff00000000000000000001ffffffff00000000000000010000000000000000ffff000000000000000000000001000000000000ffff0000000000000000ffff0001000000000000ffff00010001ffff0001000100000000ffff0000000000000000000000000000000100000000000000000000000000000000000000010000ffff0000ffff00010000ffff000000000000000100010000000000000001000000000000000000000000ffff000000000000000000000000000000000001ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014888f125379cd5d0ab6f)

Testing Decode AMBE

Test result: Success (6101420200a0ffff0000000100000001ffff000100000000000000000001ffff00000000ffff000100000000ffffffff0001ffff0000000000000000000000000000000000000000000100010000ffff00000000000000000000ffff000000010000ffff00000000ffff000000000001ffff00000000ffff000000000000000000000000000000010000000000000000000000000001000000000000000000000000ffff000000000000000100000000000100000001ffff0000000000000000ffff0000ffffffff00000000000000000001000000010000ffff00000000000000000000ffff00000000000000000000000000000000ffffffff0000ffff0000000000000001000000000001000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000010000ffff00000000ffff0001)

Testing Encode PCM

Test result: Success (61000b01014899e025359fe0b08f2b)

Testing Decode AMBE

Test result: Success (6101420200a0000000000000ffff00000000ffffffff00000000000000010000ffff00010000ffff0000000000000000000100000000000100010000ffff000000000000000100000000ffff000000000000ffff00000000ffff00010000ffff0000000000000000000000000001ffff0000000000000000ffff00010001000000000000000000000001000000000000000000000000ffff00000000ffff0000000000010001ffff00000000ffff00000001ffffffff000000000000ffff0000000100000001000000000000ffff000100000000000000010001000000010000000000000000ffff0000000000000000000000000000000100000000ffff000000000000000100000001000000000000ffff00000000000000000000ffff000000000000000100010000ffff0001ffff0000000000000000000000000000ffff000000000000)

Testing Encode PCM

Test result: Success (61000b010148b543ad63cdd4a8033f)

Testing Decode AMBE

Test result: Success (6101420200a00000ffff0001000000000000ffff0000000000010001ffff000000000000000000010000000100000000000100000000ffff00000001ffff0001000000000001ffff00000000000000000000000000010001000000000000000000000000000000000000000000000000ffffffff0000000000000000000000000000000000010000ffff00000001000000010000ffffffffffff0000ffff0000000100000000ffff0001000000000000000000000000ffff00000001000000000000000000000000000000000000000000000000ffff00000001ffff00000000000000000000000000000001000100000000ffff000000000001ffffffff0001ffff0000ffff000000010000000100010000000000000000000100010001000000000000000000000000000000010000ffff000000000000000000000000ffff00010000ffff)

Testing Encode PCM

Test result: Success (61000b01014886528d21a9f0fc032f)

root@DMRLink:/home/test/DV3000/Analog_Bridge#

 


161 - 180 of 9820