Jump to content

BillW50

Members
  • Posts

    1,182
  • Joined

  • Last visited

  • Days Won

    47

Everything posted by BillW50

  1. Oh crap! There is a Perform USB Recovery charging (Device Monitor -> Diagnostics -> Advanced). But I have been told it won't work for cells under 1.0v.
  2. What does EScribe's Device Monitor show for cell voltages?
  3. How do you know it isn't charging? The HCigar VT133 comes with the charging screen set to 0% (which is off). First, "Connect and Download Settings" (button) In EScribe under the screen tab, adjust the charging slider to 40% or higher. You can also change on this tab what displays on the screen when it is charging. Don't forget to "Upload Settings to Device" if you make any changes.
  4. Oh good, I know a bit about Gateway machines. Yes Evolv will repair your board. They will probably ask you to unsolder it from the Reuleaux. But if you are not experienced at soldering, just tell them this.
  5. Close EScribe, disconnect any DNA. Then run this file called USBRemover that I would give a shot. This removes the driver from Windows and then EScribe will reinstall the driver. What kind of Windows machine is this anyway? https://www.dimensionengineering.com/software/USBRemover.zip
  6. Ok you uninstalled EScribe and then reinstalled SetupES_2016-02-27 (v1.0.42.0).exe or 2016-02-29 right? Then connect it up to the Reuleaux DNA200 and from EScribe -> Tools -> Update firmware. Then pick the 2016-02-23.sw-update file. Will it allow you to do this? And what update did you use when it just quit?
  7. Did you try removing all of the batteries, then connect it to EScribe without the batteries?
  8. No nothing is wrong. Batteries are never exactly what they state on the capacity. They could be 2443mah or 2561mah or something. Just lower the watt hours until it reads 100. You don't need to run the battery analyzer or anything. Especially if you are going to swap batteries.
  9. Yes. The DNA200 is only configurable for two in series or three in series.
  10. What this does is to remove the DNA driver from the OS on your computer. And when you connect it again, it will reinstall the driver again.
  11. There is a file that you can run that is called USBRemover here somewhere that I would give a shot first. If that fails, contact VS. Use Evolv if VS doesn't want to help. Update: https://www.dimensionengineering.com/software/USBRemover.zip
  12. Some USB cables are charge only cables. Hopefully you didn't try a second USB cable that is also a charge only cable. I think they should color code those things or something. Otherwise it sounds like the USB port has a broken pin off of the circuit board or something. UPDATE: Oh CB popped in. Yes rebooting is a good idea. Although you tried two computers already. Is this the first time using these computers with EScribe?
  13. Easy, the board is acting on its own. I would check for any juice on the board. If that isn't it, then it needs to be replaced or repaired.
  14. But the Device Monitor isn't showing the Up button being pressed.
  15. You can also swap one of the values to show profile as well.
  16. Sometimes users end up with juice inside and can cause lots of weird problems. And no, I personally haven't ran across one acting like that one. This is a first. I believe HCigar warranty is 6 months. Although I don't know how much luck you will have with them. Also if that doesn't pan out, open a ticket with Evolv. Evolv might ask you to remove the board from the VT200.
  17. I believe I heard someone mention 0.00110 worked well for them. Try that one and let me know.
  18. Yes that is one way you can try and see how it works. There are others here that knows more about this area than I. Hopefully they will be around soon.
  19. Sorry, we all scattered when you said the word "notchcoil". (just kidding!) Maybe this will help. /topic/67048-topic/?do=findComment&comment=903567
  20. That Screenshot balloon is covering the button pressed status. I am guessing the only one that you had pressed at all was the fire button. The first one you can see just the fire button being pressed. It also seems you had this for awhile and it was working fine, right? Then this problem popped up, right? Man it looks like part of the board is working and part of it is dead. Does the display work when unplugged from the USB? Besides a bad board, maybe a bad connection to the 510. Not only check the hot wire, but the ground is just as important.
  21. Do you know how to take a snapshot of the screen? If so can you take a snapshot of EScribe's Device Monitor while the fire button is held down and upload it here?
×
×
  • Create New...