HK1087201B - Methods and structures for utilizing a memory device for a plc - Google Patents

Description

Method and structure for memory device using PLC

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority from pending U.S. provisional patent application serial No. 60/436,252 (attorney docket No.2002P20757US) filed on 12/23/2002 and from pending U.S. provisional patent application serial No. 60/436,249 (attorney docket No.2002P20758US) filed on 12/23/2002, both of which are hereby incorporated by reference in their entirety.

Background

Commercially available Programmable Logic Controllers (PLCs) may be equipped with memory devices for storage. The memory device, which may be a memory cartridge, is often an Electrically Erasable Programmable Read Only Memory (EEPROM) device. A common method of using the memory cartridge involves the storage of PLC configuration and programming information.

U.S. patent No.5,727,170(Mitchell) is hereby incorporated by reference: "the PLC has a user configurable protocol port attached thereto. Briefly stated, a special flag bit may be set at the PLC communication port or as a result of a user program or I/O event, which thereby allows the communication port to be activated. This is accomplished by the flag bit causing an interrupt to appear in the PLC user program, which allows the user to communicate using the user specified protocol scheme rather than the standard communication/programming protocol when this special bit is not set. "see abstract.

U.S. patent No.5,485,590(Hyatt) is hereby incorporated by reference as if set forth: the "modules connect the programmable controller to a plurality of serial communication networks over which data may be exchanged according to different protocols. The module has a central controller and independent port circuits for each network. Each port circuit includes a microprocessor and a shared memory, both the central controller and the port microprocessor having access to exchange data using the shared memory. The central controller transfers data from the shared memory to the module outputs coupled to the other components of the programmable controller. The removable memory cartridge stores a plurality of programs for execution by the port microprocessor to exchange data over the network using different communication protocols. Configuration data is stored in a module that defines which program is to be transferred from the memory cartridge to the shared memory of each port circuit. Protocol parameter configuration queries are stored for each program so that the user may be queried to select parameter values for the communication protocol used by the program. "see abstract.

U.S. Pat. No.5,991,510(Beaulieu) is hereby incorporated by reference for all that it claims: "the robot drive has operating and configuration parameters at the installation location stored in an easily removable storage device on or near the drive so that special data including teaching stations, such as related to arm design and system layout, can be maintained in connection with the drive and installation, whereby the drive system can be installed and replaced in minimal time as the storage device does not need to be reprogrammed. This removable storage device, in the form of a static memory or master key (e.g., Dallas key or EProm, etc.), may be affixed to the robot body or to a board remote from the vicinity, and may store arm design parameters, be programmed while on the robot or off-line, and become the only part configured for design manufacturing relative to the arm set. Furthermore, nominal system layout parameters may be pre-stored in the key, and when the key is secured to the robot drive, the robot automatically has information about both arm design and system layout that will help avoid collisions and provide a starting point for accurate teaching of the transfer station. In addition, the precise location parameters for each transfer station may be stored in a key when the robot is installed. Thus, the key will contain all the information necessary to make the robot unique to the unique system, and when the robot drive is replaced, by affixing the original key to or near the new robot, all the parameters of the original robot will be assumed. "see abstract.

U.S. Pat. No.4,937,419(Kolodziej) is hereby incorporated by reference: "programmable welding and machine controllers are used to control welding machines. The controller includes a central processing unit containing a stored control program connected to a memory running the welding operation of the machine and the operation of the machine itself. The controller receives inputs from the machine in its various operating states as well as a data entry and display unit and a current monitor of the welding operation that generates an output through the output of the heating control to activate the ignition circuit to control the welding operation. The backup of the stored program may be obtained through an accessory port of the memory backup storage unit. "see abstract.

Summary of the invention

Certain exemplary embodiments can provide a method for utilizing a memory cartridge connected to a PLC, the memory cartridge comprising a plurality of memory segments. The method may comprise a plurality of acts comprising: providing a storage box containing a storage module; and provides the storage cartridge with project files. The project file may contain a user program, a recipe containing a plurality of input values, and a structure of a data log file stored separately from the data log file, each input value from the plurality of input values corresponding to a process variable.

Brief Description of Drawings

The invention and its various potential embodiments will be more readily understood by the following detailed description in conjunction with the accompanying drawings in which:

FIG. 1 is a block diagram of an exemplary embodiment of a system 1000;

FIG. 2 is a block diagram of an exemplary embodiment of a data structure 2000;

FIG. 3 is a flow chart of an exemplary embodiment of a method 3000;

FIG. 4 is a flow diagram of an exemplary embodiment of a method 4000;

FIG. 5 is a flow diagram of an exemplary embodiment of a method 5000;

FIG. 6 is a flow chart of an exemplary embodiment of a method 6000;

FIG. 7 is a flowchart of an exemplary embodiment of a method 7000;

FIG. 8 is a flow diagram of an exemplary embodiment of a method 8000; and

fig. 9 is a block diagram of an exemplary embodiment of an information device 9000.

Detailed Description

As used herein, an I/O device may encompass any sensory oriented input and/or output device, such as an audio, video, tactile (including temperature, pressure, pain, texture, etc.), olfactory, and/or taste oriented device including, for example, a monitor, display, keyboard, keypad, touch pad, pointing device, microphone, speaker, video camera, scanner, and/or printer, potentially including a port to which an I/O device may be attached or connected.

As used herein, a rendering device makes perceivable to a person, for example, as data, commands, text, graphics, audio, video, animation, and/or hyperlinks, etc., such as by any visual and/or audio means, such as by a display, monitor, electronic newspaper, visual enhancer, speaker, cochlear implant, etc.

As used herein, an information device can be any general purpose and/or special purpose computer, such as a personal computer, workstation, server, minicomputer, mainframe, supercomputer, computer terminal, laptop, wearable computer, and/or Personal Digital Assistant (PDA), mobile terminal, bluetooth device, communicator, a "smart" phone (such as a handspring Treo-type device), instant messaging service (such as Blackberry) receiver, pager, facsimile machine, cellular telephone, traditional telephone, telephonically-transmitted device, programmed microprocessor or microcontroller and/or peripheral integrated circuit elements, an ASIC or other integrated circuit, a hardware electronic logic circuit such as a discrete element circuit, and/or a programmable logic device such as a PLD, PLA, FPGA, or PAL, or the like, among others. In general, any device on which resides a finite state machine capable of executing at least part of the methods, structures, or/and graphical user interfaces described herein may be used as an information device. An information device may include well-known components such as one or more network interfaces, one or more processors, one or more memories containing instructions, and/or one or more input/output (I/O) devices, among others.

Fig. 9 is a block diagram of an exemplary embodiment of an information device 9000. Information device 9000 can comprise a network interface 9100. Network interface device 9100 can comprise a telephone, cellular modem, telephone data modem, fax modem, walkie-talkie, ethernet card, cable modem, digital subscriber line interface, bridge, hub, router, or other similar device. Information device 9000 can be connected directly and/or indirectly to other information devices via network interface 9100.

Information device 9000 can further comprise a processor 9200. The processor 9200 can be a central processor, a local processor, a remote processor, a parallel processor, and/or a distributed processor, among others. The processor may be a general purpose microprocessor such as a Pentium III series microprocessor manufactured by Intel corporation of Santa Clara, Calif. In another embodiment, the processor may be an Application Specific Integrated Circuit (ASIC) or a Field Programmable Gate Array (FPGA), both of which have been designed to implement in their hardware and/or firmware at least some of the embodiments disclosed herein. Processor 9200 can adapt information device 9000 to execute according to a plurality of instructions.

Information device 9000 can further comprise a memory 9300. Memory 9300 can comprise any device capable of storing analog or digital information, including, for example, non-volatile memory, Random Access Memory (RAM), read-only memory (ROM), flash memory, magnetic media, hard disk, floppy disk, magnetic tape, optical media, optical disk, Compact Disk (CD), Digital Versatile Disk (DVD), and/or a disk array (raid array), among others. The memory may be coupled to the processor and may store instructions adapted to be executed by the processor according to embodiments disclosed herein. The memory 9300 can be adapted to store instructions 9400.

Instructions 9400 can comprise a plurality of instructions written in a machine-readable language. When instructions 9400 are executed by processor 9200, instructions 9400 can be adapted to process information. In an efficient embodiment, information used by processor 9200 using instructions 9400 can provide information to and/or be modified by processing operations.

Information device 9000 can further comprise an I/O device 9500. I/O device 9500 can be adapted to allow information device 9000 to communicate directly and/or indirectly with other information devices and/or users.

Fig. 1 is a block diagram of an exemplary embodiment of a system 1000. As shown, system 1000 may include a controller 1200, such as a Programmable Logic Controller (PLC). System 1000 can comprise a machine and/or process that can be monitored and/or controlled by PLC 1200. System 1000 can further comprise hardware and/or software adapted to allow a user to communicate with PLC 1200. PLC1200 can be a commercially ordered PLC. Alternatively, PLC1200 can be an information device. PLC1200 can be utilized to monitor and/or control a process, such as an industrial process. For example, PLC1200 can monitor and/or control alarm indicators, relays, sensors, another controller, and/or a motion device, such as a motion controller, such as a stepper motor controller, a servo controller, a brake controller, or the like; motion drivers such as stepper drivers, servo drivers, and the like; and/or actuators such as stepper motors, servo motors, linear motors, ball screws, servo valves, hydraulic actuators, pneumatic valves, and the like.

PLC1200 can comprise a Central Processing Unit (CPU) via which instructions can be processed and determine appropriate control signals. PLC1200 can further comprise and/or be coupled to an input-output (I/O) device. The I/O device can render information obtained from PLC 1200. A user can also interact with PLC1200 via an I/O device. As used herein, interaction means receiving an alarm or notification, revising or switching programs, checking control algorithms, and/or modifying a graphical display, etc.

A storage device, such as storage cartridge 1100, can be coupled to PLC1200 directly or via a network. In certain embodiments, memory cartridge 1100 can be inserted into PLC1200 and/or directly connected to PLC 1200. The storage device may be non-volatile memory, ROM, random access memory, flash memory, magnetic media, hard disks, floppy disks, tape, optical media, optical disks, CDs, DVDs, and/or disk arrays, among others. The memory device can provide storage of instructions or data usable by the CPU of the PLC.

In an exemplary embodiment, PLC1200 can be coupled to a user interface device 1300 via a network 1600. Network 1600 may be public, private, circuit-switched, packet-switched, virtual, radio, telephone, cellular, cable, DSL, satellite, microwave, AC power, twisted pair, Ethernet, token ring, LAN, WAN, Internet, intranet, wireless, Wi-Fi, Bluetooth, airport (airport), 802.11a, 802.11b, 802.11g, and/or any equivalents thereof, and so forth.

The user can interact with PLC1200 through user interface device 1300. The user interface device 1300 may be an information device. For example, via user interface device 1300, the user can be connectable to PLC1200 and/or can be controlled by PLC1200 to monitor a process. The user can also interact with PLC1200 via user interface device 1300.

PLC1200 can further be coupled to a process element 1400 through a network 1600. Process element 1400 can comprise a machine tool, a robot, a chemical reactor, a furnace, a reactor, an assembly machine, a packaging machine, and/or a portion of a transfer device, among others. In an operative embodiment, process element 1400 can be controlled, influenced, and/or monitored via PLC 1200.

The PLC may further communicate with a user through a network interface device 1500. The network interface device 1500 may be a telephone, cellular telephone, modem, cellular modem, telephone data modem, fax modem, walkie-talkie, ethernet card, cable modem, digital subscriber line interface, bridge, hub, router, or other similar device. When located remotely from PLC1200, network interface device 1500 can be adapted to allow a user to communicate with PLC 1200. Network 1600 may be further coupled to a peripheral network 1700 through a network interface device 1500. Peripheral network 1700 may be public, private, circuit-switched, packet-switched, virtual, radio, telephone, cellular, cable, DSL, satellite, microwave, AC power, twisted pair, ethernet, token ring, LAN, WAN, internet, intranet, wireless, Wi-Fi, bluetooth, airport, 802.11a, 802.11b, 802.11g, and/or any equivalents thereof, and so forth.

The peripheral network 1700 may be further connected to a remote user interface device 1800. The remote user interface device 1800 may be an information device including an I/O device. In an operative embodiment, peripheral network 1700 can be adapted to allow a user to interact with PLC 1200. Peripheral network 1700 can allow a user to interact with PLC1200 at a location hundreds or even thousands of miles away from PLC 1200. Peripheral network 1700 can be used to enhance utility and reduce programming, administration, and/or maintenance costs attributed to PLC1200 and/or monitoring and/or control of process element 1400. Process element 1400 can be one of a number of process elements.

Fig. 2 is a block diagram of an exemplary embodiment of a data structure 2000. An exemplary embodiment of data structure 2000 may contain a project file 2100. Project file 2100 can be stored on a storage device such as a memory cartridge. Project file 2100 can contain program 2200, recipe 2300, information representing data log file structure 2400, information representing recipe structure 2500, and/or support document 2600, among others. The data log file structure 2400 can be stored separately from a corresponding data log file, which can be stored on any storage device. Recipe structure 2500 can be stored separately from a corresponding recipe 2300. Project file 2100, and/or one or more elements thereof, can be adapted to allow a PLC to monitor and/or control a process element.

Program 2200 may comprise a set of machine-readable instructions. Program 2200 can be transmitted to the PLC. Program 2200 can be executable on a PLC. Program 2200 can be stored in project file 2100. In an operative embodiment, program 2200 can be adapted and/or adaptable to facilitate the performance of tasks by a PLC such as displaying process streams, transmitting information, storing information, processing information, prompting a user for input, controlling process variables, and/or reporting process outputs, etc.

Recipe 2300 can include at least one of a plurality of input values, each input value from a plurality of input values corresponding to a process variable. Each process variable can be used to monitor and/or control the process via the PLC. Recipe 2300 can include parameters for setting values such as machine speed, machine dimensions, product type, product composition, product size, product label, package type, package dimensions, package label, pressure, temperature, and/or any other relevant process parameter. Recipe 2300 can be stored in project file 2100. Recipe 2300 can be communicable to provide settings to program 2200 for rendering a product makable and/or a process operable using the PLC. Alternatively, recipe 2300 can be communicated to a different processing device and/or software to provide settings to render a product markable and/or a process operable.

Information representing the data log structure 2400 can contain symbolic representations of how the data log file is formatted for storage and retrieval. Information representing data log file structure 2400 may be stored in project file 2100. The information representing the data log file structure 2400 can include a series of values and/or characters associated with structural features of the data log file. The data log file and/or information representing the data log structure 2400 can be stored on the memory cartridge or on another storage device. Information representing the data log file structure 2400 can be adapted to render a data log file storable by a machine and/or readable by a machine. Information representing the data log file structure 2400 can be stored separately from the data log file.

The information representing the recipe structure 2500 can contain symbolic representations of how the recipe is formatted for storage and retrieval. Information representing recipe structure 2500 can be stored in project file 2100. The information representing the prescription structure 2500 may include a series of values and/or characters that are related to structural features of the prescription. Information representative of the recipe structure 2500 can be suitable for rendering the recipe machine-storable and/or machine-readable. Information representing the recipe structure 2500 can be stored separately from the recipe.

Support document 2600 can contain textual and/or visual representations of information assimilable to improve understanding of the PLC, the memory cartridge, hardware components associated with the PLC, software components associated with the PLC, and/or the process being controlled, among others. Support document 2600 can be stored in project file 2100. In an exemplary embodiment, support document 2600 can be reviewed by a user at a user interface device to facilitate understanding and/or modifying a PLC, hardware related to a PLC, software related to a PLC, a process, a project file, a data log file, information representing the structure of a data log file, a recipe, and/or information representing the structure of the recipe, and/or the like. Alternatively, support document 2600 may be rendered to a user via an I/O device connectable to an information device.

FIG. 3 is a flow diagram of an exemplary embodiment of a method 3000 for using a storage device. At act 3100, a beginning memory segment on the memory cartridge can be located where the project file, or any component thereof, can be read from and/or written to. Alternatively, the starting memory segment may be located on the memory device. In an efficient embodiment, the project file may occupy a single memory segment. Alternatively, in an efficient embodiment, the project file may occupy multiple memory segments.

At act 3200, the project file can be provided to the memory cartridge. Alternatively, the project file may be provided to the storage device. Providing the project file to the storage device can allow information contained in the project file to be sequentially transferred to the PLC. For example, in the event of a power failure, volatile memory is erased in the PLC, and certain information erased from the volatile memory can be recovered from the project file stored in the storage device.

FIG. 4 is a flow diagram of an exemplary embodiment of a method 4000 for using the memory device. At act 4050, the user may request to obtain (e.g., see, hear, rendered, and/or obtain access to) information stored and/or storable on a storage device. The information can include programming code, programming code documentation, support documentation pertaining to hardware and/or software associated with the PLC, process data, recipe code, and/or recipe information, one or more data logs, and the like. The user can potentially improve monitoring, control, and/or management of the PLC and/or at least one process element having the obtained information.

At act 4100, the user can be prompted to select a language for rendering information from a plurality of language choices. The user may be allowed to provide a selection corresponding to the selected language. The user may be allowed to make selections on an I/O device connectable to the information device. The language choices may include any language such as english, german, french, italian, spanish, and/or chinese, among others. The user may select a language by providing a user input corresponding to the selected language.

At act 4200, the user input may be received corresponding to a selected language. The user input may be received as a result of a user interacting with an I/O device connected to the information device. The user input can improve the communication capability of information to and from the PLC by transmitting the information in a language preferred and/or better understood by the user.

At act 4300, the information may be located on a storage device. This information can be located through actions of the PLC or any information device directly and/or indirectly connected to the PLC. Locating this information can facilitate communication between the user and the PLC.

At act 4400, the information can be provided to the user in response to user input corresponding to the selected language. The information is provided to the user interface device in the selected language. Alternatively, the information may be provided to any I/O device and/or any information device in the selected language.

FIG. 5 is a flow diagram of an exemplary embodiment of a method 5000 for using a storage device. At act 5100, a first identifying stamp can be provided for the data log record. The first identifying stamp may comprise calendar data and/or a clock time associated with requesting, collecting, receiving, and/or recording a data log record. Alternatively, the first identifying stamp may relate to a processing unit, such as a machine, meter, and/or device, etc., associated with the data log record. For example, the first identifying stamp may be a processing unit identifier such as a machine number, a sensor number, and/or an actuator number, among others. In an effective embodiment, the process identifying stamp can assist a user in analyzing and categorizing the data log records.

At act 5200, the PLC may allow the user to select a second identifying stamp from a plurality of choices. Identifying a stamp selection may include various data and/or time elements including year, month, day of week, hour, time zone, minute, second, and/or portion of second, etc. Alternatively, the second identifying stamp may comprise various numbers and/or symbols associated with the processing unit.

At act 5300, a user input corresponding to selection of a second identifying stamp can be received from the selection device. The second identifying stamp may improve the user's ability to analyze the process log record. Alternatively, the second identifying stamp may reduce storage space requirements for the data log record by providing a second identifying stamp that is smaller than the first identifying stamp.

At activity 5400, the selected second identifying stamp can be provided to the storage device in response to a user input. In an efficient embodiment, providing the second identifying stamp to the storage device may provide information to a user, and when the user subsequently analyzes the data log record, the information within the second identifying stamp may be adapted to improve the efficiency of analyzing, classifying, and/or otherwise processing the information in the data log record.

FIG. 6 is a flow diagram of an exemplary embodiment of a method 6000 for using a memory device. At act 6100, a first setting can be provided corresponding to an instruction to erase or not erase the data log from the storage device after the data log is read. The instructions to erase or not erase the data log file after reading the data log file may allow a user to more efficiently manage data storage and retrieval on the storage device. Erasing the data log file can provide assurance that no data log record on the storage device has been previously read.

At act 6200, the user may be allowed to select a second setting corresponding to an instruction to erase or not erase the data log from the storage device after the data log is read. The second setting may provide an instruction opposite to the first setting. Providing the second setting may allow a user to improve control over the data storage resource.

At activity 6300, the data log can be read from the storage device. The data log may then be erased or not erased from the storage device in response to user input. Reading the data log can allow the user to transmit information for additional processing and/or storage in response to analyzing and/or improving the need to monitor, control, and/or report process elements controlled by the PLC.

FIG. 7 is a flow chart of an exemplary embodiment of a method 7000 for using the memory device. At activity 7100, the user can be prompted allowed to select elements for the project files stored on the storage device. The selectable elements may include the project file, the program, the recipe, information indicative of the recipe structure, information indicative of the data log file structure stored separately from the data log file, and/or support documentation pertaining to the process, the PLC, hardware associated with the PLC, and/or software associated with the PLC.

At activity 7200, a user input corresponding to an option to store at least one project file element can be received from a selection device. Providing a user with a storage option may allow the user to customize the storage plan to fit the needs of the unique system, which take into account such factors as: other means for storing the project file, the size of the memory cartridge, the amount of process data collected for storage in the data log file, the frequency of storing the process data collected for storage in the data log file, the number of recipes storable in the memory device, and/or the number and/or content of available support documents, and the like.

At activity 7300, the project file elements may be written to the storage device in response to a user input. The project file element may be written at the beginning of a blank memory segment. Alternatively, the project file element may overwrite a previously stored project file.

Fig. 8 is a flow chart of an exemplary embodiment of a method 8000 for using the memory cartridge. At activity 8100, a first head marker representing a beginning memory segment of a data log record to be written may be located on a storage device. The data log record may be of a size that can be stored on a single memory segment. Alternatively, the data log record may be of a size that can be stored on multiple memory segments. The memory segments available for data log storage may be spatially and/or logically contiguous and/or may be continuously writable.

At activity 8200, a data log record that can include a second head marker can be written to at least the beginning memory segment. The data log record may be written onto at least one blank memory segment.

Alternatively, the data log record may overwrite at least one memory segment used by an older data log record. The second head marker may contain information reflecting a location of a next memory segment for storage of a next data log record. In an exemplary embodiment, the data log file may be written in a logically circular buffer. The logically circular buffer is characterized by data log records written to adjacent memory segments, the buffer beginning at a beginning memory segment. When the buffer is full, the logically circular buffer is further characterized by the writing of the next data log record at the beginning of the buffer. The next data log record may overwrite the oldest data log record written in the logically circular buffer. For example, if the buffer is full, the next data log record to be written may be written at the beginning of the buffer, thus overwriting the data log record previously at the beginning of the buffer. The logically circular buffer may comprise a circular buffer in which memory segments are physically adjacent to each other.

At activity 8300, the first head marker can be changed to a record marker reflecting a data log record written in at least the beginning memory segment. The record flag (as changed) may indicate a successful write of the data log record containing the second head flag.

After activity 8200 and before activity 8300 is fully completed, a power failure may occur. A power failure before activity 8300 is fully completed may leave a data log file with both head markers open at the same time. At activity 8400, in an operative embodiment, the PLC can ensure the presence of a single head marker after a power failure via error checking techniques. The error checking technique may be any compensating method, a Fletcher checksum method, a cyclic redundancy check method, and/or an extended precision checksum method, etc. Error checking techniques, which may be associated with knowledge of the location of problematic records and/or the location and/or direction of records added to a storage device, may identify which record is the most recent and, therefore, which head marker is erroneous.

In an operative embodiment, the PLC may disable and/or eliminate the older, duplicate head marker, or possibly convert the older, duplicate head marker into a non-head marker that results in the presence of a single head marker in the data log file, the single head marker corresponding to the new record. Changing the value of the binary bit may disable older, duplicate head markers. Alternatively, on each of the data log records, the PLC can check and test a flag, such as a timestamp flag, to determine the most recently written record.

At activity 8400, the data log record can be read from the storage device. In an efficient embodiment, the data log record can be read from the at least one memory segment in response to the data log structure. Information representing the data log structure may be stored separately in the storage device.

Still other embodiments will become readily apparent to those skilled in this art from the foregoing detailed description and the accompanying drawings of certain exemplary embodiments. It should be understood that numerous variations, modifications, and additional embodiments are possible, and accordingly, all such variations, modifications, and embodiments are to be regarded as being within the spirit and scope of the appended claims. For example, no particular act or element, any particular order of such acts, or any particular interrelationship of such elements, is required unless explicitly stated to the contrary, regardless of the content of any portion (e.g., title, section, abstract, drawing figure, etc.) of such application. Further, any act may be repeated, any act may be performed by multiple entities, and/or any element may be replicated. Further, any acts or elements may be excluded, the order of the acts may be varied, and/or the interrelationship of the elements may be varied. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.

Claims (20)

1. A storage case, comprising:

a first portion adapted to store a user program, the user program being adapted to control a process;

a second portion adapted to store a recipe comprising a plurality of input values, each input value from the plurality of input values corresponding to a process variable; and

a third portion of the structure adapted to store a data log file separate from the data log file, the data log file structure specifying a location in the data log file of each of a plurality of identifying stamps, each identifying stamp including at least one of calendar data and clock time.

2. The storage case of claim 1, further comprising:

a fourth portion of the structure adapted to store the prescription separately from the prescription.

3. The storage case of claim 1, further comprising:

a fourth section adapted to store a support document relating to at least one of the user program, the recipe and the data log file.

4. The storage case of claim 1, comprising:

a fourth portion adapted to store a support document relating to at least one of the user program, the prescription, and the data log file, wherein the support document contains an image.

5. A method for utilizing a memory cartridge connected to a programmable logic controller, the memory cartridge comprising a plurality of memory segments, the method comprising a plurality of acts, said acts comprising:

providing the storage box, wherein the storage box is used for accommodating a storage module; and

providing a project file to the memory cartridge, the project file containing a user program, a recipe comprising a plurality of input values, and a structure of the data log file stored separately from the data log file, wherein each input value from the plurality of input values corresponds to a process variable, the structure of the data log file specifying a location in the data log file of each of a plurality of identification stamps, each identification stamp comprising at least one of calendar data and clock time.

6. The method of claim 5, wherein the project file further comprises a structure of the recipe stored separately from the recipe.

7. The method of claim 5, the project file further comprising a support document relating to at least one of the user program, the recipe, and the data log file.

8. A method for utilizing a memory cartridge connected to a programmable logic controller, the memory cartridge comprising a plurality of memory segments, the method comprising a plurality of acts, said acts comprising:

prompting a user to select a language to display information relating to project files stored in a memory cartridge coupled to the programmable logic controller on a user interface device connected to the programmable logic controller;

receiving a user input corresponding to a selected language; and

in response to the user input, displaying information relating to the project file in the selected language on the user interface device, the memory cartridge being adapted to store a structure of a data log file stored separately from the data log file, the structure of the data log file specifying a location in the data log file of each of a plurality of identifying stamps, each identifying stamp comprising at least one of calendar data and clock time.

9. The method of claim 8, further comprising:

information stored in a selected language is located in the memory cartridge.

10. The method of claim 8, further comprising:

information in a default language is located in the memory cartridge.

11. A method for utilizing a memory cartridge connected to a programmable logic controller, the memory cartridge comprising a plurality of memory segments, the method comprising a plurality of acts, said acts comprising:

prompting, on a user interface device connected to the programmable logic controller, a user to select at least one project file element for storage in the memory cartridge, the project file element containing a user program, a recipe comprising a plurality of input values, a recipe structure stored separately from the recipe, a data log file structure stored separately from the data log file, and a document relating to elements of the project file, wherein each input value from the plurality of input values corresponds to a process variable, the data log file structure specifies a location in the data log file of each of a plurality of identification stamps, each identification stamp comprising at least one of calendar data and clock time; and

user input is received corresponding to selection of at least one project file element for storage in the memory cartridge.

12. The method of claim 11, further comprising:

providing the at least one project file element to the memory cartridge in response to the user input.

13. The method of claim 11, further comprising:

in response to the user input, a second project file containing the at least one project file element is provided to the memory cartridge, the second project file being different from the first project file stored on the memory cartridge.

14. A method, comprising:

at a memory cartridge of the programmable logic controller, storing a user program adapted to control a process when executed by the programmable logic controller;

at a storage cartridge, storing a recipe comprising a plurality of input values, each input value from the plurality of input values corresponding to a process variable; and

at the storage cartridge, storing a structure of a data log file separate from the data log file, the structure of the data log file specifying a location in the data log file of each of a plurality of identifying stamps, each identifying stamp including at least one of calendar data and clock time.

15. The method of claim 14, further comprising:

the structure of the recipe is stored on the storage box separately from the recipe.

16. The method of claim 14, further comprising:

storing support documents on a memory cartridge relating to at least one of the user program, the recipe and the data log file.

17. A method for utilizing a memory cartridge connected to a programmable logic controller, the memory cartridge comprising a plurality of memory segments, the method comprising a plurality of acts, said acts comprising:

prompting a user to select a language to display information on a user interface device connected to the programmable logic controller that contains project files stored in a storage device coupled to the programmable logic controller;

receiving a user input corresponding to a selected language; and

in response to the user input, displaying on the user interface device, in the selected language, information containing an item file stored in a storage device, the storage device adapted to store a structure of a data log file separately from the data log file, the structure of the data log file specifying a location in the data log file of each of a plurality of identifying stamps, each identifying stamp including at least one of calendar data and clock time.

18. The method of claim 17, further comprising:

locating information stored in the selected language in the storage device.

19. The method of claim 17, further comprising:

locating information in a default language in the storage device.

20. The method of claim 17, further comprising:

locating information in a default language in the storage device; and translating the information into the selected language.