Clearing Interface Memory

[jason99]

Does downloading a timer and macros file to interface memory clear timers and macros from a file previously downloaded, or must Clear Interface Memory be run before downloading a second file if I  don't want the ones from the first fille to be run anymore?

[zach1234]

I think (to be safe) do the clear memory feature. Now if you have software-driver-x10 problems with clearing the interfaces memory you can just rewrite over it. I don't really have problems I don't clear the interfaces memory because I have software problems.  I also Have a link: http://kbase.x10.com/wiki/Creating_A_Timer its not exactly what you want but it has useful information.

[Walt2]

I always do a Clear Memory, but that might simply be a left over from my old beta test days.  The interface has a list of items, and if the new list is shorter, some of the old list remains if not cleared out (erased) first.  If there is an error, it is quite possible that what remains of the old list might get executed.  With that, some rather strange or unexpected events will happen.

BTW, for me, a Clear Memory on my CM15a will set all the flags.  This seems to be firmware dependant, though.

[Oldtimer]

I always do a clear memory before downloading updates to the CM15A.  However my CM15A doesn't set all the flags when I do it.  In addition to what's already been posted the clear memory has the additional advantage of clearing out any dangling macros without having to execute that function separately.

[HA Dave]

I've found that if I create a NEW macro (make an addition to the program) I can upload and go. The only time I noticed an error or problem is when I alter a Marco (like change a modules H/U code) then it doesn't seem to save the change.

But generally speaking... I tend to go through the entire clearing process. Clearing the memory, then removing the batteries, unplugging the USB and removing the CM15A from power for a few seconds.

I've also taken up emptying the trash (recycle bin?), a tip I read here from steven r. I have found in my case that I can go weeks and weeks and never look at the AHP software. Then I get an idea... and spend hours writting and tuning macros.... clearing the interface and downloading.

[steven r]

...I've also taken up emptying the trash (recycle bin?), a tip I read here from steven r....

I think in most cases clearing the CM15A isn't needed but once burned we tend to take the extra step just to be safe.

...I have found in my case that I can go weeks and weeks and never look at the AHP software. Then I get an idea... and spend hours writting and tuning macros...

Like my chair idea. 

[KDR]

I've also taken up emptying the trash (recycle bin?), a tip I read here from steven r.

I read somewhere... (been looking for it) That if you delete a macro and don't clear the waste basket that the macro is not really deleted and can still run and/or mess up the new macro. If I find it I will post a link. (Maybe somewhere in some paperwork I have. Off to look)

^{----------------KDR}

[steven r]

I read somewhere... (been looking for it) That if you delete a macro and don't clear the waste basket that the macro is not really deleted and can still run and/or mess up the new macro. If I find it I will post a link. (Maybe somewhere in some paperwork I have. Off to look)

Might of been me.  It may of been on an earlier version also. May or may not be a problem now. Once burned, however....

This is a related bug I found that was in a previous software version.