[arm-allstar] Full duplex with details
chris novara
chris at redcrosscommunications.org
Sun Apr 1 02:47:48 EST 2018
Ok, more info
I have a stand alone Hub (psudo) connected at my restaurant high bandwidth
We have multiple nodes remotely connected to our hub via internet from several users around the state. Some are half duplex and some are full duplex
-using two full duplex nodes-
We are trying to get full duplex audio between two nodes that are setup using option 0 so there is no hang/telemetry and we have the “link to link=yes” set ok
When we test, we get fuzzy, garbled audio if two nodes are transmitting at once.
However, if one node transmits at a time - all works great
Are we missing any settings that prevent clean full duplex audio ?
Chris Novara
Phone: 541-778-1175
Eugene, Oregon
Email-Chris at redcrosscommunications.org
> On Mar 31, 2018, at 8:42 PM, arm-allstar-request at hamvoip.org wrote:
>
> Send arm-allstar mailing list submissions to
> arm-allstar at hamvoip.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> or, via email, send a message with subject or body 'help' to
> arm-allstar-request at hamvoip.org
>
> You can reach the person managing the list at
> arm-allstar-owner at hamvoip.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of arm-allstar digest..."
>
>
> Today's Topics:
>
> 1. Re: arm-allstar Digest, Vol 46, Issue 67 (Charles Wiant)
> 2. Full duplex audio through hub (chris novara)
> 3. Re: Full duplex audio through hub (David McGough)
> 4. Re: Full duplex audio through hub (Doug Crompton)
> 5. Pi3B+ greatly exceeds expectations!!! (Doug Crompton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 31 Mar 2018 21:18:45 -0400
> From: Charles Wiant <kd8itc at aol.com>
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] arm-allstar Digest, Vol 46, Issue 67
> Message-ID: <1627ec8f9b3-c89-43cc at webjas-vaa011.srv.aolmail.net>
> Content-Type: text/plain; charset=utf-8
>
> i have used v71 for over a year no issues.charles WV8CW
>
>
>
>
>
>
>
> -----Original Message-----
> From: arm-allstar-request <arm-allstar-request at hamvoip.org>
> To: arm-allstar <arm-allstar at hamvoip.org>
> Sent: Sat, Mar 31, 2018 12:00 pm
> Subject: arm-allstar Digest, Vol 46, Issue 67
>
> Send arm-allstar mailing list submissions to
> arm-allstar at hamvoip.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> or, via email, send a message with subject or body 'help' to
> arm-allstar-request at hamvoip.org
>
> You can reach the person managing the list at
> arm-allstar-owner at hamvoip.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of arm-allstar digest..."
>
>
> Today's Topics:
>
> 1. Re: Kenwood TM-V71 / D710 notes (David)
> 2. Re: Kenwood TM-V71 / D710 notes (David)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 30 Mar 2018 23:38:44 -0500
> From: David <david at kg5rdf.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Kenwood TM-V71 / D710 notes
> Message-ID: <E1f28Hw-00079B-9T at semf01.mfg.siteprotect.com>
> Content-Type: text/plain; charset=utf-8
>
> Yes
>
>
> Sent from my T-Mobile 4G LTE Device
> -------- Original message --------From: Jeff Karpinski via arm-allstar <arm-allstar at hamvoip.org> Date: 3/30/18 11:22 PM (GMT-06:00) To: ARM Allstar <arm-allstar at hamvoip.org> Cc: Jeff Karpinski <jeff at 3d0g.net> Subject: Re: [arm-allstar] Kenwood TM-V71 / D710 notes
> I?ve not modified the 71 in any way. Were you running CTCSS on them? Did they accept DTMF?
>
>
>> On Mar 30, 2018, at 10:15 PM, David via arm-allstar <arm-allstar at hamvoip.org> wrote:
>>
>> I have run two v71 with zero issues or modification, for over a year, on a 25 site linked system. They were the Allstar access point. I moved the Allstar to the system hub and intigrated a CAT800 with extender card.
>> I mention this because the v71 worked perfectly for short term solution without any modification.
>> David www.nctc.info
>>
>>
>> Sent from my T-Mobile 4G LTE Device
>> -------- Original message --------From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org> Date: 3/30/18? 8:33 PM? (GMT-06:00) To: ARM Allstar <arm-allstar at hamvoip.org> Cc: Doug Crompton <wa3dsp at gmail.com> Subject: Re: [arm-allstar] Kenwood TM-V71 / D710 notes
>> Jeff,
>>
>> There is one thing I am not following in you writeup.? I think the TMV71
>> is active low for PTT. This works fine with the default active low settings
>> and a FET or PNP transistor which is what you are suppose to use to drive
>> PTT. You would never connect PTT out of the FOB directly to PTT without
>> interface parts.? All FOBS manufactured for radios use a FET or NPN to
>> drive PTT. You can look at the various schematics and those at the
>> hamvoip.org site for modifying the FOBS.
>>
>> On the DTMF issue dropping COS. I have not heard that one and I do not have
>> a radio to test. Let me make sure I have this right.
>> You are saying that when you key a radio transmitting to the node radio and
>> have good COS as shown on the simpleusb-tune-menu view display that when
>> you hit a DTMF tone on the radio talking to your node radio the COS drops?
>> This sounds more like a level issue perhaps the DTMF level is so high it is
>> clipping out of the node radios bandpass? It could also indicate loss of PL
>> from the radio you r are keying the DTMF on. Have you tried different
>> radios?
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>>
>>
>>
>> On Fri, Mar 30, 2018 at 9:00 PM, "Jeff Karpinski via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>>> This seems the best place to capture my notes on setting up a Pi based
>>> Allstar node with the Kenwood TM-V71 (or D710 which uses the same chassis).
>>> Yes, it?s been done before but the info is pretty scattered and I found a
>>> CTCSS bug in the radio that others apparently missed.
>>>
>>> I went the modded CM108 approach that?s pretty well documented. Fobs
>>> secured from https://www.ebay.com/itm/272374780193 <
>>> https://www.ebay.com/itm/272374780193> for a couple bucks each. Buy a
>>> couple extras, just in case you hose one up, plus I got one unit that
>>> looked fine but spewed ungodly RF noise. Generally followed the mod details
>>> found here: http://www.garydion.com/projects/usb_fob/ <
>>> http://www.garydion.com/projects/usb_fob/>. You don?t need the right
>>> channel so don?t bother with it.
>>>
>>> Grab an old PS/2 keyboard or mouse and wack the cable off. Strip it back
>>> and tone out all the wires. Remember, the connector is male so the pins are
>>> mirrored from what?s shown in the Kenwood manuals. Follow this layout:
>>> https://www.i2cchip.com/minidin_male_large.gif <https://www.i2cchip.com/
>>> minidin_male_large.gif>
>>>
>>> Wire up as follows:
>>>
>>> CM108????????? Male DIN
>>> Ground???????? Pin 2 and cable shield (ground)
>>> COS???????????? Pin 6 (SQC)
>>> PTT????????????? Pin 3 (PKS)
>>> Left?????????????? Pin 1 (PKD)
>>> Mic?????????????? Pin 5 (PR1)
>>>
>>> In the Radio settings, you?ll need to set the following options:
>>>
>>> 517 DAT.BND to A or B depending on what side of the radio you want to use
>>> for Allstar operations.
>>> 518 DAT.SPD to 1200 (de-emphasized audio).
>>> 520 SQC.SRC to SQL
>>>
>>> And via the Kenwood MCP-2A programming software on the Data Terminal page
>>> (yes, it?s the only way to change these settings):
>>>
>>> PR1 Pin Output Level (for packet mode): 8
>>> PKD Pin Input Sensitivity (For packet 1200bps mode): 3
>>>
>>> If you don?t change these settings, you?ll probably have a difficult time
>>> in getting the audio levels right in simpleusb.
>>>
>>> Speaking of, here?s my simpleusb settings:
>>>
>>> Active simpleusb stanza: [usb]
>>> USB device String:?????? 1-1.4:1.0
>>>
>>> Card is:???????? 0
>>> Name is:???????? usb
>>> Rx Level:??????? 500
>>> Rx no-delay:???? 0
>>> Rx audio-delay:? 0
>>> Tx A Level:????? 300
>>> Tx B Level:????? 500
>>> preemphasis:???? no
>>> deemphasis:????? no
>>> plfilter:??????? yes
>>> rxboost:???????? yes
>>>
>>> PTT:???????????? Active HIGH
>>> PTT status:????? Un-Keyed
>>>
>>> CTCSS (input):?? Ignored
>>> COS (input):???? CM108/CM119 Active HIGH
>>> COS (test):????? Un-Keyed
>>> COS (composite): Un-Keyed
>>>
>>> OK, now down to the bugs I found. First, in hamvoip 1.5, if PTT is set
>>> Active HIGH, on boot-up the radio will remain keyed until something is
>>> transmitted. I worked around this by editing /etc/asterisk/rpt.conf and
>>> enabling a startup_macro by finding and editing the following lines:
>>>
>>> startup_macro = *920
>>>
>>> ; Play a Node announcement
>>> 920=localplay,/etc/asterisk/local/myid
>>>
>>> Instructions for creating custom audio files like ?myid' from your text
>>> can be found here https://www.hamvoip.org/tts-how-to.pdf <
>>> https://www.hamvoip.org/tts-how-to.pdf>
>>>
>>> Once asterisk starts up and plays the announcement, it gets in sync with
>>> the actual PTT status and stays good from there on.
>>>
>>> The radio bug? I really wanted to use CTCSS to keep other on-freq traffic
>>> from leaking into connected nodes. Problem is, Asterisk would show a ?hang
>>> up? after every DTMF tone received. If I disabled CTCSS, everything worked
>>> perfectly. The "View COS, CTCSS and PTT Telemetry" option in simpleusb gave
>>> a similar clue, showing COS briefly going CLEAR the moment I sent a DTMF
>>> tone from my HT. Convinced this was still a software issue, I disconnected
>>> everything and tied an LED from the SQC line to ground on the radio. Sure
>>> enough, SQC went high with keying and proper PL, but the moment I sent a
>>> DTMF tone, it winked out for a few milliseconds. CTCSS disabled, no
>>> winking. I suspect this is why a lot of other folks came to the conclusion
>>> that these Kenwood radios didn?t support COS based CTCSS control. For
>>> giggles, I tried the same setup with DCS (Digital Code Squelch) and voil?!
>>> It worked perfectly! No COS winking while sending DTMF. Since this node is
>>> just for neighborhood use, I can easily live with the DCS compromise.
>>>
>>> I?m fully aware there are other ways to skin these cats as hamvoip /
>>> Asterisk are crazy-powerful. CTCSS decode could be done inside the
>>> software. The PPT line could be inverted with a simple transistor. I
>>> suspect everyone?s Allstar setup ends up being a bit custom, this is simply
>>> what worked for me.
>>>
>>> One last tip, if you?re enabling Echolink. In addition to the detailed
>>> mods to /etc/asterisk/echolink.conf listed in https://www.hamvoip.org/
>>> echolink_howto.pdf <https://www.hamvoip.org/echolink_howto.pdf>, note the
>>> default echolink servers are outdated. They should be as follows:
>>>
>>> server1=nawest.echolink.org
>>> server2=nasouth.echolink.org
>>> server3=servers.echolink.org
>>> server4=backup.echolink.org <http://backup.echolink.org/>
>>>
>>> 73, N0KAI
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
> ------------------------------
>
> Message: 2
> Date: Fri, 30 Mar 2018 23:42:23 -0500
> From: David <david at kg5rdf.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Kenwood TM-V71 / D710 notes
> Message-ID: <E1f28LU-0000LP-I5 at semf02.mfg.siteprotect.com>
> Content-Type: text/plain; charset=utf-8
>
> I am still using one as my simplex link in. It has double duty as the controller for a upgraded DR1 run in FIX FIX with Wires X on it. I DTMF it all the time to turn links on and off.
>
>
> Sent from my T-Mobile 4G LTE Device
> -------- Original message --------From: Jeff Karpinski via arm-allstar <arm-allstar at hamvoip.org> Date: 3/30/18 11:22 PM (GMT-06:00) To: ARM Allstar <arm-allstar at hamvoip.org> Cc: Jeff Karpinski <jeff at 3d0g.net> Subject: Re: [arm-allstar] Kenwood TM-V71 / D710 notes
> I?ve not modified the 71 in any way. Were you running CTCSS on them? Did they accept DTMF?
>
>
>> On Mar 30, 2018, at 10:15 PM, David via arm-allstar <arm-allstar at hamvoip.org> wrote:
>>
>> I have run two v71 with zero issues or modification, for over a year, on a 25 site linked system. They were the Allstar access point. I moved the Allstar to the system hub and intigrated a CAT800 with extender card.
>> I mention this because the v71 worked perfectly for short term solution without any modification.
>> David www.nctc.info
>>
>>
>> Sent from my T-Mobile 4G LTE Device
>> -------- Original message --------From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org> Date: 3/30/18? 8:33 PM? (GMT-06:00) To: ARM Allstar <arm-allstar at hamvoip.org> Cc: Doug Crompton <wa3dsp at gmail.com> Subject: Re: [arm-allstar] Kenwood TM-V71 / D710 notes
>> Jeff,
>>
>> There is one thing I am not following in you writeup.? I think the TMV71
>> is active low for PTT. This works fine with the default active low settings
>> and a FET or PNP transistor which is what you are suppose to use to drive
>> PTT. You would never connect PTT out of the FOB directly to PTT without
>> interface parts.? All FOBS manufactured for radios use a FET or NPN to
>> drive PTT. You can look at the various schematics and those at the
>> hamvoip.org site for modifying the FOBS.
>>
>> On the DTMF issue dropping COS. I have not heard that one and I do not have
>> a radio to test. Let me make sure I have this right.
>> You are saying that when you key a radio transmitting to the node radio and
>> have good COS as shown on the simpleusb-tune-menu view display that when
>> you hit a DTMF tone on the radio talking to your node radio the COS drops?
>> This sounds more like a level issue perhaps the DTMF level is so high it is
>> clipping out of the node radios bandpass? It could also indicate loss of PL
>> from the radio you r are keying the DTMF on. Have you tried different
>> radios?
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>>
>>
>>
>> On Fri, Mar 30, 2018 at 9:00 PM, "Jeff Karpinski via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>>> This seems the best place to capture my notes on setting up a Pi based
>>> Allstar node with the Kenwood TM-V71 (or D710 which uses the same chassis).
>>> Yes, it?s been done before but the info is pretty scattered and I found a
>>> CTCSS bug in the radio that others apparently missed.
>>>
>>> I went the modded CM108 approach that?s pretty well documented. Fobs
>>> secured from https://www.ebay.com/itm/272374780193 <
>>> https://www.ebay.com/itm/272374780193> for a couple bucks each. Buy a
>>> couple extras, just in case you hose one up, plus I got one unit that
>>> looked fine but spewed ungodly RF noise. Generally followed the mod details
>>> found here: http://www.garydion.com/projects/usb_fob/ <
>>> http://www.garydion.com/projects/usb_fob/>. You don?t need the right
>>> channel so don?t bother with it.
>>>
>>> Grab an old PS/2 keyboard or mouse and wack the cable off. Strip it back
>>> and tone out all the wires. Remember, the connector is male so the pins are
>>> mirrored from what?s shown in the Kenwood manuals. Follow this layout:
>>> https://www.i2cchip.com/minidin_male_large.gif <https://www.i2cchip.com/
>>> minidin_male_large.gif>
>>>
>>> Wire up as follows:
>>>
>>> CM108????????? Male DIN
>>> Ground???????? Pin 2 and cable shield (ground)
>>> COS???????????? Pin 6 (SQC)
>>> PTT????????????? Pin 3 (PKS)
>>> Left?????????????? Pin 1 (PKD)
>>> Mic?????????????? Pin 5 (PR1)
>>>
>>> In the Radio settings, you?ll need to set the following options:
>>>
>>> 517 DAT.BND to A or B depending on what side of the radio you want to use
>>> for Allstar operations.
>>> 518 DAT.SPD to 1200 (de-emphasized audio).
>>> 520 SQC.SRC to SQL
>>>
>>> And via the Kenwood MCP-2A programming software on the Data Terminal page
>>> (yes, it?s the only way to change these settings):
>>>
>>> PR1 Pin Output Level (for packet mode): 8
>>> PKD Pin Input Sensitivity (For packet 1200bps mode): 3
>>>
>>> If you don?t change these settings, you?ll probably have a difficult time
>>> in getting the audio levels right in simpleusb.
>>>
>>> Speaking of, here?s my simpleusb settings:
>>>
>>> Active simpleusb stanza: [usb]
>>> USB device String:?????? 1-1.4:1.0
>>>
>>> Card is:???????? 0
>>> Name is:???????? usb
>>> Rx Level:??????? 500
>>> Rx no-delay:???? 0
>>> Rx audio-delay:? 0
>>> Tx A Level:????? 300
>>> Tx B Level:????? 500
>>> preemphasis:???? no
>>> deemphasis:????? no
>>> plfilter:??????? yes
>>> rxboost:???????? yes
>>>
>>> PTT:???????????? Active HIGH
>>> PTT status:????? Un-Keyed
>>>
>>> CTCSS (input):?? Ignored
>>> COS (input):???? CM108/CM119 Active HIGH
>>> COS (test):????? Un-Keyed
>>> COS (composite): Un-Keyed
>>>
>>> OK, now down to the bugs I found. First, in hamvoip 1.5, if PTT is set
>>> Active HIGH, on boot-up the radio will remain keyed until something is
>>> transmitted. I worked around this by editing /etc/asterisk/rpt.conf and
>>> enabling a startup_macro by finding and editing the following lines:
>>>
>>> startup_macro = *920
>>>
>>> ; Play a Node announcement
>>> 920=localplay,/etc/asterisk/local/myid
>>>
>>> Instructions for creating custom audio files like ?myid' from your text
>>> can be found here https://www.hamvoip.org/tts-how-to.pdf <
>>> https://www.hamvoip.org/tts-how-to.pdf>
>>>
>>> Once asterisk starts up and plays the announcement, it gets in sync with
>>> the actual PTT status and stays good from there on.
>>>
>>> The radio bug? I really wanted to use CTCSS to keep other on-freq traffic
>>> from leaking into connected nodes. Problem is, Asterisk would show a ?hang
>>> up? after every DTMF tone received. If I disabled CTCSS, everything worked
>>> perfectly. The "View COS, CTCSS and PTT Telemetry" option in simpleusb gave
>>> a similar clue, showing COS briefly going CLEAR the moment I sent a DTMF
>>> tone from my HT. Convinced this was still a software issue, I disconnected
>>> everything and tied an LED from the SQC line to ground on the radio. Sure
>>> enough, SQC went high with keying and proper PL, but the moment I sent a
>>> DTMF tone, it winked out for a few milliseconds. CTCSS disabled, no
>>> winking. I suspect this is why a lot of other folks came to the conclusion
>>> that these Kenwood radios didn?t support COS based CTCSS control. For
>>> giggles, I tried the same setup with DCS (Digital Code Squelch) and voil?!
>>> It worked perfectly! No COS winking while sending DTMF. Since this node is
>>> just for neighborhood use, I can easily live with the DCS compromise.
>>>
>>> I?m fully aware there are other ways to skin these cats as hamvoip /
>>> Asterisk are crazy-powerful. CTCSS decode could be done inside the
>>> software. The PPT line could be inverted with a simple transistor. I
>>> suspect everyone?s Allstar setup ends up being a bit custom, this is simply
>>> what worked for me.
>>>
>>> One last tip, if you?re enabling Echolink. In addition to the detailed
>>> mods to /etc/asterisk/echolink.conf listed in https://www.hamvoip.org/
>>> echolink_howto.pdf <https://www.hamvoip.org/echolink_howto.pdf>, note the
>>> default echolink servers are outdated. They should be as follows:
>>>
>>> server1=nawest.echolink.org
>>> server2=nasouth.echolink.org
>>> server3=servers.echolink.org
>>> server4=backup.echolink.org <http://backup.echolink.org/>
>>>
>>> 73, N0KAI
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
> ------------------------------
>
> End of arm-allstar Digest, Vol 46, Issue 67
> *******************************************
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 31 Mar 2018 10:38:28 -0700
> From: chris novara <chris at redcrosscommunications.org>
> To: arm-allstar at hamvoip.org
> Subject: [arm-allstar] Full duplex audio through hub
> Message-ID:
> <7214D89D-0CC4-4D20-858E-906E0EB05268 at redcrosscommunications.org>
> Content-Type: text/plain; charset=us-ascii
>
> We are having trouble with full duplex audio through a Hub running in Psudo mode
>
> I enabled link to link and we are using option zero (if that even matters)
>
> Anything we are missing ?
>
> Audio is all noise and garble. But passes normal audio to multiple users just fine one at a time.
>
> Thoughts ?
>
> Chris Novara
> Phone: 541-778-1175
> Eugene, Oregon
> Email-Chris at redcrosscommunications.org
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 31 Mar 2018 22:11:37 -0400 (EDT)
> From: David McGough <kb4fxc at inttek.net>
> To: "\"chris novara via arm-allstar\"" <arm-allstar at hamvoip.org>
> Cc: chris novara <chris at redcrosscommunications.org>
> Subject: Re: [arm-allstar] Full duplex audio through hub
> Message-ID:
> <Pine.LNX.4.44.1803312205360.16814-100000 at goliath.inttek.net>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> Hi Chris,
>
> It's not clear to me what the problem is, or what you're trying to do?
>
> If you're wanting MULTIPLE simultaneous in-bound audio streams on a single
> pseudo node, all the user's audio will get mixed together, like several
> simultaneous conversations going on in a room---you can hear all of them
> at the same time.
>
> A pseudo node doesn't implements "Talk Groups" or similar methods
> segregate conversations, like found on Trunked radio repeaters, etc.
>
> 73, David KB4FXC
>
>
>
>> On Sat, 31 Mar 2018, "chris novara via arm-allstar" wrote:
>>
>> We are having trouble with full duplex audio through a Hub running in Psudo mode
>>
>> I enabled link to link and we are using option zero (if that even matters)
>>
>> Anything we are missing ?
>>
>> Audio is all noise and garble. But passes normal audio to multiple users just fine one at a time.
>>
>> Thoughts ?
>>
>> Chris Novara
>> Phone: 541-778-1175
>> Eugene, Oregon
>> Email-Chris at redcrosscommunications.org
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 31 Mar 2018 22:29:06 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Full duplex audio through hub
> Message-ID:
> <CAMp6vstuwCvZkT2u4d0Aoi7RFR86-wGzgjB1oNfcSCR6NA2chg at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Chris,
>
> When you ask a question you have to explain more about what the issue is.
> What you are trying to do? How you have things connected? You mentioned
> hub. The definition of a hub in Allstar could be 2 nodes both connected to
> a single node or 50 nodes all connected to a single node. It is really a
> lose definition. Why are you using duplex 0 and link to link? Are you
> connected to a repeater?
>
> We get so many questions that look like this! You have to take you time and
> give more details. We can't read minds!
>
> I put the thingamabob inside the whatchamacallit, turned the doohickey and
> the wuteveritis still doesn't work. Any ideas?
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Sat, Mar 31, 2018 at 1:38 PM, "chris novara via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> We are having trouble with full duplex audio through a Hub running in
>> Psudo mode
>>
>> I enabled link to link and we are using option zero (if that even matters)
>>
>> Anything we are missing ?
>>
>> Audio is all noise and garble. But passes normal audio to multiple users
>> just fine one at a time.
>>
>> Thoughts ?
>>
>> Chris Novara
>> Phone: 541-778-1175
>> Eugene, Oregon
>> Email-Chris at redcrosscommunications.org
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 31 Mar 2018 23:42:29 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] Pi3B+ greatly exceeds expectations!!!
> Message-ID:
> <CAMp6vss8w1XZmsjcdCFcgGPLS3+YrKcS11VBs4bM6awb3dMJNA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> ANNOUNCING A BIG BREAK THROUGH!
>
> We have lab tested a Pi3B+ this weekend and found it greatly exceeds
> expectations. A method to extract heat from the device has allowed us to
> push the processor speed to almost 4Ghz and keep the core temperature below
> about 60C. This has resulted in the ability to run four radio nodes
> flawlessly. We will be testing more but in the initial tests we did not
> connect a USB hub to connect further radios. We estimate at least eight
> radio nodes running a combination of Allstar, Echolink, and IRLP with
> multiple supermon connections would be possible. In our tests the load
> average never went above about .10.
>
> We will be publishing the full details in the coming weeks as well as
> enhanced software to support the higher speeds. The specialized cooling
> mechanism will be required and full construction details will be
> forthcoming. Attached are preliminary photos showing the specially designed
> "heat tube" which extracts heat from the Pi3B+ processor. It essentially
> sucks the heat out and transfers it to the large heat sink where a high
> speed fan dissipates the heat.
>
> The other benefit is that the Pi3B+ board even at these greatly extended
> speeds draws only slightly more current. The cooling fan actually draws
> more current than the Pi itself.
>
> This is a great break through that we will be sharing with the rest of the
> world. You may even hear about it on the evening news! Stay tuned for more
> information.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20180331/bdc8f9dd/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: DSC03249.jpg
> Type: image/jpeg
> Size: 54005 bytes
> Desc: not available
> URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20180331/bdc8f9dd/attachment.jpg>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: DSC03248.jpg
> Type: image/jpeg
> Size: 64634 bytes
> Desc: not available
> URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20180331/bdc8f9dd/attachment-0001.jpg>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
> ------------------------------
>
> End of arm-allstar Digest, Vol 46, Issue 68
> *******************************************
More information about the arm-allstar
mailing list