Drivers Terratec Input Devices

Posted on by



The package provides the installation files for Microsoft USB Input Device Driver version 10.0.4. If the driver is already installed on your system, updating (overwrite-installing) may.

  1. Drivers Terratec Input Devices Device
  2. Drivers Terratec Input Devices Download
  3. Drivers Terratec Input Devices
  4. Drivers Terratec Input Devices Interface
  5. Drivers Terratec Input Devices Adapter
  1. Download Terratec TV-tuner drivers or install DriverPack Solution software for driver scan and update. Download Download DriverPack Online. Are you tired of looking for the drivers for your devices? DriverPack Online will find and install the drivers you need automatically.
  2. Device/driver settings. Find the IR receiver's device by looking in the dmesg output for a line similar to: input: IR-receiver inside an USB DVB receiver as /class/input/input4. Additionally, the IR receiver will be listed if you execute the command: cat /proc/bus/input/devices For example.
  3. AMD Rolls Out Its First 2021 Graphics Driver - Get Radeon 21.1.1 Intel Adds Support for Iris Xe Max Graphics (DG1) - Get Version 27.20.100.9168 The New RTX 461.09 Graphics Driver Adds Support for NVIDIA’s A40 GPU.
TerraTec-DT-USB-XS-Diversity-Stick

A DVB-TUSB device from TerraTec.

It is supported under Linux.

  • 1Overview/Features
  • 2Making it Work (generic for all dib0700)
    • 2.2Drivers
      • 2.2.3All relevant kernel modules options
    • 2.3Remote control support
      • 2.3.2Using LIRC
    • 2.4Specific to the Model
      • 2.4.1Specific Remote control support

Overview/Features

Features two tuners, and have two antennas. You’ll have adapter0 and adapter1 in /dev/dvb, which you can use separately.

The Diversity option is a hardware based feature that allows for the device’s two receivers to be configured in a combined use mode to achieve better reception on a single channel. The diversity feature of the DiBcom demodulators is currently not implemented in the Linux-DVB drivers, so only the dual tuner configuration is presently supported on such devices [1].

It seems that either this tuner stick does not have a very sensitive tuner, or the small antennas that come with it are simply insufficient for real-life use, unless one lives next door to a broadcast tower and has a direct line-of-sight to it. It is thus likely that an external antenna with a builtin amplifier is needed when this tuner is used.

Components Used

Identification

Two identical looking devices are known. They can be distinguished by their USB ID:

  • The first device has USB ID 0ccd:005a. It is supported by the official sources (see below).
  • The second device has USB ID 0ccd:0081. It is supported by the official sources since 14.01.2009 – make sure your sources are up to date.

Note: 0ccd is the Vendor USB ID (VID) of TerraTec, while 005a and 0081 are the Product USB ID (PID) of the sticks.

Other Images

  • front

  • back

  • Input plugs


Making it Work (generic for all dib0700)

Firmware

August 21, 2008 - New firmware file fixing the last cause for i2c errors and disconnects and providing a new, more modular i2c request formatting.

You will need the dvb-usb-dib0700-1.20.fw firmware file in /lib/firmware or the relevant place for your distribution.

You may need to change the name of the file to dvb-usb-dib0700-1.10.fw or create a link until the driver code reflects that change.

For archival purposes: dvb-usb-dib0700-1.10.fw firmware file

August 29,2008 - Issues with Firmware 1.20. Some issues have been found with the latest version of the firmware. Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch.

November 15,2008 - Issues with Firmware 1.20.

  • The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers
  • dvb-usb-dib0700-1.20.fw firmware file is now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed. The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect.
  • The mercurial drivers have been changed so they now load 1.20 firmware. To revert to 1.10 firmware you need to rename your firmware file to dvb-usb-dib0700-1.20.fw or provide a link of that name.
  • To avoid spurious remote control signals with 1.20 firmware, you need to edit /etc/modprobe.d/options or from Ubuntu onwards /etc/modprobe.d/options.confand add:

November 28,2008 - i2c errors. Changes were made to the remote control drivers on November 16,2008 to correct the repeat key problem. The card is generally stable for dual tuner reception and remote control function with Firmware 1.20.

November 10,2009 - mt2060 I2C write failed.Possible regression of a driver bug raised against Ubuntu running 2.6.27-14 and 2.6.31-2.17 causing mt2060 I2C errors in MythTV useage with firmware 1.20. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397696Recommend check the kernel extensions listed here for Low Noise Activation and rc_polling are loaded with correct config file name for your distribution, EIT listings information is turned off until a suitable delay (500ms-1000ms)is added to a single card (not both) and the card has correctly been added to the database as two tuners (no additional NULL entries) in the mythtv recordcard table.

Drivers

It requires the dib0700 driver. Just use Mercurial by following the How to Obtain, Build and Install V4L-DVB Device Drivers instructions.

Forcing the activation of LNAs (Low Noise Amplifier)

You may have to force LNA to get this card working:

In /etc/modprobe.d/options add:

Drivers Terratec Input Devices Device

Disabling the remote control sensor

You may want to disable the remote control sensor if you are using another one and want to avoid error messages in the logs:

In /etc/modprobe.d/options add:

All relevant kernel modules options

In /etc/modprobe.d/options add:

Get the parameters list using

The debug values are bit fields, with each bit representing a different category. Add values to turn on multiple debugging categories.

dib3000mc
debug
Turn on debugging
Values: integer
Default: 0 (off)
buggy_sfn_workaround
Enable work-around for buggy SFNs
Values: integer
Default: 0 (disabled)
mt2060
debug
Turn on debugging
Values: integer
Default: 0 (off)
dvb_usb_dib0700
force_lna_activation
Force the activation of LNAs (Low Noise Amplifier), if applicable for the device
Values: integer
Default: 0 (automatic/off)
dvb_usb_dib0700_ir_proto
Set IR protocol
Values: integer 0=NEC, 1=RC5, 2=RC6
Default: 1
debug
Set debugging level
Values: integer (bitmap) 1=info, 2=fw, 4=fwdata, 8=data
Default: 0 (none)
dvb_usb
debug
Set debugging level
Values: integer (bitmap) 1=info, 2=xfer, 4=pll, 8=ts, 16=err, 32=rc, 64=fw, 128=mem, 256=uxfer
Default: 0 (none)
disable_rc_polling
Disable remote control polling
Values: integer
Default: 0 (enabled)
force_pid_filter_usage
Force all DVB USB devices to use a PID filter, if any
Values: integer
Default: 0 (disabled)
dvb_core
dvb_net_debug
Enable debug messages
Values: integer
Default: 0 (disabled)
frontend_debug
Turn on frontend core debugging
Values: integer
Default: 0 (off)
dvb_shutdown_timeout
Wait n seconds after close() before suspending hardware
Values: integer
Default: 0
dvb_force_auto_inversion
Set whether INVERSION_AUTO is forced on
Values: integer
Default: 0 (off)
dvb_override_tune_delay
Wait n milliseconds for lock after a tuning attempt
Values: integer
Default: 0
dvb_powerdown_on_sleep
Turn LNB power off on sleep
Values: integer
Default: 1 (enabled)
cam_debug
Enable verbose debug messages
Values: integer
Default: 0 (off)
debug
Turn on debugging
Values: integer
Default: 0

Drivers Terratec Input Devices Download

dvbdev_debug
Turn on device debugging
Values: integer
Default: 0 (off)
dibx000_common
debug
Turn on debugging
Values: integer
Default: 0 (off)

Remote control support

Using evdev

As long as the evdev module is loaded, a remote that is recogniced as hid device will be treated as a usb keyboard and this means that you can avoid using lirc.

However, many of the keys on your remote may generate keycodes which are not mapped to anything, by default.

In X you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys may generate keycodes that X doesn't recognize at all and the device does not support keymaps, or this would be easy to fix.

Using LIRC

Usually remote controls in linux are managed by the lirc software collection.

To get lirc up and running you need to configure some things.

  • Settings for the hardware
    • Where does lirc get its input from? aka. the DEVICE. E.g. /dev/input/event3
    • How to handle the input? aka. the DRIVER. E.g. devinput
  • Settings for mapping driver output generated by your remote (a bunch of hex numbers) to key names (something like 0..9, Volume+, Next, Record)
  • Settings for mapping key presses to actions (usually located in your .lircrc)
Mythubuntu case

On mythubuntu 10.10, you just have to add this line in /etc/udev/rules.d/65-persistent-hauppauge.rules

Device/driver settings

Find the IR receiver's device by looking in the dmesg output for a line similar to:

Additionally, the IR receiver will be listed if you execute the command:

For example:

In this example, the remote control gives output into /dev/input/event4.

The event number depends on your particular system and can vary.

Drivers Terratec Input Devices

Eventually this event number can even vary at every reboot.

You could create a new udev rule in /etc/udev/rules.d/65-persistent-hauppauge.rules.

This would make IR receivers handled by the usb_dvb framework always always be linked to /dev/input/dvb-ir.

But Linux systems running recent udev will automatically create non-varying names, a nicer and automatic way of providing a stable input event name:

LIRC will use it without needing a special kernel module. use the dev/input (or devinput. Check this with the command 'lircd --device=help'.) driver and specify the input event device in /etc/lirc/hardware.conf

If you have REMOTE and TRANSMITTER sections in your hardware.conf file, they should look like this:

Remote key setup

See device specific section below or try [2].


Sample .lircrc

A sample .lircrc can be found LircrcExample here.

Keys repeated twice

But there is still the problem of the key repeats for it, so that each keypress will be repeated twice. The patches, as mentioned above, may not work, but a workaround is possilbe. It is described in http://ubuntuforums.org/showthread.php?p=4253678

Simply add config = echo ' > /dev/null before the main config in .mythtv/lircrc or .lircrc

So each 2nd keypress will be suppressed. This works in some application but not others (e.g. vlc).

Alternatively there is a patch for the kernel driver that solves it, it can be found here.

Finally if that doesn't work and you have the silver remote (A415-HPG-WE-A) then changing the lircd.conf line as follows can prevent the duplicate key presses. This has the side-effect of disabling key repeats for the remote entirely. Changetoggle_bit_mask 0x80000000totoggle_bit_mask 0x00000000

Note: do not try to comment out (using #) any line in this file, or lirc won't work anymore.

Do NOT do this:

Replace the original line instead.


Specific to the Model

Specific Remote control support

The remote is supported at least in the Mercurial repository (see Drivers section above).

TerraTec gray-orange remote

Apparently this remote is sold with (at least) the TerraTec Cinergy DT USB XS Diversity, TerraTec Cinergy 2400i DT, and TerraTec Cinergy T USB XXS.

The dvb-usb-dib0700 module needs to be loaded with the option dvb_usb_dib0700_ir_proto=0 to set the IR protocol to NEC (which is used by this device).

The following keycodes should work with it, specify them in /etc/lirc/lircd.conf:

Note: the most recent model of this remote requires four different codes (replace them in above list).

Should you need to quickly test all possible keycodes, just use this script to generate a list, which you can copy/paste to your lircd.conf file:

The result looks like this:

Copy these keycodes just after the begin statement of your lircd.conf file.You can leave the original keycodes, duplicated values are not a problem.Once lircd is restarted, run the irw program and press your remote keys to show the missing codes:

Sample Kernel Output

From 2.6.23-tuxonice-r6 (gentoo) with drivers compiled from repository 11th Feb 08:

User Experiences

See the talk page.

External Links

Retrieved from 'https://www.linuxtv.org/wiki/index.php?title=TerraTec_Cinergy_DT_USB_XS_Diversity&oldid=32249'
Front view of the Terratec Grabby device

An USB audio/video capture device from TerraTec.

  • 2Rev 1/2
    • 2.4Making it Work
  • 3Rev 3
    • 3.4Status

Overview/Features

  • USB interface
  • Inputs: Composite, S-Video and Snapshot button
  • Leds: Power (green) and Record (red)

Rev 1/2

Components Used

  • EM2860 (USB interface)
  • EMP202 (audio codec)
  • SC8113 (Video Signal Processor)
  • FM24C02C (eeprom)

Other Images

  • Grabby board (front)

  • Grabby board (front - high resolution)

  • Grabby board (back - high resolution)

Identification


Making it Work

Basic support since kernel v4.6.

Assuming video device is `/dev/video1` with composite input and audio device is `hw:2,0`:

  • under vlc (recommended):

NOTE: vlc apparently can't deduce all acquisition parameters on it's own, so we have to specify width/height parameters.Also, a bit of caching is necessary to have proper audio/video. Here I use 10ms to have minimal latency.

Terratec
  • under mplayer:

NOTE: we need to force audio, disable immediate mode and set proper audio rate to have sound.


Firmware

Input

No firmware is required.


Drivers

Sample Kernel Output


Remote Control Support

Remote Control is not supported.

Rev 3

This is a very different model, based on a CX23103.

Components Used

All the components are on the front side of the board, the back is empty.

Terratec
  • CX23103
  • 77117 1532J 55058
  • 24C02RP K537P (eeprom?)


Other Images

  • Grabby Rev3 open

  • Grabby Rev3 board

Identification

Status

On a Debian Stretch with a 4.7.8-1 kernel, the Grabby v3 works with ffplay and qv4l2, but the picture quality is not very good, sometimes some lines or the whole display 'jumps'. And with some video sources captured on Linux, there is more noise than signal while those same video sources display ok with the Windows drivers.

Drivers Terratec Input Devices Interface

Audacity can capture the sound properly but qv4l2 sound output stutters a lot and keeps displaying the following errors :


Firmware

The driver loads v4l-cx231xx-avcore-01.fw into the Grabby.

Drivers Terratec Input Devices Adapter

The windows drivers CD also contains a firmware with the following MD5 hash : a9f8f5d901a7fb42f552e1ee6384f3bb

Drivers

The Grabby v3 use the following kernel module : cx231xx

Sample Kernel Output

At some point, I also got a crash:

Remote Control Support

Remote Control is not supported.

External Links

Retrieved from 'https://www.linuxtv.org/wiki/index.php?title=TerraTec_Grabby&oldid=36450'