Lotem 800

Prerequisites

Hardware:

• DDB-1N board (for installation details please refer to version 2.2 release notes)
• FCO 26334 - New X Motor (if old loading system is used).
• FCO 27094 - Tilted paper metal detector.

Software:

This version upgrade can be from versions 2.10.08, 2.20.10 or 2.30.05.
Note: When upgrading from version 2.1, you have to apply 2 changes to the Registry manually (See Appendix B -Version Installation Procedure).

New Features and Solved Bugs

Version Control:
This version includes the following version control items:

1. Adds a new Registry key folder: Scitex/Projects/Lotem 800/Version.
   This folder includes 2 values:

• Main Version Number - Indicates the version number (for example 3.10.09).
• Service Pack - Indicates the service package number. The Service Pack value starts at '0'. Each 'update' adds an incremental value.
  The previous Registry folder (Scitex/Projects/Lotem 800), that included only the version number, was deleted because it caused confusion with the Lotem 800 folder.

2. Adds a new folder C:\Lotem\Version. In this folder, you can find a new text file named VersionInfo.txt that lists the version number for different components in the software. (See appendix A). At the top part of each script you can find the version number and description of the problem the script corrects.
   

Machine Related

New features:

1. Supports Dual Loading Cassette.
2.  Supports Local 3 board.
3.  Supports Strobe 7 board.
4. Supports Distribution board Rev C.
5. Supports MCF board Rev. C.
6. Supports NUC comp level N and higher.
7. Improves the 'stop machine' process: Ensures the release of grippers, rollers, actuators and the disconnection of power to the motors when the Stop button is pressed.
8. Improves protectors. For example, in case one of the motor interlocks is open, a new protector prevents any motor operation and sends the relevant error message to the console. Until now, the hardware prevented operation and to the user it seemed that operation had started because no error message appeared.
9. Includes "User Troubleshooting and Tips" in the Help Menu. These tips describe common errors that users may encounter when using the Lotem 800 platesetter and how to resolve them. It also offers some useful tips that may help avoid problems.
10. Enables remote operation of the Lotem for troubleshooting and diagnostics.
    a. A new "Remote Support" button is available when you select Utilities. The Remote Support option activates the VNC and/or NetMeeting to allow remote connection.
    b. In addition, the button displays a Safety Warning dialog box. This dialog box includes an option to terminate the remote session (See Appendix E). (The NetMeeting and VNC should be configured NOT to allow automatic connection).
11. Includes a new dialog box during S/W installation, which prompts the user to define an actual machine configuration (See appendix C).
12. Adds an Export Registry File utility -
    a. The utility is auotomatically ran in the very beginning of the installation process in order to back the original Registry file. It exports the registry key 'Scitex\Projects\Lotem 800'. It saves it as a regular registry file. The file name is composed from 'Lotem' and the machine version number. For example: 'Lotem 800 - 3.10.09.reg'. The appropriate registry file will be located in 'C:\OldVer' folder.
    b. The utility can be activated by double clicking the 'ExportRegistryFile.exe' file in the 'C:\Lotem\Util' folder. In this case, a 'Save As' dialog box opens and the user can choose the name and the location of the registry file( Any name/location, including a floppy disk).
    c. There is also a shortcut for operating this utility, located under the following path: 'Start' -> Lotem 800 -> Export Registry File.

• The purpose of this utility is to save the 'Lotem' registry key only. It doesn't give the user the option to export other registry keys. 'Regedit' should be used for this purpose.
  

Solved Bugs:

1. "C++ debug error".

• Each Punch System definition includes Punch Units (punch motors). After closing punch motors that appear in some Punch Systems, a C++ debug error appears when doing Config or Expose from the Brisque.

2. Increased timeout for Brisque communication solves the problem of the PC

• Getting disconnected with small expose files.

3. Touch Memory is closed by default (Touch Memory does not work properly yet).
4. Faulty vibration errors are prevented during drum acceleration. The hardware disregards the detector while the drum speed is below 200 RPM. (This improvement applies to machines with Distribution board Rev. C only!).
5. Automatic restore of the file lotem_ddb.sav - it includes the laser factors. Previously, the file was initialized and all the laser factor values were lost after installation.