[arm-allstar] Node locking up

[Doug Crompton]

John,

 I think I would try the easiest path first since you have a new SD card.
That would at least eliminate a problem there. Burn a new card from the
online image, update it in the setup, and configure it with your parameters
and see how that goes.


*73 Doug*

*WA3DSP*

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


On Wed, Aug 22, 2018 at 1:31 PM, "John Arto via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi Doug,
> Please see below. Thank you for your help with this.
> John
>
> Message: 4
> Date: Wed, 22 Aug 2018 10:15:38 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Node locks up RX-keyed
> Message-ID:
>     <CAMp6vssm8e3pk9x_q8GYU3yC1qKmWDMWD4S-BwWDQAoAst2xMA at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> John,
>
>   That is a hard one to troubleshoot. From what you are saying Allstar was
> in fact telling it to key based on the simpleusb-tune-menu view
> indications. A couple of questions -
>
> Does this node have a good Internet connection? Yes, it is WIFI but I am
> going to run a cat -5 to it to see if this helps.
> Is there any high power RF nearby? Well, All this equipment is in a rack.
> The repeater is two shelves below the node and running 50 watts.
> Is there any possibility that it could be being keyed by someoneyou are
> connected to? Not that I am aware of.
> Does it happen when connected to other places? Yes, this happens when i am
> connected to other nodes also. sometimes after a day or so.
> Is it possible to substitute another Pi and/or URI? I do not have another
> at this time. I am looking at ordering them because I did want to make a
> portable node but have been holding off until i can get this straightened
> out.
> Also you could try another SD card as it is possible there could be some
> corruption there. Yes, I have a brand new card and was thinking of starting
> from scratch instead of just copying the image I made.
> Are you using the latest updates?* Yes, I run the update once a week.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio> *
>    On Wednesday, August 22, 2018, 10:00:16 AM PDT,
> arm-allstar-request at hamvoip.org <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. webtranceiver (wayne hale)
>   2. Node locks up RX-keyed (w7jca)
>   3. Re: webtranceiver (Doug Crompton)
>   4. Re: Node locks up RX-keyed (Doug Crompton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 21 Aug 2018 12:57:25 -0700
> From: wayne hale <waynehale at mac.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] webtranceiver
> Message-ID: <7DD7C74E-7DD3-4048-8E61-95BB34C1B2E6 at mac.com>
> Content-Type: text/plain; charset=utf-8
>
> Somebody must be working on the Webtranceiver issue.  Node 2000 is now
> reachable via webtranceiver and when I checked today (08/21/2018) 2000 was
> connected to 2040.  It recognized my login correctly but when I
> interrogated it with *70, it correctly id?d 2040 but recited ?space? as
> tranceive as on the screen there was a blank space between 2040 and W6IZK
> as being connected.
>
> No other nodes I tried will stay connected more than a second or two.
>
> Wayne W6IZK
>
> ------------------------------
>
> Message: 2
> Date: Wed, 22 Aug 2018 07:03:21 -0700
> From: "w7jca" <w7jca at yahoo.com>
> To: <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] Node locks up RX-keyed
> Message-ID: <001901d43a20$e3312400$a9936c00$@yahoo.com>
> Content-Type: text/plain;    charset="us-ascii"
>
>                 Good morning,
>
>
>
> I have a node that has been operating for a few weeks now. Every so often I
> would get complaints that the node is sending a dead carrier with no audio.
> I could never find out what was going on. It would work ok for a day or two
> but then I would get a complaint about this. I monitored the node last
> night
> and finally seen it happened. I was connected to the WIN System for about
> 20
> mins and then 2 guys were having a QSO and all of a sudden my node keyed up
> and stayed keyed. It said "Node 48467 RX-Keyed" (my node is 48467) and
> looking at the node the COS (composite) keyed, COS (input) keyed, all the
> others said cleared. I grabbed my HT and pushed the PTT and then everything
> cleared and went back to normal. I am at a loss of what is going on.
>
>
>
> My setup is as follows. I have a raspberry Pi 3 connected to a URI
> connected
> to a Motorola CDM 1550. This is setup as simplex mode that connects RF to
> my
> repeater which is a Yaesu DR-2x. The wires-x is turned off. I shutdown the
> digital side a few weeks ago because when I started getting the complaints,
> I thought the digital side was causing this. I have PL`s set on both TX &
> RX
> on the repeater as well as the node radio. When I actually saw the node
> lock
> up there was no transmission from the repeater or the node radio.
>
>
>
> Any thoughts?
>
>
>
> Thank you
>
>
>
> John, W7JCA
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 22 Aug 2018 10:06:48 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] webtranceiver
> Message-ID:
>     <CAMp6vssou81Tq5o5nUQqyxkTbkc8eroW5CBQhQKVUjRFOk__6A at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Wayne,
>
>  If you are talking about the web transceiver I don't know as it has been
> hit or miss for quite sometime due to enhanced security restrictions in
> browsers regarding java. If you are having general connection problems in
> your nodes make sure you are using the latest V1.5.3-40 update which is
> using DNS node lookup from our servers. If you are still having problems
> check that the node(s) are registered using check_reg.sh - if not we could
> issue a temporary registration line you could add that uses our servers.
> The next update, coming soon, will add all hamvoip V1.5 users to the
> hamvoip registration server.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Tue, Aug 21, 2018 at 3:57 PM, "wayne hale via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Somebody must be working on the Webtranceiver issue.  Node 2000 is now
> > reachable via webtranceiver and when I checked today (08/21/2018) 2000
> was
> > connected to 2040.  It recognized my login correctly but when I
> > interrogated it with *70, it correctly id?d 2040 but recited ?space? as
> > tranceive as on the screen there was a blank space between 2040 and W6IZK
> > as being connected.
> >
> > No other nodes I tried will stay connected more than a second or two.
> >
> > Wayne W6IZK
> > _______________________________________________
> >
> > 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: Wed, 22 Aug 2018 10:15:38 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Node locks up RX-keyed
> Message-ID:
>     <CAMp6vssm8e3pk9x_q8GYU3yC1qKmWDMWD4S-BwWDQAoAst2xMA at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> John,
>
>   That is a hard one to troubleshoot. From what you are saying Allstar was
> in fact telling it to key based on the simpleusb-tune-menu view
> indications. A couple of questions -
>
> Does this node have a good Internet connection? Is there any high power RF
> nearby? Is there any possibility that it could be being keyed by someone
> you are connected to? Does it happen when connected to other places? *Is it
> possible to substitute another Pi and/or URI? Also you could try another SD
> card as it is possible there could be some corruption there. Are you using
> the latest updates?*
>
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio> *
>
> On Wed, Aug 22, 2018 at 10:03 AM, "w7jca via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> >                Good morning,
> >
> >
> >
> > I have a node that has been operating for a few weeks now. Every so
> often I
> > would get complaints that the node is sending a dead carrier with no
> audio.
> > I could never find out what was going on. It would work ok for a day or
> two
> > but then I would get a complaint about this. I monitored the node last
> > night
> > and finally seen it happened. I was connected to the WIN System for about
> > 20
> > mins and then 2 guys were having a QSO and all of a sudden my node keyed
> up
> > and stayed keyed. It said "Node 48467 RX-Keyed" (my node is 48467) and
> > looking at the node the COS (composite) keyed, COS (input) keyed, all the
> > others said cleared. I grabbed my HT and pushed the PTT and then
> everything
> > cleared and went back to normal. I am at a loss of what is going on.
> >
> >
> >
> > My setup is as follows. I have a raspberry Pi 3 connected to a URI
> > connected
> > to a Motorola CDM 1550. This is setup as simplex mode that connects RF to
> > my
> > repeater which is a Yaesu DR-2x. The wires-x is turned off. I shutdown
> the
> > digital side a few weeks ago because when I started getting the
> complaints,
> > I thought the digital side was causing this. I have PL`s set on both TX &
> > RX
> > on the repeater as well as the node radio. When I actually saw the node
> > lock
> > up there was no transmission from the repeater or the node radio.
> >
> >
> >
> > Any thoughts?
> >
> >
> >
> > Thank you
> >
> >
> >
> > John, W7JCA
> >
> > _______________________________________________
> >
> > 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 51, Issue 62
> *******************************************
>
> _______________________________________________
>
> 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