Chuck, I fixed all my issues. I didn't realize the difference between a NMEA & Garmin sentence. I deselected all sentences that started with "P" in the SNSRCFG program, reloaded the GPS file, and my warning went away. I was able to update the firmware with your advice. Thanks again for your help, Corey On 11/14/2014 11:51 PM, app_rpt-users-request@ohnosec.org wrote:
Send App_rpt-users mailing list submissions to app_rpt-users@ohnosec.org
To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request@ohnosec.org
You can reach the person managing the list at app_rpt-users-owner@ohnosec.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..."
Today's Topics:
1. Re: EchoLink Policy Reminder (Johnny Keeker) 2. Voter board (Corey) 3. Re: Voter board (Chuck Henderson) 4. Re: Voter board (Chuck Henderson) 5. Re: Voter board (Chuck Henderson)
----------------------------------------------------------------------
Message: 1 Date: Fri, 14 Nov 2014 14:44:54 -0800 From: Johnny Keeker <cypresstower@yahoo.com> To: kk6ecm <kk6ecm@gmail.com>, Kirk Just Kirk <wb6egr@gmail.com> Cc: app_rpt mailing list <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] EchoLink Policy Reminder Message-ID: <1416005094.33956.YahooMailBasic@web163604.mail.gq1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1
When they kill our accounts we'll say EchoStink Stunk -------------------------------------------- On Tue, 11/11/14, Kirk Just Kirk <wb6egr@gmail.com> wrote:
Subject: Re: [App_rpt-users] EchoLink Policy Reminder To: "kk6ecm" <kk6ecm@gmail.com> Cc: "app_rpt mailing list" <app_rpt-users@ohnosec.org> Date: Tuesday, November 11, 2014, 7:08 PM
They can close/kill my account anytime. EchoStink sounds horrible most of the time...constant drivebys from dingalings that connect and disconnect over and over and say nothing...or connect at 3 in the morning and call CQ CQ. For 5 minutes.....I am so tired of that shit I could delete it tonight.
On Nov 11, 2014 2:00 PM, "kk6ecm" <kk6ecm@gmail.com> wrote: Can anyone shed light on this Echolink requirement and Allstar? I'm not sure what makes us compliant. We have Echolink enabled on our repeater... I know of no way a non-ham could link in during an Echolink connection. Is there a way of setting app_rpt so an Echolink connection precludes all others? Also, Echolink has Apps for the PC, Android, and the iPhone/iPad... Their PC app (phones are RF, but not ham) seems to invalidate their rf only policy, although they do verify a license before granting a node number. What am I missing?
Thanks,Bobkk6ecm Sent from iPad
---------- Forwarded message ---------- From: EchoLink Support <support@echolink.org> Date: Wed, Sep 3, 2014 at 9:14 AM Subject: EchoLink Policy Reminder To:
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser).? This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73
EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.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.
-----Inline Attachment Follows-----
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.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.
------------------------------
Message: 2 Date: Fri, 14 Nov 2014 23:10:57 -0700 From: Corey <kc7mrq@bresnan.net> To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Voter board Message-ID: <5466EE71.1090107@bresnan.net> Content-Type: text/plain; charset=utf-8; format=flowed
I built a through hole voter board and interfaced it to a GPS 18 LVC and my server. I set the board up as a master, transmit. The LED shows the GPS locked and 98 command shows the GPS, but I am getting the following error when telnetting into the board:
Warning: GPS Data time period elapsed.
The error is timestamped and occurs every second. I made sure the data format was NMEA per archived messages on here by connecting the GPS to SNSRCFG. The config appears to be set up correctly. What other areas do I need to look at to fix this warning?
I did notice you can choose quite a few NMEA messages in the SNSRCFG profile. Does it matter if all are checked?
I have a second issue with updating the firmware. The board is at Rev 1.41. I tried updating it, but haven't had any luck so far. Nothing happens when I click on the "capture target" button after resetting the voter board. The target ip is the voter board and the bootloader ip in the voter is my laptop with ENC_Loader.
The IC(s) were originally programmed by a friend in another state so I never experienced what it take to do the initial programming.
Thanks for your help, Corey
------------------------------
Message: 3 Date: Sat, 15 Nov 2014 00:27:46 -0600 From: Chuck Henderson <rpt2@chuck.midlandsnetworking.com> To: Corey <kc7mrq@bresnan.net> Cc: app_rpt mailing list <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] Voter board Message-ID: <CADEYVwj=UeTqkKzfERG8Oz+Rj+XZKYH649TCjaYYqtoUFoQ7og@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
set the bootloader IP to be the same as the voter board IP, or make it different than anything else on the network. It is the IP that the voter board uses when it is running the bootloader code. It can not have the same IP as your laptop. That will not work.
On Sat, Nov 15, 2014 at 12:10 AM, Corey <kc7mrq@bresnan.net> wrote:
I built a through hole voter board and interfaced it to a GPS 18 LVC and my server. I set the board up as a master, transmit. The LED shows the GPS locked and 98 command shows the GPS, but I am getting the following error when telnetting into the board:
Warning: GPS Data time period elapsed.
The error is timestamped and occurs every second. I made sure the data format was NMEA per archived messages on here by connecting the GPS to SNSRCFG. The config appears to be set up correctly. What other areas do I need to look at to fix this warning?
I did notice you can choose quite a few NMEA messages in the SNSRCFG profile. Does it matter if all are checked?
I have a second issue with updating the firmware. The board is at Rev 1.41. I tried updating it, but haven't had any luck so far. Nothing happens when I click on the "capture target" button after resetting the voter board. The target ip is the voter board and the bootloader ip in the voter is my laptop with ENC_Loader.
The IC(s) were originally programmed by a friend in another state so I never experienced what it take to do the initial programming.
Thanks for your help, Corey _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.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.