• @thantik
    link
    English
    2
    edit-2
    1 year ago

    Does your ifconfig show a can0 device? After flashing? After reboot?

    • TristanOP
      link
      fedilink
      2
      edit-2
      1 year ago

      @thantik no, it does not. And I just realised that running the same canbus query script throws an error that I didn’t see before, saying no such device

      The /etc/network/interfaces.d/can0 file is there and correct though

      • @thantik
        link
        English
        2
        edit-2
        1 year ago

        And /etc/network/interfaces.d/can0 Looks a bit something like this?:

        allow-hotplug can0
        iface can0 can static
        bitrate 1000000
        up ifconfig $IFACE txqueuelen 128

        Sorry, Lemmy is mangling the shit out of formatting.

        It sounds like the CANBUS board might have some sort of defect, tbh.

        • TristanOP
          link
          fedilink
          21 year ago

          @thantik yup, it’s identical other than the mangled mastodon indent haha

          So just to check, when I reflash the board, it does show up in ifconfig but as soon as I make any changes in printer.cfg and hit save and restart, it’s now not in ifconfig

          • @thantik
            link
            English
            2
            edit-2
            1 year ago

            Save and Restart should only be restarting the firmware for Klipper/Klippy – ifconfig is part of the underlying Linux subsystem. It shouldn’t disappear from there just because you restarted Klipper. I’d be willing to bet the canbus board is either flashed with some wrong firmware option (check which microcontroller is being used on it!) – or that there is a physical defect with the board which is causing it to get stuck in programming mode on power cycle. I’m almost positive they aren’t using an external eeprom on that board, which would be my next guess (bad eeprom).

            From what I can discern, YOU aren’t doing anything wrong.

            • TristanOP
              link
              fedilink
              21 year ago

              @thantik the ebb is the rpi2040 so there’s only the one option for the microcontroller

              The issue happens with and without the ebb hooked up and the board works fine without canbus enabled so I’m sure that’s the right microcontroller

              Tomorrow I’ll go back through and maybe start from scratch, reflash the bootloaders and then try fresh from there

              In the mean time it all works if just using USB so I always have that fallback