Chipdip _verified_ May 2026

But what exactly is ChipDip? Despite its colloquial name, ChipDip is not a single product but a specialized method of applying —specifically targeting surface-mount devices (SMDs) and chip components. Defining the Process ChipDip refers to a selective coating technique where individual electronic components (or small clusters) are literally "dipped" into a liquid coating material, typically a UV-curable acrylic, silicone, or epoxy. Unlike traditional spray or brush coating, which covers an entire PCB, ChipDip is precise. It focuses protection only where it is needed most: on delicate chip resistors, capacitors, LEDs, and small ICs.

In the fast-paced world of electronics manufacturing, where component sizes shrink to nanoscale and board densities rival city blocks, the smallest details often determine product longevity. While soldering and pick-and-place machines grab the headlines, a quiet, reliable process called ChipDip is playing a crucial role in protecting modern circuitry. chipdip

The next time you design a mixed-technology board with sensitive connectors, optical components, or high-reliability requirements, ask your CM about ChipDip. It may be the simplest solution you never knew you needed. About the author: This article was compiled from industry best practices and technical datasheets from leading conformal coating suppliers. Always consult your material data sheet (MDS) for specific application parameters. But what exactly is ChipDip

If a manufacturer sprays the entire board, the light output from the LEDs drops by 15% due to optical absorption in the coating. Worse, the coating on the resistor solder joints cracks after 500 thermal cycles. Unlike traditional spray or brush coating, which covers

8 Comments

Jason Green on July 7, 2014 at 12:52 pm

Hi Ben,
Great article and a very comprehensive provisioning guide! Things are moving very fast at snom and the snom 7xx devices (except currently the 715) are now supplied automatically as “Lync ready” and can be easily provisioned straight out of the box. A simple command of text into the Lync Powershell and voila!

You can find all the details here:
http://provisioning.snom.com/OCS/BETA/2012-05-09 Native Software Update information TK_JG.pdf

Regards,
Jason
Jason Green on July 7, 2014 at 12:54 pm

Link above was broken:

http://provisioning.snom.com/OCS/BETA/2012-05-09%20Native%20Software%20Update%20information%20TK_JG.pdf
Ben Lee on July 7, 2014 at 2:03 pm

Hi Jason, Thanks. It’s good to hear that’s an option, this post was based off a mini customer deployment we had a few months ago…
(Also can’t wait to test out the upcoming BToE implementation)

Ben
Jan Boguslawski on October 14, 2015 at 10:43 pm

Hi Ben,

just stumbled across your great article. Please note the guide still available (now) here:
http://downloads.snom.com/snomuc/documentation/2012-02-06_Update-Guide-SIP-to-UC.pdf

is kind of superseded by the fact that for about 2-3 years the carton box FW image (still standard SIP) supports the UC edition documented MS hardcoded ucupdates-r2 record:

“not registered”: In this state the device uses the static DNS A record ucupdates-r2. as described in TechNet “Updating Devices” under: http://technet.microsoft.com/en-us/library/gg412864.aspx.

In short: zero-touch with DNS alias or A record is possible. SIP FW will not register but ask for the CAB upload based UC FW and auto-pull it if approved (but only if device was never registered: fresh from box or f-reset).

btw: the SIP to UC guide was made as temporally workaround, but I guess the XML templates still provide a good start line.

Also kind of superseded with Lync Inband Support for Snom settings:

http://www.myskypelab.com/2014/07/lync-snom-configuration-manager.html
http://www.myskypelab.com/2014/08/lync-snom-phone-manager.html

another great tool – powershell on steroids with Snom UC & SIP: http://realtimeuc.com/2014/09/invoke-snomcontrol/
(a must see !)

Please dont mind if I was a bit advertising.

Thanks and greetings from Berlin, also to @Nat,
Jan
Susan on October 15, 2015 at 5:55 pm

Fantastic article! Thanks for sharing. We’ll be transitioning our Snom 760s to provision from Lync shortly.

Are there any licensing concerns involved?
Ben Lee on October 15, 2015 at 6:11 pm

Thanks Susan,
From a licensing point of view you need to make sure you have the UC license for the SNOM phones and on the Lync side if you are doing Enterprise Voice need a Plus CAL for the user concerned…

Hope that helps?

Ben
Ben Lee on October 15, 2015 at 6:12 pm

Thanks Jan 🙂
Susan on October 15, 2015 at 6:12 pm

Thanks for the licensing info. It helps a lot!