Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink /ambe_audio / DV3000u/PiDV
Hello Steve, Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results With the -n switch, the dongle never sends back the
0AMBE3000R Version 6100010031 Wrote: 5 bytes a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment.
When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400. Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch. Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that. BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days. On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything. Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com, so that link is dead. Just in case you didn't know. 73's from Guy VE2VAG _______________________________________________ Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman@msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests. Steve On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote:
Richard, 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
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Guy, The problems we had with ambe_audio on the new version of dmrlink has been fixed. You can do a git pull and copy ambe_audio.py to /opt/dmrlink/ambe_audio. I will be working on the configuration document next week. Really all that is left is pointing dmrlink.cfg at your master and configure ambe_audio.cfg. As far as DMRGui, thats what I get for using tinyurl. Lesson learned. ;( Here is a fresh link to DMRGui.zip <http://dvswitch.org/files/DMRGateway/DMRGui.zip> 73, Steve N4IRS On 04/07/2017 05:23 AM, Guy Vachon VE2VAG wrote:
Hello Steve,
Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results
With the -n switch, the dongle never sends back the
0AMBE3000R Version 6100010031 Wrote: 5 bytes a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment.
When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400.
Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch.
Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that.
BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days.
On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything.
Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com, so that link is dead. Just in case you didn't know.
73's from Guy VE2VAG _______________________________________________
Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman@msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed"
Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests.
Steve
On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote:
Richard, 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
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Steve, I've been testing with the latest version of ambe_audio but still only getting audio flowing ASL>DMR, is there something that needs doing at the master to allow traffic to flow DMR>ASL ? I've attached my config files. Thanks Peter On 07/04/2017 11:08, Steve Zingman wrote:
Guy, The problems we had with ambe_audio on the new version of dmrlink has been fixed. You can do a git pull and copy ambe_audio.py to /opt/dmrlink/ambe_audio. I will be working on the configuration document next week. Really all that is left is pointing dmrlink.cfg at your master and configure ambe_audio.cfg.
As far as DMRGui, thats what I get for using tinyurl. Lesson learned. ;( Here is a fresh link to DMRGui.zip <http://dvswitch.org/files/DMRGateway/DMRGui.zip>
73, Steve N4IRS
On 04/07/2017 05:23 AM, Guy Vachon VE2VAG wrote:
Hello Steve,
Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results
With the -n switch, the dongle never sends back the
0AMBE3000R Version 6100010031 Wrote: 5 bytes a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment.
When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400.
Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch.
Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that.
BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days.
On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything.
Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com, so that link is dead. Just in case you didn't know.
73's from Guy VE2VAG _______________________________________________
Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman@msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed"
Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests.
Steve
On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote:
Richard, 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
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.keekles.org/pipermail/allstar-digital/attachments/20170405/c4f77610/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
------------------------------
End of Allstar-Digital Digest, Vol 19, Issue 5 ********************************************** _______________________________________________ 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
Peter, Yes, BM treats DMRlink as a "SmartPTT" connection. Your Master admin needs to configure the TS / TG / Radio ID. Your BM admin should know how to do configure a SmartPTT connection. Make sure you use the term SmartPTT. 73, Steve N4IRS On 04/07/2017 06:27 AM, Peter wrote:
Steve, I've been testing with the latest version of ambe_audio but still only getting audio flowing ASL>DMR, is there something that needs doing at the master to allow traffic to flow DMR>ASL ?
I've attached my config files.
Thanks
Peter
On 07/04/2017 11:08, Steve Zingman wrote:
Guy, The problems we had with ambe_audio on the new version of dmrlink has been fixed. You can do a git pull and copy ambe_audio.py to /opt/dmrlink/ambe_audio. I will be working on the configuration document next week. Really all that is left is pointing dmrlink.cfg at your master and configure ambe_audio.cfg.
As far as DMRGui, thats what I get for using tinyurl. Lesson learned. ;( Here is a fresh link to DMRGui.zip <http://dvswitch.org/files/DMRGateway/DMRGui.zip>
73, Steve N4IRS
On 04/07/2017 05:23 AM, Guy Vachon VE2VAG wrote:
Hello Steve,
Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results
With the -n switch, the dongle never sends back the
0AMBE3000R Version 6100010031 Wrote: 5 bytes a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment.
When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400.
Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch.
Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that.
BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days.
On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything.
Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com, so that link is dead. Just in case you didn't know.
73's from Guy VE2VAG _______________________________________________
Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman@msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed"
Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests.
Steve
On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote:
Richard, 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
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Peter, BM recently changed the way smart Ptt connections are configured on the master. Trust me I just went through three masters changing them all! Please make sure your local bm admin is aware of that and if he has any questions or needs an example to contact me, N3fe, directly and I will give him a hand. Corey N3fe Sent from my iPhone
On Apr 7, 2017, at 6:32 AM, Steve Zingman <szingman@msgstor.com> wrote:
Peter, Yes, BM treats DMRlink as a "SmartPTT" connection. Your Master admin needs to configure the TS / TG / Radio ID. Your BM admin should know how to do configure a SmartPTT connection. Make sure you use the term SmartPTT.
73, Steve N4IRS
On 04/07/2017 06:27 AM, Peter wrote: Steve, I've been testing with the latest version of ambe_audio but still only getting audio flowing ASL>DMR, is there something that needs doing at the master to allow traffic to flow DMR>ASL ?
I've attached my config files.
Thanks
Peter
On 07/04/2017 11:08, Steve Zingman wrote:
Guy, The problems we had with ambe_audio on the new version of dmrlink has been fixed. You can do a git pull and copy ambe_audio.py to /opt/dmrlink/ambe_audio. I will be working on the configuration document next week. Really all that is left is pointing dmrlink.cfg at your master and configure ambe_audio.cfg.
As far as DMRGui, thats what I get for using tinyurl. Lesson learned. ;( Here is a fresh link to DMRGui.zip <http://dvswitch.org/files/DMRGateway/DMRGui.zip>
73, Steve N4IRS
On 04/07/2017 05:23 AM, Guy Vachon VE2VAG wrote:
Hello Steve,
Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results
With the -n switch, the dongle never sends back the
0AMBE3000R Version 6100010031 Wrote: 5 bytes a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment.
When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400.
Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch.
Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that.
BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days.
On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything.
Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com, so that link is dead. Just in case you didn't know.
73's from Guy VE2VAG _______________________________________________
Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman@msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed"
Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests.
Steve
On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote:
Richard, 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
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Thanks Corey I'm just waiting to hear back from Rudy as I've requested a dedicated TG for the link. Peter On 07/04/2017 17:34, Corey Dean wrote: Peter, BM recently changed the way smart Ptt connections are configured on the master. Trust me I just went through three masters changing them all! Please make sure your local bm admin is aware of that and if he has any questions or needs an example to contact me, N3fe, directly and I will give him a hand. Corey N3fe Sent from my iPhone On Apr 7, 2017, at 6:32 AM, Steve Zingman <szingman@msgstor.com<mailto:szingman@msgstor.com>> wrote: Peter, Yes, BM treats DMRlink as a "SmartPTT" connection. Your Master admin needs to configure the TS / TG / Radio ID. Your BM admin should know how to do configure a SmartPTT connection. Make sure you use the term SmartPTT. 73, Steve N4IRS On 04/07/2017 06:27 AM, Peter wrote: Steve, I've been testing with the latest version of ambe_audio but still only getting audio flowing ASL>DMR, is there something that needs doing at the master to allow traffic to flow DMR>ASL ? I've attached my config files. Thanks Peter On 07/04/2017 11:08, Steve Zingman wrote: Guy, The problems we had with ambe_audio on the new version of dmrlink has been fixed. You can do a git pull and copy ambe_audio.py to /opt/dmrlink/ambe_audio. I will be working on the configuration document next week. Really all that is left is pointing dmrlink.cfg at your master and configure ambe_audio.cfg. As far as DMRGui, thats what I get for using tinyurl. Lesson learned. ;( Here is a fresh link to DMRGui.zip <http://dvswitch.org/files/DMRGateway/DMRGui.zip><http://dvswitch.org/files/DMRGateway/DMRGui.zip> 73, Steve N4IRS On 04/07/2017 05:23 AM, Guy Vachon VE2VAG wrote: Hello Steve, Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results With the -n switch, the dongle never sends back the 0AMBE3000R Version 6100010031 Wrote: 5 bytes a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment. When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400. Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch. Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that. BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days. On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything. Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com<http://vyous.com>, so that link is dead. Just in case you didn't know. 73's from Guy VE2VAG _______________________________________________ Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman@msgstor.com><mailto:szingman@msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org><mailto:allstar-digital@lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com><mailto:6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests. Steve On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote: Richard, 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 _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.keekles.org/pipermail/allstar-digital/attachments/20170405/c4f77610/attachment.html><http://lists.keekles.org/pipermail/allstar-digital/attachments/20170405/c4f77610/attachment.html> ------------------------------ Subject: Digest Footer _______________________________________________ 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 ------------------------------ End of Allstar-Digital Digest, Vol 19, Issue 5 ********************************************** _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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
Oh, I have a direct line with Rudy. I will let him know to check his email. What master is this on? Sent from my iPhone
On Apr 7, 2017, at 12:56 PM, Peter <g7rpg@hotmail.com> wrote:
Thanks Corey
I'm just waiting to hear back from Rudy as I've requested a dedicated TG for the link.
Peter
On 07/04/2017 17:34, Corey Dean wrote: Peter,
BM recently changed the way smart Ptt connections are configured on the master. Trust me I just went through three masters changing them all! Please make sure your local bm admin is aware of that and if he has any questions or needs an example to contact me, N3fe, directly and I will give him a hand.
Corey N3fe
Sent from my iPhone
On Apr 7, 2017, at 6:32 AM, Steve Zingman <szingman@msgstor.com> wrote:
Peter, Yes, BM treats DMRlink as a "SmartPTT" connection. Your Master admin needs to configure the TS / TG / Radio ID. Your BM admin should know how to do configure a SmartPTT connection. Make sure you use the term SmartPTT.
73, Steve N4IRS
On 04/07/2017 06:27 AM, Peter wrote: Steve, I've been testing with the latest version of ambe_audio but still only getting audio flowing ASL>DMR, is there something that needs doing at the master to allow traffic to flow DMR>ASL ?
I've attached my config files.
Thanks
Peter
On 07/04/2017 11:08, Steve Zingman wrote:
Guy, The problems we had with ambe_audio on the new version of dmrlink has been fixed. You can do a git pull and copy ambe_audio.py to /opt/dmrlink/ambe_audio. I will be working on the configuration document next week. Really all that is left is pointing dmrlink.cfg at your master and configure ambe_audio.cfg.
As far as DMRGui, thats what I get for using tinyurl. Lesson learned. ;( Here is a fresh link to DMRGui.zip <http://dvswitch.org/files/DMRGateway/DMRGui.zip>
73, Steve N4IRS
On 04/07/2017 05:23 AM, Guy Vachon VE2VAG wrote:
Hello Steve,
Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results
With the -n switch, the dongle never sends back the > 0AMBE3000R > Version > 6100010031 > Wrote: 5 bytes > a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment.
When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400.
Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch.
Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that.
BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days.
On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything.
Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com, so that link is dead. Just in case you didn't know.
73's from Guy VE2VAG _______________________________________________
Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman@msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed"
Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests.
Steve
On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote: > Richard, > 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 > > > _______________________________________________ > Allstar-Digital mailing list > Allstar-Digital@lists.keekles.org > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Amazing! I'm on the UK master, 2342. I sent the message through facebook. Peter On 07/04/2017 18:21, Corey Dean wrote: Oh, I have a direct line with Rudy. I will let him know to check his email. What master is this on? Sent from my iPhone On Apr 7, 2017, at 12:56 PM, Peter <g7rpg@hotmail.com<mailto:g7rpg@hotmail.com>> wrote: Thanks Corey I'm just waiting to hear back from Rudy as I've requested a dedicated TG for the link. Peter On 07/04/2017 17:34, Corey Dean wrote: Peter, BM recently changed the way smart Ptt connections are configured on the master. Trust me I just went through three masters changing them all! Please make sure your local bm admin is aware of that and if he has any questions or needs an example to contact me, N3fe, directly and I will give him a hand. Corey N3fe Sent from my iPhone On Apr 7, 2017, at 6:32 AM, Steve Zingman <szingman@msgstor.com<mailto:szingman@msgstor.com>> wrote: Peter, Yes, BM treats DMRlink as a "SmartPTT" connection. Your Master admin needs to configure the TS / TG / Radio ID. Your BM admin should know how to do configure a SmartPTT connection. Make sure you use the term SmartPTT. 73, Steve N4IRS On 04/07/2017 06:27 AM, Peter wrote: Steve, I've been testing with the latest version of ambe_audio but still only getting audio flowing ASL>DMR, is there something that needs doing at the master to allow traffic to flow DMR>ASL ? I've attached my config files. Thanks Peter On 07/04/2017 11:08, Steve Zingman wrote: Guy, The problems we had with ambe_audio on the new version of dmrlink has been fixed. You can do a git pull and copy ambe_audio.py to /opt/dmrlink/ambe_audio. I will be working on the configuration document next week. Really all that is left is pointing dmrlink.cfg at your master and configure ambe_audio.cfg. As far as DMRGui, thats what I get for using tinyurl. Lesson learned. ;( Here is a fresh link to DMRGui.zip <http://dvswitch.org/files/DMRGateway/DMRGui.zip><http://dvswitch.org/files/DMRGateway/DMRGui.zip> 73, Steve N4IRS On 04/07/2017 05:23 AM, Guy Vachon VE2VAG wrote: Hello Steve, Sorry for the delay in answering, was overloaded with work. Dunno if you still needed the test, but anyhow, I've tried again the command with and without the -n switch, and also 2 times back to back with the -n switch (if I understood correctly the test you asked for) and still the same results With the -n switch, the dongle never sends back the 0AMBE3000R Version 6100010031 Wrote: 5 bytes a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 we are expecting. When the –n switch is removed from the the command, I do receive it at the moment. When I was making tests, I’ve checked the dongle’s serial baud rate with “stty -F /dev/ttyUSB0” and it stated at first that the dongle was at 460800 bauds. I bought my ThumbDV when they came out at first, way before the new model that is at 460800, so I knew mine was at 230400. Even if i tried sending the command python “AMBEtest3.py -n -s /dev/ttyUSB0” after setting the serial baud rate baud rate at 230400 with "stty -F /dev/ttyUSB0 230400", it would not work. Only way to ge the expected result was by removing the –n switch. Also, the AMBEtest3.py python command with the –n switch removed always worked, even without trying setting the baud rate of the dongle at 230400 before that. BTW, I'm using the RC1 image from the links in your instructions. And the above tests were made without doing any git pull that I was in the posts made during the last couple of days. On my side, I went thru all the instructions from your document, and I'm ready for the next part about the configuration. But I know you, Mike and the rest of the team are working hard with bug hunting, so please keep up the good work and thanks for everything. Also, in regard of my initial question about DMRGui, it was because the link for it in the files section of the DVhamswitch website sends us on a parked domain for sale at vyous.com<http://vyous.com>, so that link is dead. Just in case you didn't know. 73's from Guy VE2VAG _______________________________________________ Date: Wed, 5 Apr 2017 08:14:57 -0400 From: Steve Zingman <szingman@msgstor.com><mailto:szingman@msgstor.com> To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org><mailto:allstar-digital@lists.keekles.org> Subject: Re: [Allstar Digital] DMRGateway / DMRGui / DMRLink/ambe_audio / DV3000u/PiDV Message-ID: <6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com><mailto:6cf8d6ee-9f4d-4d17-da7a-cc124ea90ea9@msgstor.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" Guy, I do not have the first generation ThumbDV. Could you try with the -n switch and when it fails, try with the -n switch? No reboot between tests. Steve On 4/4/2017 9:18 PM, Guy Vachon VE2VAG wrote: Richard, 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 _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.keekles.org/pipermail/allstar-digital/attachments/20170405/c4f77610/attachment.html><http://lists.keekles.org/pipermail/allstar-digital/attachments/20170405/c4f77610/attachment.html> ------------------------------ Subject: Digest Footer _______________________________________________ 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 ------------------------------ End of Allstar-Digital Digest, Vol 19, Issue 5 ********************************************** _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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
participants (4)
-
Corey Dean -
Guy Vachon VE2VAG -
Peter -
Steve Zingman