Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS

Prinergy Evo Connectivity - Lotem 800 II/ Lotem Quantum

This page contains set up and configuration instructions specific to your Prinergy Evo to Lotem 800II/Lotem Quantum workflow, preconfigured process templates for your Lotem 800II/Lotem Quantum platesetters, and additional notes, comments, and tips.

Connectivity documentation | Process Templates and Notes | Known Limitations | Resources

Device Models:

Connectivity documentation

Process Templates and Notes

- (1.8MB)
 
Known Limits
Device Models
Date tested
Tester
Evo version
Device RIP
Protocol /
File Format
RIP OS
Process Template
Notes
   
   Lotem 400 Quantum Jan 2004 Tamar Kadman 1.0.6.2 CS Xpose 2.00.064 + upd 3.5.

Lotem Controller  1.50.08

Or

Xpo 3.00.79

 

 GDAPI Windows 2000 Server (for CS Xpose)

Windows 95 (for Lotem Controller)

 Prinergy Evo to Lotem Quantum via GDAPI connectivity process template Prinergy Evo to Lotem 800II/Lotem Quantum Family Connectivity User Guide - (1.8MB)

Use to output imposed images on plates.

  1. In Prinergy Evo, Process Template Editor dialog box, open this process template.
  2. In the Layout section, Name list, select the correct plate size.
  3. In the Render section, Device resolution list, select the correct resolution for the device.
  4. In the Calibration & Screening section, Harmony Medium list, select the required calibration.
  5. In the Screen Rulings list, select the required screen settings.

  6. Save the process template.
   
   Lotem 400 Quantum MCU Jan 2004 Tamar Kadman 1.0.6.2 CS Xpose 2.00.064 + upd 3.5.

Lotem Controller  1.50.08

 GDAPI Windows 2000 Server (for CS Xpose)

Windows 95 (for Lotem Controller)

 Prinergy Evo to Lotem Quantum via GDAPI connectivity process template Prinergy Evo to Lotem 800II/Lotem Quantum Family Connectivity User Guide - (1.8MB)

See Output Imposition images.
 
   Lotem 800 II, SCU, DLC, MCU Jan 2004 Tamar Kadman 1.0.6.2 CS Xpose 2.00.064 + upd 3.5.

Lotem Controller  3.75.09

Or

Xpo 3.00.79

 GDAPI Windows 2000 Server (for CS Xpose and Lotem Controller)

Windows 2000  Professional (for Lotem Controller only)

 Prinergy Evo to Lotem Quantum via GDAPI connectivity process template Prinergy Evo to Lotem 800II/Lotem Quantum Family Connectivity User Guide - (1.8MB)

See Output Imposition images.
   
   Lotem 800 Quantum, SCU, DLC, MCU Jan 2004 Tamar Kadman 1.0.6.2 CS Xpose 2.00.064 + upd 3.5.

Lotem Controller  3.75.09

Or

Xpo 3.00.79

 GDAPI Windows 2000 Server (for CS Xpose and Lotem Controller)

Windows 2000  Professional (for Lotem Controller only)

 Prinergy Evo to Lotem Quantum via GDAPI connectivity process template Prinergy Evo to Lotem 800II/Lotem Quantum Family Connectivity User Guide - (1.8MB)

See Output Imposition images.
 
   Lotem 800 II with Spectrum Jan 2004 Tamar Kadman 1.0.6.2 CS Xpose 2.00.064 + upd 3.5.

Lotem Controller  3.75.09

 GDAPI Windows 2000 Server (for CS Xpose and Lotem Controller)

Windows 2000  Professional (for Lotem Controller only)

 Prinergy Evo to Lotem Quantum via GDAPI connectivity process template Prinergy Evo to Lotem 800II/Lotem Quantum Family Connectivity User Guide -  (1.8MB)

See Output Imposition images.
 
   Lotem 800 Quantum with Spectrum Jan 2004 Tamar Kadman 1.0.6.2 CS Xpose 

2.00.064 + upd 3.5.

Lotem Controller  3.75.09

   Windows 2000 Server (for CS Xpose and Lotem Controller)

Windows 2000  Professional (for Lotem Controller only)

 Prinergy Evo to Lotem Quantum via GDAPI connectivity process template Prinergy Evo to Lotem 800II/Lotem Quantum Family Connectivity User Guide - (1.8MB)

See Output Imposition images.
  Lotem 850 April 2006 Tamar Kadman 3.0.6.5 CS Xpose 

2.00.064 + upd 3.5.

GDAPI Windows 2000 Server    
  Lotem 850 Quantum April 2006 Tamar Kadman 3.0.6.5 CS Xpose 

2.00.064 + upd 3.5.

GDAPI Windows 2000 Server    

Known limitations

None

Resources

  • Fully supported
  • Device connectivity has been tested
  • A pre-configured process template is available
  • Pend = Tested and supported but pre-configured process templates are not currently available.

Device connectivity is not supported.

Reasons:

NT= Not tested
P = Performance problems
Cnct = Problems connecting
Qlty = Poor quality output
Pend = Not currently tested or supported but currently undergoing testing.