#So, your octopus caught on fire. What do you do now?
46 messages · Page 1 of 1 (latest)
is this an octopus or an octopus pro? If pro I can photograph my pro so you can see the wiring
Send a pic anyway, I'm going to order a Pro in case this one is broken broke
This is my pro with 48v
that has the advantage that you can go 48V later if you want and is not much more in price
also easier to flash IIRC
@severe rampart FYI this thread
Looks like you fried your 3.3v regulator. Which LEDs do you have there connected to signal and 5v?
is the probe wired correctly? or is the 3.3v line shorted to ground?
Pretty sure the driver configuration was the root of the problem. The 2209 drivers were configured for hardware SPI which is not supported. We actually had two of these boards blow up in the same manner yesterday in VC from two different users
Swapping the board to UART should fix the issue in theory, but it’s entirely possible that something else was wrong as well.
Probe and LED wiring were pre-done (part of a kit) so I doubt those are the issue, but it’s entirely possible.
I could see it being the jumpers for sure though I haven't seen that happen myself. The reason I was looking at the led header was that it is DuPont so polarity can be swapped and being a 2 pin connector it could go on either side of the 3 pins.
@toxic glacier @vast karma
Here's the board I got, is this the """o p t i m a l""" pro version? Or is there a more updated version?
There is a more updated version but that one is fine
That is a 1.0 F429
1.01 H723 is the latest
We actually had two blow up, both were formbot kits and the instructions for the electrical section makes no mention of the jumpers for the drivers
First was from a different user though. 3.3v regular blew up as well as the chip next to the USB-C port
This is the latest octopus pro BTW
That's weird. I've seen people start up and attempt to run with incorrect jumpers a couple dozen times over the years so I'm surprised to hear that's what caused the damage.
Though I could believe that some change in recent versions of the MCU allows this failure mode.
Very well could be. For all I know maybe it’s something else entirely. I’m almost tempted to try it on mine and replace that regulator if I blow it up. Also @severe rampart said he had seen this happen to someone else before as well so that’s at least a sign that it may be the root problem
Still seems a bit funky given the board comes preinstalled with all the jumpers
also @astral olive how much you want for that dead octopus? I'll put a new regulator on it
🙂
Send me your mailing address and I'll send it over. Consider it paid from the assistance and a Christmas gift.
I'm 99.99% confident that all of the data cables are connected properly.
@toxic glacier @vast karma
almost, one thing needs changed
move those two from motor power to power
motor-power is not connected on that board 🙂
perfect
looks good, if you need help, feel free to jump in a need help channel
I can help with the config 🙂
If you aren't using the bed output, you don't need power going to bed power, but you DO need power going to motor power