Messages

yikes, dude... *thwap-you-upside-the-head*

This is why you talk to us beforehand.

You should do the library either in C++ or Ruby.

hahah, yeah the lib is part of a bigger project so no go there, I'll jump on IRC some time and have a chat to you

Yeah I'll come have a chat to you guys on IRC in a few days I reckon, just dealing with a small checksumming issue on my comms library and then it should be on like donkey kong.

The library/app is a .NET assembly that runs under mono, so I'm thinking to get things done to start with I'll P/Invoke the existing libraries to talk DCE back to the DCERouter (and maybe write a native .NET lib for it later).

Might be easiest if I set up an Ubuntu PPA to push builds through, will chat to you guys about this in any case (was also thinking about helping restructure the existing LinuxMCE packages if thats something that people want doing?).

Hey all, just an update on where things are at. I've still been pecking away at various bits on and off - but spent last night rewriting a lot of the code with a new approach so should be able to spend my time actually making progress not dealing with other issues.

I'll try to push a weekly update on here - if you don't see anything, give me a PM poke and I'll get off my laurels (again).

Okay, slampt has complained this update wasn't exciting enough... *pops confetti cannon*

Where things are at: I've partially written a generic NX8E comms library, it can send and receive messages over the wire to the NX8E. Now I'm implementing all the messages we need to do simple things. When those things are testing and working, I'll create a device template and code it up to talk DCE back to LinuxMCE.

Phase 1 = Simple Zone status.
Phase 2 = Bypassing zones, managing codes, etc - thoughts/suggestions guys?

I might end up throwing together a few quick standalone tools as well.

I'm excited! </BigKev></AussieJokes>

Hey all, just an update on where things are at. I've still been pecking away at various bits on and off - but spent last night rewriting a lot of the code with a new approach so should be able to spend my time actually making progress not dealing with other issues.

I'll try to push a weekly update on here - if you don't see anything, give me a PM poke and I'll get off my laurels (again).

Hey guys, just an update that I've found time recently to start working on this again.

Decoding and parsing data from the panel has been working for a while now - I've rejigged the classes and whatnot and am aiming to have return communication and zone status working in some capacity in the next two weeks - then it's a case of implementing DCE notifications, which should again be pretty straightforward.

los93sol - I'll probably drop you a PM in the next week or so when I hit a problem

Forgot to mention this in my OP, I'm referring to .NET running under the freely available Mono runtime: http://www.mono-project.com/Main_Page

(Though if people went down the path of using a pure C# module for the DCE protocol - you could open up to Microsoft's .NET runtime under Windows and the possibility of providing support for devices that only have proprietary binary drivers available for Windows).

Hi Guys,

I'm working on some device modules for MCE and was wondering if you guys would accept drivers written in .NET ?
Some of the stuff I'm doing in C++ at the moment would be a lot quicker in a language with proper inheritance/interface model (as well as real generics, templates suck!).

Understandably this would be throwing another language into the mix, but then again - the DCE protocol makes this fairly transparent.

Following on from this, if you guys aren't opposed to .NET based submissions - would you want modules to be P/Invoke'ing the existing C++ DCE library (good for maintenance from your POV), or using a pure C# module (good for module stability, bad for maintenance).

Let me know what you guys think - for now I'll be plugging away at this C++ code but would love to be able to switch to C#!

Hey brake16,

I'm currently in the process of implementing a communication library for the NX-8E for slampt. It's been a bit slow going as I've not had much time for work recently, but once I've done this I'll also be using the VistaICM2 stuff as a base for integrating support into LinuxMCE.

Currently the IO and message parsing/checksumming code is done, all that needs doing now is implementing message handlers for each type of event and generating some hooks for third party applications. If you've got C++ experience, I'd more than appreciate some help writing message handlers once I get the base MessageHandler class finished.

I'll be releasing the code under the GPL also - but I don't want to get ahead of myself until it's all sorted.