#DYMO LABELWRITER 400 DRIVER UPDATE#
With the text file, I could specify one of the printer's internal bar code fonts and the resolution was great. In order to download the latest DYMO Label software update click here. When I printed a label with the windows driver, the printer driver translated the third-party fonts as images and the resolution was fuzzy. When I used the text file method, I had a third-party font package installed.
You may find that everything looks perfect. If you want to print a bar code, see if the printer includes any windows bar code fonts and select one of them for your LabVIEW string control/indicator. You'll want to set the color of the front panel window to white and will probably have to play around some with the position of front panel controls to get everything to fit onto the label. I would suggest that you first create a LabVIEW front panel with some text that you need to print and just do a File>Print Window. I don't see anything in the Dymo api that is similar. There were a bunch of commands preceded by a '^' character and I could define font type, size, text, etc. USB Connection (Included With USB Cord For FREE) + Wired Ethernet Network Ready (Cat5) (75.00) + Optional Wireless Internet Network Ready (WiFi) (125.00) AC Adapter Type. The zebra printer I used had support for a low level language that the printer would recognize and interpret. The Dymo LabelWriter 400 desktop label printer is an affordable desktop label printer. The method I mentioned using with a text file may not be possible. I have no experience with this and I'm just speculating. You would still have to have an ActiveX interface to Word to create the data and invoke the macro. If you wanted to call another application to print, it might be done by importing the VB example into Word as a VBA macro. This would involve calling it's various methods and properties and is certainly possible but a bit tedious. Since it appears that they provide an ActiveX (Com) interface to the printer, you could use the ActiveX functions in LabVIEW.
0 kommentar(er)
