Film-Tech Cinema Systems
Film-Tech Forum ARCHIVE


  
my profile | my password | search | faq & rules | forum home
  next oldest topic   next newest topic
» Film-Tech Forum ARCHIVE   » Operations   » Digital Cinema Forum   » NEC NC2000C problem - red lights (Page 1)

 
This topic comprises 2 pages: 1  2 
 
Author Topic: NEC NC2000C problem - red lights
Gronw Roberts
Film Handler

Posts: 60
From: Y Felinheli, Gwynedd, Wales
Registered: Oct 2015


 - posted 01-09-2016 12:37 PM      Profile for Gronw Roberts   Email Gronw Roberts   Send New Private Message       Edit/Delete Post 
I arrived at work today to find that our fill in projectionist had a bit of a nightmare during the afternnon showing of The Force Awakens. He'd already played the 2d version without a problem but when he played the 3D version the Doremi server lost communication with the NEC NC2000C projector and the rear status indicator started flashing red.

From what I understand it sounds like the dowser didn't open, the douser button kept flashing white and the screen said "waiting".

He said he might have seen the enable button on the front of the Dolby DFC100 filter controler turn red too. He said things we're a bit of a blur by then!

He had to turn the projector off at the wall to re set it, it wasn't responding at all. After re booting everything worked as it should and the show went ahead.

Any ideas as to what might of happened? I'm keeping an eye on things at the moment, I'm in the middle of a 2D showing of the same film and everything looks good.

 |  IP: Logged

Mark Gulbrandsen
Resident Trollmaster

Posts: 16657
From: Music City
Registered: Jun 99


 - posted 01-09-2016 12:44 PM      Profile for Mark Gulbrandsen   Email Mark Gulbrandsen   Send New Private Message       Edit/Delete Post 
Possibly the Security Manager had an issue that the reboot cleared. Look at the server and projector logs to see if there are any obvious issues that were logged...

Mark

 |  IP: Logged

Gronw Roberts
Film Handler

Posts: 60
From: Y Felinheli, Gwynedd, Wales
Registered: Oct 2015


 - posted 01-09-2016 01:10 PM      Profile for Gronw Roberts   Email Gronw Roberts   Send New Private Message       Edit/Delete Post 
Thanks Mark. How would I go about doing that? I've never had to do it before.

 |  IP: Logged

Gronw Roberts
Film Handler

Posts: 60
From: Y Felinheli, Gwynedd, Wales
Registered: Oct 2015


 - posted 01-09-2016 05:48 PM      Profile for Gronw Roberts   Email Gronw Roberts   Send New Private Message       Edit/Delete Post 
Sorry for the double post. I can't edit the last one for some reason.

I figured out how to get a detailed report off the Doremi but when I try to open the .tgz file I get what mostly looks like a massive amount of Japanese writing / symbols.

What am I doing wrong here?

 |  IP: Logged

Frank Cox
Film God

Posts: 2234
From: Melville Saskatchewan Canada
Registered: Apr 2011


 - posted 01-09-2016 06:04 PM      Profile for Frank Cox   Author's Homepage   Email Frank Cox   Send New Private Message       Edit/Delete Post 
A .tgz file is a tarred and gzipped archive. Did you uncompress it into a text file? If not, then you're reading a binary compressed file and it won't make any sense.

 |  IP: Logged

Stephan Shelley
Jedi Master Film Handler

Posts: 854
From: castro valley, CA, usa
Registered: Nov 2014


 - posted 01-09-2016 06:14 PM      Profile for Stephan Shelley   Email Stephan Shelley   Send New Private Message       Edit/Delete Post 
use the Dolby log analyzer:

http://loganalyzer.dolbycustomer.com/

 |  IP: Logged

Gronw Roberts
Film Handler

Posts: 60
From: Y Felinheli, Gwynedd, Wales
Registered: Oct 2015


 - posted 01-09-2016 06:46 PM      Profile for Gronw Roberts   Email Gronw Roberts   Send New Private Message       Edit/Delete Post 
Great,thanks. I'm having a look through it now.

Edit: The problems occoured on our 2pm screening (9/1/16). Here's what the log said:

No suitable NTP server configured
The NTP servers set on this device are either dead, not reachable or mistyped.
Please set reachable NTP servers to allow time of this device to remain accurate.
This will also prevent the mediablock clock to drift.
If a media block drift out of it allowed offset (i.e.: 360s) the card may have to be changed.
Invalid boot sequence detected
in drmreport/doremi/log/bootseq.log :

Line 164:[Sat Jan 9 13:49:55 2016][WARNG]: bootsequence-check: Invalid boot sequence detected

Invalid boot sequence detected can be the consequence of:

The users bad practice of shutting down the unit improperly: a unit should always be switched off either:
Using the GUI: Menu > Logout... > Shutdown
By pressing the front power button (less than one second)
A power shortage: To avoid this we recommand using an Uninterruptible Power Supply
A system freeze or crash: this could be due to a memory/CPU issue please run a memtest to confirm or infirm:
When the unit is booting at grub window press the Esc button
From the 4 options menu select the last one memtest
Run this test for 12 hours
Report found errors to the DOREMI Support

HDD Failure (frozen)
in drmreport/doremi/log/kern.log :

Line 798:Jan 4 09:02:58 dcp2000 kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0x2 frozen

Line 836:Jan 4 10:14:15 dcp2000 kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0x2 frozen

Line 852:Jan 4 10:17:20 dcp2000 kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0x2 frozen

Line 891:Jan 4 10:34:00 dcp2000 kernel: ata5: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0x2 frozen

Line 907:Jan 4 10:43:53 dcp2000 kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0x2 frozen

Line 917:Jan 4 10:45:08 dcp2000 kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0x2 frozen

Line 957:Jan 4 11:21:48 dcp2000 kernel: ata5: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0x2 frozen

Line 3049:Jan 6 16:38:00 dcp2000 kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0x2 frozen

Line 3116:Jan 6 19:41:18 dcp2000 kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0x2 frozen

NOTE: This notifcation is that there is an issue with the hardware you are connecting to the server for ingest or export. For DCP2000, DCP2K4 and Showvault that it is ATA5 (CRU) or ATA6 (DVD) are ingest drives, and not part of the content raid.
Please remove the media and have it tested by the distributor of the drive. For the IMS1000 the ata2 an external drive plugged in via USB or eSATA. (ata3 is the internal raid card)
NTP no server suitable for synchronization found
in drmreport/doremi/log/time.log :

Line 102:[Mon Jan 4 09:01:55 2016][ERROR]: ntpdate: no server suitable for synchronization found

Line 104:[Tue Jan 5 06:25:12 2016][ERROR]: ntpdate: no server suitable for synchronization found

Line 106:[Tue Jan 5 09:33:45 2016][ERROR]: ntpdate: no server suitable for synchronization found

Line 110:[Wed Jan 6 10:14:26 2016][ERROR]: ntpdate: no server suitable for synchronization found

Line 112:[Thu Jan 7 10:56:19 2016][ERROR]: ntpdate: no server suitable for synchronization found

Line 114:[Fri Jan 8 12:05:29 2016][ERROR]: ntpdate: no server suitable for synchronization found

Line 124:[Sat Jan 9 06:25:10 2016][ERROR]: ntpdate: no server suitable for synchronization found

Line 126:[Sat Jan 9 13:44:35 2016][ERROR]: ntpdate: no server suitable for synchronization found

Line 128:[Sat Jan 9 13:50:00 2016][ERROR]: ntpdate: no server suitable for synchronization found

Edit the configuration file /doremi/etc/ntpservers and specify a valid NTP server under the variable: NTPSERVERS="" Found a NTP server close to your location at www.pool.ntp.org, or if you have an TLMS, set the target at the IP address of the TLMS server. To make sure the server is available from the Doremi server ping it from a terminal window.
It is highly recommended to use NTP, if the server drifts and RTC goes outside the allowed amount it is not covered under warranty

Playout logs with warnings
in drmreport/doremi/log/odeticsd.log.2.gz :

same error repeated 7 times

in drmreport/doremi/log/odeticsd.log.1.gz :

same error repeated 47 times

in drmreport/doremi/log/odeticsd.log :

same error repeated 16 times

Line 204:[Sat Jan 9 13:34:01 2016][INFO ]: AsRun: "00000002-0000-0000-0000-000000000000"," ","00:00:00.00","00:00:00.00","0","0","I"

Line 209:[Sat Jan 9 13:34:06 2016][INFO ]: AsRun: "3a3367df-764b-9041-abdf-4e19f53703cf"," ","00:00:00.00","00:00:00.00","0","0","I"

Line 242:[Sat Jan 9 13:37:40 2016][INFO ]: AsRun: "16450522-2acd-4272-9f8f-185e124bf3b5"," ","00:00:00.00","00:00:17.09","0","0","I"

Line 247:[Sat Jan 9 13:38:04 2016][INFO ]: AsRun: "f9285c82-914e-4e6e-abfe-5dc6fe55017a"," ","00:00:00.00","00:00:00.00","0","0","I"

Line 252:[Sat Jan 9 13:38:08 2016][INFO ]: AsRun: "d243375e-a7d9-418e-a4c8-e4a58e7b579f"," ","00:00:00.00","00:00:00.00","0","0","I"

Line 257:[Sat Jan 9 13:38:12 2016][INFO ]: AsRun: "09fa2430-3b6e-49a2-92bb-4060581491c9"," ","00:00:00.00","00:00:00.00","0","0","I"

Line 266:[Sat Jan 9 13:38:25 2016][INFO ]: AsRun: "00000002-0000-0000-0000-000000000000"," ","00:00:00.00","00:00:00.11","0","0","I"

Line 8219:[Sat Jan 9 13:52:19 2016][INFO ]: AsRun: "16450522-2acd-4272-9f8f-185e124bf3b5"," ","00:00:00.00","00:00:11.14","0","0","I"

Line 8224:[Sat Jan 9 13:52:35 2016][INFO ]: AsRun: "f9285c82-914e-4e6e-abfe-5dc6fe55017a"," ","00:00:00.00","00:00:10.16","0","0","I"

Line 8229:[Sat Jan 9 13:59:39 2016][INFO ]: AsRun: "16450522-2acd-4272-9f8f-185e124bf3b5"," ","00:00:00.00","00:06:58.21","0","0","I"

The AsRun log entry is recorded in the odetices.log, it is a reference to all playback clips according to the CPL
For more info on what the AsRun log means please see: AsRun, (playback log) in the Odetices.log
The last charactor is a warning, "I", "C" or "CE" [Mon Sep 30 19:43:26 2013][INFO ]: AsRun: "c5e2c6b6-5d8a-40f7-8452-d5001dd11997"," "," 00:00:00.00","00:40:00.05 ","0","0","I
[Mon Sep 30 20:45:00 2013][INFO ]: AsRun: "c5e2c6b6-5d8a-40f7-8452-d5001dd11997"," ","00:40:00.05","01:36:22.00","0","0","CE"
[Mon Sep 30 21:30:55 2013][INFO ]: AsRun: "2953ba7e-ee32-46a7-9f29-86f9429f6a3b"," ","00:00:00.00","00:01:33.19","0","0","C" "I = incomplete or C = complete or CE = complete with errors" "I" I- Playback was incomplete (It didn't play for lenght of time states in the CLP, e.g. stopped before the end) "C" C- Playback was complete (Start to Finish of Clip) "CE" CE- Playback was complete with exceptions. There was an issue (e.g. pause etc)
This charactors "I", "C" or "CE" is only a warning that have ocourred during the playback.

PCIe connection issues
in drmreport/doremi/log/kern.log :

same error repeated 17 times

Line 4771:Jan 8 12:06:07 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 5113:Jan 9 13:42:34 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 5802:Jan 9 13:44:06 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 5808:Jan 9 13:44:08 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 5811:Jan 9 13:44:10 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 5819:Jan 9 13:44:13 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 6515:Jan 9 13:49:33 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 6538:Jan 9 13:49:33 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 6542:Jan 9 13:49:35 dcp2000 kernel: pciehp: Card not present on Slot(1)

Line 6550:Jan 9 13:49:38 dcp2000 kernel: pciehp: Card not present on Slot(1)

The PCIe card is in a ShowVault and is where the PCIe cable plugs into, the other end connects to the IMB. Try to remove and reseat the PCIe, and test.
Dolby 3D not calibrated
in drmreport/doremi/etc/dfc100.matrix :

Line 1:1.000000000000 0.000000000000 0.000000000000

Line 5:1.000000000000 0.000000000000 0.000000000000

This device has not been color calibrated for Dolby 3D. If the server is used to play Dolby 3D content without calibration done, it will result in a color distortion. you must ingest the Dolby 3D DLM (doremi License message) to be able to add dolby 3D to the device manager. To add the 3D capability to a DCP2000 you need the following

Dolby 3D license, from Doremi
Manual: DCP-2000_Dolby3D_Calib_000465_v1_1.pdf
The 3D colour calibre DCP from Doremi must be ingest
Run installation pkg: dcp2000_dfc100wizard-1.2.pkg
unity.txt file.

#2, 3, 4 & 5 of the above are on our EU ftp site ftppublic. Dolby_3D_for_Doremi.zip
ftp://ftppublic@ftppublic.doremitechno.org/products/DCP-2000/Option_pkg/Dolby_3D/Dolby_3D_for_Doremi.zip The matrix configuration file is /doremi/etc/dfc100.matrix. It is a plain text file.
Hardware Fan 1 Speed is below 4000 RPM
Hardware Fan 1 Speed is too slow.
This fan should spin between 4000 rpm and 7700 rpm.
Hardware Fan 2 Speed is below 4000 RPM
Hardware Fan 2 Speed is too slow.
This fan should spin between 4000 rpm and 7700 rpm.
Projector Communication Error
in drmreport/doremi/log/odeticsd.log.2.gz :

Line 39521:[Mon Jan 4 16:50:07 2016][ERROR]: 'Projector': Communication Error: Failed to execute the command to the DLP (Get Response Message Failed).

in drmreport/doremi/log/odeticsd.log.1.gz :

Line 2766:[Tue Jan 5 12:41:14 2016][ERROR]: 'Projector': Communication Error: Failed to execute the command to the DLP (Get Response Message Failed).

Line 3201:[Tue Jan 5 22:51:23 2016][ERROR]: 'Projector': Communication Error: Failed to execute the command to the DLP (Get Response Message Failed).

Line 8020:[Wed Jan 6 23:20:06 2016][ERROR]: 'Projector': Communication Error: Failed to execute the command to the DLP (Get Response Message Failed).

Line 13305:[Thu Jan 7 22:57:17 2016][ERROR]: 'Projector': Communication Error: Failed to execute the command to the DLP (Get Response Message Failed).

Line 17624:[Fri Jan 8 22:40:55 2016][ERROR]: 'Projector': Communication Error: Failed to execute the command to the DLP (Get Response Message Failed).

in drmreport/doremi/log/odeticsd.log :

Line 137:[Sat Jan 9 13:30:16 2016][ERROR]: 'Projector': Communication Error: Failed to execute the command to the DLP (Connection Refused).

Line 8361:[Sat Jan 9 22:44:50 2016][ERROR]: 'Projector': Communication Error: Failed to execute the command to the DLP (Get Response Message Failed).

 |  IP: Logged

Leo Enticknap
Film God

Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000


 - posted 01-09-2016 09:29 PM      Profile for Leo Enticknap   Author's Homepage   Email Leo Enticknap   Send New Private Message       Edit/Delete Post 
Not being able to sync the time with an NTP server shouldn't be a show killer. Our DCP2000 meows and hisses if it can't connect to time.nist.gov (which it occasionally fails to do), but it's never refused to play content on account of this.

However, it does look like you have two bad fans. I'm a bit surprised that they're both malfunctioning. Never been cleaned and caked up with crud? Power supply issue? The bad fans could be causing more general overheating that is making the server unreliable.

 |  IP: Logged

Stephan Shelley
Jedi Master Film Handler

Posts: 854
From: castro valley, CA, usa
Registered: Nov 2014


 - posted 01-09-2016 10:26 PM      Profile for Stephan Shelley   Email Stephan Shelley   Send New Private Message       Edit/Delete Post 
This a show vault with IMB? I would reseat the PCIe card and reseat the PCIe cables as well.

 |  IP: Logged

Marco Giustini
Film God

Posts: 2713
From: Reading, UK
Registered: Nov 2007


 - posted 01-10-2016 05:20 AM      Profile for Marco Giustini   Email Marco Giustini   Send New Private Message       Edit/Delete Post 
I believe you can ignore the fan errors and the PCIexpress errors too - double check with Doremi but I've been there before.

The only real error I see is the projector communication failure. Check your ethernet/switch, maybe replace the cables.
Also you could try deleting the projector from the device list. Then save and add it again.

 |  IP: Logged

Mark Gulbrandsen
Resident Trollmaster

Posts: 16657
From: Music City
Registered: Jun 99


 - posted 01-10-2016 09:30 AM      Profile for Mark Gulbrandsen   Email Mark Gulbrandsen   Send New Private Message       Edit/Delete Post 
I have seen air filters plug up and fan readings go haywire in projectors before. Especially the ICP will over heat and actually throw an error and then shut down the projector. I assume your filters are all clean? Also have a look at the projector log.

Mark

 |  IP: Logged

Gronw Roberts
Film Handler

Posts: 60
From: Y Felinheli, Gwynedd, Wales
Registered: Oct 2015


 - posted 01-10-2016 02:57 PM      Profile for Gronw Roberts   Email Gronw Roberts   Send New Private Message       Edit/Delete Post 
We've had the NTP error since day 1 but were told to ignore it by the guy that installed our equipment.

The filters should be clean, we've only been running the server and projector for about a month.

I can't seem to find any info about how to get the logs from the projector. Can you help me out?

 |  IP: Logged

Marco Giustini
Film God

Posts: 2713
From: Reading, UK
Registered: Nov 2007


 - posted 01-10-2016 05:03 PM      Profile for Marco Giustini   Email Marco Giustini   Send New Private Message       Edit/Delete Post 
NTP stands for Network Time Protocol, it's supposed to keep the clock of your server synchronised.

It's not great not to have it set - in the end it may give you trouble - but it's not the cause of the issue on this occasion.

 |  IP: Logged

Leo Enticknap
Film God

Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000


 - posted 01-10-2016 06:31 PM      Profile for Leo Enticknap   Author's Homepage   Email Leo Enticknap   Send New Private Message       Edit/Delete Post 
Is this server connected to the Internet? If not, it's never going to be able to sync with an NTP server (unless you have one on the local network).

The reason for the time sync is that the media block's internal clock cannot be changed by the end user. This is a security measure, to prevent a theater from trying to play a DCP at times not allowed by the key (e.g. after it's expired), simply by changing the time in the server's BIOS. However, it can wander (the cat745's clock in one of my houses is now 11 minutes fast). The DCP server, therefore, attempts to "dial 123" (speaking clock in Britain!) every time it boots, by asking an external NTP server what the time is. Once it syncs the time successfully, it uses that time as the system time until the next shutdown or reboot, even if the media block's clock has wandered a bit.

For your Doremi to be able to do this, it needs to be connected to the Internet, and the address of a server configured in the system settings. Because the Doremi does have DNS capability, I use time.nist.gov in ours. The Dolbys in our other two houses don't, so I've put the IP addresses for the government NTP server in Las Vegas (geographically the nearest) into ours.

To get the logs from an NEC, open Digital Cinema Communicator, go into service mode, then Info > Log > Error Log.

 |  IP: Logged

Mark Gulbrandsen
Resident Trollmaster

Posts: 16657
From: Music City
Registered: Jun 99


 - posted 01-10-2016 07:39 PM      Profile for Mark Gulbrandsen   Email Mark Gulbrandsen   Send New Private Message       Edit/Delete Post 
You need DCC in order to get the projector logs. You should be able to get it from your install guy or your local technician. If you have a computer on the network you can also get it by loging on to the projectors Web Server and pressing the "Get DCC" button. You will need your projector's IP address to get the web server. It's handy to have to change lamps over using the side buttons on the projector. The buttons are not bad once learned, but DC makes that so much easier and you can have a laptop connected to align the lamp using the internal light meter. This way you are not looing at the little readout and reaching in the back to make adjustments. You can also monitor temperatures and fan speeds, and really mess up the projector with the appropriate access passwords and such if you so desire...

Web Server looks like this...

 -

Mark

 |  IP: Logged



All times are Central (GMT -6:00)
This topic comprises 2 pages: 1  2 
 
   Close Topic    Move Topic    Delete Topic    next oldest topic   next newest topic
 - Printer-friendly view of this topic
Hop To:



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.

© 1999-2020 Film-Tech Cinema Systems, LLC. All rights reserved.