eucalyptus.

DNA75c short atomizer error?.

10 posts in this topic

Hello.

My DNA 75C is "short" when remove the atomizer.

After resetting, it becomes "CHECK ATOMIZER" before attaching the atomizer.

I examined it with ATOMIZER ANALYZER, after removing the atomizer, the value of 100 ohms or more appears.

My MOD is actually not short-circuited.

Is there a problem with my board? .

Revision:20
Theme:Default Theme. ( "Factory Setting Reset." )
 

75c_1.png

75c_2.png

75c_3.png

75_1.png

75_2.png

Share this post


Link to post
Share on other sites

Have you checked the ohm's at the connector with an ohm meter using the same "off/on " process? 

1 person likes this

Share this post


Link to post
Share on other sites

Also, have you tried another atomiser as some atomizers have longer or shorter 510 pins and devices have different 510 connectors so it could be a conectivity thing.......

1 person likes this

Share this post


Link to post
Share on other sites

 

Thank you for your reply.

510 The connector is removed once it is confirmed.

Resistance value between ATM and GND is about 500 ohms when the board is not connected and nothing is connected.

Since this value is almost equal to normal DNA 75, it is judged that it is not physically short-circuited.

Share this post


Link to post
Share on other sites

More likely to be a minor bug in the software (there are two hardware comparators, one looking at over-the-counter and one looking at over-current)

The hardware of the DNA 75C is fairly similar to the regular 75, except for all the added components for puff recording and timing and running the screen and storing the configurable UI etc. But the software is a completely new codebase. 

It's probably just interpreting or displaying the error state wrong. We'll add that to the list of small bugs to clean up, but I wouldn't worry about it too much. 

Share this post


Link to post
Share on other sites

Hello.

Thanks,for reply!.

 

When a short circuit is detected, it forcibly shuts off and a click sound is emitted from the board. Since it seems to be a malfunction at first glance, I expect it to heal. However, because it is not a fatal factor, priority is low and it is OK.

Share this post


Link to post
Share on other sites

We were able to replicate and correct this, the fix will be in the next service pack. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now