Use this page to understand used space and optimally utilize the available space in the Zio wall module.
| Name | Definition |
| Used Count / Space | Displays count of memory used or parameters of given type configured. |
| Max Count / Space | Displays the maximum allowed memory or parameters of a given type. |
| % | Displays Used/Max in percent. |
| File A (Bytes) |
Displays the total memory used by File A. This file contains configuration for the following: 1. Categories and Parameters 2. Home Screens 3. Occupancy Override Options 4. Group Table, Send Table and Fail Detect Table. |
| File B (Bytes) |
Displays the total memory used by File B. This file contains configuration for the following: 1. Default Home Screen 2. Tenant Access to Parameters 3. Setpoint Parameters Default Values |
| File C (Bytes) |
Displays the total memory used by File C. This file contains configuration for the following: 1. Schedule 2. Enumeration Range used in different parameters |
| Total File Size | Displays the sum of File A, B anc C and other internal files. A maximum of 4950 bytes can be used in Spyder for TR75, 2000 bytes for TR71 and 1020 bytes for TR70 wall module configuration. Internal files are of fixed lengths and are tracked by tool. |
| The following are some tips to reduce usage in each of the major resource areas of Zio Plus. | |
| On a per-Zio basis | |
| File A |
1. Reduce the number of parameters. 2. Trade one type of parameter for a "less expensive" type of parameter. (Value from Wall Module and Network Setpoint parameters consume about twice as much space as Value from Controller parameters.) 3. Use the exact same limit for multiple Values from Wall Module or Network Setpoints. The Tool will recognize this and reuse existing limits. 4. Reduce the number of categories. This doesn't save much, but could result in squeezing in another parameter. 5. Reduce the number of home screen options. This doesn't save much, but could result in squeezing in another parameter. 6. Reduce the number of occupancy override options. |
| File B |
1. Reduce the number of Value from Wall Module parameters. 2. Reduce the number of other parameters. This doesn't save much, but could result in squeezing in another Value from Wall Module parameter. |
| File C |
1. Use a 5-2 schedule scheme instead of 7 or 8 day. 2. Disable scheduling. 3. Use the exact same enumeration set for multiple parameters. Even if a parameter doesn't use all of the ordinals in a common set, it may still be able to use the common set. This is especially true of a Value from Controller parameter. Value from Controller parameters are "display only" so there is no risk of a Zio user setting an illegal ordinal from the common set. 4. Reduce the number of enumerations. 5. Use an existing ordinal/label from some other set as the default for another parameter instead of creating a duplicate. |
| Total file size for Zio | 1. See above tips for Files A, B, & C. |
| Number of Fail Detects |
1. The tool increments fail detect count for every parameter that is of type
Value from Controller or Network Setpoint. Reducing the number of such
parameters will reduce Fail Detects count. 2. The tool also increments fail detect count when schedule is enabled. The count is least for 5-2 type schedule and highest for 8 day schedule. The tool user should always prefer 5-2 or 5-2-1 type schedules to save resources. 3. Disable scheduling. |
| Number of Send table entries |
1. Reduce the number of Value from Wall Module parameters. 2. Reduce the number of Network Setpoint parameters. 3. Use a 5-2 schedule scheme instead of 7 or 8 day. 4. Disable scheduling. |
| Number of Group table entries | 1. See above tips for Send table entries. |
| Number of Value from Controller parameters | 1. Reduce the number of Value from Controller parameters. |
| Number of Network Setpoint parameters | 1. Reduce the number of Network Setpoint parameters. |