Other useful functions

FP-X series

The master memory makes program transfer easy, and a real-time clock is also included

The built-in 512kb flash-ROM can store a 32-k step pro- gram as well as the comments and FPWIN Pro source file.

Program update in a remote location is easy by simply sending master memory for local installation.

As the master memory stores the password informa- tion, password protection can be applied for program transmission. Similarly, upload prohibition/permission can be set up.

The built-in real-time clock enables periodical repeated control and periodical data logging.

		To the field	Program
Master memory		operation	Program
Master memory			transfer
FPWIN GR/Pro				FP-X
				FP-X

			Password used μ Password locked
			Password used μ Password locked
			Upload prohibited set μ Upload prohibited
	Program		Upload prohibited set μ Upload prohibited
			Upload prohibited not set μ Upload permitted
		FP-X	Upload prohibited not set μ Upload permitted
	transfer	FP-X
	transfer

Programs can be saved without a backup battery, making maintenance easier

The programs and comments are stored in flash-ROM requiring no backup batteries.

A backup battery (AFPX-BATT) is provided for data and the real-time clock. 1 battery for C14, 2 for C30 and 3 for C60 can be attached. A 2-battery installation can operate for a long time (10 years or more) without maintenance. (The real-time clock does not work with- out a battery.)

Battery holder

Connector

Backup battery for FP-X (AFPX-BATT)

F-ROM data saving (data can be saved without a battery)

FP-X can store a program, comments, a total of 55 words of data and bit setting values in a flash memory without a battery. All of the data and bits can be stored by adding optional batteries, but writing into a flash- ROM is possible without a battery by using applied in- structions (F12, P13). Perfectly suited for data storage of the setup values and recipes modified several times a day. *

Reading

Flash-ROM

Writing

*The limitation in a flash-ROM designates the number of rewrites to be 10,000, or the feasible number to be approx 30,000. However, rewriting every second will generate a memory failure within a few hours.

01/2008