-
Posts
5 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by bender
-
-
On 5/21/2018 at 12:03 AM, Jetro said:
My Paranormal that won't startup properly is still dependent on the battery voltage be under 3.70 volts to start with no issues. Themes and firmware make no difference.
I also got a Thinkvape Finder 250c. It has zero issues starting or vaping. I now have 3 250c mods. Two that have no problems and one that won't startup properly.
I read some where on the web that someone was having startup issues and they had strange voltages on battery 3 and 4 on their Paranormal. As you know these boards can be wired for 2, 3 or 4 batteries. So I modified the default theme to show the 4 batteries. This is what I found :
The Paranormal with problems starting, battery 3 reads 0.234 to 0.932 volts usually 0.547 volts , battery 4 reads 0.354 to 0.737 volts usually 0.604 volts.
The Paranormal with no issues, battery 3 reads 0.010 to 0.035 volts usually 0.010 volts, battery 4 reads 0.007 to 0.009 volts.
The TV Finder with no issues, battery 4 reads 0.005 to 0.056 volts, usually 0.024 volts.
If you want to check this out here is the theme. You can lock the mod and turn off autolock from Main screen. The battery screen is accessed from the Settings screen so you can see the voltages.
JT
On 5/21/2018 at 8:06 PM, Jetro said:When I made the theme all I did was make a battery screen that has voltage fields for four cells. Cell1, Cell2, Cell3 and Cell4.
It makes no difference whether the batteries are charging or not or whatever voltage they are at. I am seeing the same small amount of voltage on cells 3 &4 on the Paranormals and cell 4 on the Finder.
As far as how I am getting these voltage readings on the nonexistent batteries I have no idea. All I can say is what I see in the fields on the screen. Because of the way the balance connection is jumpered from the positive terminal of the battery to the unused pins on the balance connector it should not show any voltage on the nonexistent cells. But it does. Other than voltage or current leakage in the balance circuit I have no explanation to why it shows these small voltages. But it does and it is fairly consistent. Also on the Finder and Paranormal that wake up and work properly the voltages are very small ( .005 to .056 volts ). The Paranormal that will not wake up as in my first post in this thread the voltages on cells 3 & 4 are between .234 & .932 volts. Again, I have no idea why.
PM sent
JT
Out of curiosity I have made also a theme like Jetro described for my Paranormal 250C (which has only two batteries) which will display the voltage reading for all 4 batteries.
I can confirm that my device (which will not wake up with fully charged battries) is showing strange voltage readings for the non-existing battery 4!
Typical readings are:
Battery 1 (existing): 4.075V
Battery 2 (existing): 4.145V
Battery 3 (not-existing): 0.011V
Battery 4 (not-existing): 1.013V
If I drain Batteries 1 and 2 to around 3.7V I don't have any issue to start the device from 'deep sleep', but the voltage reading for battery 4 will still read 0.95V - 1.01V ! Battery 3 is always around 0.01V...
I did not change the battery configuartion (2 batteries) of my device, just added to display the voltages for batteries 1-4 in the theme. Could it be that the board is checking these voltages during boot-up and refuses to start due to inconsitencies? Are these checks perhaps some-how bypassed when connected to USB?
Bender
-
On 7/3/2018 at 7:06 AM, Sternenwolf said:
I just got two Finder DNA250C - a red and a black one. Only the RED one shows the "I do not want to wake up"-fault.
red: Version 1.1 SP33.2 INT - produced May 4, 2018
black: - Version 1.1 SP33 INT - produced March 23, 2018
First of all I disabled "deep sleep" in escribe and loaded to device … did not solve the problem ...
Loaded default theme of my Paranormals, which do not show this fault … did not solve the problem
enabled and disabled "deep sleep" in escribe again and loaded to device - took battery off and put it back - let device start …
Fault of "not waking up from deep sleep" did not show up again … fine 😁
I would also be interested where you find the "deep sleep" otion in escribe
So far I could only locate the "Automatically lock when idle" option under the "safety" panel in escribe...
Thanks!
-
Update from my side:
The problem with my Paranormal DNA 250C seems as Jetro explained on 16th of May to be related when using freshly charged cells.
When I put two fully charged cells (I use two EFEST 18650 3000mA 35A 3.7V charged to 4.2 V) into the device, It would not turn back on from deep sleep. It comes back on directly plugging in the usb cable connected to a 5V power source (a bit a problem when out and about...) If continue a bit of vaping and drain the batterys a bit, the problem would not happen again untill i put back in freshly charged batteries and let the device go to sleep.
Some times I manage to get the device back on again if I open the Battery compartment and then hold down the fire button ~30 sec. After closing the device again It some times comes back.
My current firmware version is: 1.1 SP33 INT
Board settings can be seen from the attached image...
I will try with the new firmware and see if it improoves...
-
I have a similar problem with my Paranormal DNA 250C. After it went to sleep for a while it would not switch on the screen when a button is pressed. I pressed then some *wild* button combinations (because I thought the device went in some blocked mode) until the screen came back on and i could unlock the device with the normal 5x button press. Happend sofar 3-4 times and I got the device now for a week.
I will try to find out if its just a time delay after the first button press or try some slight wiggling in the usb port to see if this helps...
I would be interestred to know if this is a firmware issue (i have still the original one) or a hardware issue (then i would send back my device for replacement)
Thanks...
Won't turn on from deep sleep
in General Discussion
Posted
Hi DeadMan,
I know you said we should not ask about the beta firmware... But I'm my self a software developer working with prototypes (soft- and hardware) in an scientific research environment and I'm happy to offer my experience to resolve this issue. So if it's not a matter of days to release the firmeware I'm happy to support with some alpha testing, also outside of the forum....
Cheers,
bender