Lowbytes
-
Posts
170 -
Joined
-
Last visited
-
Days Won
7
Content Type
Profiles
Forums
Downloads
Posts posted by Lowbytes
-
-
Using the Power supply from my Amazon Dot - giving me the same Numbers on the USB Doktor but 4,97V and 0,98A used for Charging on the mod
i´m familiar with electronics (technician electronics and radio ham) but thats weird
-
James - now its getting weird - connected an USB Doktor between mod and Charger -
telling me that 5.11 V and 0,96Amps are used - the mod telling me 4,74V and 0,446A are used for charging?????????????????????????
What da hack is going on? Charger is one of these amazon basic wall power chargers rated 2A - where are the missing 0,5 Amps?
-
Hi James
I´m using exact the same charger without any problem! So - if i would guess.......it will work for you!
BUT - using an Amazon Basic charger (2Amps) give me 4,74 V 0,335A charging - changing to Samsung Charger (2Amps) giving me 5,02V 0,665A charging - changing to Nexus6 Charger giving me 4,97V 0,411A charging - changing to the Alexa Power supply giving me 4,98V 1,0A charging - so every charger is working but giving different charging amps..........Same Cable same Mod same 18650 just switching the USB connector from one charger to the next!
-
I think i´ve sorted out a possible USB Charging problem
The 2Amp charger delivering 5,246 V output current - i have exactly the same charger mine delivering 5,02 V
Specification for max USB Voltage is afaik 5,250 V - so i think that you´ve Programmed a max USB voltage somehow?!
So as you can see - 2 identical chargers giving 2 different output currents - you´ll never know what you get ;-)
But anyway i´ve attached pictures x1 Charging with a 500ma Charger - Charging with the non working charger - the non working charger - all Pictures taken with firmware sp23 - with sp21 Charger is working!
Regards
Mikel
-
Okay - asap ....... I hope he´ll drop me the Informations -
Perfect Service - thank you for your good work (the whole Team)
Regards
Mikel
-
vor 1 Minute schrieb James:
What charger is he using? I will order one to test. Thanks!
Thanks for it James - but as Forest Gump said .......you´ll never know what you get..........
Maybe he has a chinese clone warrior - usual what you get if you order via amazon ;-)
Did you changed anything USB related during the reprogramming of the SP23 ?
-
User went back to Sp22P2 - charging now working again - with the same Charger (Original Samsung Wall Charger) and the same cable
So - now - what´s causing this issue??? I´ve no ideas!
SP22P2 - Charging okay SP23 Charging not okay ....
My mod no Problems with any combination of chargers - Cables and firmware ............
-
Neither do I - it´s a bit curious - but it´s been reported to us............
@copyman I´ve only reported - tested with my mod - no problem - should i tell the user that he´s a liar?????
-
Here is another one.......... A report that was given in the GERMAN DNA75C group:
A 2 amps limited AC charger is not working in charging mode anymore
The same charger/cable was proper charging the cell via usb before the sp23 update - now it is starting to charge cell and reporting fully charged after a few seconds
Charging with a 500ma rated charger still working
I´ve ask user to downgrade and check to make sure that it is not hardware related - but he will stay on sp23!!!! So just for your information if you´ll have any other USB related problems reported!
Regards
Mikel
-
After a couple of puffs
Conditions = room temp 23°C - SS304 0,37 Ohms manually set to 0,338 (27°C) and locked - temp set to 200°C - 35 Watts Punch - 20 Watts Power limit
Maybe it helps you to see the numbers with this settings (manually set ohms and locked)
-
Here my results - waking up by Fire button - connected to USB - started escribe
-
Well said sir!
-
Happened while not charging - running own created Theme but the same with Data Miner Theme
-
Also adjusting the Coil resistance affects the power settings
If im on Main screen - (for example Power is set to 20 Watt) - changing to coil resistance - increasing the resistance manually - Power will be set to 15 Watts
-
Here´s my feedback about the latest SP23 for DNA75C
Room Temperature - still reading to high on a Hcigar VT75C - Measured Room Temp is 23°C (Digital Thermometer) VT75C reporting 27,5°C
Board Temperature - reading 33,8°C after 6 Hours in deep sleep
So - i might using wrong numbers in the Case analyzing?
Beside this Problems seems to work great when setting the measured 27,5°C as reference for the coil temp
-
Do you think that it will be released quicker if you tell them that you buy a yihi product???????
Good luck!
-
2
-
-
Thanks for sharing - i´ve added a warning in the German DNA75C Group to be careful !
-
Okay ok you got me there ! ;-)
65 Millimeters - grrrrr
-
1
-
-
BUT - the size of an unprotected flat top cell should be 65 millimeters (corrected) - no matter if it is a 18650 or a 26650
For me it looks like that the Area around the positive contact inside the tube is isolated - or do you think that the spring loaded contact is pushed against some area behind the spring load???
In the german DNA75C Group no one reported problems with 26650 cells on the Hcigar DNA75C - beside getting weak Bat..........
-
We´ve been informed, that users got problems with the latest service pack
It seems that there is something wrong with displaying Cell Voltage or Battery Meter - randomly
(i´m not on the latest service pack so i do not know exactly whats up with this "bug")
Is there any information that we can pass on to the German DNA75C Group?
Regards
Mikel
-
Mine is doing fine after initially cleaning - but i´d not looked inside the mod
Overall i am fairly satisfied with the Hcigar DNA75C
-
Good to hear!
Vape on!
-
If it is a HCIGAR VT75C try to clean the threading of the Bat cover and the inner thread witch alcohol
We´ve had such issues due some production residues - after cleaning the problem was gone!
-
vor 5 Stunden schrieb ndb:
For the benefit of whoever else might get tripped by this, after I sent my .ecig files to @James, he came back with a resolution that he allowed me to share here:
Basically I was using a steam-engine curve for 316L that was, for some reason, missing the lowest -58F point so that the curve started at 68F (maybe something got screwed up when I downloaded the csv and imported it in escribe, I don't know).
This caused noise-induced errors to the measurements performed during the initial phase of firing to fall below the minimum allowed temperature of 68F, hence the temp protect error.
Replacing that TFR curve with the stock 316 that comes with escribe did indeed solve the problems.
Now, using the stock profile is not mandatory, the important thing is to be sure that the curve starts well below what we consider the minimum ambient temperature we'll be vaping at, to avoid initial lower readings to be considered "out-of-range".
I'm not sure I've thanked James enough for finding this out... ;-)
Then something went wrong with the download or with uploading it to the DNA75C
The steam-engine TFR Curve is complete with all needed temp points
Possible bug with new Firmware 1.1 SP23
in General Discussion
Posted
So okay - i stay tuned ;-)
Thank you!