#I am currently stuck at Installing USB-CAN-Bridge Klipper to my manta m8p v2/ebb sb2209 can (rp2040)
106 messages · Page 1 of 1 (latest)
Is lsusb seeing it?
not sure😅
You sure you actually flashed that manta successfully?
Looks like it's present...but still running not-usb-bridge firmware
(Unless there's some other h723 based device plugged in)
this was the first error message
Show your work
what exactly?
The part where you flashed the manta
ok i am still a bit confused. this is still in the "mainboard flashing " part of the guide.
The manta is your mainboard
yes
At the risk or over simplifying, youou configure the firmware for it, then you flash the firmware, then you start with the ip link stuff
This is the order of operations in the guide
So to get from your first screenshot to the second screenshot, you should have done some other steps in between
Please show your console output from when you did those steps
This part here, basically
No
You're skipping an entire section of the instructions
The one I screenshot
This down here (sorry I know its cut off)
You have to actually do that
wait a min let me check
I think i am not functioning correctly anymore, i will get some sleep and restart again tomorrow. i will come back and tell you if it worked.😐
Sounds like a plan
I finally managed to flash the mainboard and toolhead.🫣
as you said I left out a few steps, and on top of that I also missed the part where I am supposed to add my device id...😐
tomorrow I will take a look at the "final steps".
Amazing what a difference a bit of sleep makes
hi. its me again. i am now done with the final steps i think, but now i just get this
"Printer is not ready The klippy host software is attempting to connect. Please
retry in a few moments." error message. could you please save me again?😅
Can you show me the output from your canbus query, and what you put into your printer.cfg?
can i just copy paste the .cfg in chat or is there a better way?
Can just upload the whole file as an attachment
sry no clue how to get it😕
From ssh, when you got the uuids
I assume that blue "trying to connect" eventually turns to a red "failed to connect". Which mcu does it say failed?
mcu 'EBBCan': Unable to connect
Okay, that's good to some extent. It doesn't even try the ebb until it knows the main mcu is working
So at least we know one half of the system is working correctly 😛
Yes
do i need to run something before this line?
Alright, tap the reset button on the toolhead board, then run that again?
wait this should be the result i copied from yesterday
Found canbus_uuid=433218693816, Application: Klipper
if thats what you mean
That's the one from the main board, not the toolhead
Is that fresh? Or something you dug up from your notes
fresh
Okay
And that was a single tap on the reset? ( not a double tap)
Reason I ask, is that says its still in canboot (aka katapult)
Not klipper
Which strongly suggests that klipper still needs to be flashed onto it
single tap
Yep, so klipper doesn't appear to be on your toolhead board yet then
ok
You should redo the "flashing klipper" portion of esotericals toolhead guide
ok thanks ill try that, tomorrow😁
Okay klipper is now on the toolhead. sadly i just found the next error😐
What thermistor do you actually have? Where is it plugged in?
pt1000 pluged in at the tollhead board
but i am not sure if the pin in the cfg file is correct
Plugged into which port
If its in the 4 pin port, you need to use that whole block of "max31865" stuff in the sample config
it is
where can i find these?
What do you mean? They're in that block of stuff in the sample config for the toolhead board
Yes
And get rid of any conflicting lines above
(So the old sensor_pin and sensor_type)
Not because they'll actually do any harm: last line wins when there's repetition. But it's a good way to confuse yourself later
You sure you got the sensor_type line?
And just like that, you're off to the startup guide!
well i just tested the endstops (manually) x is always triggered, z (tap) wont respond but y works just fine, thats the only one not on the toolboard
Make sure you don't still have an conflicting x endstop pin in your main printer.cfg
And as for tap, you don't actually have a z endstop at all then, you have a z probe
Make sure you follow the setup instructions for tap to sort that out
true but shouldnt it show it as "triggerd when i move the toolhead up and refresh it?
i will do
The probe should
But if you haven't followed the instructions yet, klipper will still be looking for some other actual z endstop
Which obviously can't respond, since it's not there
ok i will look into it.
thanks i wouldnt have made it this far without you😁
You'd have figured it out eventually