Dusky Sky Controller

[coley]

A quick search of the forums returns quite a few hits on the dusky sky controller.
There seems to be numerous starts at getting it integrated - but I don't see any templates/devices having been completed.

What is done/not done?
What is the best approach for integration?

I'd like to get this PnP and am willing to do the legwork to achieve this.

-Coley.

[tschak909]

I do not know of any device templates submitted.

This would have to be done.

But also, any packages required to make it work, would also need to be folded into the build.

Also, can the dusky stuff be detected, a la USB etc?

-Thom

[coley]

Yep, the little unit can be detected when its plugged in, at least the USB ver is, I don't have the serial one to check.

Code:

root@moon264:~# lsusb -v -d6666:f100

Bus 004 Device 004: ID 6666:f100 Prototype product Vendor ID
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x6666 Prototype product Vendor ID
  idProduct          0xf100
  bcdDevice            9.04
  iManufacturer           1 Dusky Control
  iProduct                2 Sky/Sky+ Digibox Controller
  iSerial                 0
  bNumConfigurations      2
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           41
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          3 Config. 1: HID
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.00
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      81
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     2
    iConfiguration          4 Config. 2: non-HID
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      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     0x0008  1x 8 bytes
        bInterval              10
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
Device Status:     0x0001
  Self Powered

-Coley.

[tschak909]

Okay, then that goes into the pnp section of the device template. Now you need to make a device template, either C++ or GSD that can control the device.

I am a C++ person myself, but...

-Thom

[coley]

Thom,
Is C++ overkill for this? I'll try either but the device is just one-way comms. Injects remote commands in the rf port of the box.

I tried a GSD device template and the orbiter pops up that its detected.
Now what commands go into the device? as its not so much an end point or device to be controlled but for another device e.g. the sky box, to be "controlled via" this.

thanks
-Coley.

 - spotted edit Ruby codes, I guess I should be looking in there

[tschak909]

this is a "cable box" ... keep in mind, that LinuxMCE needs to have commands for things you need to be able to do.. look at the other cable box templates for ideas.

-Thom

[coley]

The unit I have just controls one box, but they are available to control multiple sky boxes, would each sky-box then be a child of this device?
Is it not more along the lines of something like a USB-UIRT?

thanks
-Coley.

[tschak909]

then each device would be a child of the interface device, and would be dealt with in RecievedCommandForChild.

If you use a UIRT, you could..but you would lose bi-directional control. maybe this is important, maybe it isn't.

But also keep in mind that a UIRT can only deal with one IR zone at a time, so two Sky boxes, unless they can respond to two different sets of IR codes, would not work in this situation.

-Thom

[coley]

Sorry Thom, maybe I wan't clear enough, I don't have a UIRT, but was thinking of it conceptually as a similar interface.
Md/core  -> Dusky - OP1 -> skybox1
                            - OP2 -> skybox2
                                       .
                                       .
                            - OP(n) -> skybox(n)

-Coley.

[tschak909]

Yes. It's set up the same way in the device tree. As I said, you deal with DCE::ReceivedCommandForChild, basically dealing with the commands that come across it like a giant switch statement....

So you have two device templates:

(1) an interface device template
(2) a child device template with all the commands of the box.

And the switch() inside ReceivedCommandForDevices() deals with passing on commands from (1) to (2)

-Thom

[coley]

Ok, so I'm guessing (1) the interface device template needs to be a DCE device - C++, and then I can reuse the sky plus template that already exists for (2) and add my new interface as a parent, i.e. it can be controlled by either IR interface or this.

thx
-Coley.

[tschak909]

unfortunately, since the child device already probably has IR commands in it.. i'm not sure.. you could try...

-Thom

[gtsupport]

@ Coley,

How did things go with the template for this device??  I've got one, but as I could never get it working its sitting in a box somewhere.  Is it time to dust the thing off and give it another try?  I don't have the expertise to develop this myself, but am sending you much good will and encouragement on behalf of anybody who has tried to get these working in the past 

Matt

[coley]

Unfortunately my free time is a bit curtailed with a new baby girl at the moment, hopefully I'll get back to this soon.

-Coley.

[totallymaxed]

Unfortunately my free time is a bit curtailed with a new baby girl at the moment, hopefully I'll get back to this soon.

-Coley.

What are you even doing in here... Congratulations on becoming a dad :-)

All the best to you and your family

Andrew