[App_rpt-users] Repeater Stuck Locked open for 18 hrs

Pierre Martel petem001 at gmail.com
Tue Apr 24 20:23:53 UTC 2018


the trick is to have more then one way to skin the cat.  2 failure at the
same time is pretty rare, 3 failure even more. the only way I could see
such great amount of bad luck would be a direct hit from lightning.

take care of your health.


2018-04-24 15:24 GMT-04:00 Loren Tedford <loren at lorentedford.com>:

> Sorry Pierre for being short winded.. Let me get back to you Tuesday..
> Right at the moment Medical issues and relaxation needs to be my priority
> up until Surgery on Monday.. But yeah I don’t like pi’s that much but in
> hind site I understand where your coming from.. I don’t like hardware tot
> either.. But not sure If I am willing to take the chance on software
> again..
>
>
>
> Anyway I will catch every one when I can get back to concentrating on this
> topic later on..
>
>
>
> Loren Tedford (KC9ZHV)
> Phone Main: 1+ (631) 686 – 8878 Option 1
> Fax: 1-618-551-2755
> Email: loren at lorentedford.com
> Email: KC9ZHV at KC9ZHV.com
> http://www.lorentedford.com
> http://www.kc9zhv.com
> http://forum.kc9zhv.com
> http://hub.kc9zhv.com
> http://Ltcraft.net
> http://voipham.com
>
>
>
> *From: *Pierre Martel <petem001 at gmail.com>
> *Sent: *Tuesday, April 24, 2018 2:18 PM
>
> *To: *Users of Asterisk app_rpt <app_rpt-users at lists.allstarlink.org>
> *Subject: *Re: [App_rpt-users] Repeater Stuck Locked open for 18 hrs
>
>
>
> yup I did,
>
> Is my post so far off subject for you to ask that question.
>
> I use a similar method on my side but on an atmel. when I did the circuit
> the RPI was not yet available. Of course it does not do as much as the
> circuit I discribed but it does work. In fact beside the fact that I
> receive an email from my asterisk system, I usely dont even know that my
> node was stuck or that a uri was not working properly. Am I lazy.. yup..
>
>
>
> 2018-04-24 15:10 GMT-04:00 Loren Tedford <loren at lorentedford.com>:
>
> Hey Pierre by chance did you get to read the entire thread on this?
>
>
>
> Loren Tedford (KC9ZHV)
> Phone Main: 1+ (631) 686 – 8878 Option 1
> Fax: 1-618-551-2755
> Email: loren at lorentedford.com
> Email: KC9ZHV at KC9ZHV.com
> http://www.lorentedford.com
> http://www.kc9zhv.com
> http://forum.kc9zhv.com
> http://hub.kc9zhv.com
> http://Ltcraft.net
> http://voipham.com
>
>
>
> *From: *Pierre Martel <petem001 at gmail.com>
> *Sent: *Tuesday, April 24, 2018 2:08 PM
> *To: *Users of Asterisk app_rpt <app_rpt-users at lists.allstarlink.org>
>
> *Subject: *Re: [App_rpt-users] Repeater Stuck Locked open for 18 hrs
>
>
>
> I really dislike mechanical TOT. Why not use a small RPÏ that can monitor
> the 2 URI and use it to drive 2 or 3 relay? Those relay could, reset the
> MB, power off the radios, power off/on the router.
>
>
>
> A simple circuit that have a phototransistor that drive an input of the
> rpi would be easy to install, just use 2 small tube that cover  the geen
> led to feed the phototransistor (maybe a simple straw would do!)  . pretty
> sur that just a npn phototransistor could be driven directly with just a
> small pull up resistor to make the sensing part of the circuit and the rest
> is just simple coding either in python or in C.  Could even had automation
> like ping fail that reset the router/wifi link. you could even monitor the
> ASL system for activity and compare the 'software state' to the hardware
> state.
>
>
>
>
>
> 2018-04-24 13:25 GMT-04:00 Loren Tedford <loren at lorentedford.com>:
>
> The way it stands at the moment I am not entirely sure… Here is what I
> found during reinstallation the Memory failed a self check that I ran while
> putting Windows on it to stress test the machine.. The hard drive doesn’t
> seem to want to take any data at this point.. But before attempting to
> format reinstall on this machine the system booted still.. My guess is some
> thing mechanical could have caused Asterisks to have failed at this point..
> Honestly it seems to be a bit of a waste of my time to continue working on
> this machine when I have a second one exact specs sitting here ready to
> go.. We are doing the just in case TOT timer in the radios and this will
> affect autopatch users and anyone else that doesn’t let the system fully
> drop.. This is for my own re assurance that I have to the best of my
> ability solved the issue..
>
>
>
> Loren Tedford (KC9ZHV)
> Phone Main: 1+ (631) 686 – 8878 Option 1
> Fax: 1-618-551-2755
> Email: loren at lorentedford.com
> Email: KC9ZHV at KC9ZHV.com
> http://www.lorentedford.com
> http://www.kc9zhv.com
> http://forum.kc9zhv.com
> http://hub.kc9zhv.com
> http://Ltcraft.net
> http://voipham.com
>
>
>
> *From: *Steve Zingman <szingman at msgstor.com>
> *Sent: *Tuesday, April 24, 2018 12:14 PM
> *To: *app_rpt-users at lists.allstarlink.org
> *Subject: *Re: [App_rpt-users] Repeater Stuck Locked open for 18 hrs
>
>
>
> I'm a little confused, Did Asterisk fail or memory and possibly a
> motherboard?
>
> On 4/24/2018 12:50 PM, Loren Tedford wrote:
>
> Well technically it could have been controlled by the two meter repeater
> had the two meter repeater responded under normal circumstances.. What I am
> going to do for future repeater operations is to put TOT timers on the
> radio and I don’t care whether individuals on Autopatch that are calling
> Emergency services get disconnect etc because of radio tot.. No longer am I
> going to rely on asterisk to handle the TOT primarly.. Because of this
> experience.. We now know that we have fried some memory and possibly a
> motherboard but my testing at this point is stopping.. Moving forward with
> new gear..
>
>
>
> We originally turned off the TOT timer in the radios because of scenario
> involving autopatch and calling during severe weather..
>
>
>
> Loren Tedford (KC9ZHV)
> Phone Main: 1+ (631) 686 – 8878 Option 1
> Fax: 1-618-551-2755
> Email: loren at lorentedford.com
> Email: KC9ZHV at KC9ZHV.com
> http://www.lorentedford.com
> http://www.kc9zhv.com
> http://forum.kc9zhv.com
> http://hub.kc9zhv.com
> http://Ltcraft.net
> http://voipham.com
>
>
>
> *From: *DuaneVT . <selkie2 at comcast.net>
> *Sent: *Tuesday, April 24, 2018 11:46 AM
> *To: *app_rpt-users at lists.allstarlink.org
> *Subject: *Re: [App_rpt-users] Repeater Stuck Locked open for 18 hrs
>
>
>
> Radio Control was referenced as "Auxiliary Service".
>
>
>
> Per *Part 97 : **Sec. 97.201 Auxiliary station*
>
> (a) Any amateur station licensed to a holder of a Technician, General,
> Advanced or Amateur Extra Class operator license may be an auxiliary
> station. A holder of a Technician, General, Advanced or Amateur Extra Class
> operator license may be the control operator of an auxiliary station,
> subject to the privileges of the class of operator license held.
>
> (b) An auxiliary station may transmit only on the 2 m and shorter
> wavelength bands, except the 144.0–144.5 MHz, 145.8–146.0 MHz, 219–220 MHz,
> 222.00–222.15 MHz, 431–433 MHz, and 435–438 MHz segments.
>
> So 2 meters and above now.
>
> 73, Duane KA1LM
>
>
>
>
>
>
>
> _______________________________________________
>
> App_rpt-users mailing list
>
> App_rpt-users at lists.allstarlink.org
>
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
>
>
> To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
>
> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
>
>
>
>
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://lists.allstarlink.org/
> cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
> the page. Enter your email address and press the "Unsubscribe or edit
> options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
>
>
>
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://lists.allstarlink.org/
> cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
> the page. Enter your email address and press the "Unsubscribe or edit
> options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
>
>
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://lists.allstarlink.org/
> cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
> the page. Enter your email address and press the "Unsubscribe or edit
> options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20180424/c48a2099/attachment.html>


More information about the App_rpt-users mailing list