<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    your english is fine!<br>
    i apologize for responding so late.  i was on tdy and this is my
    first day back in the office.<br>
    not much of a christmas season for me!<br>
    <br>
    i am so grateful that the technical world is so willing to share
    their<br>
    expertise and knowledge with me.  i am very eager to try your
    suggestion.<br>
    at this point, i don't know what version firmware we have but will
    start<br>
    prodding this problem.  i feel confident that i am going in the
    right<br>
    direction with your help.<br>
    thank you very much.<br>
    <div class="moz-cite-prefix">On 12/19/2014 2:52 PM, Jaffet Martinez
      Pagan wrote:<br>
    </div>
    <blockquote
cite="mid:CAH4w05BnjtF8n7m370O_4eEzE0Cuet9s+v8k1RJNVTYG9CJitQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi:
        <div>Excuse my English. I hope you can understand me.</div>
        <div>First:</div>
        <div>You have to do the upgrades. The actual firmware is 3.10
          and update the Linux version  is 2.6. Some old basalts have
          Linux 2.4. You have to update to 2.6. Kinemetrics has a step
          by step process in the web page.<span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13px;line-height:19.2000007629395px"> </span><font
            color="#000000" face="sans-serif"><span
              style="line-height:19.2000007629395px">An incompatibility
              exists between this Rockhound version (v3.10) and Linux
              2.4, so you have to update to Linux 2.6. Go to the
              kinemetrics web page in the wiki section:rock family
              section</span></font></div>
        <div><font color="#000000" face="sans-serif"><span
              style="line-height:19.2000007629395px">Second:</span></font></div>
        <div><font color="#000000" face="sans-serif"><span
              style="line-height:19.2000007629395px">If the problem
              continue you have to reprogramming the CF card. If you can
              use a new CF is better. Please see the link: </span><span
              style="line-height:19.2000007629395px"><a
                moz-do-not-send="true"
href="http://www.cdwg.com/shop/products/Transcend-CF200I-Industrial-Grade-flash-memory-card-16-GB-CompactFlas/2431762.aspx?cm_mmc=email-_-Shipping_Conf-_-Body-_-Browse_Products">http://www.cdwg.com/shop/products/Transcend-CF200I-Industrial-Grade-flash-memory-card-16-GB-CompactFlas/2431762.aspx?cm_mmc=email-_-Shipping_Conf-_-Body-_-Browse_Products</a></span></font></div>
        <div><font color="#000000" face="sans-serif"><span
              style="line-height:19.2000007629395px">I have replaced two
              of them. I am using industrial grade. </span></font></div>
        <div><font color="#000000" face="sans-serif"><span
              style="line-height:19.2000007629395px">I hope this can
              help you</span></font></div>
        <div><font color="#000000" face="sans-serif"><span
              style="line-height:19.2000007629395px"><br>
            </span></font></div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">2014-12-19 19:40 GMT-04:00 lynn.kaisan
          <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:lynn.kaisan@noaa.gov" target="_blank">lynn.kaisan@noaa.gov</a>></span>:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"> thank you all!<br>
              <br>
              i do appreciate your help.<br>
              <br>
              very generous!<br>
              =================================
              <div>
                <div class="h5"><br>
                  <div>On 12/19/2014 1:26 PM, Merritt, Jonah wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div>
                        <div>Hello everybody,<br>
                          <br>
                        </div>
                        We are seeing the same issues! Jacob is
                        correct...if you reboot the Basalt (or Granite)
                        it loses contact with the gateway. This issue
                        seems to have manifested itself more is
                        subsequent Linux updates (we are running 2.6
                        update 6). We also almost exclusively use Raven
                        XE or GX440 modems.<br>
                        <br>
                        What I have found that all is well after
                        performing the "netconfig" script and setting up
                        NetWatcher. However, once you reboot you loose
                        all remote connectivity. If you get into the
                        Basalt locally via SSH and restart networking
                        (/etc/init.d/networking restart) all is well
                        again....until the datalogger reboots again. <br>
                        <br>
                      </div>
                      It should be noted that if you are able to log
                      into the Raven, you can successfully ping the
                      Basalt.<br>
                      <div><br>
                        I have contacted KMI about this and it was
                        suggested that the problem resides with the
                        modem and not the digitizer. I'm not convinced
                        that it's a Raven issue as we have used these
                        for several years without any significant
                        issues. It was also suggested that the
                        NetWatcher ping address be something else
                        besides the gateway address....say 8.8.8.8. I
                        did this without any resolution. <br>
                        <br>
                      </div>
                      <div>We will be experimenting with this over the
                        coming weeks, but I suspect that it is an issue
                        with the digitizer itself. I'll keep the group
                        posted.<br>
                        <br>
                      </div>
                      <div>Regards,<br>
                      </div>
                      <div><br>
                      </div>
                      <div class="gmail_extra"><br clear="all">
                        <div>
                          <div><font face="arial, helvetica, sans-serif">Jonah
                              Merritt <br>
                              US Geological Survey <br>
                              National Strong Motion Project <br>
                              345 Middlefield Rd. MS-977 <br>
                              Menlo Park, CA 94025 <br>
                              <a moz-do-not-send="true"
                                href="tel:%28650%29329-5696"
                                value="+16503295696" target="_blank">(650)329-5696</a>
                              (office) <br>
                              <a moz-do-not-send="true"
                                href="tel:%28650%29276-6579"
                                value="+16502766579" target="_blank">(650)276-6579</a>
                              (mobile) <br>
                              <a moz-do-not-send="true"
                                href="mailto:jmerritt@usgs.gov"
                                target="_blank">jmerritt@usgs.gov</a> </font><br>
                          </div>
                        </div>
                        <br>
                        <div class="gmail_quote">On Fri, Dec 19, 2014 at
                          4:43 PM, Jacob Crummey <span dir="ltr"><<a
                              moz-do-not-send="true"
                              href="mailto:jcrummey@usgs.gov"
                              target="_blank">jcrummey@usgs.gov</a>></span>
                          wrote:<br>
                          <blockquote class="gmail_quote"
                            style="margin:0 0 0 .8ex;border-left:1px
                            #ccc solid;padding-left:1ex">Hi Yolanda and
                            Lynn,<br>
                            <br>
                            I have seen some of our Basalts loose the
                            router info, specifically the gateway.  I
                            have yet to figure out what is causing
                            this.  It seems to happen on boot.  My guess
                            is the Basalt runs fine when initially set
                            up and then if it reboots, it looses the
                            routing table.<br>
                            <br>
                            Lynn, what version and update of Linux are
                            you using on the Basalt?  And are you using
                            the net-watcher feature that is set up in
                            the netconfig?<br>
                            <span><font color="#888888"><br>
                                -Jacob<br>
                              </font></span>
                            <div>
                              <div><br>
                                <br>
                                <br>
                                On Dec 19, 2014, at 2:22 PM, Yolanda
                                Prior <<a moz-do-not-send="true"
                                  href="mailto:yprior@usgs.gov"
                                  target="_blank">yprior@usgs.gov</a>>

                                wrote:<br>
                                <br>
                                > Have any end users of the Basalt
                                seen similar issues as Lynn below? Any<br>
                                > help for Lynn would be appreciated.
                                Thanks!<br>
                                ><br>
                                > Yolanda Prior<br>
                                > Engineering Technician<br>
                                > Albuquerque Seismological
                                Laboratory<br>
                                > <a moz-do-not-send="true"
                                  href="tel:%28505%29%20846-5662"
                                  value="+15058465662" target="_blank">(505)
                                  846-5662</a><br>
                                ><br>
                                ><br>
                                > -----Original Message-----<br>
                                > From: lynn.kaisan [mailto:<a
                                  moz-do-not-send="true"
                                  href="mailto:lynn.kaisan@noaa.gov"
                                  target="_blank">lynn.kaisan@noaa.gov</a>]<br>
                                > Sent: Thursday, December 18, 2014
                                3:01 PM<br>
                                > To: <a moz-do-not-send="true"
                                  href="mailto:yprior@usgs.gov"
                                  target="_blank">yprior@usgs.gov</a><br>
                                > Subject: help with basalt, pls?<br>
                                ><br>
                                > happy holidays, yolanda,<br>
                                ><br>
                                > my name is lynn and i work at the
                                pacific tsunami warning center.<br>
                                ><br>
                                > i am jumping into the maintenance
                                of our kinemetrics equipment without any<br>
                                > training and we seem to have a lot
                                of common problems amongst a few<br>
                                > stations.<br>
                                ><br>
                                > may i ask if you have had this
                                experience?<br>
                                ><br>
                                > i went to three sites that were not
                                transmitting seismic data.  at the<br>
                                > site, our IT guy found some
                                settings on the modem template that
                                seemed to<br>
                                > be the culprit.  things like too
                                short tcp idle and timeout time
                                settings.<br>
                                > another basalt lost its router
                                setting.  after changing those fields,
                                the<br>
                                > site would be happy and
                                transmitting data for a couple months or
                                weeks,<br>
                                > then...no data.  we are still able
                                to "see" the modem (ravens) and the<br>
                                > received signal strength indicator
                                is at acceptable levels.<br>
                                ><br>
                                > we use various models of the raven
                                x modem.  our sites are metrozet or<br>
                                > basalt equipment, sometimes both.<br>
                                ><br>
                                > if you have any idea what to check,
                                that would be great.  for one site,<br>
                                > the inject process had to be
                                restarted but it was not the fix for the<br>
                                > other two...very weird.<br>
                                ><br>
                                > thanks yolanda.  i know i am asking
                                a lot from you and i appreciate it.<br>
                                >
                                _______________________________________________<br>
                                > ANSS-netops mailing list<br>
                                > <a moz-do-not-send="true"
                                  href="mailto:ANSS-netops@geohazards.usgs.gov"
                                  target="_blank">ANSS-netops@geohazards.usgs.gov</a><br>
                                > <a moz-do-not-send="true"
                                  href="https://geohazards.usgs.gov/mailman/listinfo/anss-netops"
                                  target="_blank">https://geohazards.usgs.gov/mailman/listinfo/anss-netops</a><br>
                                <br>
_______________________________________________<br>
                                ANSS-netops mailing list<br>
                                <a moz-do-not-send="true"
                                  href="mailto:ANSS-netops@geohazards.usgs.gov"
                                  target="_blank">ANSS-netops@geohazards.usgs.gov</a><br>
                                <a moz-do-not-send="true"
                                  href="https://geohazards.usgs.gov/mailman/listinfo/anss-netops"
                                  target="_blank">https://geohazards.usgs.gov/mailman/listinfo/anss-netops</a><br>
                              </div>
                            </div>
                          </blockquote>
                        </div>
                        <br>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            ANSS-netops mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:ANSS-netops@geohazards.usgs.gov">ANSS-netops@geohazards.usgs.gov</a><br>
            <a moz-do-not-send="true"
              href="https://geohazards.usgs.gov/mailman/listinfo/anss-netops"
              target="_blank">https://geohazards.usgs.gov/mailman/listinfo/anss-netops</a><br>
            <br>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        <div class="gmail_signature">Ing. Jaffet Martinez Pagán, EIT<br>
          Puerto Rico Strong Motion Program<br>
          Civil Engeneering Department<br>
          Mayaguez Campus<br>
          University of Puerto Rico<br>
          787-832-4040 x 3341<br>
          Fax 787-831-2745</div>
      </div>
    </blockquote>
    <br>
  </body>
</html>