GormyGorm

Just an update, we (me and my friend) been doing some research and testing on this. This behavior seems to be limited to the DNA250 non color. We just tested a DNA200, and a DNA60, and they both can be powered on with full brightness and full controls through the USB port (obviously no vaping). Hooking the board up to a bench power supply, we found that the board will turn on completely with roughly 3.2v input, and it seems that the theory of USB power not being enough to power the board doesn't work out as along with the board being able to power on at 3.2v, the USB power and Input power are electrically isolated. All of that, along with the weird "fire button lockout" as I will refer to it leads us to believe that it is some sort of limp mode in the firmware. Honestly I have no clue why the board is set up the behave in such a way, I may contact Evolv directly to try to get an answer, as this has me interested, but for now, I am just happy that my board has turned out to not be DOA

Brightness was pushed to 100%, and I wasn't expecting the board to fire on USB power alone, but I was expecting the secondary functions of the fire button to still work (such as multi button functionality), which is one of the things that threw me off. It also appears that you misread the post, as I am not attempting to vape off USB, I was simply checking for basic functionality, and a dead fire button and dim screen was somewhat concerning.

So I have this DNA 250 non color board that has been sitting in storage, brand new, no balanced charging, atomizer/resistor, or battery connected, and when I connected it to the USB on my computer to check some stuff in escribe for it, it was picked up by escribe, but the screen was extremely dim, and the fire button does not show any input on the screen. I can just barely see that the up and down buttons are changing the wattage, but no input from the fire button. I also have a friend who reported the same behavior from a board in the same condition when I asked him if he has ever seen this. Is this normal behavior for a DNA 250 with nothing hooked up, and if not, does anyone know what could be causing the issue?