Jump to content

fwa

Members
  • Posts

    25
  • Joined

  • Last visited

Posts posted by fwa

  1. My Paranormal died also today, after 1 year and 2 month. When you are just in Holliday with this mod, you are very happy ;-(

    When i leave it without battery for some times, and put again the batteries, it work well during 1 or 2 minutes. After this time, it does not want to fire, or sometimes does not want to unlock. Button goes crazy…… If connected to escribe, when i try to read the parameter, i get an eeprom read error.

    Seems that temperature of the chipset rise when batteries are in the mod, and that the chipset fail to do anything.

    I take care of my mod, no trace of liquid, never fall….. it is like a new mod and I think that it is not a Lostvape default, but well an Evolv default of the chipset.  

  2. Thanks Retird ;-)

    The situation is now more bad. As you, i think now that it is not a Windows problem, but a DNA250C Chipset problem.

    Now, my Paranormal does not want to unlock, i have try to verify all the parameter and when i send the data, i get an eerom error.

    I have try to flash the firmware, with success… but no change.

    And now, after a lot of attempt to unlock, i see something very strange with the button… fire act as fire but also as up, select act as up or does not respond…… seems a big problem now.

    Well…. this box has 1 year and 2 months…. and is mostly dead.

     

  3. Problem with new Windows 10 1903.

    The monitoring windows display the value and graph, but after a small time, graph does not progress even if the value on the left part seems updated, and another small time after, the value on the left part also also no more updated (they stay fix).

    Before, with previous version of Windows 10 (1803), i don't have this problem.

    Does anyone also have experienced this ?

  4. il y a 45 minutes, Wayneo a dit :

    @tennisguru1 Simple Answer: No, as it's not mentioned at all above.

    Long answer: The DNA75 only ever needed 1 update which was named and released  2016-06-05. You can see your current firmware version in 'Device Monitor', lower right hand corner

    And what about the DNA Go update ? Just buy one….don't want to brick it with the update, but also does not want to brick it with the idle state problem….

  5. fwa said:



    So if i follow your mind, now the level does not reflect the level of the battery reflecting his voltage but now the capacity.
    Ok, let's try, i am now at 20% 5675 Wh. So 100% = 5 x 5675 = 28375Wh, which seems correct.
    Sans_titre2.png 
    It is really strange that before the update, the level reflect exactly the reference of the battery csv. I have always used this to charge at 3.8V per cell my box for storage. I do this for my RC models as for my box :).

    I must simply change my reference observing the charge for my different box, regarding what is the Wh at 3.8v



    An update: i am now at 25%
    Sans_titre3.png 
    25% with 6955Wh which mean 27820Wh.... this fluctuate a lot o.O


    And after changing the power in Kanthal using Escribe, so i reloaded the parameter, i get this:
    Sans_titre4.png 

    A jump to 46% from before 25%...... really strange 9_9
  6. ChunkyButt200 said:

    14% of 28.05 watt hours is 3.927 watt hours. that is very close to your remaining 3.814 charge estimate in device monitor, so that seems correct. can't say why at 3.63v it doesn't reflect 35.8%. however, 14% sounds more accurate than 35.8%, looking at your charge estimate. i'm not even positive if my math is correct.



    So if i follow your mind, now the level does not reflect the level of the battery reflecting his voltage but now the capacity.
    Ok, let's try, i am now at 20% 5675 Wh. So 100% = 5 x 5675 = 28375Wh, which seems correct.
    Sans_titre2.png 
    It is really strange that before the update, the level reflect exactly the reference of the battery csv. I have always used this to charge at 3.8V per cell my box for storage. I do this for my RC models as for my box :).

    I must simply change my reference observing the charge for my different box, regarding what is the Wh at 3.8v
  7. VapingBad said:


    They have indeed, it was a problem that was only introduced with the early versions of 1.2, a side effect of other changes that should no be consigned to history.



    Ok, but it seems that we have another problem now.

    Sans_titre.png 

    Voltage on the 3 cells is correct, but the level is very strange. When i check on my battery curve in the mod section, 3.63V is about 35.8% so why is it indicated 14% ?

    Sans_titre1.png    

    test.png

  8. Bobby said:

    Great! Thanks.

    Just a tip for non-English users:
    If you get a screwed up discharge profile after you have loaded the file:

    a. set your Windows country settings to English (decimal sign should be "." and thousand seperator should be "," (normally your numbers would be eg. 1.234,56 but now they should be 1,234.56).
    b. restart Escribe
    c. Load the esig file
    d. restore your windows setting.

     



    Hello Bobby,

    Thank you for this working solution. Seems that Evolv must correct this problem, otherwise we will get some surprise when exchanging preset.

  9. I have a question to Evolv Team.

    The battery type could be actually Lipo or LiFePo4

    When we use VTC4 from Sony or LG Battery, the chemistry of those batteries are not a Lipo, not a LiFePo4.

    Nominal max charge voltage for a Lipo is 4.2V
    Nominal max charge voltage for a LiFePo4 is 3.6V

    So regarding this, we should stay in Lipo mode if we want a full charge (100%) of our Sony or LG batteries.

    Is it correct ?

    Could you also specify the Max charge voltage for the optimization also available in Escribe for the 2 chemistry ?
    Actually I know that for Lipo it is 4.1V & 4.2V
    What for LiFePo4 ?

    In advance.... Thank you....

×
×
  • Create New...