|
This topic comprises 5 pages: 1 2 3 4 5
|
Author
|
Topic: Issue with Enigma link decryptor
|
Tommy Zackariasson
Film Handler
Posts: 31
From: Ed, Dalsland, Sweden
Registered: Aug 2011
|
posted 06-02-2014 03:09 PM
Just got an e-mail from our tech-company (translated by Google):
"BACKGROUND During the first months of 2014 encountered a problem that affects everyone using serial 2 - projectors. DLP projectors use all the PCB " Enigma Link Decryptor " Playback encrypted movie content. For the server to accept the connection to the projector so it requires that a number of conditions are met. One of these is that there is available space in Enigma card to store new log files . Enigma card should always be empty at the log files. An emptying of these done every time a show or a clip has has finished in the server, but : If play is stopped and closed manually before it times out so will no log files will be extracted . A common example : Projectionist stops playback before it has been finished because no visitor is left in the auditorium to see the credits . " All digital cinema servers retrieves consistent only log files from the same day and time as the current playback is stopped . So why will the next film screening unable to extract log files from the previous display . This is the cause of the problem. Cinemas has called into problems related to this information sheet has had one or more of the following messages on their projectors. ( Error taken from a Barco Series 2 ) 1.Code 5835 : "ti -link decryptor - security log is almost full" ( Error ) 2.Code 5836 : "ti -link decryptor - security log is full" ( Error ) 3.Code 5831 : "ti -link decryptor - system error" ( Error ) Showing your projector on the error No. 1, playing after the current display is not up any more films. only a show to result in projector is locked and thus demonstrates the error No. 2. Would your projector to show the error message # 2 must Enigman replaced. The logs are then already filled to max and will not go to get out of the projector. Would your projector to show the error message # 3 but not in combination with any of the others. Try first and foremost, a reboot of the projector. This need not be related to the problem log . The solution is a manual extraction via your streaming server . However, there are a few requirements versions that must be met before this can be done. Note , a manual extraction does not always work . In some cases , the cards have been beyond redemption of other reason than that the log files had an earlier date. In these few cases, so having one or more log files in Enigma The card has become corrupt and hence they can not be charged out of the card. The problem then is that, although the logs which are not corrupt nor can be removed. The cards that ended up in the position can not be saved and must be replaced."
Sorry about the poor translation but I think you get the picture. It seems that if you have a ti link decryptor version earlier than 1.6.22 you should upgrade asap!
| IP: Logged
|
|
|
|
|
Steve Guttag
We forgot the crackers Gromit!!!
Posts: 12814
From: Annapolis, MD
Registered: Dec 1999
|
posted 06-02-2014 06:39 PM
I have made a bit of a study on this one and if you search the forums as Carsten mentioned you'll see MANY other discussions on the matter.
By the description, this is a Barco projector (their error codes). Depending on your server and software revision, one can take preemptive measures as well as likely download the logs. In the case of the Dolby server, one has to be on System 4.7.0 or higher and there is a CLI script behind a log in password that will allow one to tell the Enigma to downloaded EVERYTHING...it takes about an hour. And then after that...you'll need to run 16 5-second blank shows in 5 minute intervals to pull them again in about 512 hunks. I have done this now on all of our customers preemptively after it successfully recovered about 8 "almost full" conditions.
Now the nasty one is once the enigma is full, it is a brick unless you are TI to recover it.
The even more nasty one is the corrupted enigma...as I understand it, if there was a problem during a download...say you killed the projector power while the security logs were being downloaded...you could get a corruption. There are 16 banks in the Enigma, each with 512 entries. The trigger will be cocked...because when the system makes it through downloading 8190 logs over the course of months the normal way...when it gets to that corrupted entry...BAM, the enigma bricks.
I have determined that Christie is the least likely to have this problem (by sheer luck, in my opinion because I doubt they knew about this potential when they designed the projector). Christie puts the Enigma on the PIB module...which stays powered since that is also the communication system...as such, the Enigma probably never loses power suddenly. This is not the case for either NEC or Barco...both of which I've had Enigma issues.
The other server brands also have a means to force the download and I've heard mixed results.
| IP: Logged
|
|
|
|
|
|
|
|
|
|
Monte L Fullmer
Film God
Posts: 8367
From: Nampa, Idaho, USA
Registered: Nov 2004
|
posted 06-05-2014 08:24 PM
Wonder if that is what happened to us last Friday:
a DP2K-20C suddenly stopped during a performance (it has the SX-3000 IMB installed in the slot). Thus, following procedure with IMB installs is to: shut down the IMB via the TMS, then kill the power to the projector (by flipping the breaker in the panel that controls this unit since we have no said booths at this location...which can be a PITA at times..) wait for 10 seconds the turn on the projector and this powers up the IMB. Then, reconnect in the TMS.
This trick worked, but again, presentation shut down after 40 min into the presentation. This time, the tech was called, who just happened to be in the area, looked at it and couldn't totally figure it out and had to call GDC on this one for some help.
Found out that the cache log file in the BARCO was all but full which caused the shutdown.
There was a firmware update that the "ST" can clear out the cache.
I remember then, that with BARCOS, that the log files cache needs to be emptied out from time to time to prevent this shutdown to happen. Tech did the firmware update and clear out the cache and our issue was taken care of.
Now, what I presented above: would this be the same issue, or something else, for it sounds like what happened here with my description above.
Now, going back to what Brad mentions about not shutting off the units, I know of a lot of locations that do weekly cold reboots at least once a week, including us. Thus, are we in danger of what happened in the above case?
thx-Monte
| IP: Logged
|
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 5 pages: 1 2 3 4 5
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion
and agrees to release the authors from any and all liability.
|