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