Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - PKWilson

Pages: 1 [2]
Developers / Re: WM5 - WM6.1 PlutoMo
« on: March 30, 2009, 06:08:31 am »
I just thought I'd mention something that I have found on my WM6.1 device (HTC Universal). I have been able to run the standard mobile orbiter on WM6 quite successfully over Wifi and GPRS. I found that when the orbiter starts, it created a temp file in /Application Data/Volatile (eg IMGxxxx.tmp). The problem was that it just kept growing until it filled the devices memory. Once it had filled it, the orbiter would open up every time and I could use it. Of course, I then no longer had any volatile memory left.

I once changed the registry entry for the volatile memory location to my memory card and started to run the orbiter and after a few hours it had created a 2Gb tmp file, but still hadn't opened the orbiter. (I had an 8Gb card and didn't wait to see how big it would get).

I haven't seen any posts about this before, so I just thought I'd mention it.

Users / Re: Australian LMCE users.....
« on: October 15, 2008, 08:07:15 am »
Just to add to the PLCBUS discussion. I pretty much have all my house lights using it now. I've only bought one crystal wall switch, and yes, it was a bit of a pain having to patch up half the existing wall switch hole to make it fit.

I also tried using standard clipsal or hpm (can't recall which) momentary switches for the lights, but I didn't really like the stiff feel of them. You had to give them a good push to get them to work. So I've gone for the simtone momentary wall switches. Sadly, the square size means I'm back to patching and painting the wall switches to make them fit, but they have a much nicer feel and look in my opinion.

My biggest problem is that the ripple control signal that is sent out by the power company to control tariffs plays havoc with my dimmed lights. They flicker badly for about 10 seconds on the hour, almost every hour. Not sure how to fix that. I'm going to see if the Megaman DimmERable (not to be confused with the dimmable range) compact fluorescent lights are any soon as they make it to Australia and assuming they work with the PLCBUS dimmers.


Users / Re: Australian LMCE users.....
« on: October 15, 2008, 07:32:33 am »
Hi all, I'm in Brisbane and also a happy LMCE + PLCBUS user.


Users / Re: Advanced event criteria options
« on: June 13, 2008, 05:54:39 am »
Up until now I have been trying to do this by adding a timed event and then going into the Advanced Configuration to edit the criteria.

I thought I would have a go by creating an advanced event based on the interval timer. I tried using the same notation as the timed event (time of day = 1m), but this doesn't seem to work.

How do I specify the interval when creating an interval timer advanced event?


Users / Re: Advanced event criteria options
« on: June 13, 2008, 05:03:44 am »
Thanks Thom

Unfortunately setting a criteria using the House Mode (not PK_HouseMode) appears to have no affect.

When I have a criteria set to House Mode = 2, it doesn't matter if I have set my house to any other number, the criteria always acts if House Mode = 2 is true.

As in the example in my previous post, all I'm doing is running an interval timer (Time of Day = 1m) and checking to see what the House Mode is (House Mode = 2). No matter what I set the house to in the security screen on the orbiter, it always triggers that event as if House Mode = 2 was true. In my test case, by turning a light on.

Maybe it's just a glitch on my system. I'd love to hear if this simple event works correctly on another system.

Also, the Room Mode is just another criteria in the Advanced Event criteria dropdown, after PK_Skin and before Specific Date. I have no idea what it's referring to.


Users / Re: Any experience on PLCBus with Linux MCE Automation
« on: June 13, 2008, 03:40:06 am »

I'm using it as well, also with Dan's Ruby integration following the instructions on the pages Darren mentioned.

I have the usb interface and I'm controlling a few 2 load lamp modules, single load lamp modules and plugin appliance modules.

I'm also using it in Australia as one of the few options available and its working well.


Users / Re: Display Temperature
« on: June 13, 2008, 03:12:05 am »
I've done a similar thing with my bathroom fan. I have a temp sensor up against the showers hot water pipe so that whenever the shower is in use the bathroom fan automatically comes on, then turns off when the temp starts to drop.

I have a different temperature sensor to you, but just use the Temp Changed event to turn the fan off and on. If your temp sensor child device has the temp changed event, you should be able to do the same thing.

Users / Re: Advanced event criteria options
« on: June 13, 2008, 03:02:45 am »
Thanks for that info. I was able to find the house mode numeric equivalents in the ruby code.

Unfortunately it doesn't appear to do anything. The event I'm testing with is just a simple "Check every minute and if the house is in 'Armed - away' mode, turn a light on.

So my event criteria are:

Time of day = 1m AND
House Mode = 2

It doesn't matter what I have in the house mode, it always turns the light on. I've tried using numbers, "Armed - away", "ARMED_AWAY", contains "away" as well as all those in single quotes and a number of other variations, but it doesn't matter what I put in as a value, the light always turned on.

Do I need to have another criteria?

I have used the pk_housemode criteria with a "House Mode Changed" event and it works fine with the numeric values, I just don't seem to be able to get the House Mode criteria to have any affect at all.

Does anyone have any other ideas?

Thanks for your help.


Users / Advanced event criteria options
« on: June 07, 2008, 09:15:37 am »
Hi all,

I'm sure this must be documented somewhere, but I'm struggling to find it. Can anyone point me to where I can find the values that are accepted by the event criteria, specifically:

House Mode
User Mode
Room Mode
Time of Day

I've tried various combinations of numbers, words (armed, away etc). I managed to work out Daytime and Night for the time of day..but I assume there are more.

Is there a definitive list of all the event criteria and the values they expect?


Users / IR Transmitter Help
« on: March 08, 2008, 08:05:35 am »
Hi All,

I'm trying to set up a device that I want to control through the LIRC Embedded Transmitter. Its a fan, not an A/V device, so I assume I don't use the Add A/V Equipment option. I created a new device under the Climate Category with the "Controlled via" set to "LIRC Embedded Transmitter"

I have the LIRC Embedded Transmitter device set up and I have added the new fan device as a child to the transmitter.

I've create an LIRC conf file for the device which was trained using irrecord and the fan devices remote. It shows up when I run:

linuxmce@dcerouter:~$ irsend LIST "" ""
irsend: ev100
irsend: mceusb

So I have the standard MCE remote and the ev100 (fan) remote configured.

I can run:
linuxmce@dcerouter:~$ irsend SEND_ONCE ev100 On
linuxmce@dcerouter:~$ irsend SEND_ONCE ev100 Off

and my fan turns on and off.

What I don't understand is what my next step in LinuxMCE is. I have tried Manually adding the On and Off commands to the devices command list, but I don't understand how it knows to use the ev100 remotes configuration for On to turn the fan on. I have tried to send a command to the device, but my transmitter doesn't even flash to indicate that it is transmitting, like it does when I use irsend.

All the help I have found is related to A/V devices and talks about going to AV Properties to configure the IR Commands...does this mean I have to set my fan up as an AV device?

I'll include some of my ev100.conf file below in case that helps.

Any help would be greatly appreciated.


begin remote

  name   ev100
  eps            30
  aeps          100

  ptrail          0
  repeat     0     0
  gap    81098

      begin raw_codes

          name On
              750    1800     750    1750    2000     550
             1950     600     700    1800     700    1850
             1950     600    1950     550     700    1850
              700    1850    1950     550    1950     600
             1950     600     650    1900    1900     600
              700    1850     650    1900     650    1850
             1950     600    1900     650    1900     600
              650    1900    1950     600     650

          name Speed
              750    1800     750    1750    2000     550
             2000     550     700    1850     650    1850
             1950     600    1950     600     650    1850
              700    1850    1950     600    1950     550
             1950     600     650    1900    1900     600
              700    1850     650    1900     650    1850
             1950     600    1950     600    1900     600
              700    1850    1950     600     650

Users / Re: Adding support for newer tv tuner
« on: March 04, 2008, 07:20:47 am »
Thanks for that info.

Going from memory, as far as I could tell it was only creating the one /dev/video0 device. If I tried adding a card on /dev/video1 it just said it was unavailable. When I added the V4L capture card, it gave me the option of 3 inputs - Television, S-Video & Composite. This lead me to believe that I had to install one tuner as a DVB capture device and the analogue one as a V4L capture device. When the DVB capture device was set up on its own, it worked fine, it was only when I then added the V4L device that it stopped working.

The reason why I tried to cheat by just doing a "make modules" instead of compiling the full kernel was that I couldn't get "make menuconfig" or "make xconfig" to work in the LinuxMCE DVD distro. It's been 5-6 years since I was last playing around with recompiling kernels and I'm a bit out of practice.

I've decided to try a full kubuntu install to see if I can get the card working in that and then I'll install the LinuxMCE 0710 b4 CD distro over the top. Hopefully I'll have more luck.


Users / Adding support for newer tv tuner
« on: March 04, 2008, 12:37:10 am »
Hi all,

I'm fairly new to LinuxMCE and was just wondering what the best option for adding support for a newer tv tuner is. I have the Winfast DTV2000H card. I had read up before buying it to check that it was supported only to find out afterwards that there was a revision update and I have the type J which isn't natively supported.

While I can force it to work using the "option cx88xx card=51" switch in the module options file, this only offers limited support. That is, the digital tuner works but analogue and the composite/s-video inputs don't (analogue kinda does, without sound).

I did try to patch the module using a patch found here :, but I only had limited success with it. I tried to cheat by just downloading the kernel source 2.6.22 and only doing a "make modules" and copied over the .ko files without recompiling and installing a whole new kernel, so maybe this is why. The card autodetected and loaded without errors after the patch and it did show the extra input options. I was initially able to tune and watch digital tv in MythTV, but as soon as I added the analogue tuner to MythTV it seemed to kill the digital tuner. After adding the analogue tuner I couldn't get a lock on a digital channel in MythTV (only showed l _ _ lock and not L M S) and the bit error (BE) went up to 13000ish and MythTV would freeze after a few seconds. If I deleted all the tuners from MythTV and added just the digital back in, it would work again. Also, trying to use the composite video source from outside MythTV would kill the digital tuner again and I would have to delete it from Myth and add it back in again to get it working.

So, my question is, what is the best way for me to add support for the newer card? Do I do a full recompile of the kernel with the patch? Install a newer kernel that supports the card or is there some other way to add it in? If I do have to recompile a new kernel, are there any implications for running LinuxMCE and is there a recommended source version to use.

I'm now running a fresh install with LinuxMCE 0710 b4.


Users / Re: mceusb2 ready to go for ir transmitter?????? in 0710 Beta 3
« on: February 23, 2008, 04:09:57 am »
Thanks for that. I had looked at that page and I have done everything up to the MythTV part. Controlling an A/C (as in Air-conditioning, not a typo of A/V) through MythTV wasn't that useful for me.  ;)

I'm actually wanting to create an IR Climate device and that's where I run into difficulties. From my understanding (which is a bit vague at the moment, I'm new to this) I need an interface device (the IR transmitter) to control IR equipment, but I can't set the mceusb2 device up as an interface yet.

So I'm wondering if there was a way of setting up a generic interface that runs scripts for the commands (like you've done in MythTV for the channel changing), but so that it will work in LMCE for general control and responding to events.


Users / Re: mceusb2 ready to go for ir transmitter?????? in 0710 Beta 3
« on: February 23, 2008, 03:30:29 am »

Just wondering if anyone has got this working. I have got my MCE remote (V2) working using irsend from the command to control a portable A/C unit, I just can't see any way of telling LMCE to do it.

I just used irrecord to create an lircd.conf from my A/C's remote, then inserted a new remote device into LMCE and reloaded. The I was able to use irsend using the remote and commands from the new device. But that's as far as I have been able to get and have no idea where to go from here.

Has anyone got mceusb2 transmitting from within LMCE? I'd love to hear how you did it.


Pages: 1 [2]