Aug 102015

As many of you know, Google is removing support for NPAPI in the Chrome browser. Our existing JavaScript SDK utilizes this API. We have been diligently working on a new communication mechanism that will work on all browsers and will avoid such things as NPAPI and Active-X and will decouple the SDK from browser specific implementations.

The good news is that we are currently testing our new communication protocol and it will be ready for a Beta release soon.

We have worked hard to make sure that the new SDK will be backwards compatible. There will be the addition of an initialization method, but the existing API works the same.

Our new SDK will utilize TCP/IP to communicate between the browser and a Windows service running on the client machine. The new service will be installed with DLS when upgrading to the new version. A range of ports will be available for our windows service, if the browser cannot bind to one of the ports, it will fall back to our legacy plug-in architecture. For additional security, the service will accept connections only from localhost.
Stay tuned to this blog for more information.

Dec 042014

A some may be already aware of, Google has announced that it will phase out support for NPAPI in Chrome with the ultimate removal in Sept 2015.   We use NPAPI in the framework for plugin support for most browsers except for IE which we use an ActiveX plugin.  We are investigating alternatives to NPAPI but we have not come up with a solution yet.

In the mean time before Sept 2015, you will have to possibly change several settings in your Chrome browser in order to use the DYMO Label Framework:

  1. Click on the Chrome Customize button in the upper right of your browser
  2. Find the Settings option
  3. Click on the “Show Advanced Options” link
  4. Click on the “Content Settings” button or browse to chrome://settings/content
  5. Verify that “Allow all sites to run JavaScript” is enabled
  6. Verify that under Plug-ins that “Run Automatically” is selected
    1. You can check in the “Plug-in exceptions” to see if the site you are running the Framework from is set to “Allow” instead of “Block”
  7. Verify that “Unsandboxed plug-in access” is not set to “Do not allow any sites….”



This should get things working.

Another work around, though less than ideal is to use the extension IE Tab.  This will put a web page into an IE browser tab within Chrome and will use the ActiveX plugin instead of the NPAPI version.  It has options to add a wild card URL that will automatically use the IE Tab when it matches.  We recognize that this is not a valid long term solution.

Update (4/15/2015)
With version 42 of Chrome, Google now disables NPAPI which is required to run our plugin. However, you can manually enable it by typing the following into the Chrome address bar and adjusting the setting:

Update (4/20/2015)
It has been our experience that just enabling NPAPI may not be enough. In some instances, close the chrome browser then uninstall and re-install the DLS software for the plugin to appear in the plugin list: chrome://plugins/
Go here to see if your browser has the framework installed correctly: Check Environement

Update (5/8/2015)
In some situations, a full shutdown and reboot is required after all the steps have been performed for the plugin to appear in Chrome.

Sep 032014

Some LabelWriter 450 and 450 Turbo label printers manufactured after April 1, 2014 will not install properly on computers running Windows 7 when connected through a USB 3.0 port. DYMO has a software update available that will fix this problem. For assistance, check here to determine if your label printer is affected and to install the software update. You can also call DYMO Customer Support at 1 (877) 724-8324, Monday-Friday, 8 am – 6 pm (EST).

Mar 242014

Hello everyone!

A new version of our JavaScript library is now available. This version fixes several printing issues specific to Internet Explorer 11.

The new DYMO Label Framework JavaScript Library 1.2.6 is available here: http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.1.2.6.js

The latest has been updated to version 1.2.6 as well: http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.latest.js

Jan 022014

There is currently a bug in Windows 8.1 that causes any label with a barcode to print abnormally in DLS. We are awaiting a fix from Microsoft, but in the meantime, you will need to modify a setting in DLS to workaround the issue. To do this, go to Edit -> Preferences. Navigate to the LabelWriter printer tab and change the “Print Quality” to “Text”.


There is one side effect to making this change and that is your labels will always print at a resolution of 300×300 DPI. For barcodes, we typically like to switch our printers into high resolution mode (300×600 DPI) in order to improve barcode scanning reliability. When the “Print Quality” setting is set to “Auto” or “Barcodes and graphics”, the resolution will always be 300×600 if a barcode is present on your label. That being said, for most barcodes, 300×300 DPI is plenty of resolution. You may encounter scanning issues for barcodes with lots of data or 2D barcodes, though.

We apologize for this inconvenience and will keep everyone updated on a fix for this issue.

Microsoft has released a fix for this issue. It can be downloaded from the below links. Thanks Bjorn for the heads up!

KB2911106, released on 13/01/2014, solved this issue in Windows 8.1
Download x86 : http://www.microsoft.com/en-us/download/details.aspx?id=41569
Download x64 : http://www.microsoft.com/en-us/download/details.aspx?id=41570

Nov 202013

Hello everyone!

A new version of our JavaScript library is now available. This release addresses compatibility issues with IE11. If your web application is compatible with IE11, we strongly recommend that you upgrade to the new version.

The new DYMO Label Framework JavaScript Library 1.2.5 is available here:  http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.1.2.5.js

The latest has been updated to version 1.2.5 as well: http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.latest.js

Nov 122013

Hello everyone,

Today marks the first of our featured software posts. Over the coming weeks and months, we will highlight real applications that use the DYMO SDK. These posts will provide information and quotes from DYMO SDK developers/customers/users/etc. explaining how they were able to successfully integrate DYMO printers into their real world solutions. First up today, Datarecovery.com.

Michael, a programmer/analyst working at Datarecovery.com, says:

At Datarecovery.com, Inc., we use DYMO label printers crucially in our business to keep track of clients’ problem hard drives and other storage media at our offices, as well as the new drives we use for returning data, clone drives we use in recovery work, the containers we store case materials in, and any other equipment and materials associated with a data recovery case. With the DYMO SDK and label templating, we were able to integrate one-click printing of all labels needed into our case tracking system. Once newly received case materials have been checked into our system, we have a “Quick Labels” link that immediately prints labels based on what items were just checked in. We’ve also made a simple jQuery dialog that allows for printing different quantities of the various types of labels at will. The labels include the case number, item type code, checked in date, last name initial, and a barcode for scanning into our system. The extremely simple process, enabled by the DYMO SDK, results in aiding in our critical tracking of all case items.

Here are some screenshots showing how Datarecovery.com has integreated DYMO printers into their case tracking system:


If you would like to learn more about Datarecovery.com, please visit their website at www.datarecovery.com. If you would like your DYMO SDK application featured here on the blog, please comment on the following blog post with more information about your software: http://developers.dymo.com/2013/10/31/calling-all-dymo-sdkers/

Oct 312013

Hello again,

We at DYMO our very appreciative of our SDK community. Over the years, we’ve seen some very interesting and cool applications that integrate with DYMO printers. We thought it would be fun to showcase some of these applications here on our developer blog! If you’ve been involved with the creation of a DYMO SDK application and would like to have it shown here on the blog, just comment on this post with some information about your application (description, pictures, website link, etc.). We’ll sort through all of the responses and pick some of our favorites and showcase them on the blog. We’ll keep all of the responses private and contact those that we want to showcase directly before posting anything to the blog. We look forward to seeing what everyone has created!

Sep 302013

A quick post here to help out some of our developers that are integrating CardScan into their applications. We receive quite a few CardScan SDK questions and usually we have to forward them over to the correct support group. This is due to a miscommunication on our part, and we wanted to get the correct CardScan SDK support information out there. All CardScan SDK questions should be directed to the email and phone numbers below. We apologize for any confusion.

Email: [email protected]

Phone: 800-942-6739×1   M-F, 8:30am-5:30pm EST

Aug 142013

Hello everyone,

We thought it would be helpful to have sort of an “interactive” post where you could ask questions about our SDKs. Here’s how it will work:

  • Add a comment to this post asking any question you like regarding DYMO SDKs. It can be anything: how to setup a simple SDK application, potential bugs you may have encountered, etc.
  • We will sort through your questions and pick a some of the best ones to answer in this post.
  • This post will be updated with the questions and answers so everyone can see them

Once we’ve picked out the best questions, we’ll approve all of the other questions and they will appear in the comments section of this post so other developers can help you out. We’re looking forward to your questions!

  1. Is there a way to interact with Dymo label printers from an iOS app? Sample app would be great. (from Steven Hepting)

Currently, the only way to print from an iOS device is using the DYMO Proxy Service that is installed with DLS. This service acts as the “middle-man” between your iOS device and your DYMO printers. For more information on how to use this proxy service, see the following blog posts: http://developers.dymo.com/tag/ios/. Please note that this service is still in BETA and has not been extensively tested outside of DYMO.

  1. Is the proxy service available for Mac? (from Matthew Dever)

The proxy service is a Windows only tool. Also note, the proxy tool is a beta release and there are no plans to move it out of beta.