Re: cm11 0xfe 0x66???

[wevitofrito <marchigom@xxxxxxxxx>]

Yes, after trying sending a lot of differetn commands to CM11 and
without obtaining more messages than 0xfe, 0x66, I used the ActiveHome
software, and misteriosly it worked. I dont konw how or why.

Really strange!

thanks for your replying













On 20 oct, 13:09, nob...@xxxxxxxxxxxx (Dave Houston) wrote:
> I am not sure it has any meaning. Normally, the CM11A only sends a few
> unsolicited codes. 0xA5 repeated every second indicates power has been
> interrupted, 0x5A repeated every second indicates it has data in its buffer,
> 0x5B indicates a macro has been triggered, 0x55 indicates the CM11A is ready
> (after sending a command to powerline). It also sends a checksum after you
> have sent it a command via the serial port.
>
> 0xFE 0x66 would seem to be address codes J2 and A1 but they really only have
> those meanings when received in the proper context.
>
> However, it is not uncommon for the CM11A to have its brain scrambled after
> which it will send nonsense repeatedly, sometimes repetitive, sometimes
> random. The most common cause is, while the CM11A is plugged into the
> powerline, leaving the serial cable connected to the CM11A but unconnected
> on the other end. Usually, this can be cleared by a quick power-cycle but
> I've seen incidences where a longer rest was needed.
>
> Have you managed to clear it? That isn't clear from your latest post.
>
>
>
>
>
> wevitofrito <marchi...@xxxxxxxxx> wrote:
> >But..do you know the meaning of that message?Why CM11 is sending tha
> >bytes?
>
> >thanks!
>
> >Dave Houston ha escrito:
> >> Leave it unplugged from the powerline (sans batteries) for 45 minutes or
> >> longer.
>
> >> wevitofrito <marchi...@xxxxxxxxx> wrote:
>
> >> > Hi everyone! i'm a new member of the group. I've been reading your
> >> >comments for a long while, they're very useful!
> >> > i'm a student who is developing the final degree proyect about x10.
> >> > And today, to my surprise, my CM11 doesn't respond, i only
> >> >receive
> >> >0x66 0xfe 0x66 0xfe 0x66 0xfe..and so on..and i don't know what could
> >> >be the cause.
> >> > i've removed the batteries, unplugged..
> >> > i'm very worried!! Could anyone help?
>
> >> > thanks in advance
>
> >>http://davehouston.net
> >>http://tech.groups.yahoo.com/group/roZetta/
> >> roZetta-subscr...@xxxxxxxxxxxxxxx
>
> http://davehouston.nethttp://tech.groups.yahoo.com/group/roZetta/
> roZetta-subscr...@xxxxxxxxxxxxxxxx Ocultar texto de la cita -
>
> - Mostrar texto de la cita -