EBB42 + Cartographer

[Sliver]

Basic Information:

Printer Model: BLV mgn Cube

klippy (2).log (121.6 KB)

MCU / Printerboard: Octopus f446
Host / SBC OrangePi
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Please help, ebb42 is on my head, I bought a cartographer (or rather, a clone from IDM), connected everything according to the instructions docs.cartographer3d.com but if I connect the cartographer, the printer does not start at all, everything is fine without it, I can’t get the canbus_uuid of the cartographer either, it gives an error

mcu ‘EBBCan’: Unable to connect
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer

~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0

Traceback (most recent call last):
File “/home/orangepi/klippy-env/lib/python3.9/site-packages/can/interfaces/socketcan/socketcan.py”, line 679, in _send_once
sent = self.socket.send(data)
OSError: [Errno 105] No buffer space available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/home/orangepi/klipper/scripts/canbus_query.py”, line 64, in
main()
File “/home/orangepi/klipper/scripts/canbus_query.py”, line 61, in main
query_unassigned(canbus_iface)
File “/home/orangepi/klipper/scripts/canbus_query.py”, line 25, in query_unassigned
bus.send(msg)
File “/home/orangepi/klippy-env/lib/python3.9/site-packages/can/interfaces/socketcan/socketcan.py”, line 658, in send
sent = self._send_once(data, msg.channel)
File “/home/orangepi/klippy-env/lib/python3.9/site-packages/can/interfaces/socketcan/socketcan.py”, line 681, in _send_once
raise can.CanError(“Failed to transmit: %s” % exc)
can.CanError: Failed to transmit: [Errno 105] No buffer space available

sudo ifconfig -a
can0: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 128 (UNSPEC)
RX packets 1124 bytes 8046 (7.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 188 bytes 894 (894.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[mdewayne7]

Hi Sliver, and welcome. I cannot offer direct help as I do not know enough, but I can direct you a few places…

The "dirty" Flag and the Team's Position

Background Klipper’s main-line code is published on GitHub. Upon start, Klipper checks if the locally installed code is the same as the code published in this official repository. If not, the code is marked as dirty, and a respective notification is placed in the klippy.log. This warning can look like: Git version: 'v0.12.0-439-g1fc6d214-dirty' Untracked files: klippy/extras/autotune_tmc.py, klippy/extras/gcode_shell_command.py, klippy/extras/motor_constants.py Modified files: klippy/chelper/s…

and…

Contact

Though using a clone, not sure they’ll be able to help…

Also, consider reading:

Cartographer V3/V4: Reverse engineering

I did try all four combinations and the only one that works for me is the Carto supplied Katapult with Carto supplied Klipper. I was not able to get the other three to enter bootloader via CAN. I wonder if perhaps @Esoterical managed to make it work reliably? Thank you. UPDATE: I can confirm that https://github.com/Klipper3d/klipper/pull/7251 fixes the issue.

Eddy Current Inductive probe - Klipper documentation

Good luck!

[Sliver]

Thanks a lot for the direction, I’m going to read, otherwise I don’t have any ideas left, I’ve been struggling with it for the third day…

[cardoc]

Exactly what hardware did you buy?

Is it advertised to be equivalent or did you get bad advice?

[mdewayne7]

I had thought about your issue a little more, and while I have no experience utilizing CAN, my gut instinct(from what I’ve read, which I do not fully comprehend) is that maybe the carto clone isn’t properly terminated or in the CAN in the right place. Otherwise maybe flashed incorrectly?

If you’re not familiar with this guide, I’ve read only good things, so maybe you can find some help here:

Home

Otherwise if you want to just get back to printing, revert to whatever probe you were using before. While rapid scanning is nifty and all, it’s not that big of a timesaver until you’ve got a bulletproof setup.

[Sliver]

Thank you all so much for your help and advice!!! After rereading a huge amount of information, I came to a decision… The mapper is flashed in can mode by default and in this mode the bitrate is 1 Mbit, my Octopus and EBB42 were flashed to a bitrate of 0.5Mbit, because of this disagreement, nothing worked, as soon as I flashed the MCU and EBB42 to a bitrate of 1 Mbit, everything worked!

~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
Found canbus_uuid=ea18f90fd0ca, Application: Klipper - Cartographer

Found canbus_uuid=aaab58deece6, Application: Klipper - EBB42