Please login or register.

Login with username, password and session length
Advanced search  

News:

The X10Hub (PiX10Hub) is here! Created by the Community, for the Community.:)% #:)

Author Topic: Stumped on CM11A protocol...  (Read 8139 times)

pconroy

  • Hero Member
  • *****
  • Helpful Post Rating: 9
  • Posts: 294
Stumped on CM11A protocol...
« on: February 14, 2010, 04:26:22 PM »

If anyone here recalls their code for the CM11A - I've got a question.

I'm confused watching the data coming to the PC from the CM11A.

Suppose, I have a motion detector on M-3. And it detects motion, so I'll expect an M-3 On sequence of bytes.

After sending a 0xC3, I see:
   0x03 ==> number of data bytes is three
   0x02 ==> F/A mask

Then:
   0x0A   ==> cool, it's an address and it decodes to "M-3"

Then:   
   0X02   ==> also fine, that's "M - On".

But then what's this third byte trying to tell me???
   0xa0   ==> it's an Address byte.



Is it the brightness value?
In other words 0xA0/210 * 100%

That doesn't make any sense to me..
I see it for M-3 "Off" too. 
So I'm stumped...

thanks
Logged

Charles Sullivan

  • Hero Member
  • *****
  • Helpful Post Rating: 93
  • Posts: 1565
    • HEYU - X10 Automation for Linux, Unix, and Mac OSX
Re: Stumped on CM11A protocol...
« Reply #1 on: February 14, 2010, 11:45:15 PM »

If anyone here recalls their code for the CM11A - I've got a question.

I'm confused watching the data coming to the PC from the CM11A.

Suppose, I have a motion detector on M-3. And it detects motion, so I'll expect an M-3 On sequence of bytes.

After sending a 0xC3, I see:
   0x03 ==> number of data bytes is three
   0x02 ==> F/A mask

Then:
   0x0A   ==> cool, it's an address and it decodes to "M-3"

Then:   
   0X02   ==> also fine, that's "M - On".

But then what's this third byte trying to tell me???
   0xa0   ==> it's an Address byte.



Is it the brightness value?
In other words 0xA0/210 * 100%

That doesn't make any sense to me..
I see it for M-3 "Off" too. 
So I'm stumped...

thanks

You are trying to read too many bytes.  The 0x03 is the number of bytes following in the buffer, which includes the F/A mask byte.   There are only 2 data bytes.  See section 4.3 of the protocol.


Logged
Yesterday it worked.
Today it doesn't work.
X10 on Windows is like that.

HEYU - X10 Automation for Linux, Unix, and Mac OS X     http://www.heyu.org

pconroy

  • Hero Member
  • *****
  • Helpful Post Rating: 9
  • Posts: 294
Re: Stumped on CM11A protocol...
« Reply #2 on: February 15, 2010, 03:09:29 PM »

Ahhhhhhhhhh.
I missed that.
Thank you!
Logged
 

X10.com | About X10 | X10 Security Systems | Cameras| Package Deals
© Copyright 2014-2016 X10.com All rights reserved.