[arm-allstar] Can someone listen to this?

Michael Staggs tausciam at gmail.com
Sun Mar 25 22:04:57 EST 2018 

Ok thanks. Stupid newbie mistake at my end. I managed to get it to give me my call sign (as node status), the time and even connect to a node. I didn’t hear anything on that node, but every time I get one of those -- Hungup 'DAHDI/pseudo-1017137996' then my node keys up PTT, transmits a click and beep. How do I stop it from doing that? I think it may work fine if I can get it to stop transmitting a click and beep every time I get one of those hungup messages. 

Sent from Mail for Windows 10

From: Doug Crompton via arm-allstar 
Sent: Sunday, March 25, 2018 9:25 PM
To: ARM Allstar
Cc: Doug Crompton
Subject: Re: [arm-allstar] Can someone listen to this?

Mike,

 You have the commands wrong!  All commands are preceded by '*'  - so it
would be *80  and *81 etv.  See the function howto at the hamvoip.org
website.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Sun, Mar 25, 2018 at 9:58 PM, "Michael Staggs via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Now I think we’re getting somewhere.  I tried that asterisk command line
> client like you suggested. I tried all the DTMF numbers and got an accurate
> decode. But, as you can see, I tried 80# and should have gotten system
> info. Instead, the node ignored it and kept pressing PTT and beeping once
> every time it processed one of these “hungup” messages.
>
> [Mar 25 20:54:14] NOTICE[431]: chan_simpleusb.c:2486 simpleusb_read: Got
> DTMF char 8
> [Mar 25 20:54:14] NOTICE[431]: chan_simpleusb.c:2486 simpleusb_read: Got
> DTMF char 0
> [Mar 25 20:54:14] NOTICE[431]: chan_simpleusb.c:2486 simpleusb_read: Got
> DTMF char #
>     -- Hungup 'DAHDI/pseudo-1017137996'
>     -- Hungup 'DAHDI/pseudo-1813806455'
>     -- Hungup 'DAHDI/pseudo-339115842'
>     -- Hungup 'DAHDI/pseudo-1401804253'
>     -- Hungup 'DAHDI/pseudo-550276261'
>     -- Hungup 'DAHDI/pseudo-253795532'
>     -- Hungup 'DAHDI/pseudo-2051900826'
>     -- Hungup 'DAHDI/pseudo-251788801'
>     -- Hungup 'DAHDI/pseudo-1752626256'
>
> Sent from Mail for Windows 10
>
> From: Doug Crompton via arm-allstar
> Sent: Sunday, March 25, 2018 8:28 PM
> To: ARM Allstar
> Cc: Doug Crompton
> Subject: Re: [arm-allstar] Can someone listen to this?
>
> Mike,
>
>  I think what you are experiencing is possibly something we are seeing in
> the FET driven PTT. Try putting a 10K resistor with a .01 uf capacitor in
> parallel from the gate of the 2n7000 to ground. The 2n7000 is often used as
> a DC switch like we are using it but we often forget it is a wideband part
> and can be used to generate RF well up into the HF spectrum. I suspect it
> is F getting into the FET that could be causing your problem.  See if this
> solves your problem.
>
> Also be aware that if you bring up the Asterisk client from the menu and
> you hit your DTMF buttons one by one you should see the tone decode in the
> text there. Press 0-9 ABCD #*  and you should see then accurately decode in
> the display.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Sun, Mar 25, 2018 at 3:16 PM, "Michael Staggs via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Yes, I quoted my original email to you. You answered me and I built that
> > PTT circuit exactly like you have it there. It was stuck on PTT and that
> > appears to have solved it. The PTT doesn’t stick anymore. It appears to
> > hear my DTMF tones and respond to them. I have the resistors on the
> Baofeng
> > exactly as described. I built the PTT circuit you described. When I send
> > DTMF tones to get status or the time, it hits PTT, clicks about 10 times,
> > lets up, hits PTT again, clicks about 10 times, lets up… and does that
> > about 10 times.
> >
> > You can hear what it’s doing here: https://instaud.io/1X0q
> >
> > So, what I’m asking is why it’s doing that? It’s responding to DTMF
> tones.
> > It is hearing me. But, that’s what I’m hearing back.
> >
> > Sent from Mail for Windows 10
> >
> > From: Doug Crompton via arm-allstar
> > Sent: Sunday, March 25, 2018 12:49 PM
> > To: ARM Allstar
> > Cc: Doug Crompton
> > Subject: Re: [arm-allstar] Can someone listen to this?
> >
> > Mike,
> >
> >   I think I answered this before as I remember you sending this email. I
> > would follow the simple FOB modification howto on the hamvoip.org web
> > page.
> > We don't remove any resistors and although you could do that the more you
> > mess around with the board the more you have the chance to screw
> something
> > up. There is also no reason to remove the connectors on the FOB. You can
> > solder directly to the connector leads.
> >
> > You must use the PTT circuit as described in the hamvoip.org howto
> > schematic as well as the diode in the COS line and use the resistors to
> > lower the audio levels between the 888 and the FOB.  You use  cosfrom=usb
> > NOT usbinvert.
> >
> > Also be aware that the 888 can introduce RF feedback into the circuit so
> > don't use the rubber duck antenna. It is best to use an external antenna
> a
> > distance away. Strange things can happen when you get RF back into the
> > electronics.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> > On Sun, Mar 25, 2018 at 11:32 AM, "Michael Staggs via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Sorry… Baofeng 888s
> > >
> > > I wired the chip up COS and PTT to the pins as shown here:
> > >
> > > http://www.garydion.com/projects/usb_fob/
> > >
> > > I wired the left and right jacks up according to here:
> > >
> > > https://hamvoip.org/hamradio/usb_fob_simple_modification/
> > > images/DSC02054.jpg
> > >
> > > And I wired the Baofeng 888s up according to these instructions:
> > >
> > > http://crompton.com/hamradio/baofeng888/New-888-mods.pdf
> > >
> > > I used the RPi2-3 Image Version 1.5rc16 image
> > >
> > >
> > > Sent from Mail for Windows 10
> > >
> > > From: Doug Crompton via arm-allstar
> > > Sent: Sunday, March 25, 2018 8:59 AM
> > > To: ARM Allstar
> > > Cc: Doug Crompton
> > > Subject: Re: [arm-allstar] Can someone listen to this?
> > >
> > > Mike,
> > >
> > >    I am not sure what you are doing there. What radio are you
> interfacing
> > > to? What circuit are you using? What FOB are you using? Did you modify
> > the
> > > FOB?
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >
> > >
> > > On Sun, Mar 25, 2018 at 1:58 AM, "Michael Staggs via arm-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > I’m making great progress with my node. When I plug the pi in, it
> shows
> > > up
> > > > on allstarlink as active. I had problems with it holding PTT down and
> > > just
> > > > clicking. So, I added the resistor, transistor and diode on PTT as in
> > the
> > > > schematic. Now, however, I’m getting this. I told it to give me the
> > > > status…or maybe the time. Instead, I got these short little
> > transmissions
> > > > of clicks. You can hear it here:
> > > >
> > > > https://instaud.io/1X0q
> > > >
> > > > On receive, I already have the 10k resistor. Is this because I didn’t
> > add
> > > > the 47k resistor and 10uf capacitor before it goes to the FOB? Or is
> > this
> > > > completely different? I really don’t want to keep buying electronic
> > > > supplies if it’s not going to work anyway, but if it’s truly what’s
> > > causing
> > > > this then I will buy them. I have a 68k resistor and 100uf capacitor,
> > but
> > > > those won’t work, will they?
> > > >
> > > > Sent from Mail for Windows 10
> > > >
> > > > _______________________________________________
> > > >
> > > > 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
> >
> > _______________________________________________
> >
> > 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

More information about the arm-allstar mailing list