Today I posted some long overdue updates. Quite some time ago it was agreed to loosen up the xPL protocol with regard to the values in the xPL message body.
From pure ASCII it now allows UTF8 encoding for the values (keys remain ASCII only). At the same time the length restriction of 128 characters was lifted, which basically means that the value can be as long as the overall message size supports (which is set at 1500 bytes).
So todays updates are the xPLLib for .NET, version 5.3, updated to allow these changes and the WireShark dissector, version 1.1, which will now show a warning (for backward compatibility) in cases of UTF8 and long values.
There are some other minor updates too, check the changelog for those.
I’ve recently turned to WireShark to do some network analysis but found tracking the bits and bytes of xPL not too easy, though still not difficult. But when I read that WireShark can be extended using Lua, I started fiddling around with that to see how I could get xPL support in WireShark. And this post is about the results…
The ‘dissector’ I wrote (download is below) will examine xPL packets, and dissect them into the underlying components. This allows you to use WireSharks filtering capabilities to find just the xPL messages you need. Beyond that it will analyze the structure of the messages received and validate that against the xPL protocol, flagging any malformed messages. Continue reading
I recently lost a lot of data and had to restore it, the full set is 225GB, so thats quite a bit to download. Fortunately last summer (2010) I decided to go for an online backup service, with a set-and-forget promise for the backups. The initial backup took 2 months to complete, but after that all went pretty smooth.
So I was a happy Mozy customer (MozyHome product) for quite a while, unfortunatley the restore capabilities of the Mozy software are completely crap, and you only find out to late… Continue reading
A new version (0.3) of the RFXmitter driver for Girder is available as of today. Several bug fixes and a debug option. The update is on the Girder page.
It includes the earlier, but never publicly available, version 0.2.1, so check the readme because both 0.2.1 and 0.3 contained breaking changes.
In my attempt to further automate my home, I’m trying to create UPnP devices for my appliances. The simplest examples are power switches and lights that can be controlled using the UPnP protocol. Obviously that’s not very user friendly, so I decided to experiment with a webinterface for the interaction, while keeping the UPnP functionality. The UPnP part can then be connected to the RFXcom devices for actually controlling my X10 and HomeEasy equipment (still working on my DevCom project for the hardware connection part) Continue reading
So here’s a new post on something I’ve been using for years. A simple actionlist that has grown to a tool I use very often. Maybe ‘tool’ sounds complicated, but it really isn’t, I guess thats part of why I like it so much. So what is it? In its essence its a way of working to get your project meetings done efficiently. As a side effect I created a spreadsheet with several tabs for listing actions, issues, risks and the like for a project. Over the years it changed to reflect my way of working, so maybe its better to elaborate on that before explaining the sheet. Continue reading
What is it?
A shortcut/link to a URL visible on the network, by (ab)using UPnP technology.
What does it do?
When Windows users on a network (local subnet) browse their network, they will see icons, with a description. When they double click them, a webpage pops up. Example: On my homeserver eMule runs as a peer-2-peer file sharing application. It features a webinterface and before I had a shortcut installed on each computer/laptop in the house. Now, I have installed the app on my homeserver and they simply double click the device “eMule downloader” from the network. Continue reading
When starting with UPnP development, some test projects, I initially started of with the Microsoft stack, as its already included in most Windows versions. But the documentation on the microsoft UPnP stack is so sparse, all examples I could find, were in C and then still only controlpoints, no devices. Hence I started using the Developer tools for UPnP (formerly by Intel). They contain a fully functional C# UPnP stack, and a code generator that generates a C stack. Just compile the C# stack and the resulting dll can be used from any (including VB) .NET language. Besides that the toolset contains a number of very usefull UPnP utilities.
The tools where initially available as the Intel UPnP tools, and after having disappeared from the Intel website for some time they have been relaunched as open source. Currently the stack is being maintained by Ylian Saint-Hilaire (Intel), and he does a good job at it (several bugfixes and improvements I submitted landed in the code quickly). Its a pitty that there isn’t a public forum for the UPnP tools.
This post is mostly about my experiences getting things up-and-running using the C# stack, which has its peculiarities, so here is what I learned; Continue reading
During the development of the experimental UPnP gateway, I ran into more bugs in the xPLLib, some pretty serious ones to be honest. So as of yesterday the new version is available.
The SMS application remains functionally the same, its only updated because it might be affected by the bugs fixed in the new lib.
Check the xPL page for the details and downloads.
Just finished an update of the UPnP gateway. After some more reading I found out that for the AV devices (audio/video) there is a different event mechanism using the ‘LastChange’ statevariable. Whatever, besides the nitty gritty details, it just shows more usefull info now. Continue reading