Re: Labview driven USB Label printer



HaemoPhil wrote:Dear Labview user,

I'm looking to implement a USB Label printer into my Labview
application, this printer should print out some parameters that where
used in the running application.
Does someone of you know if there exemple exist for such USB
communication system or did some one already experienced USB
communication with Labview and a third part device like a printer.
Unfortunately USB is not just another
communication interface with an according API to program like you are
used with serial or GPIB. USB is just the lowest level of the
electrical specification and protocol for an interface and the actual
data transfer is then managed in a differnt protocol level that is
highly device specific.

VISA does allow to communicate with USB devices on raw level which
means you have to implement the higher level protocol yourself. But
without the exact protocol specification used by the device you can't
do that and many devices especially in the consumer area do not really
specify the exact protocol they use or use one of the predefined
protocol classes all modern OS do already have some protocol support
for.

As such it is difficult to give a generic advice that would fit all USB
devices. Printers I would expect to be handled by the Windows printer
manager and should be accessed through the standard Windows printer
interface. Label Printers are somewhat special as they do not fit well
into the page oritented printing system Windows and most other OS's are
using so they usually have their own application that controls them.
This application accesses the label printer usually over a proprietary
protocol interface. While the protocol itself is almost never disclosed
the interface API sometimes is and that can be either a DLL interface
or an Active X Automation Server interface (and newer versions probably
Net).

Depending on what interface is provided AND documented you will either
have to use the Call Library Node to access the interface API DLL or
the Active X (or .Net) functions to get the according interface
running. Trying to talk to the device on USB raw is no option IMHO
eventhough the protocol may be documented  (which is highly
unlikely).

Rolf Kalbermatter
.



Relevant Pages

  • [Full-Disclosure] FW: Cisco Vulnerability forensic protocol analysis results.
    ... AMILABS CISCO IP PROTOCOL EXPLOIT TESTING RESULTS ... Cisco router interfaces using either all or one of the following IP ... of a remote Cisco interface uses all of them. ... output buffer failures, 0 output buffers swapped out Router4# ...
    (Full-Disclosure)
  • Re: [RFC v2] Another approach to IR
    ... This is the same as protocol selection for psmouse ... This has nothing to do with the raw interface nor with lirc. ... happens with the evdev interface and already affects the in-kernel drivers. ... On IR remote receivers, internally, there's just one interface per hardware. ...
    (Linux-Kernel)
  • Re: [discuss] 2.6.19-rc5: known regressions (v2)
    ... ACPI: IRQ0 used by override. ... registered new interface driver usbfs ... USB Universal Host Controller Interface driver v3.0 ... root hub lost power or was reset ...
    (Linux-Kernel)
  • Re: [RFC v2] Another approach to IR
    ... This is the same as protocol selection for psmouse ... This has nothing to do with the raw interface nor with lirc. ... happens with the evdev interface and already affects the in-kernel drivers. ... since it only applicable to IR, not to input devices in general. ...
    (Linux-Kernel)
  • Re: [RFC v2] Another approach to IR
    ... This is the same as protocol selection for psmouse ... This has nothing to do with the raw interface nor with lirc. ... happens with the evdev interface and already affects the in-kernel drivers. ... since it only applicable to IR, not to input devices in general. ...
    (Linux-Kernel)

Loading