Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    CAN support broken in 1.17.3.b1?

    Scheduled Pinned Locked Moved Issues & Bugs
    canbusbug
    6 Posts 3 Posters 1.5k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      johand
      last edited by johand

      I am working on an application with CAN-communication. I have been using 1.14.0.b1 and everything is working fine. I now upgraded to latest firmware. When my WiPy is booting (before boot.py executes) all communication on the bus shuts down. Downgrading to 1.14.0.b1 makes the system working again. If I disconnects the TX wire between WiPy and CAN-transceiver receiving data is working and no problem on the bus.

      I have tried this on 2 different WiPy, 2 different expansion boards and 2 different CAN-tranceivers (SN65HVD230).

      Using P4/P3

      1 Reply Last reply Reply Quote 1
      • J Offline
        johand
        last edited by

        Have been thinking about this a bit more. Since the problem occur before the CAN object is instatiated, it must be somthing happening with the IO during boot that makes the tranceiver do someting bad with the bus.

        If I disconnect the TX wire between WiPy and tranceiver during boot and connect after boot everyting is fine.

        1 Reply Last reply Reply Quote 1
        • J Offline
          johand
          last edited by

          Some more testing...

          When trying this with some testequipment on my desk 1.14 works fine, but when rebooting my WiPy with 1.17 communication between the 2 other CAN nodes stops for a short time.

          When I try this in the environment where I plan to use the system (on a vehicle, J1939 bus) both 1.17 and 1.14 cause the same problem.

          Do I have something connected the wrong way? I use a board called CJMCU-230 with a SN65HVD230 tranceiver. 3v3 and GND connected to the expansion board. CRX goes to G24 and TRX to G11.

          Can this be a problem with the design of the CAN tranceiver board? Anything that can be done with the connection between WiPy and CJMCU-230?0_1523372259961_MVIMG_20180410_162817.jpg

          X 1 Reply Last reply Reply Quote 1
          • X Offline
            Xykon administrators @johand
            last edited by Xykon

            @johand Can you try adding a pull-up on the TX line? Try 100k first and then 10k.

            During init all the pins are configured by default as input / weak pulldown, so overriding this with a stronger external pull-up might help.

            You could also try looking into Pin.hold() to save the pin state prior to reset/deepsleep.

            Christian Ehlers

            J 1 Reply Last reply Reply Quote 1
            • J Offline
              johand @Xykon
              last edited by

              @xykon 100k didn´t help, but 10k seems OK. Haven´t been able to reproduce the issue with the resistor connected.

              Thanks!

              1 Reply Last reply Reply Quote 3
              • T Offline
                TravisT
                last edited by

                I have also been finding some CANbus issues on powerup.

                I have been finding similar quirks which cause system wide boot up to cause issues because the pycom module does not always work on the bus. Sometimes this also seems to cause faults for other system.

                I will be adding 10k pull up and pull downs in my design to help mitigate startup and reprogramming issues.

                What is the weak pull down resistors? I am guessing between 47k and 100k

                1 Reply Last reply Reply Quote 0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                • 1 / 1
                • First post
                  Last post

                Pycom on Twitter

                Pycom