Can't Clear Interface Memory

[kenny]

I have been having problems with commands not
doing anything and macros not executing and
so decided to do an interface clear and then
a fresh reload.  Although a box pops up
saying that the hardware memory has been
cleared, checking the hardware configuration
indicates that exactly as much space as
before is being taken up.

It is impossible to tell now whether new
downlaods are accepted since they don't
necessarily execute and you can't wipe the
slate clean.

[murphy]

The hardware configuration indicates the
amount of space that will be taken by the
currently defined program.  It does NOT
indicate what is currently in the CM15As
memory.

[donald mcmow]

If you want to make sure that the interface
is clean then after clearing memory, try to
execute a macro using a remote(do this
while you don't have your computer hooked
up). If your computer is hiiked up then you
might be executing the macro from your
computer and not the one stored in your
interface. If you can't execute your macro
then the interface is clean. You can also
take out the batteries, unplug the
interface both from AC and USB, for a few
seconds - then put everything back together
and try your macro again (NO AHP running).
No lights comming on = clean interface
slate.

[andyd]

My observation is that removing CM15a from
power and removing batteries does not clear
the CM15a memory. (Nor did I expect it to)

The easiest way to clear the memory is to
execute the clear memory command.  If you
don't trust that then load a null macro/timer
build then disconnect the computer to test
the CM15a in isolation.

There is no way to determine how much memory
is being used by CM15a, except to do a fresh
download and to trust the hardware
configuration memory usage which, as has been
stated before, is only an estimate of the
memory that will be used by the AHX currently
active in AHP.

Andy

[kenny]

I did remove the batteries and disconnected
the power.  After teh first download there
was no change but at some point after
subsequent downloads it all came back to
life.  While it wasn't working it didn't even
see x10 codes sent from other transmitters.