[arm-allstar] Time out timer and watchdog functions

Mon Feb 16 16:16:54 EST 2015

This is good news.
We now know the fault condition that cause my radio to warm its self.
Is there not a time out timer function in Asterisk that would cause this
fault to be ignored after a set time? I expect this type of thing must
happen often.

Bench testing is fun. :-)
I sure have more confidence in the BBB :-)

Thanks
Dave
VE7PKE

On Mon, Feb 16, 2015 at 10:39 AM, Tom Robson <ve7did at dccnet.com> wrote:

> We tested this morning and found out indeed it was my radio which I turned
> off was
> the culprit.  I was turning OFF only the radio which was asserting COS
> (active low)
> which was causing Daveś radio to go into constant transmit.
>
> Not a good situation... if a radio somehow gets turned off because of a
> power fail
> condition.  I think this could be fixed by having the COS be an active
> high.
> Hopefully the simpleusb can operate on an active high.
>
> As we are new to this stuff, it looks like it is good to play with the
> radios on
> the bench for a while...
>
>
> ...73 Tom ve7did
>
>
> Dave:
> > Perhaps it is me who is causing the problem.  Did you leave us connected
> up
> >  together? If so like Doug said if the COS is asserted it could keep
> your tx on.
> > Hereś the key, I turned my radio OFF probably around 23:00 last night
> and just did
> > the same tonight.   When my radio is OFF, COS will be asserted as it
> goes to ground
> > when COS is asserted with no power on.
>
>
>
> On Sun, 15 Feb 2015 16:22:40 -0800
> Dave Miller <ve7pke at gmail.com> wrote:
>
> > Doug and Dave,
> > Thanks for the information.
> > If it ever happens again I shall do some more digging.
> > My first concern was that I was locking up a high profile local repeater
> so
> > I just cycled the power first. I will be more methodical next time.
> >
> > I will try to answer what I can below.
> >
> >
> >
> > On Sun, Feb 15, 2015 at 4:00 PM, Doug Crompton <doug at crompton.com>
> wrote:
> >
> > > Dave,
> > >
> > >  I concur with Dave's response but it would be good to have more info.
> > > What happened to you is rare assuming it wasn't a locked up channel -
> you
> > > were connected to someone else that had there COS asserted
> indefinitely. I
> > > have not seen a 1.2.1 version BBB lockup like that.
> > >
> > > Ok that is good to know.
> >
> > > Were you connected to anyone else at the time?
> > >
> > Not that I know of. I guess its possible someone was connected to me.
> > Since its a simplex node could a connection from a duplex node cause an
> > issue?
> >
> > > If so the first thing to do is disconnect everyone else if it goes away
> > > you know it was not your system.
> > >
> > Good suggestion , Next time ;-)
> >
> > >
> > > Is the green light on the USB FOB blinking? If you pull the USB out and
> > > reinserted does it clear?
> > >
> > Don't know
> >
> > >
> > > Did you transmit on HF or any other band with high power in the
> vicinity?
> > >
> > > No that I recall. All I was doing yesterday was playing on RX with my
> > Hermes light. I have an Igate running 20 Watts in another building on
> > property but its on 2M this was on 220. I have had it running for  a few
> > days and had not noticed the issue.
> >
> > > If this should happen again log into the system and  enter the client -
> > > asterisk -rvvv
> > >
> > OK Will do
> >
> > >
> > > See if any errors are coming across the screen.  There are key and
> unkey
> > > command for simpleusb. At the clinet prompt type:
> > >
> > > susb key (or unkey)
> > >
> > > and see if you have control of the PTT. Of course leave it unkey.
> > >
> > > Remember if you are connected to a bunch of nodes and one of them
> hangs up
> > > you will also. The TX timeout is always a good idea. I set mine in the
> > > Alincos to 5 minutes but you could go shorter, just not so short you
> cut
> > > off normal transmissions.
> > >
> > > I have it set even shorter for now. I will lengthen once I get more
> > confidence in system
> >
> > > Also unrelated but the best way to run the Alinco's is in medium power
> > > with a small muffin fan over the heatsink. They will run all day like
> that.
> > > I would never use high power especially on a busy channel. You will
> > > eventually lose the final.
> > >
> > OK I was running low power. A fan will be a good thing eventually.
> >
> > Thanks
> > Dave
> > VE7PKE
> >
> > >
> > >
> > >
> > > *73 DougWA3DSPhttp://www.crompton.com/hamradio
> > > <http://www.crompton.com/hamradio>*
> > >
> > >
> > > ------------------------------
> > > Date: Sun, 15 Feb 2015 10:57:53 -0800
> > > From: ve7pke at gmail.com
> > > To: arm-allstar at hamvoip.org
> > > Subject: [arm-allstar] Time out timer and watchdog functions
> > >
> > >
> > > The node I am testing out went rogue last night.
> > > When I went into the shack the radio was stuck in TX and warm ;-)
> > > I have since enable the built in time out time in the alinco ;-)
> > > lsnodes show the time out time is enabled.
> > > How to do troubleshoot this.
> > > Thanks
> > > Dave
> > > VE7PKE
> > >
> > >
> > > _______________________________________________ arm-allstar mailing
> list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit
> the
> > > BBB web page -
> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
> > >
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB web page -
> > > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
> > >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150216/2d4f2b7a/attachment.html>