Jump to content

mactavish

Members
  • Posts

    236
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by mactavish

  1. Spirometry said:

    SP3 added some extra protections. Reading the ultra low resistances with the copper plug will just display a question mark.

    Thanks! That's odd though since when I wrote my posts earlier in this thread, I believe I was using SP3. I did see the "?", but after making the plug really tight, it showed the resistance. I could be mistaken on the SP version I was using at the time. I do hope they fix the issue.
  2. Wayneo said:

    @Mactavish While I agree with you wholeheartedly, you do realize you're talking to an Engineer. He's been asked to stop posting that comment on locking numerous times.


    I don't know how an Engineer with access to a PC, CANNOT do a simple Print Screen when asked, and instead submits an out of focus, incorrect orientation image.





    Everytime I see him post, in my head I start singing a Frank Zappa song, posted a line from it once, only to have Saint VapingBad delete the comment. Aah, this one will also probably get deleted, but before doing so, I wish they'd go and look at doing the same for him and his posts.

    And now another quote, from I believe Einstein. "He has been given a large brain by mistake, since for him the spinal cord would suffice."

    Thanks for the heads up!
  3. Just curious about this behavior. On both my DNA200 and DNA75 devices, I have a Stainless Steel notch coil reading at 26 ohms in TC mode. Ohms never locked and stay consistent. With the Atty at room temp, when I switch the mod to "power mode", the ohms immediately show as 29 ohms, as I puff the ohms rise to .32 ohms. If I put the mod down, let it cool, the ohms go back down to .29 again, but never the .26 ohms that I see when in TC mode. Wondering why I am seeing two different initial cold ohm readings, depending on being in TC or Power mode?

  4. "Sweet Spot Vapors Ti wire is a specific alloy of Titanium with lots of engineering to reduce chance of TiO2, etc." Titanium grade 1, is NOT an "ALLOY", most titanium users, and a few experts dispute these SSV claims, some even laugh at them. PBusardo likes it mostly as they include a CSV file, but while I enjoy Phils reviews, he's no expert on a lot of subjects. Do yourself a favor and save some money by using real titanium G1, the CSV file can be found on SteamEngine site, and the Temco ti works fine with every mod I own that has a built in TI preset. The main reason to use titanium in the first place is to avoid alloys. https://www.temcoindustrial.com/titanium-wire-grade1-non-resistance.html

  5. dylang919 said:

    I bought this tool and it only worked on my Lavabox. I have 12 DNA 200's and tested it on 6 of them and it worked in 1. Would there be a reason for this happening? It's not reading the plug at all, just shows a question mark. I don't understand why.

    I had that issue on a few of my mods until I tightened it even more then I was comfortable with. When it was further down I got a reading.
  6. James said:

    I don't think the internal resistance has changed. 1.2 SP3 may have trouble reading resistances that low, probably due to some of the extra protection code we added. I'll have to look at it this coming week. Other than this issue, I am glad it is working well for yall. :)

    I'll just add, with SP3, the Vaporshark DNA200 and SNY SDNA75, the copper plug read resistance fine, same as before updates. However, I just received my HCigar VT75 Nano, an 18650 mod, like the SNY. In the Atty check, all I get is the "?", NO ohm resistance reading at all. I manually set it at "0.002", same as the SNY, as a GUESS. UPDATE: screwed the copper plug down till it was super tight, got a reading of 0.004. Just wasn't making the connection.
  7. James said:

    If the setpoint is 450F and the DNA is spending 75% of its time at 449.5F instead of 450.5F, it still ought to display the message. The purpose of messages is helping people not math. :)

    As far as overshoot goes, the new firmwares have a "Temp Peak" option in Device Monitor. That shows the maximum temperature observed by the temperature protection code at any point during the puff.

    Exactly, well said! Also, was not aware of the new Temp Peak option, thanks.
  8. Nick said:



    Our technology has never been TC or Temperature Control, it has been Temperature Protection or TP, meaning we are not controlling it per se, but preventing it from going over the set temperature. Our policy has always been to give the most accurate information possible, if the temperature is not being limited because it could potentially go over the setting, we don't display the message. This has always been how it was coded and intended to my knowledge, the only difference now is the control system is so precise and fast that we are not at risk of going over the set temperature.

    I do understand your point of view however and will bring it up internally.

    Yes, temperture protection, that's what I should have said, and that's how I've explained it to those that get confused about the onscreen message. You may recall we got into the true meaning of that message a year or so a go, so I could fully understand it. Glad you are open minded enough to see the point I was making.
  9. Nick said:



    I actually noticed this on the first one we made as soon as I hooked it up and vaped it for initial testing.

    I investigated this with James a bit, and the reason isn't because it isn't working, it is because it is actually working so well now that it doesn't hit the threshold required to trigger the message in many cases.

    This was a very satisfying revelation on our end for what we originally thought could have been a bug. We hope you guys are as satisfied as we are with the results of our work on this.

    I have come to rely on the TC notification. And have defended it to so, so many that originally see it as a WARNING, and not a notice that your device is working properly and just letting you know you have achieved the temperature you set it to. And then in future updates you allowed the TC message to be turned off, for those that did not care for it. My point being, while I'm certainly happy for a better vape experience, you have also introduced another variable. I can see folks saying, sometimes I get the TC message on screen, sometimes I don't! Personally I think if possible there should be a consistently of the TC message, and that if the user, like me has it set for on screen display, then I expect it to display every time I hit the temp target I set it to, regardless of the current wire material. Does this not seem logical?
  10. retird said:

    @mactavish.... James just up a possible resolution of your issue... Could you test it as yours is still not charging right?  THX

    https://forum.evolvapor.com/topic/65665-topic/?do=findComment&comment=888330

    Seems James is working on it some more. I work all day and don't have the ability to test. I'm sure he will get it right with the help of the others. Wish I was RETIRED! Got a few years left.
  11. retird said:

    Saw where you  already posted this 2 days ago and  Evolv is working on it... doesn't effect ALL VS200's as I understand... 

    Here is your previous post:

    https://forum.evolvapor.com/topic/65665-topic/?do=findComment&comment=888277

    Yes, it's getting lost in that thread and I looked to see if someone made an official BUG REPORT, and not seeing one thought it appropriate to do so. The 1.2 version is still on the download page, perhaps adding a note for vaporshark owners would be helpful to avoid surprises?
  12. Did the upgrade to 1.2 on my VS DNA200. So far there are a few others that have confirmed this ODD behavior. Plugged in to charge. One of my on screen settings is to see "USB CURRENT", normally shows close to the 2 amp charge I get with my iPad wall charger. This field is now showing low numbers, constantly changing, charging is SLOW. I didn't change the setting, before update, it shows AMPS being delivered by the USB connection. It was a steady number like 1.96 amps. Now this field is showing numbers constantly changing, none close to 2 amps. Ramping from zero up then back down. I've done 2 soft resets, tested with two different chargers and cables. Hoping this bug can be fixed quickly with another minor update?

  13. ChunkyButt200 said:

    correct if i'm wrong but aren't you supposed to take 80% or what you see in AA and apply that number to the mod res field?

    80% of 20 = 16 

    Not if you use the 99% copper plug. You use the actual ohms you see on the screen. Look earlier in this thread as I put the link to the original discussion.
  14. dwcraig1 said:

    I'm surprised this wasn't mentioned before so here goes. I just checked my SDNA 75 again for mod resistance, not only was I wanting to see than it was still 0.002? but wanted to see how many digits the the right of the decimal point it reads and it's 3. So how did  DJSLB come up with ).0016?? Just something I was thinking about, perhaps he measured it with other means.

    In his latest video, he has moved, and made a new office. It's a long winded video, no devices reviewed, but he does reverse the camera and show some of the tools he uses. I don't recall anything specific like a scope, but I was not paying 100% attention. Take a look at it if you have time, perhaps you can pick up on it. He does briefly point out his heat sync devices. I noticed these on his desk as at one point as I was considering buying them. They are used to get all the case thermal numbers. Not that costly, and there is a thread on here where one of the mods discusses them, just too limited for me as a single use tool.
  15. KTMRider said:

    Why wouldn't you roll back until a new firmware comes out? It fixed my VS. 

    First of all I don't need this mod right now. Secondly, I have bad experiences in doing such in the past. And mostly, I'd like to see how Evolv handles this. I assume a quick new version of the software/firmware to be offered. It's great that you and I participate in forums like this and ECF, but many users may simply update via Escibe or just somewhere on the net, and have a VaporShark DNA200, and will have a bad experience. I doubt Evolv wants to put out buggy software/firmware and then have to explain a work around as to make it work properly. I applaud your efforts, and perhaps what you have done will help them figure out the bad code. If it were my only mod, or it made my computer stop working, I would have followed your discovery already. Let's see how fast Evolv fixes this, they mentioned having Apple Mac software out in late 2015, or first quarter of 2016. Last I looked, it's the 3rd quarter, and we're behind! :)
×
×
  • Create New...