LCDproc development and user support list

Text archives Help


[Lcdproc] Ricavision VFD USB module


Chronological Thread 
  • From: petr at palacky.net (Petr Palacký)
  • Subject: [Lcdproc] Ricavision VFD USB module
  • Date: Fri, 17 Dec 2010 17:21:32 +0100

Hi all,

because this display is designed for Win XP MCE, I tried to sniff USB
communication with SnoopyPro (you can download it from SF:
http://sourceforge.net/projects/usbsnoop/)...

1. Step
VFD is not connected.
When I connect VFD module, the display shows time "00:00:01" for a moment,
than switch to text "PC".
I repeated this step 3-times...

2. Step
VFD is not connected.
When I connect VFD module, the display showing time "00:00:01" for a moment,
than showing text "PC" (the same as in 1. step).
Next I run MediaCenter program. Now the VFD shows text (rolling from right to
left) "Welcome to Media Center Home". The volume icon is activated and volume
progress bar shows actual volume level.
Next I click on menu "My Photos" - text on VFD is now switched to static
text "My Photos".
I also click on MCE's volume button (+), the VFD shows every time actual
level.

Please, see attachment where are two filetypes for each step (SnoopyPro
format
*.usblog and standard *.xml).

Because I am not a programmer I would like to ask you if Is there possibility
on writing driver for lcdproc if I make complete reports of "what I do" and
with data from USB sniffer?

Thank you for help

Best regards
--
Petr Palacky

On Wednesday 15 of December 2010 16:03:20 Petr Palack? wrote:
> Hi guys,
>
> I have bought one of "Ricavision VFD" display connectable via USB but i am
> not able to playing with it under Linux. I found that this VFD module is
> designed for Win MCE (probably only?). After connecting +5V to the modul,
> VFD shows clock in format hh:mm:ss.
>
> Because Ricavision company is gone, I have no support nor full module name.
> On module board is text: "CWT_7046 V08".
> Display controller chip is brushed so I can not read its part number.
>
> You can see product image here:
> http://www.parkit.cz/picture/large/20090114212709578979882.JPG
>
> After connecting I can see that two new USB device were detected ...
>
> 05e3:0608 and 13ec:0030
>
> ... but no USB-serial device was created.
>
> /var/log/messages:
> ===============================================
> Dec 15 15:52:24 localhost kernel: [ 7456.424577] usb 4-3: new high speed
> USB device using ehci_hcd and address 16 Dec 15 15:52:24 localhost kernel:
> [ 7456.557772] usb 4-3: configuration #1 chosen from 1 choice Dec 15
> 15:52:24 localhost kernel: [ 7456.558267] hub 4-3:1.0: USB hub found Dec 15
> 15:52:24 localhost kernel: [ 7456.558596] hub 4-3:1.0: 4 ports detected Dec
> 15 15:52:24 localhost kernel: [ 7456.664518] usb 4-3: New USB device found,
> idVendor=05e3, idProduct=0608 Dec 15 15:52:24 localhost kernel: [
> 7456.664589] usb 4-3: New USB device strings: Mfr=0, Product=1,
> SerialNumber=0 Dec 15 15:52:24 localhost kernel: [ 7456.664645] usb 4-3:
> Product: USB2.0 Hub Dec 15 15:52:24 localhost kernel: [ 7456.864336] usb
> 4-3.1: new full speed USB device using ehci_hcd and address 17 Dec 15
> 15:52:24 localhost kernel: [ 7456.959503] usb 4-3.1: configuration #1
> chosen from 1 choice Dec 15 15:52:24 localhost kernel: [ 7456.963071] usb
> 4-3.1: New USB device found, idVendor=13ec, idProduct=0030 Dec 15 15:52:24
> localhost kernel: [ 7456.963131] usb 4-3.1: New USB device strings: Mfr=0,
> Product=0, SerialNumber=0
>
> # lsusb
> ===============================================
> Bus 004 Device 017: ID 13ec:0030
> Bus 004 Device 016: ID 05e3:0608 Genesys Logic, Inc.
>
> # lsusb -v -d 05e3:0608
> ===============================================
> Bus 004 Device 016: ID 05e3:0608 Genesys Logic, Inc.
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 9 Hub
> bDeviceSubClass 0 Unused
> bDeviceProtocol 1 Single TT
> bMaxPacketSize0 64
> idVendor 0x05e3 Genesys Logic, Inc.
> idProduct 0x0608
> bcdDevice 7.02
> iManufacturer 0
> iProduct 1 USB2.0 Hub
> iSerial 0
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 25
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0xe0
> Self Powered
> Remote Wakeup
> MaxPower 100mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 1
> bInterfaceClass 9 Hub
> bInterfaceSubClass 0 Unused
> bInterfaceProtocol 0 Full speed hub
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0001 1x 1 bytes
> bInterval 12
> Hub Descriptor:
> bLength 9
> bDescriptorType 41
> nNbrPorts 4
> wHubCharacteristic 0x00e9
> Per-port power switching
> Per-port overcurrent protection
> TT think time 32 FS bits
> Port indicators
> bPwrOn2PwrGood 50 * 2 milli seconds
> bHubContrCurrent 100 milli Ampere
> DeviceRemovable 0x00
> PortPwrCtrlMask 0xff
> Hub Port Status:
> Port 1: 0000.0103 power enable connect
> Port 2: 0000.0100 power
> Port 3: 0000.0100 power
> Port 4: 0000.0100 power
> Device Qualifier (for other device speed):
> bLength 10
> bDescriptorType 6
> bcdUSB 2.00
> bDeviceClass 9 Hub
> bDeviceSubClass 0 Unused
> bDeviceProtocol 0 Full speed hub
> bMaxPacketSize0 64
> bNumConfigurations 1
> Device Status: 0x0003
> Self Powered
> Remote Wakeup Enabled
>
> # lsusb -v -d 13ec:0030
> ===============================================
> Bus 004 Device 017: ID 13ec:0030
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.10
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 8
> idVendor 0x13ec
> idProduct 0x0030
> bcdDevice 2.41
> iManufacturer 0
> iProduct 0
> iSerial 0
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 34
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0xc0
> Self Powered
> MaxPower 0mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 1
> bInterfaceClass 3 Human Interface Devices
> bInterfaceSubClass 0 No Subclass
> bInterfaceProtocol 0 None
> iInterface 0
> HID Device Descriptor:
> bLength 9
> bDescriptorType 33
> bcdHID 1.10
> bCountryCode 0 Not supported
> bNumDescriptors 1
> bDescriptorType 34 Report
> wDescriptorLength 32
> Report Descriptor: (length is 32)
> Item(Global): Usage Page, data= [ 0xa2 0xff ] 65442
> (null)
> Item(Local ): Usage, data= [ 0xb0 ] 176
> (null)
> Item(Main ): Collection, data= [ 0x01 ] 1
> Application
> Item(Local ): Usage, data= [ 0xa9 ] 169
> (null)
> Item(Global): Logical Minimum, data= [ 0x80 ] 128
> Item(Global): Logical Maximum, data= [ 0x7f ] 127
> Item(Global): Report Size, data= [ 0x08 ] 8
> Item(Global): Report Count, data= [ 0x08 ] 8
> Item(Main ): Output, data= [ 0x02 ] 2
> Data Variable Absolute No_Wrap Linear
> Preferred_State No_Null_Position Non_Volatile
> Bitfield Item(Local ): Usage, data= [ 0x01 ] 1
> (null)
> Item(Global): Logical Minimum, data= [ 0x81 ] 129
> Item(Global): Logical Maximum, data= [ 0x7f ] 127
> Item(Global): Report Size, data= [ 0x08 ] 8
> Item(Global): Report Count, data= [ 0x08 ] 8
> Item(Main ): Feature, data= [ 0x02 ] 2
> Data Variable Absolute No_Wrap Linear
> Preferred_State No_Null_Position Non_Volatile
> Bitfield Item(Main ): End Collection, data=none
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0008 1x 8 bytes
> bInterval 1
> Device Status: 0x0000
> (Bus Powered)
>
> ==
>
> Is there anybody who knows this VFD module and know how to make it work
> under Linux?
>
> Thank you very much for your help



--

S pozdravem
--
Petr Palacky

Outgoing message is virus free
because we are using Linux.

Debian GNU/Linux 5.0.7, kernel 2.6.26-2-686.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SnoopyPro_VFD.tar.gz
Type: application/x-tgz
Size: 7975 bytes
Desc: not available
URL:
<http://lists.omnipotent.net/pipermail/lcdproc/attachments/20101217/837b6f2c/attachment.bin>




Archive powered by MHonArc 2.6.18.

Top of page