Film-Tech Forum ARCHIVE: Extremely Slow Boot Barco DP2K-20c w GDC SX2000AR

This is topic Extremely Slow Boot Barco DP2K-20c w GDC SX2000AR in forum Digital Cinema Forum at Film-Tech Forum ARCHIVE.

To visit this topic, use this URL:
https://ft-forum.com/ft/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic;f=16;t=002874

Posted by Marcial Feliciano Ramos (Member # 1989) on 11-27-2016, 01:59 PM:

Hi all,

We have a Barco DP2K-20c with GDC SX2000AR that takes to much time booting up. For example, if a normal boot is approx 3 minutes this one takes almost 15 to 20 minutes.

We had problems with the server and ICP. GDC and barco told me to change it; those problems were fixed but the slow boot continues.

Any one of you guys had this issue or something similar?

Posted by German Marin (Member # 918) on 11-28-2016, 03:28 AM:

Have you look into the logs? at boot up you must see something like this:

Jan 1 00:00:16 localhost local0.info clo[222]: main - starting application (version 1.6.7)
Jan 1 00:00:17 localhost local0.info dp60[283]: main - starting application (version 1.13.190) (Feb 9 2015 14:09:05)
Jan 1 00:00:17 localhost local0.info dp60[283]: main - projector type is "DP2K-20C"
Jan 1 00:00:17 localhost local0.info dp60[283]: network - lan ip-address is 192.168.254.242 (dhcp off)
Jan 1 00:00:18 localhost local0.info dp60[283]: command (port = internal) - set power on
Jan 1 00:00:32 localhost local0.info dp60[283]: lamp power supplies - 2 lamp power supplies detected
Jan 1 00:00:32 localhost local0.info dp60[283]: main - no integrated cinema media processor detected
Jan 1 00:00:32 localhost local0.info dp60[283]: main - ti-icp board detected
Jan 1 00:00:32 localhost local0.info dp60[283]: main - wait until ti-icp board ready
Jan 1 00:00:45 localhost local0.info dp60[283]: system - synchronize date to 20161127123322
Nov 27 12:33:22 localhost local0.info dp60[283]: ti-icp - type = 0x42, serial number = "01F11B****00BB"
Nov 27 12:33:25 localhost local0.info dp60[283]: main - image media block "BARCO IMB R765534" detected
Nov 27 12:33:30 localhost local0.info dp60[283]: system - ti-link-decryptor login started...
Nov 27 12:33:50 localhost local0.info dp60[283]: system - ti-link-decryptor login successful
Nov 27 12:33:52 localhost local0.info dp60[283]: command (port = internal) - select light sensor calibration file 'Scope'
Nov 27 12:33:52 localhost local0.info dp60[283]: system - load lens encoder file "R9855933"
Nov 27 12:33:52 localhost local0.info dp60[283]: command (port = internal) - execute lens file '.init'
Nov 27 12:33:52 localhost local0.info dp60[283]: system - execute lens file ".init" handled successfully
Nov 27 12:33:52 localhost local0.info dp60[283]: command (port = internal) - set dowser closed

If there are something that take a lot of time to load you can find it here.

Posted by Steve Guttag (Member # 268) on 11-28-2016, 07:06 AM:

Is the GDC getting to the SMS screen at a normal rate of speed? Does the SM connected come up within 3 minutes of reaching the SMS screen?

Generally, when a Barco takes a LONG time to boot up, it is because a security piece is not communicating (or is missing). For instance, if you had a dead Enigma module, it would take a LONG time to boot up. It wants to give that SM every chance to check in and say it is okay. It would boot up faster (though not normal) to remove the HDSDI module.

My suspicion is that it is either the signal backplane not allowing proper communication or the IMB not answering the CinemaController's calls. If you have more than one screen, the quick way to find out is to swap IMBs (before show time since the serial numbers won't match so you'll get big error there but it should allow the projector to boot up at normal speed. Failing that, swap Cinema Controllers. Again, you'll get errors and the Dallas key would also need to be moved but ignoring all of that you should see if the boot up time returns to normal (or moves with the card swap).

You are really down to the two ends of the security handshake (Cinema Controller and IMB) and that which lets them talk (Signal Backplane).

And note, if the ICP isn't properly communicating, it too could cause this but you said you changed it. I have had both the Cinema Controller and the ICP interact badly with one another and reloading their respective softwares ended the problem. In the case of the ICP, I used the ICP update/recover program...but again, you imply that you changed the ICP.

Posted by Dave Macaulay (Member # 813) on 11-28-2016, 07:08 AM:

The projector is totally unlike a film projector. A digital projector is a dozen or more interconnected computers and a light bulb.
The logs will show what slows down the startup. Send a package to Barco support and they will check for the problem. You can look yourself but it's not easy to understand... and even if you find what's hanging, a fix may not be obvious.
Servers with a port incorrectly set to DHCP or with an unreachable NTP server can hang for a few minutes waiting for information that never comes. I don't know of a similar issue with projectors, but surely there are some. You can set NTP time sync on the projector as well, I haven't seen one hang for that though.