Back to things lmce - how have you the dusky devices integrated in the systems you supply?

thanks,-Coley.

We use our DCEwhisperer API for all our devices and that applies to the Dusky too. We have a Sky remote screen and we treat Sky boxes (and other devices like BluRay players) as 'External Devices' that accessible from the main menu screen.

We can't easily port the Dusky control from Dianemo to LinuxMCE, since we diverged from the standard way of doing things. It's not easy mainly because I have no idea how this is properly done (and hence the reason why Dianemo diverged )

I've tried to get this working for the past 2 years as a gsd, and have picked it up again a couple of days ago.The furthest I've got is a template which registers but will not work because "no com port specified".wether ComPortOnPc is used as a device data field or not

Udevadm info reports it as ....../hiddev0

After an intense weekend of research, I contacted J. Heenan ,the manufacturer, who has kindly provided the following

Quote""Hi Ian,

Right, I think I'm starting to understand a bit.

The basic issue is that the 'Generic Serial Device' driver in Lmce is intended only to talk to serial devices (or, oddly, network connections), and the USB dusky is not a serial device. It doesn't even pretend to be a serial device (lots of usb devices are actually serial devices with a usb <-> serial converter built in, but not the dusky).

The USB dusky is based around a PIC16C745 - it doesn't present anything like a serial interface, it is (in USB terms) a 'HID' device. You talk to it by providing binary packets of data to the linux USB HID subsystem.

There's probably 3 approaches that might work:

1) (Easiest) Swap your USB dusky for a serial model. That should then be directly possible to use with the GSD

2) Write a network listener that accepts commands from the lmce GSD and calls 'sky-control' to pass them to the sky box. It's probably still quite a lot of work though, I don't really fully understand what would be necessary and it's probably not a very clean solution.

3) (Hardest, I think) write a lmce 'device driver' that talks directly to the USB dusky, reusing the 'sky library' code that's used in sky-control.

Hope that helps!

Cheers,

Joseph"End Quote

SO......can anyone suggest a workaround without me having to learn C++? or would anyone of you beautiful genii hazard an estimate for writing the driver ? tho I must say it's unlikelythat I could afford this option on my own--- any other USB Dusky owners willing to chip in?

.can anyone direct me to a good beginners book on C++ ? does anyone have any experience with the PIC16C745...? can anyone suggest a similar/any lmce device that has a C driver, so I can study it's code?

Basically the C library needs to be taken and put into a DCE C++ device. Each command stub made by DCEGen needs to call an equivalent function inside the aforementioned C library to do the right thing.

I am pleased to announce the birth of a little code !!!! .........concieved in trepidation at 05:50 (first install of 10.04).............birthed by DCEGen at 11:45 today,...........fathered by my "hunt and peck" right index finger

..........midwifery duties most excellently performed by the developers and contributors (forums and wiki).....thank you all.

Many thanks for the encouragement thom, have you any suggestions regarding a "simple" IDE ?

BTW I'm taking notes on every step for a wiki entry,

If any other " novice" would like to make this a joint project SHOUT NOW please,

Ian,Suppose I should dust off my lmce hat and get stuck back in here!!As you gather from the thread I have one of these devices too.I had started a C++ dce device but lost the hd and lmce install that was on

Does your Dusky device control just the one sky box? or has it more than one o/p?

are you on 810 or 1004 ?are you up for making it a collaborative effort, or do you prefer to be alone in your closet ? (bear in mind that I'm on a VERY steep learning precipice here, so altho I've got time ,I'm gonna be slow SOoh slow