my profile | my password | search | faq & rules | forum home

» Film-Tech Forum ARCHIVE   » Operations   » Digital Cinema Forum   » Barco DP2K-6E loses IP setting

Author Topic: Barco DP2K-6E loses IP setting Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 06-23-2018 04:12 AM                     A few days ago a fellow cinema operator called me about not being able to access his DP2K-6E/ICMP, not through Webcommander, not through Communicator. Turned out that the Barco Cinema Controller lost it's IP address and went back to the factory default. All other settings remained intact - after re-entering the IP address, everything went back to normal. So, no big deal, but has anyone ever experienced something like this? The machine is powered multiple times each week. As a preventative measure, I entered another secondary IP address from the factory default subnet into their windows control notebooks and added a backup bookmark to access the machine under this address in the web browser. They are not familiar with using communicator (though remote assistance is now possible). - Carsten  |  IP: Logged Michal Matys Film Handler Posts: 70 From: Prague, Czech Republic Registered: Nov 2014 posted 06-25-2018 05:14 AM                    Hi Carsetn, Had this once on 17BLP projector, never happened since, being powered down and up every day (happened 3 months ago or so). Maybe some bug with the new series of cinemacontroller boards / sw.. Michal  |  IP: Logged ChunGui Lyu Film Handler Posts: 5 From: Feltham London UK Registered: Jun 2018 posted 06-26-2018 04:24 PM                     I wouldn't worry about if only happened once.  |  IP: Logged Sergey Morozov Film Handler Posts: 16 From: Moscow, Russia Registered: Mar 2017 posted 08-06-2018 05:35 PM                     Hello! I got the same issue twice on two DP2K-6E at different sites. Both with Barco Alchemy Projectors. It was one time on each projector several month ago. Today I got same issues again. It was at cinema with six Barco's and GDC SX-3000s. After they were turned on in the morning, two of Barco's booted with default 192.168.100.2 IP. The rest four projectors booted with normal defined IP. We realized that cinema stuff cannot connect to these two Barco's, then checked and restore correct IP, and got everything OK. I found, that all these issues were with new generation of CinemaController board. Our two Barco's with this issue i told about was DP2K-10S on 1.11.141 software and DP2K-12C on 2.5.57 software. We created service ticket on Barco customer portal. I don't know why this happens. Hope they will help.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 08-06-2018 08:09 PM                     Thanks Sergey, most important is to know that it may happen and that there is an easy way to fix it. We have a DP2K-6E that is more than 2-1/2 years old and never had that issue. However, that one is not powered up daily, we only use it for special shows a few times a year. The one where it happened is a more recent machine, and only 8 months in operation. Not daily, but multiple times each week. - Carsten  |  IP: Logged Sergey Morozov Film Handler Posts: 16 From: Moscow, Russia Registered: Mar 2017 posted 08-07-2018 10:31 AM                     I have a deep look into both logfiles. In both cases IP address set to default after power interruption during the beginning of projector booting when internal CCB router was initializing. Logfiles has following info: 7094=Aug 5 22:21:28 Zal-4 local0.info ipid[1914]: input power interruption detected 7095=Aug 5 22:21:52 Zal-4 syslog.info syslogd started: BusyBox v1.20.2 7096=Aug 5 22:21:52 Zal-4 kern.notice kernel: klogd started: BusyBox v1.20.2 (2016-01-07 10:05:59 CET) 7097=Aug 5 22:21:52 Zal-4 kern.info kernel: [ 0.000000] Using HARBIN CONTROLLER machine description ..... 7125=Aug 5 22:22:11 Zal-4 user.info router-discovery.sh[1341]: router detected (2nd generation) 7126=Aug 5 22:22:13 Zal-4 user.info router-configure.sh[1754]: devicename applied 7127=Aug 5 22:22:13 Zal-4 user.info router-configure.sh[1754]: hostname applied 7128=Aug 5 22:22:14 Zal-4 user.info router-configure.sh[1754]: portforwarding rules applied (3 success, 0 failed) 7129=Aug 5 22:22:14 Zal-4 user.info router-configure.sh[1854]: devicename applied 7130=Aug 6 04:00:27 Zal-4 syslog.info syslogd started: BusyBox v1.20.2 7131=Aug 6 04:00:27 Zal-4 kern.notice kernel: klogd started: BusyBox v1.20.2 (2016-01-07 10:05:59 CET) 7132=Aug 6 04:00:27 Zal-4 kern.info kernel: [ 0.000000] Using HARBIN CONTROLLER machine description .............. 7184=Aug 6 04:01:07 Zal-4 local0.info router2[1952]: network - wan ip-address is 192.168.100.2 Now i understand this behaviour. But i'd like to have some Info-T from Barco about this issue if it is not bug but feature of internal router booting process.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 08-07-2018 04:28 PM                     Thanks Sergey, I'll try to get the logs for that machine to check for the same condition. - Carsten  |  IP: Logged Sergey Morozov Film Handler Posts: 16 From: Moscow, Russia Registered: Mar 2017 posted 08-10-2018 06:09 AM                     Barco tech support answered me that issue may happens wit both generation of CCB. And it is not bug, but feature of router initialization process. Regards, Sergey  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 08-10-2018 08:11 AM                     So - you mean that this happens if the external mains supply is cut during a critical phase of the startup process? I'll have to ask my friends wether they can remember that occurence. - Carsten  |  IP: Logged Dave Macaulay Film God Posts: 2321 From: Toronto, Canada Registered: Apr 2001 posted 08-11-2018 10:04 PM                     Can't see why this is a feature. I can see how resetting the addressing to something known could be useful, but a serial connection is all you need to readdress the projector. And an undocumented "feature" to do a reset makes little sense. Maybe Barco has decided bugs that they are not going to fix will be called features?  |  IP: Logged Steve Guttag We forgot the crackers Gromit!!! Posts: 12814 From: Annapolis, MD Registered: Dec 1999 posted 08-12-2018 12:06 PM                     There is an old saying: "If you can't fix it, feature it."  |  IP: Logged

All times are Central (GMT -6:00)

Printer-friendly view of this topic

Hop To: Select a Forum: Category: Operations -------------------- Digital Cinema Forum Film Handlers' Forum Large Format Forum Ground Level Feature Info, Trailer Attachments & REAL Credit Offsets Category: Community -------------------- Film-Yak Film Handlers' Movie Reviews The Afterlife Bob Maar's Joke-A-Thon Category: Classified -------------------- Equipment and Supplies Wanted/For Sale Help Wanted/Seeking Employment Category: System -------------------- Software Beta Testing Forum

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.