Printer Model: Homemade CoreXYHybrid-Markforged
MCU / Printerboard: Optopus Max EZ
Host / SBC Raspi
klippy.log klippy.log (38.2 KB)
Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
Hey all, I’ve been building this for months now. I have everything working and been printing parts for it. I have the EbbCam36 board on the toolhead and the cam bus has been working fine so far. Have been setting up a tool rack for more heads. Rack moves up and down with a manual_stepper which I just got working today. All was fine moving the x and y axis, homing the moving Z bed and using the gantry level.
I got up and went in another room for a while and when I came back octoprint complained the printer was not ready. Tried everything and found it lost com with the canbuss. Finally reverted to a config without the cambuss and the printer board readies up and printer works.
The EBBCam36 board has one led on and bright and one led right by the power/Can connector is on very dim. Dont know if it was like that before.
Does anyone know of a way to troubleshoot the cambus to find out if something is wrong? Did not touch anything and it just quit.
Thanks
…
The problem is, there is no information in the log. From the log. There is no data on whether the system has ever successfully started.
So, as far as I can see, it does not start because it looks like CAN does not respond.
I can only guess, there is some wiring issue.
From the schematics and your description of the LED status.
I suspect the bright one is a 3.3V power LED (green).
And the second one, is status, SWDIO LED (blue).
Well, it should be slightly less bright, but shine.
I can only guess that it may have an issue with startup, or your environment is very bright.
Anyway, a power cycle should clear the situation.
Git version: ‘v0.12.0-404-g80d185c94’
You may want to bump the Klipper and firmware versions, it will give you and us some additional CAN-related metrics.
This is not directly related, just general recommendations, feel free to ignore them.
Where did you get that
You may want to upgrade your system a little, it looks like some Debian 10 Buster.
If it is a Raspberry PI, it can be pretty simple.
I did power cycle many times, no help. Like I said everything was fine, working fine. After sitting for a few minutes came back and it had quit. Nothing touched at all. I guess have to start from scratch.
I guess your simple way is to connect EBB by USB and see if it works at all.
I’m not sure how the board flashed for CAN only will look with USB, but you should be able to at least enter the DFU and flash it.
If DFU works and you are able to flash it, it is most probably alive, and there is an issue with power/wiring.
So, if you want to check if it is working at all, you should connect only USB cable and set the VUSB jumper.
To update: I loaded everything from scratch and finally got it done. Still not sure what happened but loading everything the same as before got it to work again. No idea what happened.
