Separate names with a comma.
Discussion in 'ArcticFox Builds' started by maelstrom2001, Jun 4, 2017.
Flash the latest nightly and problem should be fixed
I am getting "atomizer short" on build 170603 on my Predator 228. Tried the tank in another mod and it worked fine. VW mode
hey this is off topic but could you help me with the arctic fox software all i can find is the latest bin. file
See the link below. the .bin file is used with NFE tools to flash custom firmware.
k i figured that out now do you now where the firmware would be for the evic primo 2.0
Try this one: http://nfeteam.org/arcticfox/nightly/af_170610.bin
It rocks man.
Try on OFW to compare
I get a similar issue, on an eVic Primo v1.
Have a look at this thread;
Assign a double-click function to "Re-read atomizer resistance" and it'll clear the short message. But it'll do it again so every now and then ya gotta double-click.
Some attys are more prone than others, to do with small fluctuations in resistance, I think.
Nightly version does not have the increasing ohms problem, but still has an issue of reading resistance wrong. On click it reads 0.25, then it returns to 0.35 on its own. Funnily, on re-read it reads it at around 0.30, then in times again returns to 0.35. No locked resistance or anything like that... Same thing in VW profiles and SS 316L profiles.
My personal opinion is that profiling system is bugged and enforces random resistances that it read at some point in time, that it believes are the correct ones, instead of refreshing the actual number that is being read on fire click.
I've also disabled smart mode, so it shouldn't be doing this on its own.
Is it possible to do this on a RX200 aswell? Tried it but keep getting check battery warnings.
Without firmware modifcation - no.
Thank you. I'm looking to turn a rx200 into a sqounking mod and this would of been the perfect solution for me
Hello, I am also having issues with "atomizer short" on an eVic Primo v1, firmwares of may and june.
All atomizers work well on eleaf pico. Tsunami RDA detected as 0.19ohm on pico, but as >0.5ohm on Primo. As soon as I fire it it goes down to 0ohm and says atomizer short.
On NToolbox, when I screw the atomizer, it reads ~0.9ohm both on Cold and Live resistance. As soon as I fire button, Cold disappears (???) and live goes to 0.5, then rises up to 1ohm.
Other atomizers such as goblin work perfectly.
Would really love to fix this. Feel free to ask for any other information.
Use recent nightly build if erratical "Atomizer short" appears in TC mode.
Sorry, forgot to mention, VW mode. Just tried af_170624.bin and still the same scenario.
Something that may help you:
it was working correctly with my tsunami VW on firmware <= 170607. Putting firmware 170624 made it fail even on the tsunami (same behaviour, cold resistance disappears "?" and get atomizer short). Hope this helps.
Oops, I missed too this:
I think this is the answer: wrong atomizer detection lead to "Atomizer Short" on firing. Use Re-Read resistance shortcut:
Screw atomizer and call this action, if there is no more hardware issues with connector and grounding, atomizer should be detected correctly and you'll see correct value on display.
I tried that trick (even setting it to double-click = re-read coil) and as soon as I fire it again, goes down to 0 + atomizer short. Doesnt seem to be screw related as I dont even touch the atomizer after I double click.
If I'm in the wrong forum I apologize to start. So I have the predator and in temp mode I get tcr error after about 1 second. So I went to tcr mode and was gonna change its settings for ss wire but can't figure out how. Also can some one please explain the advance features such as shunt and all things under expert. All help is appreciated.
Set chktcr to on