Mad Scientist
-
Posts
247 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Posts posted by Mad Scientist
-
-
I just go with numbers for the clipper shields. #2 is fast and simple. And I never have to comb my hair lol.
-
Although a single 18650 would be great for "the small mod" there are some small 2S and 3S lipos that come pretty close. If you want a really teeny tiny mod, the DNA 200 might not be the best platform to start with. Get or build a DNA 200 mod to develop and analyze your best coiling and wicking technique, then also have another teeny tiny mod for the suit pocket. As another approach, there are some 18350s where a pair would allow you to go up to about 40 Watts. My understanding is there is some way to set a somewhat permanent limit on the DNA 200 so it wouldn't allow going above a defined power level.
-
Well, I think I solved my own problem another way. I plan to make 3S packs using 18650s with a balance connector and polarized output connector on each pack. No user error really possible.. The 18650s are supposed to be kept together for life anyway. Might as well make it a marriage without possibility of divorce lol.
-
You're way ahead of me. Let us know when you've got it perfected. Sounds great! In the mean time, maybe just a diode & easily replaceable fuse to crowbar the pack. I guess the cell taps would still be an issue?John said:That will charge (and is more or less how we did it on the 40) the problem is the simplistic approach doesn't prevent charging in the battery reversed case (conducts through the body diode), doesn't protect in the one cell reversed case (pack voltage 4v) and doesn't protect the balancer taps. I have our solution down to 5 Fets but I am still not 100% happy with it.
-
Oh, I guess the charger won't work if we do this. Sorry about that.
-
High current low Rds(on) FETs are apparently now cheap enough to use as reverse battery protection. Here's a simple circuit that at first glance looks like it will do the job: http://www.ti.com/lit/an/slva139/slva139.pdf I haven't yet selected an appropriate FET for this application so if anyone has suggestions, that will save us all a lot of time. It has been a while so I'm not up to date on what all is out there anymore. Cheers.
-
Thank you!Brandon said:The Data sheet shows 3 possible orientations for the balance connector. If you are mounting using the through holes, the slot goes down (farther from the USB).
-
Excellent. Thanks!James said:Device Monitor demonstrates pretty well what can be done. It's actually limited by its paint code being on the same thread as the query code (and Microsoft's .NET Windows Forms not using hardware acceleration for drawing...). Be kind to it ( at a certain point you might be slowing it down), but you can push substantially more than 30 queries per second.
You can also set Serial Output in the Research tab to CSV (Excel). That is a 50 Hz output of all of the important values. It did slow the device down by a few percent in my tests (a candidate for future optimization), but you can get a boatload of data points... -
I know this is a dumb question, but for the balance connector, the drawings seem to show the "slot" down (farther from the USB) but the photos show the "slot" up (closer to the USB). Am I missing something? My eyesight isn't what it once was so maybe the connector is marked somewhere but anyway, which way does it go? Thanks.
-
Yes, I get that, but what is the latency of each GET transaction? So in your explanation above, what is the timing of the "wait for response"? I.e. how long is this wait? Would it be practical to obtain real time data for plots through this CLI or is it too slow? If it's too slow, can we get specs on the fast interface? I'm trying to come up with a "least pain" way to implement a wireless link between the DNA and the PC. If the CLI is fast enough to get the data out of the DNA for plots, that would seem to be perfect. As a seat of the pants guess, I'd anticipate wanting to obtain at least 30 data points per second allowing for 3 data types at 10 interleaved points per second each (like temp, power, resistance or along those lines). Is that like way slower than the thing can spit out the data or would I be bumping up against limitations of the DNA CLI's ability to parse the command, get the data and send it? Thanks very much for your help!James said:Only thing I can think of, when doing GET requests, do (1) 'send query, wait for response, send query, wait for response, send query, wait for response'.
Don't do (2) 'send query, send query, send query, wait for response, wait for response, wait for response'.
It won't send a response until its send buffer is empty, so you won't improve update rate by doing (2) (in fact, you may fill up the DNA's receive buffer, waiting forever to send, while the DNA is waiting to finish sending back to you...) and your code will be more complex. Do it the simple way, (1). -
Fantastic, thank you! Any info on timing? I'm assuming it's all "as fast as it can" but are there more than incidental timing considerations for performing, for example, a quick succession of T=GET transactions to make a temp plot?James said:Here are the main control commands. Enjoy
Fire: F=#S
Set Power Setting: P=#W
Set Temperature Setting: T=#C or T=#F or T=OFF
Set Profile: M=# (1 to 8)
Get Power: P=GET
Get Power Setting: P=GET SP
Get Temperature: T=GET
Get Temperature Setting: T=GET SP
Get Voltage: V=GET
Get Current: I=GET
Get Profile: M=GET
Get Battery: B=GET
Get Battery Cell: B=GET CELL # (1 to 3)
The Device Monitor works by issuing serial commands, so really anything it can do can be commanded. -
ClintMaas said:
[QUOTE=Mad Scientist]I'd also be very interested in the interface specs. I really want a wireless interface between the PC and the DNA. I can do a wireless serial interface. Hopefully for this it's a couple of USB to serial converters, a couple of PICS and the radios? Is all the data communication CLI?
I really want a way to go wireless as well. I just haven't found anything easy (small dongle).[/QUOTE] There are a boatload of chips and hybrids available. Years ago I did a temperature telemetry project using radios from a now defunct supplier. The radios were about half the size of a thumbnail. An eight pin PIC and DS1820 and the whole shebang was less than a cubic centimeter, not including battery. I haven't worked with any of the new crop of stuff yet but surveying what's out there, they have hybrids with the radio chip including an ARM core. Basically single chip radio and processor with a few discretes. Very tiny. Once I select the parts and get something working, I'll post back with what worked. There's a lot out there, really amazing stuff. Maybe make the DNA 200 it's own IoT WiFi web enabled mod lol. I wished for plug and play but there seems to be nothing available. -
I'd also be very interested in the interface specs. I really want a wireless interface between the PC and the DNA. I can do a wireless serial interface. Hopefully for this it's a couple of USB to serial converters, a couple of PICS and the radios? Is all the data communication CLI?
Out of curiosity: Radically new features in firmware - possible?
in EScribe, Software and Firmware
Posted
I'll never live long enough to follow all the way through on every idea I have so here's one I hope to see Implemented one day: The junction of Kanthal and nichrome is a thermocouple. No need for separate thermocouple of low thermal mass. At vape temps it will produce several milliviolts with a room temp cold junction. I'd envision a coil with a welded junction of the two wires Ian roughly midpoint. Their gauges would have to be selected for equal resistance per unit of length. Might just work