#Klipper failing

1127 messages · Page 2 of 2 (latest)

marble blade
#

I want to check something

dim elk
#

Working ID

marble blade
#

What happens if you tap the reset button on the pico, and then run the ls command again?

dim elk
#

Same

#

Wait. It is different

#

It got longer

manic bane
#

it's the same ID, just wrapped differently.

dim elk
#

I figured but wanted to be accurate

manic bane
#

the key thing is that we're not seeing the rp2040 there

#

what do you see with lsusb

dim elk
#

Still not right

marble blade
#

Can you show us

cd ~/klipper
make menuconfig
manic bane
#

and can we confirm that this is definitely the printer that you're working on, matches the name you've SSH'd into too

dim elk
dim elk
#

192.168.0.59 shauno.local

marble blade
#

Seems right

dim elk
manic bane
#

and we had some issues yesterday with making sure the correct jumpers were installed

marble blade
#

Does it show up in lsusb if you put it back into bootsel?

dim elk
#

How do I put it into bootsel

#

I closed the menuconfig

#

Should I try to recompile it?

manic bane
#

remove boot jumper, press reset, run lsusb

dim elk
marble blade
#

Remove is normal operation

manic bane
#

sorry. yes.

dim elk
#

So what should I do

manic bane
#

install boot jumper, press reset, run lsusb

dim elk
#

Identical

marble blade
#

So you've got something more fundamental going on. Bad usb cable, lack of power to the pico, stuff like that

manic bane
#

we got to this point yesterday. what's changed since then :/

dim elk
#

I was able to out the klipper to mainsail and flashed it to the pico through the USB instead

#

It IS still connected to the USB to the computer

manic bane
#

wait- the pico is connected to your laptop?

dim elk
#

Uhh, yes.

#

Unjumper the boot, connect it to the board and plug into the Pi?

manic bane
#

that explains not finding it just now, at least

dim elk
#

One second

marble blade
#

The ultimate bad usb cable

dim elk
#

Sorry for all the "unforced errors" here

manic bane
#

i mean we can continue with the laptop-to-pico flashing method, but i'd personally prefer to have working flashing from the pi/cb1

dim elk
#

Does it matter WHAT USB port it is in?

manic bane
#

if the flash took, then we need the pico plugged into the pi without the boot jumper, and to be running the ls /dev... command

marble blade
dim elk
#

ls /dev/serial/by-id/* ?

manic bane
#

ls -l /dev/serial/by-id/

dim elk
#

I have two IDs

manic bane
#

if all is bueno, there should a second ID in there with klipper in it

marble blade
manic bane
#

fair one

#

i have them as macros on my keyboard. will edit.

dim elk
#

The top one looks correct

manic bane
#

yep. so that top one is what goes in your config

dim elk
#

She's awake!

#

Alright. I will replicate this on the other ones

#

So, flash through the USB but dont forget to reconnect the USB like a dummy.

#

Thanks for the help

dim elk
#

So on one printer, the X and Y controls move at an angle

dim elk
#

It homes in the correct direction

manic bane
#

can you show a video of what you mean?

dim elk
marble blade
# dim elk

so I take it you didn't do the startup tests on that printer

#

(one motor isn't running, most likely)

marble blade
#

might be worth checking if they still buzz

#

because diagonal movement almost always means one of them isn't moving

#

(or something else that has a similar effect, like a pulley not being tightened onto the shaft or something)

dim elk
#

Nope, you're right. The Y

#

I figured it out. I thought the direction motor was going the wrong way and inverted a pin, but I inverted the enable pin not direction pin

marble blade
#

ah, yep. that'll do it

dim elk
#

Thank you, again

marble blade
# dim elk Thank you, again

On a side note, that's interesting that the motor directions don't match. Are the kits not all using the same motors?

dim elk
#

Two more printers!

dim elk
#

So the voron display flash is failing. I am following the steps John took, and I made it to "make serialflash FLASH_DEVICE=0483:df11" and it says Error 1.

When I am doing the menuconfig, am I supposed to select which serial the usb is connected to? If so how do I figure that out. Johns instructions had me set the communication interface to "Serial (on USART1 PA10/PA0)?

The LSUSB has the serial port on Bus 8

#

Also, all the printers so far are running since I got past the klippy issue. The last remaning piece of the puzzle is the display flash

prime harness
marble blade
marble blade
prime harness
dim elk
#

Corrected the settings

#

Still an issue but it connected

make: *** [Makefile:72: out/klipper.elf] Error 1

marble blade
#

And the optional features screen?

dim elk
#

Yes

#

I had the bootloader selected

marble blade
#

Try again with that fixed?

dim elk
#

Okay

#

Still saying in FS mode. I got an error 255 but the instructions said it would not be an issue if I got an ID. I don't think I got one

marble blade
#

Show the whole flash

#

Error 255 isn't inherently a concern, but I need to know what was before that

dim elk
#

I closed the window. I will do it again

marble blade
#

"No dfu capable dfu devices available"

#

Did you have the display in dfu mode ?

dim elk
#

Well, no. The jumper is on it. I thought I saw it on the list earlier

#

Nothing shows up in the DFU til

marble blade
#

Well, sounds to me like you need to get it back into dfu then

#

Might just be a power cycle

#

(I can't remember. Is there a reset button on those displays?)

dim elk
#

I power cycled the printer and it is working now

#

No errors

marble blade
#

You also left a word out of your command though

dim elk
#

fixing

#

Download done with an error

marble blade
#

Thats better

dim elk
#

I think that worked. Out of FS mode

marble blade
#

That version (with the download complete) is more what the instructions are talking about

dim elk
#

Last question, it says I need the .cfg file
home/biqu/printer_data/config/V0Display.cfg

marble blade
#

Sure

dim elk
#

I think I found it

marble blade
#

Yep