James

Does it just intermittently pause and fail with EEPROM Programming Failed, or something more consistent? If these VMs just have a tendency to pause, I wonder if we just need to increase the timeout time.

How did your cells get so low? If the cells get that low (below 2V), you'll need to select Perform USB Recovery Charging in Device Monitor.

mechaet could you save and post your settings file? I don't see anything unusual on those screens.

What voltages do you see on your battery cells in Device Monitor?

Oh, I mean your EScribe settings. iandvapyes: This happened to you before 8/21 then? How long have you been encountering it?

josh, the actual charging code does not use the battery meter, just the cell voltages. It isn't a worry for overcharging. What firmware version are you running, out of curiosity? And does it only happen if there is no atomizer attached?

Mm. Are they cross-shipping you a new one? 60 watts should work fine. The board can handle it.

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.