blueridgedog

This thread/topic is now obsolete as there is a beta version that supports OSX natively:

10.12.6 working fine with my 200. Love it.

Update process went smooth for my hack and MacPro.

Installed and ran fine on my Hackintosh running current version of OSX (10.12.5). I don't have a 75C but will scrounge one up eventually. So far, all apps in the suite open and close as they should. Same report for MacPro on same OS. Exciting! Thanks.

Actually, as a Mac user, I would rather resources be put into PMTA or improved product. If software needs to be changed, I would rather see it migrate to a Chrome extension or similar.

No news in that I don't think such a thing will ever be. The number of Mac users is so small as to make this a huge time sink for little return.

Well stated. Is it oxidization or carbon? oxidization

Bootcamp works fine as you are running Windows natively. I am going to put a windows partition on my next Mac, but don't have a burning need to do it now, especially since the new mac pros will be out around September.

One tip, I always look at the cold resistance with a new build so that I can then see if it slips off due to a poor atomizer, loose connection or similar.

What are you using for a curve or TCR value for each of them?

I have stopped doing updates via Virtualbox for that reason.

Could be a tight button (button that needs thinning).

It sounds like you have checked temp dominant for the profile...it will now let you pick between showing your temp settings or wattage settings based on your selection for each profile.

In theory you should be able to put on an atomizer with kanthlal and have it detect it is not TC capable, so your only concern is to go into your profiles and up the max kanthal power. I think the stock setup is 125w.

I have yet to find a person that could perform the VirtualBox based force firmware.

Useful to know. I can theorize that the system will cough a bit if it is asked to shift into charge mode while firing, but regardless, it is probably something that can be tweaked in the firmware.

I doubt the tool will show you a .08 or a .1 mod resistance unless there is an error. One of mind starting reading the ohms off by .05 (a massive amount for Ti) and it ended up being poor grounding (I had to remove the board and reseat it).

That is a calculated value, so if you build a new coil with substantially different resistance and you fired it with ohms locked at .56, then it would "think" that the difference between .56 and what it was reading was due to temperature, and calculate what that temperature might be and show it to you.

Power off PC, unplug all non-essential USB, do a cold power up with the DNA200 connected, launch escribe and do a firmware update under tools. If that fails, fill out a form for an RMA.

I have seen other "won't wake from sleep without USB connection" posts. I have not seen a user step that would correct that assuming the button action was indeed working. Thus far they all have been RMA issues with the board.

Bravo for you!

Verify you have the language you want on the profile tab in escribe, that the wire type is selected correctly and for non-temp wires you have checked/unchecked the right box.

If you think you have an issue, then adjust the ohms lock value downward if you want it to ask you more often vs having the mod make the decision.

On the Mod tab, then under Manufacture Settings, what do you have under ohm lock range? In my experience there is nothing odd about it not asking if it is a new coil as it only asks if it is so close it can't deduce the correct answer.

Post a screen shot of device monitor firing it. Lower your pre-heat significantly.