Specifications

PICED FAQ

Page 26

1.3.2.12 Keeping Project Changes

Problem

How to you keep the changes a user has made to Scenes, Schedules, Irrigation and System IO

when you update the project ?

Solution

1. Transfer the project from the unit to PICED (using the C-Touch Colour Transfer Utility).

2. Make changes to the project.

3. Transfer the project from PICED to the unit.

1.3.2.13 Memory Usage

The amount of memory (RAM) used in the Colour C-Touch depends on the size of the project and,

in particular, the amount and size of images used.

Colour C-Touch has an "Image Manager" which controls the loading and storing of all images used

by Colour C-Touch. When a project is opened, the Image Manager loads all images needed by the

project. If an image is used more than once, the Image Manager makes sure only one copy is

loaded to save memory. If you are using bitmaps, then the full amount of memory required will be

already used at this time. If you use JPEGs, however, the situation is a bit different. The JPEG

gets loaded straight away. The first time the JPEG gets drawn, it is "expanded" to a bitmap and

then drawn. This expanded bitmap then gets stored for the next time the image needs to be drawn.

The result of this is that the memory usage can gradually increase over time as images are

displayed for the first time.

1.3.3 PAC Unit

1.3.3.1 Time Keeping

The PAC contains a real time clock. Like all clocks, it does gain or lose time slowly. If the PAC is to

be used for time-based logic, then it is important to ensure that the PAC clock stays synchronised.

If there are other C-Bus devices which also contain a clock (for example, C-Touch), then these

devices will broadcast the time on a regular basis and keep the PAC synchronised.

If you do not have one of these devices, then there will be no way of knowing what the PAC time is,

nor is it easy to set the PAC time. If you are using time-based logic, it is recommended that you

also have a C-Touch on the network to act as a master time-keeper.