Octopus V1.1 detected but is unresponsive.
I keep getting the message "Octopus V1.1 detected but is unresponsive." whenever I try to flash my board. I already went in mainsail and set up the v-core 3 config but returned to the BTT configurator and tried to flash the firmware to the board as a final step. Fortunately the message came up and doesn't allow me to flash the firmware because Klipper isn't running on my board.
42 Replies
How are you flashing (SD card or DFU)?
DFU
additionally: I unplugged cables with connections that i custom-made in case they were faulty
did you remove everything except for power to the octopus and the usb C on octopus to USB A on pi?
yes
How are you powering the octopus? Is your pi connected to the Internet?
i have the board powered by the psu via the power cables
and the pi would already have to be connected to the internet to get to this step anyway so yes
No. You need network connection, but unless you have set the wifi or connected it to Ethernet you are just using the locally created hotspot and are not connected to the Internet
You need the Internet because the klipper firmware won't compile without it
well yes i am connected to the internet. i was just saying that I got here already with internet connected and rat os set up with the configuration
I would try flashing it again
I'll take another look and try to manually flash tonight
Yeah I'm not sure where to go from here. Flashing the octopus doesn't work whether I do it via SD card or DFU. The board seems to have all led's lit and indicated that it recognized the sd card with the blue led but doesn't seem to want to install the firmware.
I bought a replacement board to try even though I'm skeptical because the last board showed many signs of life
You could've just gone to mainsail and commented out your board in printer.cfg to confirm. I'm fairly sure this warning is just because the klipper c_helper didn't compile (this happens if the pi has no internet connection and you proceed to board flashing).
Bug is fixed in 2.1 which precompiles both klipper and moonraker code.
So what do I fix exactly?
My pi is connected to internet
Ignore the error, continue with the installation guide (go to mainsail,
/ instead of /configure)Yeah but it still doesn't do anything
What doesn't do anything?
I keep seeing mcu error
On mainsail
Which printer?
As if the board wasn't flashed
Is the octopus uncommented in your printer.cfg?
Vcore3
I will check actually. I believe it is
Okay, here's a few things i need before we can continue debugging:
1) Post your printer.cfg
2) Post a picture of your board
3) Open the command prompt (win + r, type "cmd", hit enter). Then do:
Password is
raspberry. Change ratos.local to your chosen hostname, if you changed it.
And post the results (it's a list of USB devices connected to the RPi)I will send updates when I get to this again tomorrow. It's a little late for me. I'm eager to get this up and running
okay this is what i have right now
I put the cables back in because it did not make a difference whether they were plugged in or not
Yeah no connection to the octopus
Remove this
REmove this, the board can't boot with the boot0 jumper in place, it'll always enter the DFU bootloader
Then reboot the board and it should be good to go
So do I remove both of those jumpers? Because both screenshots point to a different jumper
Yes, you remove both
One is for USB power (that will cause issues), the other is for the boot0 jumper (which will prevent the board from booting klipper)
That jumper (boot0) is also why you got that "Detected but is unresponsive" warning.
It should've been taken off after booting into dfu mode (there's a notice about this that's shown too late currently, it's fixed in 2.1)
okay that worked
thank you so much
my extruder reports 159 degrees
Sounds like a PT1000:
@miklschmidt mhh, i have the same problem. Board powered from power supply (as all other printer) and pi connected via USB C. Put the jumper for boot0, removed the jumper after reset but nothing.. the configuration can't detect the board. It stay with the older klipper (the board was on another machine)
Can’t detect or doesn’t flash?
Sorry. "Octopus 1.1 detected but unresponsive".
Click the reset button on the board, and go back to control board selection
(if you've removed the boot0 jumper)
So the board get flashed right but the configurator can detect it. It's the new 2.1 version