Blackbox restarts by itself

[Steve]

Great question. The only time I do not use that switch is when I am doing heavy stress-testing. otherwise, I have not had any trouble. I noticed those specs and added one to my cart! Let us know how it works out.

[elemental]

You are welcome. You can find an inline USB switch on Amazon or Adafruit. I have the model from Adafruit and use it often. make sure it will carry at least 2A @ 5V.
Amazon Adafruit

Thanks for that Steve. I've been using USB switch the RIITOP USB Extension Cable also on Amazon,which stated that it supported 2A @5V. So I wonder why it didnt work....?
The one you linked on Amazon supports up to 3A @5V so I guess there is a better reliability?

[Steve]

You are welcome. You can find an inline USB switch on Amazon or Adafruit. I have the model from Adafruit and use it often. make sure it will carry at least 2A @ 5V.
Amazon Adafruit

[elemental]

Hello arteom and @Steve

Thanks and yes I figured out the issue being I used a USB extension cable switcher in order to switch the device on and off instead of pulling out the cable from the back of the device.

But that was most likely the problem and now it works just fine. Thank you for your responses.

[Steve]

arteom is 100% correct here. I cannot stress enough how important it is to properly power our devices. Use the supplied cable and wall adapter. Do not use extension cables, long USB runs, or USB cables that are not designed to carry power (2A @ 5V). Otherwise, you will experience the things you mention above. Can you confirm you are using the supplied cable? Where (in the world) are you located?

[arteom]

I picked up my blackbox second-hand and this was happening. I resolved it by using a better (thicker) usb cable. I would look at how you are powering it.

[elemental]

Hello

Not sure if anyone encountered the same issue but after a long session with blackbox it restarts out of the blue. This happened to me more frequently recently when sequencing and tweaking my sounds with ADSR and FX.

Maybe something to consider for future firmwares if this bug is already known?

Thanks