James

Has this happened to anyone who is not on 8/21? The battery meter has changed because that message indicates it accidentally restarted without savings its settings. Most likely it indicates a firmware bug. Do you have any special settings presently? If so, could you attach them please?

The board should be totally fine doing Battery Analyzer. IIRC we did the stock curves using a LiPo at 50W, using resistor blocks and no fan. The Board Temperature sensor will protect well before the board should have any problems, and even at high powers it takes a while to get that hot. I admit I've not tested with a fan present, but I can't see that making a difference unless the Board Temperature sensor was being cooled by the fan better than the rest of the board... What power were you doing the test at? Hmm. Send Help Desk a ticket for a replacement, and have them send the board to us to take a look at. We'll see what we can see. Thanks! James

LiFePO4 has very little real capacity above 3.3V. It's mostly useful to know when the charging is complete. In my testing it took about 1 puff to get from 3.6V back down to 3.3V. I got the LiFePO4 curve in EScribe by using Battery Analyzer.

Oh... If it's inside VirtualBox, make sure you let the virtualized OS see that unknown device. It's actually the bootloader (failsafe) USB.

Tools->Reboot->Hard Reboot does not work? That only requires the bootloader not the firmware. The fact that it's responding with a Product ID of 0x8405 suggests the bootloader is not entirely dead.. (What version did you have before? Anything 7/29 R1 or newer has the same core firmware and so uploading doesn't put into bootloader mode.)

blueridgedog: Have you tried Tools->Update Firmware? If it fails half-way through, you can use that to manually reupload it.

I've added the ability to put the new and old coil ohms in a custom location on-screen to the 2015-08-21 firmware.

I've added the customizable lock clicks to the 2015-08-21 firmware.

Posted 2015-08-21. Main features are localizations, customizable lock clicks, and customizable position for showing the new/old Ohms in the New Coil Yes/No? message.

Change the charging brightness from 0%. It goes to the charging screen at the time when it would normally turn the screen off (if charging).

Could you take a video of this?

techbearus, if you are using three different atomizers in the same profile you're probably better off with Ohm Lock off, as if it is working right that means your 510 is relatively stable/good. Ohm Lock isn't meant to be used if you are switching atomizers on the same profile. (Some people set up one profile per atomizer, though.)

If anyone is interested in helping translate EScribe into their native language, I've posted a Github: https://github.com/Evolvapor/EScribeTranslations You can edit these and send pull requests for changes. (Or use a software like TortoiseGit, or e-mail.) It being on Github should make it easier to make corrections etc. hopefully. (Does anyone know if there is a better service for this for translations?) Thank you!

Most of the benefit of logging in is for manufacturers. Production Utility (in Tools) requires being logged in. Production Utility does link the serial number to a manufacturer, so that when you click Get Information, it will say the name they entered for their account as who it was produced by. On request, we can also mark an account's manufacturer profile as 'confirmed'. Doing this makes it say "Confirmed" in Get Information, which serves as a bit of a 'genuine check' for the mod, instead of just for the board. I'd add some user benefits to logging in if I could think of any to offer.

mikepetro: Hmm. We could do that. What kind of banner are you talking about? A generated image with statistics on it, or...?

lsusb just gets a maintained list of VIDs and PIDs. It doesn't query the device. Whether it shows or not isn't related to whether USB is working. 268b:0405 is the DNA 200, yes.

pdizzle, are you running the 2015-08-07 firmware?

Posted the 2015-08-17 EScribe. Same firmware as 2015-08-07, adds the option of installing ECigStats.

D022A, what version of firmware were you running at the time? What mod is this? Could you PM me the serial number? Thanks! Help Desk should be able to look at your board and replace it.

Has cell 1 ever read properly? If not, how did the mod pass through Production Utility? (Did the mod maker not use it?)

Once you hit the Fire button, does it stay on? That'd narrow it down between a USB Voltage reading issue and a sleep pin related issue.

The newer versions of EScribe (in the Early Firmware thread) save where the program was when you last closed it. If this is not working, hmm. Do you have a multimonitor setup? Running in Extra Large Fonts by any chance? The fire button should not cause reboots. If you're able to fire at a reasonable wattage though the power connector has to be fine...

How do you know pressing the fire button reboots the device specifically? What behavior are you seeing? Does something display on the device screen? If you see anything on screen, that rules out it being a firmware issue. If Device Monitor works then your firmware is working. What are you seeing for battery voltage? I wonder if something is wrong with your battery connector. When you use Device Monitor, are you able to fire? Or does it say CHECK ATOMIZER? (What are the battery voltages reading? Keep in mind, battery voltage is read over the balancer taps, whereas power actually comes from the main connector (JST in the Hana's case).)

Google for LiPo discharge curves, or the discharge curve for your particular battery to see what will happen. You will see that capacity does not advance much at all once you are in the 3V range - at that point a LiPo battery is essentially drained. Weak Battery will move horizontally along that curve to lower C levels until it finds what the battery can sustain at its current state of charge, allowing you to use all the capacity available at lower C levels. You can see on these curves that the 10C line will end at a lower capacity than 5C, which ends at a lower level than 1C, etc. When the battery is really low, it simply can't do 50W, and a few puffs later, can't do 40, 30, etc. But we have it give you what the battery can stably give. Letting the battery fall even further before reducing the current demanded of it won't help. Without the Weak Battery feature (it's not just a warning message), you see the capacity falls off a cliff on those discharge curves? You'd be done already. Unless your battery connections have a ton of resistance, lowering it is unlikely to buy you more than a percent or two.

Hello promod2000avenger, What do you mean by XP 'flashes between black and normal screen'? This sounds like a bug we ought to fix. Could you describe the behavior (or post a video)? Thanks, James