• Send the strips one by one - change offset for every strip. (This bug is fixed in Brisque version 3.)

Expose aborts with error messages 6801 and 5230. When working with SFL

• Check that all expose parameters on Brisque are standard:
  (Dupli=0 in screen set, number of copies=1 in plate expose, no negative offset).

• Verify that the VLSI & SFL are working properly - plotter diag can be run from the Brisque to check them.

Expose aborts with message ‘Job aborted by Host’.

• Check that all expose parameters on the  Brisque are standard:
   (Dupli=0 in screen set, number of copies=1 in plate expose, no negative offset).

• Verify that the VLSI & SFL are working properly - plotter diag can be run from the Brisque to check them.
• Check power supply - disconnect the main power to the transformer and measure the 3 phases on customer socket >120V.

• Verify that the drum speed does not exceed the maximum allowed per plate size / resolution.

• Redefine the punch configuration in the Lotem database: Open the press format on the Brisque. Then save it with the new configuration.

• Verify that each punch motor opens on the Lotem and has the following registry parameters: Height Pos = 500, Width Pos = 45.
• Open the punch database files (C:\Lotem\Data Base\Punch) and verify that the files are not corrupted (It can be opened by a word pad editor).

• Verify that the drum speed matches the plate size and resolution according to the recommended table. See release notes 2.10.06 or 2.2.

• Check that all of the diode’s work.
• Check that the hard disk, in the Brisque, is not fully loaded.
• Decreases drum speed. Make sure that continuous screening is turned on.

• Go to scismit/imagesetter/update plot mode. It should be set to plotters.

• Verify that resolution / intensity or plate types are defined.

Communication problems between Brisque and Lotem. When working with SFL

• Open a terminal window and ping the Lotem IP address.
• Open a terminal window and type 'mon4'.
• Open plot diag-plotters-sfl and run test. If it passes, this will initialize SFL.
• Open the terminal window and type 'lsdev -Cpci'. Check if SFL is available or defined. If it is defined, type 'cfgmgr'. When finished, type 'lsdev -Cpci' and see if available. If it is, try typing ‘mon4’ again.
• Open the terminal window and type 'lsdev -Cpci' . Check if SFL is defined or available. If it is defined, type 'cfgmgr'. Then try to communicate again. If this doesn't work, remove the SFL, boot the Brisque, shutdown and reinstall the SFL. Restore the database or registry.

• Verify that the Lotem is in Ready or Service mode.
• Verify that a correct IP number has been put in the Brisque scismit / platesetter.
• Try to ping the Lotem from the Brisque and the Brisque from the Lotem. If it does not work, then the TCP/IP configuration of both units should be checked.
• Verify that the fibers are connected correctly and that the SFL/VLSI diag from the Brisque is passing.
• Open each of the files inside the Lotem database directory with Word Pad to ensure that they are not corrupted or wrongly set.
• Verify that no more than 3 Plate Types, 2 Res/Int tables or 3 Punch configurations have been set up.

• Check that the load policy in the plate expose is set correctly.
• Check that the PC in ready State.
• Check that the loading system status in the Lotem is 'expecting plate / paper'.
• Verify that the Brisque is not set to Plotters No Film Mode in the scismit / imagesetter.

• Check the queue to see if the plate expose symbol is blinking. In operation control click on plate expose-ok.
• Check if the GUI is in ready status, otherwise change it to online.

• Some parameters in the Lotem database/registry are not defined correctly or are missing.
• Verify that the Spiral Motor is not disabled (=0) in the expose registry.

• Use the power switch to shut down and restart the Lotem.

System error 7123 or  5230 - On Brisque progress indicator        doesn’t advance.

1. Check the connectors pins on both sides
2. Replace the cable between the TSP and the Lotem
3. Replace the DDB board.
4. Replace the MCF board.
5. Replace the Strobe board.

6. Replace TSP board on the brisque

1. mso-list:l12 level1 lfo17;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Check if the TSP board it set tight

2. Replace the TSP.

1. mso-list:l21 level1 lfo18;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Power the brisque off and wait 1 minute

2. mso-list:l21 level1 lfo18;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Power the brisque up and see it the problem repeated. If it does take out the rotation board and expose job that you have a temp of it and that you know that it pass before if the brisque freeze again replace the TSP. If not replace the rotation board.

3. mso-list:l21 level1 lfo18;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Load the version with overwrite

4. Do called start.

System error 5155
Symptom - Expose won’t start

1. Check the TSP board driver.

2. Do release from the plt_config.dlg

3. Release the TSP by using “monNsp’ command (from terminal)

4. Check the cable connection between the Lotem and the TSP.

5. Replace the TSP cable

6. Replace the TSP board.

Error message “can’t open device driver”
Symptom - Expose won’t start

1. Check the configuration table to see if   another board occupies the PCI slot

-  open terminal and write lsdev –C

-  check if the TSP identify as nsp0 and as  Availeble ,if it’s nsp1 do:

-  rmdev –l nsp1 -d

-  do cfgmgr

-  check that now the TSP identify as nsp0

2. Power the brisque off and wait one minute then tern it on.
3. Replace the TSP board

System Error 7120
Symptom - expose process won’t start.

1. Run TSP Diag
2. Check that the porch seat tight on the board
3. Load the software with overwrite
4. Replace the TSP board

1. mso-list:l15 level1 lfo19;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Run TSP diag.

2. mso-list:l15 level1 lfo19;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Check that the brisque version is OK

3. mso-list:l15 level1 lfo19;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Check that the expose parameters are OK-mesh/res/angle

4. mso-list:l15 level1 lfo19;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Reload the expose S/W.

5. mso-list:l15 level1 lfo19;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">Replace the DDB

6. Replace the TSP board.

1. Check the configuration table to see if another board occupies the PCI slot.

- Open terminal and write lsdev –C

- Check if the TSP identify as nsp0 and as  Available ,if it’s nsp1 do:

- rmdev –l nsp1 -d

- Do cfgmgr

- Check that now the TSP identify as nsp0.

1. Check to see if Lotem application  is  running

2. go to config and click once on expose to see if Lotem says connected-if  not 

A. open the plate  dialogue  and try to reset the screen processor  if that doesn’t  work

B. open a terminal window and type mon4- this will check the VLSI connection- if  it says ok then you must type q to quit out of mon4 - if it says to type “ow 33 a0 “then type the command to reset the VLSI.

C. If you have TSP Open a terminal window and type MonNsp- this will check the TSP connection ,if  it not OK then type #lsdev –C |grep NSP0

This will show you if the TSP board is available if it’s not type #mkdev –l NSP0.

D. open a terminal window and ping the ip address of the the Lotem - the screen should continue to scroll if the tcpip communication is working, hit ctrl and c to get out- if not then check the cable s and configuration.

E.Hit the up arrow above scismit and double  click on plotter diag.

then hit 2 for plotters and then 2 for Lotem 800  then hit 1 for sfl and then 1 again  for registers and then 1 again for plx - this test should pass and this will init the sfl card and reset the communication for the sfl card. Then hit the esc key and y to escape diagnostics.

3. go to the Lotem pc and check  under setting the number  of defined plates- there must be a maximum of 5  otherwise the Lotem will not communicate to the Brisque.

4. check the sfl cable to make sure that the light  is coming out of one end and the cable .

5. open a terminal window and type  lsdev -Cspci and see if the sfl0 is defined or available.  If it is defined then type cfgmgr and then again type lsdev -Cspci to see if it is now available  and then type mon4 to see if it is working.  The sfl board in the Brisque is slot dependent- do not move it to another slot!

6. On the Lotem- go to start, settings, msdos prompt  and ping the  ip address of the Brisque.

7. If you can ping the Lotem from the Brisque and the sfl or tsp works (mon4 or  monNsp) and you do not have too many plate definitions on the Lotem then you have a corrupt  database - reload the database  on the Lotem.

8. Make sure you have the Lotem update 1.27 or highter  loaded on the Brisque- this should be loaded by opening up a terminal window and with the cd installed type                UpdInstall UpdLotem    (do not do it through smit install_latest)

Do not load the TSP update for the Dolev along with the  Lotem update 1.27

9. Make sure the Lotem I.P address is correct  under scismit/platesetter.

10. Open a terminal window and type smit hosts and then list all hosts and make sure you do not  have duplicate hostnames with different i.p. addresses

11. Make sure en0 and en1 have different I.P. range.

Expose aborted
Simptom -Mismatched Plotter line requied 52800
,Counted 52848.

1. mso-list:l7 level1 lfo25;tab-stops:list .25in;mso-layout-grid-align:none; text-autospace:none;direction:ltr;unicode-bidi:embed">Check that the pelage  between the Tsp and the DDB BRD must be close by the two screws fasten together.

2. mso-list:l23 level1 lfo24;tab-stops:list .25in;direction:ltr;unicode-bidi:embed">reload the DDB Hex file

3. Replace the DDB BRD

The problem occur when the first punch (unrequested) in the list together with other requested punch.
the Problem exist in ver 3 (all upd's) and fixed in Brisque ver 4.

1. delete all punch definitions
2. create them again while the first set should include the spiral punch (#3) only.
3. For GTO machines the first set should include spiral punch #3 + #4

1. Do one of the following:
   • Modify the settings of your default press format to match the values for the following parameters in the Lotem registry:
     • Machine/Media Width Top Mechanical Margin = 10
     • Machine/Media Width Bottom Mechanical Margin = 6

   Or:

   • Modify the values for the following parameters in the Lotem registry to match the settings for your default press format:
     • Machine/Media Width Top Mechanical Margin = 10
     • Machine/Media Width Bottom Mechanical Margin = 6
2. From the Brisque Devices window, perform ReConfigure and run the test again.

Important: When running the laser uniformity test from the Brisque, verify that all diodes (24 for the Lotem 800 S and 48 for the Lotem 800 F) are defined as Open in the laser group registry.

To copy the TSP error log:

1. On the Brisque, open the terminal and type #.../temp to access the TSP error log file.
2. Copy the TSP error log file. You can copy this file from a Macintosh computer.
   Note: Booting erases the TSP error log file.
3. If a boot was performed, copy the TSP_error.# files located in the #../scitex/version/logs directory.