Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: Extended Code reporting is flaky.  (Read 2392 times)

Charles Sullivan

  • Hero Member
  • *****
  • Helpful Post Rating: 94
  • Posts: 1565
    • HEYU - X10 Automation for Linux, Unix, and Mac OSX
Extended Code reporting is flaky.
« on: July 17, 2005, 03:53:26 PM »

Extended Codes reported in the AHP Activity
Monitor are flaky.

For whatever reason, AHP plays games with the
numbers.  E.g., for an LM14A Lamp Module, the
"data" value in an Extended Status Ack
(extended function 0x38) of a fully-on module
is actually 0xBE if the bulb is good or 0x3E
if the bulb is burned out. AHP strips off the
bulb good/bad bit, scales the result to the
0-210 range of standard lamp modules, and
reports the result as a hexadecimal number
0xD2 (= 210 decimal).

Unfortunately whatever AHP is doing doesn't
work for the 2-way Appliance Modules AM14A/
AM15A/PAM21/PAM22.  With these, the Extended
Code status  "data" value reported in the
Activity Monitor is always 0x1B regardless of
whether the module is On (0xFF) or Off (0xC0)
.
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

X10 Pro

  • Hero Member
  • *****
  • Helpful Post Rating: 23
  • Posts: 1416
Re: Extended Code reporting is flaky.
« Reply #1 on: July 21, 2005, 06:17:30 PM »

Added to our list. Thanks.
Logged
 

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