I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem. Here is the problem. -When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR. This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally. I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of. Does anyone have any suggestions on how I should start troubleshooting this? -- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
Is everybody connected to the same master? On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Yes, DMRlink, which my two repeaters are on are 3101. DMRGateway is also on 3101. My test subject on the Open Spot is also on 3101. On Wed, Apr 5, 2017 at 2:21 PM, Steve Zingman <szingman@msgstor.com> wrote:
Is everybody connected to the same master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
Further add DMRlink is ID 312307, DMRGateway is 312318. My friend helping my is 3123289. All just verified on 3101. On Wed, Apr 5, 2017 at 2:25 PM, Robert Newberry <N1XBM@amsat.org> wrote:
Yes, DMRlink, which my two repeaters are on are 3101. DMRGateway is also on 3101. My test subject on the Open Spot is also on 3101.
On Wed, Apr 5, 2017 at 2:21 PM, Steve Zingman <szingman@msgstor.com> wrote:
Is everybody connected to the same master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master? On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked" -Yes I am Peered to BM. - Yes my repeaters each have their own Masters withing DMRlink. -No AMBE_AUDIO is peered directly to BM. On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ???? On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Steve, I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you. On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
2 Masters, 1 Peer. Repeater1 connected to Master1 Repeater2 connected to Master2 Peer connected to BM ambe_audio connected to BM So, signal to and from ambe_audio do not get to R1 and R2 signal to and from ambe_audio DO get to BM and beyond signal to and from R1 and R2 DO get to BM and beyond Common point of failure, R1, R2 and ambe_audio all connect to BM Signals not passing through BM? Why can't 2 SmartPTT connections on the same BM Master talk to each other?
It appears you've summed my problem up. This configuration has worked for me and if I had to guess It stopped working about a 1-2 weeks ago. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
The last time we ran a bm upgrade was Friday. Sent from my iPhone
On Apr 5, 2017, at 4:16 PM, Robert Newberry <N1XBM@amsat.org> wrote:
It appears you've summed my problem up. This configuration has worked for me and if I had to guess It stopped working about a 1-2 weeks ago.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun! 73, Steve N4IRS On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture! N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
How do you think we feel, trying to understand you network before I can even begin to troubleshoot. On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell. Steve On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for me. Should I try and install to test it or hold off. David On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell.
Steve
On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
You could try following the draft document. Also pay attention to below. I was having the same problem as you, since I own a first generation ThumbDV which runs at 230400 bauds. When I removed the –n argument in the command: python AMBEtest3.py -n -s /dev/ttyUSB0, it then worked for me. So for people with first generation ThumbDV’s, the command python AMBEtest3.py -s /dev/ttyUSB0 must be used. Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini UNLESS your DV is not at /dev/ttyUSB0 If you run a first gen ThumbDV, the baud rate must be changed in it also to 230400. And for Steve: thank you very much for all the efforts in the software and the documents. I went thru it all, and except for the items mentionned up here, everything went well and I’m ready for the next steps. Thanks and 73s from Guy VE2VAG On 4/6/2017 11:56 AM, David KE6UPI wrote:
Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for me. Should I try and install to test it or hold off.
David
On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell.
Steve
On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
No Go pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -n -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False Reset 6100010033 Wrote: 5 bytes Product ID 6100010030 Wrote: 5 bytes Version 6100010031 Wrote: 5 bytes Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes ----------------------------------------------------------------------- On Thu, Apr 6, 2017 at 9:04 AM, Steve Zingman <szingman@msgstor.com> wrote:
You could try following the draft document. Also pay attention to below.
I was having the same problem as you, since I own a first generation ThumbDV which runs at 230400 bauds. When I removed the –n argument in the command: python AMBEtest3.py -n -s /dev/ttyUSB0, it then worked for me.
So for people with first generation ThumbDV’s, the command python AMBEtest3.py -s /dev/ttyUSB0 must be used.
Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini UNLESS your DV is not at /dev/ttyUSB0 If you run a first gen ThumbDV, the baud rate must be changed in it also to 230400.
And for Steve: thank you very much for all the efforts in the software and the documents. I went thru it all, and except for the items mentionned up here, everything went well and I’m ready for the next steps.
Thanks and 73s from Guy VE2VAG
On 4/6/2017 11:56 AM, David KE6UPI wrote:
Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for me. Should I try and install to test it or hold off.
David
On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell.
Steve
On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote:
I've encountered a strange problem on my existing system that has been working for over a year without problem. I have not recently updated the software nor have I made any changes. The day I noticed it stopped working correctly I probably haven't even logged into it for weeks. I did all of the simple stuff like rebooting/ removing power to repeaters, routers, RPI's still hasn't fixed the problem.
Here is the problem.
-When I TX on my local DMR repeater it is heard on BM by my test subject on an open spot, but the audio is not being heard on Allstar -When I TX on Allstar it goes up to BM and is heard by my test subject on his open spot, but the audio does not repeat on my local DMR repeater. -When my test subject TX's on his open spot I hear it on Allstar and DMR.
This never used to work this way, If I TX'd on my DMR repeater it was heard on Allstar, and in the opposite if I TX'd on Allstar it would be heard on my DMR repeater locally.
I hope that I formulated my question in a way that makes sense. I am unsure how to trouble shoot this because it appears that DMRGateway works in both directions...sort of.
Does anyone have any suggestions on how I should start troubleshooting this?
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Did you try without the -n? Are you on release candidate? On 4/6/2017 12:37 PM, David KE6UPI wrote:
No Go
pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -n -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False
Reset 6100010033 Wrote: 5 bytes
Product ID 6100010030 Wrote: 5 bytes
Version 6100010031 Wrote: 5 bytes
Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes
-----------------------------------------------------------------------
On Thu, Apr 6, 2017 at 9:04 AM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
You could try following the draft document. Also pay attention to below.
I was having the same problem as you, since I own a first generation ThumbDV which runs at 230400 bauds. When I removed the –n argument in the command: python AMBEtest3.py -n -s /dev/ttyUSB0, it then worked for me.
So for people with first generation ThumbDV’s, the command python AMBEtest3.py -s /dev/ttyUSB0 must be used.
Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini UNLESS your DV is not at /dev/ttyUSB0 If you run a first gen ThumbDV, the baud rate must be changed in it also to 230400.
And for Steve: thank you very much for all the efforts in the software and the documents. I went thru it all, and except for the items mentionned up here, everything went well and I’m ready for the next steps.
Thanks and 73s from Guy VE2VAG
On 4/6/2017 11:56 AM, David KE6UPI wrote:
Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for me. Should I try and install to test it or hold off.
David
On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell.
Steve
On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
I know you are running a bridge. Can I assume 1 Master and 1 Peer? The Peer is connected to BM? Your Repeaters connect to the Master? The dmrlink / ambe_audio is connected to the Master?
On 4/5/2017 2:18 PM, Robert Newberry wrote: > I've encountered a strange problem on my > existing system that has been working > for over a year without problem. I have > not recently updated the software nor > have I made any changes. The day I > noticed it stopped working correctly I > probably haven't even logged into it for > weeks. I did all of the simple stuff > like rebooting/ removing power to > repeaters, routers, RPI's still hasn't > fixed the problem. > > Here is the problem. > > -When I TX on my local DMR repeater it > is heard on BM by my test subject on an > open spot, but the audio is not being > heard on Allstar > -When I TX on Allstar it goes up to BM > and is heard by my test subject on his > open spot, but the audio does not repeat > on my local DMR repeater. > -When my test subject TX's on his open > spot I hear it on Allstar and DMR. > > This never used to work this way, If I > TX'd on my DMR repeater it was heard on > Allstar, and in the opposite if I TX'd > on Allstar it would be heard on my DMR > repeater locally. > > I hope that I formulated my question in > a way that makes sense. I am unsure how > to trouble shoot this because it appears > that DMRGateway works in both > directions...sort of. > > Does anyone have any suggestions on how > I should start troubleshooting this? > > > -- > N1XBM > Apparare Scientor > Paratus Communicare > Allstar Node # 27086, 41540, 41812, > 42086, 42658, 42657 > www.radioguysrepeaternetwork.com > <http://www.radioguysrepeaternetwork.com> > > > _______________________________________________ > Allstar-Digital mailing list > Allstar-Digital@lists.keekles.org > <mailto:Allstar-Digital@lists.keekles.org> > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital> _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
AMBEtest3.py without -n: pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False Reset 6100010033 Wrote: 5 bytes Product ID 6100010030 Wrote: 5 bytes Version 6100010031 Wrote: 5 bytes Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes FTDI Driver: pi@dmrlink:/srv/DMRGateway/DV3000 $ less /proc/modules | grep ftdi ftdi_sio 31072 0 - Live 0x7f11c000 usbserial 22526 1 ftdi_sio, Live 0x7f10f000 Image: RAT_RC1 On Thu, Apr 6, 2017 at 9:38 AM, Steve Zingman <szingman@msgstor.com> wrote:
Did you try without the -n? Are you on release candidate?
On 4/6/2017 12:37 PM, David KE6UPI wrote:
No Go
pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -n -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False
Reset 6100010033 Wrote: 5 bytes
Product ID 6100010030 Wrote: 5 bytes
Version 6100010031 Wrote: 5 bytes
Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes
-----------------------------------------------------------------------
On Thu, Apr 6, 2017 at 9:04 AM, Steve Zingman <szingman@msgstor.com> wrote:
You could try following the draft document. Also pay attention to below.
I was having the same problem as you, since I own a first generation ThumbDV which runs at 230400 bauds. When I removed the –n argument in the command: python AMBEtest3.py -n -s /dev/ttyUSB0, it then worked for me.
So for people with first generation ThumbDV’s, the command python AMBEtest3.py -s /dev/ttyUSB0 must be used.
Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini UNLESS your DV is not at /dev/ttyUSB0 If you run a first gen ThumbDV, the baud rate must be changed in it also to 230400.
And for Steve: thank you very much for all the efforts in the software and the documents. I went thru it all, and except for the items mentionned up here, everything went well and I’m ready for the next steps.
Thanks and 73s from Guy VE2VAG
On 4/6/2017 11:56 AM, David KE6UPI wrote:
Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for me. Should I try and install to test it or hold off.
David
On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell.
Steve
On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote:
-No Actually 2 masters then each repeater is peered to one master. I had to do this because of NAT hairpining. I then have the Masters talking to each others to have both repeaters "linked"
-Yes I am Peered to BM.
- Yes my repeaters each have their own Masters withing DMRlink.
-No AMBE_AUDIO is peered directly to BM.
On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com> wrote:
> I know you are running a bridge. Can I assume 1 Master and 1 Peer? > The Peer is connected to BM? > Your Repeaters connect to the Master? > The dmrlink / ambe_audio is connected to the Master? > > On 4/5/2017 2:18 PM, Robert Newberry wrote: > > I've encountered a strange problem on my existing system that has > been working for over a year without problem. I have not recently updated > the software nor have I made any changes. The day I noticed it stopped > working correctly I probably haven't even logged into it for weeks. I did > all of the simple stuff like rebooting/ removing power to repeaters, > routers, RPI's still hasn't fixed the problem. > > Here is the problem. > > -When I TX on my local DMR repeater it is heard on BM by my test > subject on an open spot, but the audio is not being heard on Allstar > -When I TX on Allstar it goes up to BM and is heard by my test > subject on his open spot, but the audio does not repeat on my local DMR > repeater. > -When my test subject TX's on his open spot I hear it on Allstar and > DMR. > > This never used to work this way, If I TX'd on my DMR repeater it > was heard on Allstar, and in the opposite if I TX'd on Allstar it would be > heard on my DMR repeater locally. > > I hope that I formulated my question in a way that makes sense. I am > unsure how to trouble shoot this because it appears that DMRGateway works > in both directions...sort of. > > Does anyone have any suggestions on how I should start > troubleshooting this? > > > -- > N1XBM > Apparare Scientor > Paratus Communicare > Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 > www.radioguysrepeaternetwork.com > > > _______________________________________________ > Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > > _______________________________________________ Allstar-Digital > mailing list Allstar-Digital@lists.keekles.org > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
I know your DV3000u passes a Windows test. I have seen the same issue running on Compass (Raspbian) Let me see what I can come up with. On 4/6/2017 12:45 PM, David KE6UPI wrote:
AMBEtest3.py without -n: pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False
Reset 6100010033 Wrote: 5 bytes
Product ID 6100010030 Wrote: 5 bytes
Version 6100010031 Wrote: 5 bytes
Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes
FTDI Driver: pi@dmrlink:/srv/DMRGateway/DV3000 $ less /proc/modules | grep ftdi ftdi_sio 31072 0 - Live 0x7f11c000 usbserial 22526 1 ftdi_sio, Live 0x7f10f000
Image: RAT_RC1
On Thu, Apr 6, 2017 at 9:38 AM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
Did you try without the -n? Are you on release candidate?
On 4/6/2017 12:37 PM, David KE6UPI wrote:
No Go
pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -n -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False
Reset 6100010033 Wrote: 5 bytes
Product ID 6100010030 Wrote: 5 bytes
Version 6100010031 Wrote: 5 bytes
Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes
-----------------------------------------------------------------------
On Thu, Apr 6, 2017 at 9:04 AM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
You could try following the draft document. Also pay attention to below.
I was having the same problem as you, since I own a first generation ThumbDV which runs at 230400 bauds. When I removed the –n argument in the command: python AMBEtest3.py -n -s /dev/ttyUSB0, it then worked for me.
So for people with first generation ThumbDV’s, the command python AMBEtest3.py -s /dev/ttyUSB0 must be used.
Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini UNLESS your DV is not at /dev/ttyUSB0 If you run a first gen ThumbDV, the baud rate must be changed in it also to 230400.
And for Steve: thank you very much for all the efforts in the software and the documents. I went thru it all, and except for the items mentionned up here, everything went well and I’m ready for the next steps.
Thanks and 73s from Guy VE2VAG
On 4/6/2017 11:56 AM, David KE6UPI wrote:
Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for me. Should I try and install to test it or hold off.
David
On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell.
Steve
On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
OK, So, 2 Masters, 1 Peer. Peer connected to BM? Repeater1 connected to Master1? Repeater2 connected to Master2? "2 masters then each repeater is peered to one master." ????
On 4/5/2017 3:24 PM, Robert Newberry wrote: > -No Actually 2 masters then each > repeater is peered to one master. I had > to do this because of NAT hairpining. I > then have the Masters talking to each > others to have both repeaters "linked" > > -Yes I am Peered to BM. > > - Yes my repeaters each have their own > Masters withing DMRlink. > > -No AMBE_AUDIO is peered directly to BM. > > On Wed, Apr 5, 2017 at 3:13 PM, Steve > Zingman <szingman@msgstor.com > <mailto:szingman@msgstor.com>> wrote: > > I know you are running a bridge. Can > I assume 1 Master and 1 Peer? > The Peer is connected to BM? > Your Repeaters connect to the Master? > The dmrlink / ambe_audio is > connected to the Master? > > On 4/5/2017 2:18 PM, Robert Newberry > wrote: >> I've encountered a strange problem >> on my existing system that has been >> working for over a year without >> problem. I have not recently >> updated the software nor have I >> made any changes. The day I noticed >> it stopped working correctly I >> probably haven't even logged into >> it for weeks. I did all of the >> simple stuff like rebooting/ >> removing power to repeaters, >> routers, RPI's still hasn't fixed >> the problem. >> >> Here is the problem. >> >> -When I TX on my local DMR repeater >> it is heard on BM by my test >> subject on an open spot, but the >> audio is not being heard on Allstar >> -When I TX on Allstar it goes up to >> BM and is heard by my test subject >> on his open spot, but the audio >> does not repeat on my local DMR >> repeater. >> -When my test subject TX's on his >> open spot I hear it on Allstar and DMR. >> >> This never used to work this way, >> If I TX'd on my DMR repeater it was >> heard on Allstar, and in the >> opposite if I TX'd on Allstar it >> would be heard on my DMR repeater >> locally. >> >> I hope that I formulated my >> question in a way that makes sense. >> I am unsure how to trouble shoot >> this because it appears that >> DMRGateway works in both >> directions...sort of. >> >> Does anyone have any suggestions on >> how I should start troubleshooting >> this? >> >> >> -- >> N1XBM >> Apparare Scientor >> Paratus Communicare >> Allstar Node # 27086, 41540, 41812, >> 42086, 42658, 42657 >> www.radioguysrepeaternetwork.com >> <http://www.radioguysrepeaternetwork.com> >> >> >> _______________________________________________ >> Allstar-Digital mailing list >> Allstar-Digital@lists.keekles.org >> <mailto:Allstar-Digital@lists.keekles.org> >> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital >> <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital> > _______________________________________________ > Allstar-Digital mailing list > Allstar-Digital@lists.keekles.org > <mailto:Allstar-Digital@lists.keekles.org> > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital> > > > -- > N1XBM Apparare Scientor Paratus > Communicare Allstar Node # 27086, 41540, > 41812, 42086, 42658, 42657 > www.radioguysrepeaternetwork.com > <http://www.radioguysrepeaternetwork.com> > > _______________________________________________ > Allstar-Digital mailing list > Allstar-Digital@lists.keekles.org > <mailto:Allstar-Digital@lists.keekles.org> > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital> _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Thanks Steve On Thu, Apr 6, 2017 at 11:06 AM, Steve Zingman <szingman@msgstor.com> wrote:
I know your DV3000u passes a Windows test. I have seen the same issue running on Compass (Raspbian)
Let me see what I can come up with.
On 4/6/2017 12:45 PM, David KE6UPI wrote:
AMBEtest3.py without -n: pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False
Reset 6100010033 Wrote: 5 bytes
Product ID 6100010030 Wrote: 5 bytes
Version 6100010031 Wrote: 5 bytes
Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes
FTDI Driver: pi@dmrlink:/srv/DMRGateway/DV3000 $ less /proc/modules | grep ftdi ftdi_sio 31072 0 - Live 0x7f11c000 usbserial 22526 1 ftdi_sio, Live 0x7f10f000
Image: RAT_RC1
On Thu, Apr 6, 2017 at 9:38 AM, Steve Zingman <szingman@msgstor.com> wrote:
Did you try without the -n? Are you on release candidate?
On 4/6/2017 12:37 PM, David KE6UPI wrote:
No Go
pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -n -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False
Reset 6100010033 Wrote: 5 bytes
Product ID 6100010030 Wrote: 5 bytes
Version 6100010031 Wrote: 5 bytes
Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes
-----------------------------------------------------------------------
On Thu, Apr 6, 2017 at 9:04 AM, Steve Zingman <szingman@msgstor.com> wrote:
You could try following the draft document. Also pay attention to below.
I was having the same problem as you, since I own a first generation ThumbDV which runs at 230400 bauds. When I removed the –n argument in the command: python AMBEtest3.py -n -s /dev/ttyUSB0, it then worked for me.
So for people with first generation ThumbDV’s, the command python AMBEtest3.py -s /dev/ttyUSB0 must be used.
Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini UNLESS your DV is not at /dev/ttyUSB0 If you run a first gen ThumbDV, the baud rate must be changed in it also to 230400.
And for Steve: thank you very much for all the efforts in the software and the documents. I went thru it all, and except for the items mentionned up here, everything went well and I’m ready for the next steps.
Thanks and 73s from Guy VE2VAG
On 4/6/2017 11:56 AM, David KE6UPI wrote:
Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for me. Should I try and install to test it or hold off.
David
On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell.
Steve
On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
We thing we are seeing the same issue with other DMRlink installs. As of right now, I don't know for sure where the bug is. I have my suspensions. We have moved testing from BM to a c-Bridge. The testing is with the current version of DMRlink and ambe_audio. I do not think it's in ambe_audio since I'm seeing some of the same symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is happening to existing "older" installs as well as the current version, I do not think the bug is in DMRlink. Once we complete testing on c-Bridge, I'll move back to BM with the exact same configuration and see what we get. Software is fun!
73, Steve N4IRS
On 4/5/2017 3:50 PM, Robert Newberry wrote:
Steve,
I'm not sure it will help, but I made a picture in PDF and e-mailed it direct to you.
On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com> wrote:
> OK, So, > 2 Masters, 1 Peer. > Peer connected to BM? > Repeater1 connected to Master1? > Repeater2 connected to Master2? > "2 masters then each repeater is peered to one master." ???? > > > > > On 4/5/2017 3:24 PM, Robert Newberry wrote: > > -No Actually 2 masters then each repeater is peered to one master. I > had to do this because of NAT hairpining. I then have the Masters talking > to each others to have both repeaters "linked" > > -Yes I am Peered to BM. > > - Yes my repeaters each have their own Masters withing DMRlink. > > -No AMBE_AUDIO is peered directly to BM. > > On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com> > wrote: > >> I know you are running a bridge. Can I assume 1 Master and 1 Peer? >> The Peer is connected to BM? >> Your Repeaters connect to the Master? >> The dmrlink / ambe_audio is connected to the Master? >> >> On 4/5/2017 2:18 PM, Robert Newberry wrote: >> >> I've encountered a strange problem on my existing system that has >> been working for over a year without problem. I have not recently updated >> the software nor have I made any changes. The day I noticed it stopped >> working correctly I probably haven't even logged into it for weeks. I did >> all of the simple stuff like rebooting/ removing power to repeaters, >> routers, RPI's still hasn't fixed the problem. >> >> Here is the problem. >> >> -When I TX on my local DMR repeater it is heard on BM by my test >> subject on an open spot, but the audio is not being heard on Allstar >> -When I TX on Allstar it goes up to BM and is heard by my test >> subject on his open spot, but the audio does not repeat on my local DMR >> repeater. >> -When my test subject TX's on his open spot I hear it on Allstar >> and DMR. >> >> This never used to work this way, If I TX'd on my DMR repeater it >> was heard on Allstar, and in the opposite if I TX'd on Allstar it would be >> heard on my DMR repeater locally. >> >> I hope that I formulated my question in a way that makes sense. I >> am unsure how to trouble shoot this because it appears that DMRGateway >> works in both directions...sort of. >> >> Does anyone have any suggestions on how I should start >> troubleshooting this? >> >> >> -- >> N1XBM >> Apparare Scientor >> Paratus Communicare >> Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 >> www.radioguysrepeaternetwork.com >> >> >> _______________________________________________ >> Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital >> >> _______________________________________________ Allstar-Digital >> mailing list Allstar-Digital@lists.keekles.org >> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > > -- > N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, > 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com > > _______________________________________________ > Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > > _______________________________________________ Allstar-Digital > mailing list Allstar-Digital@lists.keekles.org > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Problems on my end have been fixed. Thanks to everyone on the admin team who helped N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com On Apr 6, 2017 2:17 PM, "David KE6UPI" <dshaw@ke6upi.com> wrote:
Thanks Steve
On Thu, Apr 6, 2017 at 11:06 AM, Steve Zingman <szingman@msgstor.com> wrote:
I know your DV3000u passes a Windows test. I have seen the same issue running on Compass (Raspbian)
Let me see what I can come up with.
On 4/6/2017 12:45 PM, David KE6UPI wrote:
AMBEtest3.py without -n: pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False
Reset 6100010033 Wrote: 5 bytes
Product ID 6100010030 Wrote: 5 bytes
Version 6100010031 Wrote: 5 bytes
Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes
FTDI Driver: pi@dmrlink:/srv/DMRGateway/DV3000 $ less /proc/modules | grep ftdi ftdi_sio 31072 0 - Live 0x7f11c000 usbserial 22526 1 ftdi_sio, Live 0x7f10f000
Image: RAT_RC1
On Thu, Apr 6, 2017 at 9:38 AM, Steve Zingman <szingman@msgstor.com> wrote:
Did you try without the -n? Are you on release candidate?
On 4/6/2017 12:37 PM, David KE6UPI wrote:
No Go
pi@dmrlink:/srv/DMRGateway/DV3000 $ python AMBEtest3.py -n -s /dev/ttyUSB0 Setting ... /dev/ttyUSB0 d 8 N 1 False False False
Reset 6100010033 Wrote: 5 bytes
Product ID 6100010030 Wrote: 5 bytes
Version 6100010031 Wrote: 5 bytes
Set DSTAR Mode 61000c000a013007634000000000000048 Wrote: 17 bytes
-----------------------------------------------------------------------
On Thu, Apr 6, 2017 at 9:04 AM, Steve Zingman <szingman@msgstor.com> wrote:
You could try following the draft document. Also pay attention to below.
I was having the same problem as you, since I own a first generation ThumbDV which runs at 230400 bauds. When I removed the –n argument in the command: python AMBEtest3.py -n -s /dev/ttyUSB0, it then worked for me.
So for people with first generation ThumbDV’s, the command python AMBEtest3.py -s /dev/ttyUSB0 must be used.
Also, on page 3, Steve says at point 8: DO NOT edit DMRGateway.ini UNLESS your DV is not at /dev/ttyUSB0 If you run a first gen ThumbDV, the baud rate must be changed in it also to 230400.
And for Steve: thank you very much for all the efforts in the software and the documents. I went thru it all, and except for the items mentionned up here, everything went well and I’m ready for the next steps.
Thanks and 73s from Guy VE2VAG
On 4/6/2017 11:56 AM, David KE6UPI wrote:
Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for me. Should I try and install to test it or hold off.
David
On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman@msgstor.com> wrote:
OK, So Mike and I had a QSO from ASL <---> DMR Working in both directions without errors. This is on the current version of DMRlink and updated ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM on TS2 TG 3167. I'm going to do some looking at logs. After that I'm going to move to a BM Master. That will be the ONLY change I'll make. If that works, The next step will be to add a second DMRLink connection to BM. Time will tell.
Steve
On 4/6/2017 8:48 AM, Robert Newberry wrote:
I didn't mind drawing a picture it was in my mind the easiest way to show my network...haha.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
How do you think we feel, trying to understand you network before I can even begin to troubleshoot.
On 4/6/2017 8:39 AM, Robert Newberry wrote:
Wow, Steve and Mike I sure appreciate (and others I assume) your efforts. I was surely confused. It took me two days to fully wrap my arms around the issue to be able to formulate a semi coherent question and even then I still had to draw a picture!
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman@msgstor.com> wrote:
> We thing we are seeing the same issue with other DMRlink installs. > As of right now, I don't know for sure where the bug is. I have my > suspensions. We have moved testing from BM to a c-Bridge. The testing is > with the current version of DMRlink and ambe_audio. > I do not think it's in ambe_audio since I'm seeing some of the same > symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is > happening to existing "older" installs as well as the current version, I do > not think the bug is in DMRlink. > Once we complete testing on c-Bridge, I'll move back to BM with the > exact same configuration and see what we get. Software is fun! > > 73, Steve N4IRS > > On 4/5/2017 3:50 PM, Robert Newberry wrote: > > Steve, > > I'm not sure it will help, but I made a picture in PDF and e-mailed > it direct to you. > > On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman@msgstor.com> > wrote: > >> OK, So, >> 2 Masters, 1 Peer. >> Peer connected to BM? >> Repeater1 connected to Master1? >> Repeater2 connected to Master2? >> "2 masters then each repeater is peered to one master." ???? >> >> >> >> >> On 4/5/2017 3:24 PM, Robert Newberry wrote: >> >> -No Actually 2 masters then each repeater is peered to one master. >> I had to do this because of NAT hairpining. I then have the Masters talking >> to each others to have both repeaters "linked" >> >> -Yes I am Peered to BM. >> >> - Yes my repeaters each have their own Masters withing DMRlink. >> >> -No AMBE_AUDIO is peered directly to BM. >> >> On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman@msgstor.com >> > wrote: >> >>> I know you are running a bridge. Can I assume 1 Master and 1 Peer? >>> The Peer is connected to BM? >>> Your Repeaters connect to the Master? >>> The dmrlink / ambe_audio is connected to the Master? >>> >>> On 4/5/2017 2:18 PM, Robert Newberry wrote: >>> >>> I've encountered a strange problem on my existing system that has >>> been working for over a year without problem. I have not recently updated >>> the software nor have I made any changes. The day I noticed it stopped >>> working correctly I probably haven't even logged into it for weeks. I did >>> all of the simple stuff like rebooting/ removing power to repeaters, >>> routers, RPI's still hasn't fixed the problem. >>> >>> Here is the problem. >>> >>> -When I TX on my local DMR repeater it is heard on BM by my test >>> subject on an open spot, but the audio is not being heard on Allstar >>> -When I TX on Allstar it goes up to BM and is heard by my test >>> subject on his open spot, but the audio does not repeat on my local DMR >>> repeater. >>> -When my test subject TX's on his open spot I hear it on Allstar >>> and DMR. >>> >>> This never used to work this way, If I TX'd on my DMR repeater it >>> was heard on Allstar, and in the opposite if I TX'd on Allstar it would be >>> heard on my DMR repeater locally. >>> >>> I hope that I formulated my question in a way that makes sense. I >>> am unsure how to trouble shoot this because it appears that DMRGateway >>> works in both directions...sort of. >>> >>> Does anyone have any suggestions on how I should start >>> troubleshooting this? >>> >>> >>> -- >>> N1XBM >>> Apparare Scientor >>> Paratus Communicare >>> Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 >>> www.radioguysrepeaternetwork.com >>> >>> >>> _______________________________________________ >>> Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital >>> >>> _______________________________________________ Allstar-Digital >>> mailing list Allstar-Digital@lists.keekles.org >>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital >> >> -- >> N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, >> 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com >> >> _______________________________________________ >> Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital >> >> _______________________________________________ Allstar-Digital >> mailing list Allstar-Digital@lists.keekles.org >> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > > -- > N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, > 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com > > _______________________________________________ > Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital > > _______________________________________________ Allstar-Digital > mailing list Allstar-Digital@lists.keekles.org > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-b in/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Due to the nature of the list, I think this is a appropriate place to make a advanced product announcement. Kevin W3KKC, Mike N4IRR and I have been working on a line of MMDVM audio boards called INADVM. The product is produced and shipped from the US. The first version of the board is for the Arduino Due. It uses multi-turn pots for receive and transmit audio. The radio connector is a DB-9. A 12 MHz TCXO is included. On the board are LEDs for Power, PTT and Data detect. Now or the fun part. The design is through hole (not surface mount) except for the the voltage regulator and the TCXO. Those 2 parts will be pre-mounted the rest of the board will be a kit. You will receive the PC board with the regulator and TCXO mounted and all the parts needed, schematic and board layout. All ready to assemble. No surface mounted parts to solder. Sockets for the ICs. There will be a Assembled and Tested version also. Pricing: $35 for the kit plus shipping. $50 A&T plus shipping. The official introduction will be at the Dayton Hamfest. If possible We will have kits available before that. Sales will be through <http://www.masterscommunications.com/> -- "Real programmers us vi, that's why I use nano"
Sounds interesting. Will there be more information on it closer to release? Matthew Pitts N8OHU On April 6, 2017 11:27:14 AM EDT, Steve Zingman <szingman@msgstor.com> wrote:
Due to the nature of the list, I think this is a appropriate place to make a advanced product announcement.
Kevin W3KKC, Mike N4IRR and I have been working on a line of MMDVM audio boards called INADVM. The product is produced and shipped from the US.
The first version of the board is for the Arduino Due. It uses multi-turn pots for receive and transmit audio. The radio connector is a DB-9. A 12 MHz TCXO is included. On the board are LEDs for Power, PTT and Data detect. Now or the fun part. The design is through hole (not surface mount) except for the the voltage regulator and the TCXO. Those
2 parts will be pre-mounted the rest of the board will be a kit. You will receive the PC board with the regulator and TCXO mounted and all the parts needed, schematic and board layout. All ready to assemble. No
surface mounted parts to solder. Sockets for the ICs. There will be a Assembled and Tested version also.
Pricing: $35 for the kit plus shipping. $50 A&T plus shipping.
The official introduction will be at the Dayton Hamfest. If possible We
will have kits available before that. Sales will be through <http://www.masterscommunications.com/>
-- "Real programmers us vi, that's why I use nano" _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Matthew, As soon as the board layout and schematic are ready to publish they will be put up on the site. Just after I posted the announcement my "editor" had a few corrections for me. So... Kevin W3KKC, Mike N4IRR and I have been working on a line of MMDVM audio boards called INADVM. The product is produced and shipped from the US. The first version of the board is for the Arduino Due. It uses multi-turn pots for receive and transmit audio. The radio connector is a DB-9. A 12 MHz TCXO is included. On the board are LEDs for Power, PTT and Data detect. Now for the fun part. The design is through hole (not surface mount) except for the the voltage regulator and the TCXO. Those 2 parts will be pre-mounted. The rest of the board will be a kit. You will receive the PC board with the regulator and TCXO mounted and all the parts needed. All ready to assemble. No surface mounted parts to solder. Sockets for the ICs. The schematic and board layout will be posted on the web site. There will be a Assembled and Tested version also. Pricing: $35 for the kit plus shipping. $50 A&T plus shipping. The official introduction will be at the Dayton Hamvention. If possible we will have kits available before that. Sales will be through <http://www.masterscommunications.com/> On 4/6/2017 9:54 PM, Matthew Pitts wrote:
Sounds interesting. Will there be more information on it closer to release?
Matthew Pitts N8OHU
There seems to be a good deal of interest already, so here's some preliminary stuff to look at: http://www.masterscommunications.com/temp/INADVM/ Most of this information is of/for the REV1 prototype. The prototype does not have any RSSI circuitry, and there are a few silkscreen flaws, but are otherwise perfect. There are about a dozen of these out in beta testing, and all of the comments have been very positive so far. The last two files in the list are of the REV2 production unit. You can see the additional RSSI components in the upper right hand corner of the large REV2 image. You can download the two schematic files in PDF to see the differences between the prototype and the REV2 production model. The shipment of the latest revision 2 boards won't be in for about 10 days or so. However, I do have a few prototype boards available immediately for those who don't care about RSSI. They are available in kit form, or assembled and partially tested. The kit comes with the TCXO and regulator preinstalled, then the board is tested to make sure the regulator and TCXO are functioning. Inquire directly. Kevin - W3KKC On 4/7/2017 9:32 AM, Steve Zingman wrote:
Matthew, As soon as the board layout and schematic are ready to publish they will be put up on the site.
On 4/6/2017 9:54 PM, Matthew Pitts wrote:
Sounds interesting. Will there be more information on it closer to release?
Matthew Pitts N8OHU
Hey Steve, Are you guy making a board that goes on a RasPi and bypass the Arduino? David KE6UPI On Thu, Apr 6, 2017 at 8:27 AM, Steve Zingman <szingman@msgstor.com> wrote:
Due to the nature of the list, I think this is a appropriate place to make a advanced product announcement.
Kevin W3KKC, Mike N4IRR and I have been working on a line of MMDVM audio boards called INADVM. The product is produced and shipped from the US. The first version of the board is for the Arduino Due. It uses multi-turn pots for receive and transmit audio. The radio connector is a DB-9. A 12 MHz TCXO is included. On the board are LEDs for Power, PTT and Data detect. Now or the fun part. The design is through hole (not surface mount) except for the the voltage regulator and the TCXO. Those 2 parts will be pre-mounted the rest of the board will be a kit. You will receive the PC board with the regulator and TCXO mounted and all the parts needed, schematic and board layout. All ready to assemble. No surface mounted parts to solder. Sockets for the ICs. There will be a Assembled and Tested version also.
Pricing: $35 for the kit plus shipping. $50 A&T plus shipping.
The official introduction will be at the Dayton Hamfest. If possible We will have kits available before that. Sales will be through <http://www.masterscommunications.com/>
-- "Real programmers us vi, that's why I use nano" _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
David, No, it's a audio board that sits on the Arduino Due. The Due is a proven platform when paired with a good audio board. Later revs will support other processors. But that is a ways off. The boards have been received and are being tested. Should be available in the next week or so. Steve On 04/19/2017 08:50 PM, David KE6UPI wrote:
Hey Steve, Are you guy making a board that goes on a RasPi and bypass the Arduino?
David KE6UPI
On Thu, Apr 6, 2017 at 8:27 AM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
Due to the nature of the list, I think this is a appropriate place to make a advanced product announcement.
Kevin W3KKC, Mike N4IRR and I have been working on a line of MMDVM audio boards called INADVM. The product is produced and shipped from the US. The first version of the board is for the Arduino Due. It uses multi-turn pots for receive and transmit audio. The radio connector is a DB-9. A 12 MHz TCXO is included. On the board are LEDs for Power, PTT and Data detect. Now or the fun part. The design is through hole (not surface mount) except for the the voltage regulator and the TCXO. Those 2 parts will be pre-mounted the rest of the board will be a kit. You will receive the PC board with the regulator and TCXO mounted and all the parts needed, schematic and board layout. All ready to assemble. No surface mounted parts to solder. Sockets for the ICs. There will be a Assembled and Tested version also.
Pricing: $35 for the kit plus shipping. $50 A&T plus shipping.
The official introduction will be at the Dayton Hamfest. If possible We will have kits available before that. Sales will be through <http://www.masterscommunications.com/ <http://www.masterscommunications.com/>>
-- "Real programmers us vi, that's why I use nano" _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Thanks Steve, Put me down for one. David On Wed, Apr 19, 2017 at 5:55 PM, Steve Zingman <szingman@msgstor.com> wrote:
David, No, it's a audio board that sits on the Arduino Due. The Due is a proven platform when paired with a good audio board. Later revs will support other processors. But that is a ways off. The boards have been received and are being tested. Should be available in the next week or so.
Steve
On 04/19/2017 08:50 PM, David KE6UPI wrote:
Hey Steve, Are you guy making a board that goes on a RasPi and bypass the Arduino?
David KE6UPI
On Thu, Apr 6, 2017 at 8:27 AM, Steve Zingman <szingman@msgstor.com> wrote:
Due to the nature of the list, I think this is a appropriate place to make a advanced product announcement.
Kevin W3KKC, Mike N4IRR and I have been working on a line of MMDVM audio boards called INADVM. The product is produced and shipped from the US. The first version of the board is for the Arduino Due. It uses multi-turn pots for receive and transmit audio. The radio connector is a DB-9. A 12 MHz TCXO is included. On the board are LEDs for Power, PTT and Data detect. Now or the fun part. The design is through hole (not surface mount) except for the the voltage regulator and the TCXO. Those 2 parts will be pre-mounted the rest of the board will be a kit. You will receive the PC board with the regulator and TCXO mounted and all the parts needed, schematic and board layout. All ready to assemble. No surface mounted parts to solder. Sockets for the ICs. There will be a Assembled and Tested version also.
Pricing: $35 for the kit plus shipping. $50 A&T plus shipping.
The official introduction will be at the Dayton Hamfest. If possible We will have kits available before that. Sales will be through <http://www.masterscommunications.com/>
-- "Real programmers us vi, that's why I use nano" _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Kevin has created a web site for information and ordering. <http://inadvm.com/inadvm/inadvm-index.html> 73, Steve N4IRS On 4/19/2017 10:03 PM, David KE6UPI wrote:
Thanks Steve, Put me down for one.
David
On Wed, Apr 19, 2017 at 5:55 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
David, No, it's a audio board that sits on the Arduino Due. The Due is a proven platform when paired with a good audio board. Later revs will support other processors. But that is a ways off. The boards have been received and are being tested. Should be available in the next week or so.
Steve
On 04/19/2017 08:50 PM, David KE6UPI wrote:
Hey Steve, Are you guy making a board that goes on a RasPi and bypass the Arduino?
David KE6UPI
On Thu, Apr 6, 2017 at 8:27 AM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
Due to the nature of the list, I think this is a appropriate place to make a advanced product announcement.
Kevin W3KKC, Mike N4IRR and I have been working on a line of MMDVM audio boards called INADVM. The product is produced and shipped from the US. The first version of the board is for the Arduino Due. It uses multi-turn pots for receive and transmit audio. The radio connector is a DB-9. A 12 MHz TCXO is included. On the board are LEDs for Power, PTT and Data detect. Now or the fun part. The design is through hole (not surface mount) except for the the voltage regulator and the TCXO. Those 2 parts will be pre-mounted the rest of the board will be a kit. You will receive the PC board with the regulator and TCXO mounted and all the parts needed, schematic and board layout. All ready to assemble. No surface mounted parts to solder. Sockets for the ICs. There will be a Assembled and Tested version also.
Pricing: $35 for the kit plus shipping. $50 A&T plus shipping.
The official introduction will be at the Dayton Hamfest. If possible We will have kits available before that. Sales will be through <http://www.masterscommunications.com/ <http://www.masterscommunications.com/>>
-- "Real programmers us vi, that's why I use nano" _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital <http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
participants (6)
-
Corey Dean -
David KE6UPI -
Kevin Custer -
Matthew Pitts -
Robert Newberry -
Steve Zingman