<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Geir,<br>
    <br>
    can you please try this: locate the speed setup in mcp2515.cpp, it's
    around line 115. Replace the setup for 100 KBPS by this:<br>
    <br>
    <tt>    case CAN_SPEED_100KBPS:</tt><tt><br>
    </tt><tt>      //cnf1=0x03; cnf2=0xfa; cnf3=0x87;</tt><tt><br>
    </tt><tt>      cnf1=0x44; cnf2=0xe5; cnf3=0x83;</tt><tt><br>
    </tt><tt>      break;</tt><br>
    <br>
    Then try again.<br>
    <br>
    <br>
    <div class="moz-cite-prefix">Am 30.12.2017 um 20:25 schrieb Geir
      Øyvind Vælidalo:<br>
    </div>
    <blockquote type="cite"
      cite="mid:330DDAC9-D6A4-4D11-B355-BA76E0FBACEB@validalo.net">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      I don’t have anything connected to CAN3. I could try to use CAN3
      instead of CAN2. It’s a long shot, but worth a try… I’ll look into
      it tomorrow.
      <div class=""><br class="">
      </div>
      <div class="">Geir<br class="">
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">30. des. 2017 kl. 19:29 skrev Greg D. <<a
                href="mailto:gregd2350@gmail.com" class=""
                moz-do-not-send="true">gregd2350@gmail.com</a>>:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <meta http-equiv="Content-Type" content="text/html;
                charset=utf-8" class="">
              <div text="#000000" bgcolor="#FFFFFF" class=""> Ha, I
                thought 100k was a typo for 1000, sorry...  Yeah, high
                speed overflow shouldn't be an issue.  On the other
                hand, low speed means that the time to receive a frame
                increases 10x, so that opens up a larger window if the
                chip doesn't like being talked to when actively
                receiving a frame.  Perhaps there is some interaction
                between the two sides of the chip?  For example, are
                there any registers that pertain to both busses?  I only
                use CAN3, with nothing connected to CAN2.<br class="">
                <br class="">
                Greg<br class="">
                <br class="">
                <br class="">
                <div class="moz-cite-prefix">Geir Øyvind Vælidalo wrote:<br
                    class="">
                </div>
                <blockquote type="cite"
                  cite="mid:0BD0279E-952D-46D0-BDAF-21A24250CEC6@validalo.net"
                  class="">Thanks Greg. This can-bus is only 100kbit and
                  uses less than 10% of the available capacity. It is a
                  low speed, low traffic bus. And currently I don’t do
                  any transmitting on it. 
                  <div class=""><br class="">
                  </div>
                  <div class="">I don’t see why it shouldn’t work for
                    me, then.</div>
                  <div class=""><br class="">
                  </div>
                  <div class="">Geir<br class="">
                    <div class=""><br class="">
                      <blockquote type="cite" class="">
                        <div class="">30. des. 2017 kl. 19:07 skrev Greg
                          D. <<a href="mailto:gregd2350@gmail.com"
                            class="" moz-do-not-send="true">gregd2350@gmail.com</a>>:</div>
                        <br class="Apple-interchange-newline">
                        <div class="">
                          <meta http-equiv="Content-Type"
                            content="text/html; charset=utf-8" class="">
                          <div text="#000000" bgcolor="#FFFFFF" class="">
                            For what it's worth, I've been using CAN3
                            for a long time with no lockups, running the
                            OBDII ECU code.  What is different, perhaps,
                            is that all the interactions are at 500k
                            speed (vs 1000), and generally alternate one
                            frame receive, followed by one frame
                            transmit.  So, overflow should never occur
                            unless the OBD2ECU code stops, at which
                            point I probably didn't care.  Standard vs
                            extended has not been a factor, in case
                            that's a question.<br class="">
                            <br class="">
                            The only issue we had was that if you try to
                            transmit several frames back-to-back, the
                            third and subsequent frame sent were all
                            duplicates of the second frame.  That was
                            fixed by adding a delay in the code, hoping
                            that it would be sufficient for the prior
                            frame to actually get sent.  Seems to work,
                            though those frames are typically only sent
                            at startup (request of VIN or ECU Name), not
                            hammered on.<br class="">
                            <br class="">
                            Greg</div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </blockquote>
                <br class="">
              </div>
              _______________________________________________<br
                class="">
              OvmsDev mailing list<br class="">
              <a href="mailto:OvmsDev@lists.teslaclub.hk" class=""
                moz-do-not-send="true">OvmsDev@lists.teslaclub.hk</a><br
                class="">
              <a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br
                class="">
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="160">-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
  </body>
</html>