Posts Tagged ‘interface’
Demo of the HGR2488 Monitor interface for the TASCAM 2488
Posted by Parkzone Corsair in computer on September 4th, 2010
The TASCAM 2488 is a fantastic multitracker, but trying to view its small display when you are not directly in front of it or when you have an instrument hung round your neck can be a real problem. The HGR-2488 Monitor Interface Card provides the solution. This circuit board fits inside the TASCAM-2488 and reproduces the TASCAM’s LCD display on a standard PC monitor. The large screen format provided by the HGR-2488 allows the musician the freedom to create music away from the 2488, meaning you (and the rest of the band) can easily see what’s happening. For TASCAM 2488 MK1 users the low brightness of the LCD display is no longer a major drawback. No more eye strain! The HGR-2488 has been designed to be as simple as possible for the user to install inside the TASCAM 2488 without the need for soldering, special tools or modifications to the TASCAM 2488 casing. It is essentially ‘plug and play’ The HGR-2488 provides the following features: Display of the TASCAM 2488 LCD on a VGA compatible PC monitor or LCD panel Everything displayed on the TASCAM 2488 LCD is replicated on the PC monitor Display is white text on a blue background with a black border VGA mode is 800 x 600 @ 60HZ TASCAM 2488 LCD remains fully functional whether or not the PC monitor is connected No PC required — just the TASCAM 2488 and a monitor Simple to install
The Device Uses USB or Another Interface
Posted by Parkzone Corsair in USB on December 15th, 2009
To communicate with USB devices, a computer needs hardware and software that support the USB host function. The hardware consists of a USB host controller and a root hub with one or more USB ports. The software support is typically an operating system that enables device drivers to communicate with lower-level drivers that access the USB hardware.
A typical PC has one or more hardware host controllers that each support multiple ports. The host is in charge of the bus. The host has to know what devices are on the bus and the capabilities of each device. The host must also do its best to ensure that all devices on the bus can send and receive data as needed. A bus may have many devices, each with different requirements, all wanting to transfer data at the same time. The host’s job isn’t trivial.
Fortunately, the host-controller hardware and drivers in Windows and other operating systems do much of the work of managing the bus. Each device attached to the host must have an assigned device driver that enables applications to communicate with the device. System-level software components manage communications between the device driver and the host controller and root hub.
Applications don’t have to know the hardware-specific details of communicating with devices. All the application has to do is send and receive data using standard operating-system functions or other software components. Often the application doesn’t have to know or care whether the device uses USB or another interface. The host performs each of the tasks described below.
The Device Supports A Boot Interface
Posted by Parkzone Corsair in USB on December 6th, 2009
In the interface descriptor, bInterfaceclass = 03h to identify the interface as a HID. Other fields that contain HID-specific information in the interface descriptor are the bInterfaceSubclass and bInterfaceProtocol fields, which can specify a boot interface.
If bInterfaceSubclass = 01h, the device supports a boot interface. A HID with a boot interface can communicate with the host even when the host hasn’t loaded its HID drivers. This situation might occur when the computer boots directly to DOS or when viewing the system setup screens that you can access on bootup, or when using Windows Safe mode for system troubleshooting.
A keyboard or mouse with a boot interface can use a simplified protocol supported by the BIOS in many hosts. The BIOS loads from ROM or other non-volatile memory on bootup and is available in any operating-system mode. The HID specification defines boot-interface protocols for keyboards and mice. If a device has a boot interface, bInterfaceProtocol indicates if the HID supports a keyboard (01h) or mouse (02h) function. The HID Usage Tables document defines the report format for keyboards and mice that use the boot protocol. The BIOS understands the boot protocol and assumes that a boot device will support the protocol, so the BIOS doesn’t need to read a report descriptor from the device.
