Anysee E30 C Plus not tuning under Ubuntu 12.04 LTS

Asked by n00b4life on 2012-09-27

Hello, I'm not able to do a frequency scan with an Anysee E30 C Plus USB connected DVB-C adapter.

I'm running Ubuntu 12.04 LTS with kernel version 3.2.0-31-generic-pae. Anysee E30 C Plus should be supported in the kernel.

From dmesg I can see that my Ubuntu recognizes the adapter:
[ 14.964580] dvb-usb: found a 'Anysee DVB USB2.0' in warm state.
[ 14.964624] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 14.964625] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 14.965199] DVB: registering new adapter (Anysee DVB USB2.0)
[ 14.967084] anysee: firmware version:1.2 hardware id:15
[ 15.179332] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...
[ 15.212706] tda18212: NXP TDA18212HN successfully identified
[ 15.776301] dvb-usb: schedule remote query interval to 250 msecs.
[ 15.776303] dvb-usb: Anysee DVB USB2.0 successfully initialized and connected.
[ 15.778227] usbcore: registered new interface driver dvb_usb_anysee

So, why can't dvbscan, VLC, TV Headend or Kaffeine do a frequency scan with the Anysee?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu linux Edit question
Assignee:
No assignee Edit question
Last query:
2013-02-23
Last reply:
2013-03-11
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #2

Using the command 'lsusb -vvd 1c73:861f', I got this the information about my Anysee E30 C Plus:

Bus 001 Device 002: ID 1c73:861f AMT Anysee E30 USB 2.0 DVB-T Receiver
Couldn't open device, some information will be missing
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x1c73 AMT
  idProduct 0x861f Anysee E30 USB 2.0 DVB-T Receiver
  bcdDevice 1.00
  iManufacturer 1
  iProduct 2
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 83
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 4
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 0
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 1
      bNumEndpoints 4
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 0
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x1400 3x 1024 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x1400 3x 1024 bytes
        bInterval 1

n00b4life (sampo-uosukainen) said : #3

I tried to do a channel scan with 'w_scan -fc -c FI -X':

w_scan version 20111203 (compiled for DVB API 5.4)
using settings for FINLAND
DVB cable
DVB-C FI
frontend_type DVB-C, channellist 8
output format czap/tzap/szap/xine
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
 /dev/dvb/adapter0/frontend0 -> DVB-C "Philips TDA10023 DVB-C": good :-)
Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.4
frontend 'Philips TDA10023 DVB-C' supports
INVERSION_AUTO
QAM_AUTO not supported, trying QAM_64 QAM_256 QAM_128.
FEC_AUTO
FREQ (48.00MHz ... 862.00MHz)
SRATE (0.500MBd ... 8.000MBd)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
searching QAM64...
146000: sr6900 (time: 00:00) sr6875 (time: 00:03)
154000: sr6900 (time: 00:05) sr6875 (time: 00:08)
162000: sr6900 (time: 00:10) sr6875 (time: 00:13)
...
searching QAM256...
...
searching QAM128...
...
842000: sr6900 (time: 22:49) sr6875 (time: 22:52)
850000: sr6900 (time: 22:54) sr6875 (time: 22:57)
858000: sr6900 (time: 23:00) sr6875 (time: 23:02)

ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!

n00b4life (sampo-uosukainen) said : #4

I should add that I have verified, using a Windows 7 machine and the same RF signal, that my Anysee E30 C Plus is fully functional.

Launchpad Janitor (janitor) said : #5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #6

This problem still exists.

Launchpad Janitor (janitor) said : #7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #8

This problem still exists.

Launchpad Janitor (janitor) said : #9

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #10

This problem still exists.

Launchpad Janitor (janitor) said : #11

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #12

This problem still exists.

Launchpad Janitor (janitor) said : #13

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #14

This problem still exists.

Launchpad Janitor (janitor) said : #15

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #16

This problem still exists.

Launchpad Janitor (janitor) said : #17

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #18

This problem still exists.

Launchpad Janitor (janitor) said : #19

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

n00b4life (sampo-uosukainen) said : #20

This problem still exists.

Launchpad Janitor (janitor) said : #21

This question was expired because it remained in the 'Open' state without activity for the last 15 days.