Posted: January 10 2003 at 05:11 | IP Logged

Hi Guys.

I am a new X10 convert - recently bought a bunch of bits to get started with, but didn't buy any remote controller, just the PC interface (UK model).

I am currently trying to program an AWM2 Micro Module using the PC interface alone, but without success. The AWM2 programming procedure requires two successive ON commands, which is dead simple with a remote and should also be with PowerHome..........

Doesn't seem to work though and I've tried several other software packages as well. Any suggestions as to what I'm doing wrong? How do you program an AWM2 with PowerHome and NO REMOTE?? Must be a way.....

Celo.

Posted: January 10 2003 at 09:59 | IP Logged

Celo,

I did a search on the web and read the instruction manual for the AWM2 and don't see why you cant program it using the CM11A and PowerHome.  It looks to me that at the least, you should be able to just use PowerHome's internal palm pad to send the appropriate address's ON command twice.  Im not sure how you were trying to do it within PowerHome...perhaps through a macro or something similar.  Im wondering if the problem does not have something to do with timing between the commands.

One thing that is not clear from the instructions is the actual structure of the 'ON' commands.  X-10 commands are actually two steps.  First a housecode/address followed by a housecode/command.  If you were sending the 'ON' commands from a palm pad, you would have a housecode/address followed by a housecode/ON command and then repeat.  If you are working from within a macro, you could generate a housecode/address followed by a housecode/ON command and then repeat just the housecode/ON command.  This could also be considered two successive 'ON' commands.   You might even want to try programming a small delay between the 'ON' commands if working from within a macro.

Since the manual explains that it is easily programmable via a remote, I can't imagine why you couldn't do it from using the internal palm pad.  This should simulate exactly what a remote would be sending which would be two succesive housecode/address housecode/ON command pairs.

Let me know...

Dave.

Posted: January 11 2003 at 07:25 | IP Logged

Hi Dave,

Thanks for the quick reply - really appreciate it.

So far I have tried using the X10 Status window buttons, the Control Centre buttons I made and also the Palm Pad, but still with no results - my AWM2 remains stubbornly on A1.

I reckon you could be right about the timing of the signals, but then again, how many people would press the buttons on their remote at exactly the same time interval? Must be some flexibility on the timing?

The AWM2 manual does actually state that the module can be programmed using the CM11A, but as you must have seen, they don't describe how and with which software - typically vague manual. They also neglect to say whether the AWM2 should be physically switched ON or OFF prior to programming and what it's LED should be blinking/not blinking whilst out of programming mode.

Anyway, I've tried every combination and method I can think of, but still no success. I'm beginning to suspect I've got a dodgy module on my hands. I am currently waiting for another one to arrive in the post from a different supplier and will see what happens with that one. If it doesn't want to program either, then it's pretty much guaranteed to be my error somewhere.

I'm not too hot on programming or scripting and am just starting to delve deep into the PowerHome manual, so might be a little while before I'm up to speed for the programming and macro options you described. Not quite as easy as the ActiveHome drag and drop macro generator. I will get there eventually, just need to learn up first.

So, will try my new module and let you know if it works or not.

Cheers,

Celo.

Posted: January 12 2003 at 01:06 | IP Logged

Celo,

All the methods you've described use the send the housecode/address followed by the housecode/command each time you press the button.  Perhaps the device needs to be programmed using the housecode/address followed by the housecode/command housecode/command method.  You can easily set this up in a macro.  I'll outline it below:

10 X-10 1 B 5
20 X-10 1 B ON
30 X-10 1 B ON

It's really quite easy.  The above example would set your AWM2 to address B5 assuming it works.  If this doesn't do it, then it just might possibly be a bad module.

Dave.

Posted: January 16 2003 at 08:34 | IP Logged

Dave,

Sorry for not getting back to you sooner, but my second micro module got lost in the post for a couple days.

Once it arrived, I set about trying to program it using my PC interface, but again - no success. I tried every method I could think of, but it wouldn't program.

It was then I realised that I had some motion sensors (MS13) which I could use in place of a remote control - and guess what????? They worked perfectly and now both my micro modules are programmed to the addresses I want. Just set the motion sensor to the address I want, stick the micromodule into program mode and press the House/On button twice on the motion sensor and Voila!

So, there MUST be a difference in the way physical X10 devices send their signals and I think that's where the problem lies. The AWM2 modules seem to require RAW X10 signals from another X10 device, without having the computer generate them or muck about with them en-route. What do you reckon? Something to think about anyway.

I must compliment you on your PowerHome software by the way. Having played with the demos of most of the major home automation packages whilst trying to program my micromodules, I have no doubt that yours is the one I'm going for. I will be purchasing a licence shortly.

Cheers,

Celo.

Posted: January 16 2003 at 10:40 | IP Logged

Celo,

Not a problem.  Im glad that you were able to get it working, but puzzled that the CM11A could not do it .  I know I read in the manual that the CM11A should be able to do it.  If the motion sensor was able to do it, then that would indeed be the housecode/unitcode housecode/function type of command repeated two times which should be just the same as sending the 'ON' command from the X-10 status screen or the palm pad.  Perhaps it has something to do with the command originating as an RF signal.

Oh well, since it's working for you, I won't trouble myself thinking about it .

Also, thank you for the complements on the program.  Theres still a lot of features Im working on adding and I hope you find it useful in your automation endeavours.

Thanks,

Dave.