Remote Memory Usage - Revision history

The Robman: 3 revisions imported

2025-11-02T18:44:37Z

3 revisions imported

The Robman at 01:01, 10 September 2015

2015-09-10T01:01:30Z

The Robman at 19:33, 28 September 2014

2014-09-28T19:33:31Z

The Robman: Created page with "

''Back to IR Help Index'' ''Previous Topic Fav Scan '' ''Next Topic: Device Upgrades'' ..."
2014-09-28T19:31:08Z

Created page with "<table> <tr> <td width="183"> ''Back to IR Help Index'' </td> <td width="183"> ''Previous Topic Fav Scan '' </td> <td width="183"> ''Next Topic: Device Upgrades'' ..."

New page
<table>
<tr>
<td width="183">
''Back to [[IR Help]] Index''
</td>
<td width="183">
''Previous Topic [[Fav Scan]] ''
</td>
<td width="183">
''Next Topic: [[Device Upgrades]]''
</td>
</tr>
</table>
The memory available for keymoves and macros is very limited. Creating device upgrades to incorporate keymoves can save you some keymove space, and creating device upgrades from your learned signals can free up learned memory. Using an extender can give you a huge increase in the amount of keymove/macro space.

Let's take a look

The EEPROM memory is partitioned. For the URC8811, it is as follows:
[[Image:IRHelpChp3Bar1.jpg]]

Learning memory: 1021 bytes <br>
Upgrade memory: 762 bytes <br>
Keymove/Macro memory: 219 bytes

Although these numbers may vary WIDELY, in general, a single learned function consumes about 25-50 bytes, so you can usually get around 20-40 total learned functions stored before that portion of the memory is full.

A single KEYMOVE (by which you can assign an advanced code to another button) consumes between 5-6 bytes, so you can usually have up to 40 keymoves, as well. A macro can be pretty long (5-20 bytes), and if you use a bunch of macros to set up your system, as many do, you may find that the limit on this memory is stifling.

An entire device upgrade with a full set of button assignments (around 30 or so, depending upon device mode chosen) may occupy anywhere from 40 to 140 bytes (also depending on how complex the protocol is and if an additional protocol upgrade is required to support the device upgrade), so upgrades are almost always the most efficient method to get the device and button mappings you desire. You can install between 8 and 12 device upgrades, depending upon their size. Before you know it you end up with your memory full.

[[Image:IRHelpChp3Bar2.jpg]]

When you use the extender, all of the learning memory is converted to keymove/macro memory, although, a small amount of it becomes unavailable (to run the extender itself). For the 8811, this results in:

[[Image:IRHelpChp3Bar3.jpg]]

Learning memory: n/a <br>
Upgrade memory: 485 bytes (with preloaded protocols)<br>
Keymove/Macro memory: 852 bytes

The extender is just a SOFTWARE load into the EEPROM. You can still learn and decode signals by deactivating the extender, but you are unable to USE learned signals directly in the remote with the extender activated. But you don't need to use learned signals directly when you simply use the decoded learned data to build an upgrade (much more efficient, remember?), AND you have LOTS of room for keymoves and macros to customize your remote. Further more, there are other benefits to running the extender (like faster macro execution, greater flexibility in how to construct macros, keymoves onto buttons that would not normally permit it, and the availability of special functions like ToadTog, Long/Double Key press, Device Specific Macros.)

<table>
<tr>
<td width="183">
''Back to [[IR Help]] Index''
</td>
<td width="183">
''Previous Topic [[Fav Scan]] ''
</td>
<td width="183">
''Next Topic: [[Device Upgrades]]''
</td>
</tr>
</table>