|
|
This topic comprises 3 pages: 1 2 3
|
|
Author
|
Topic: Barco Communicator 5.12 released, with workaround for bad keypads
|
Leo Enticknap
Film God
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 10-19-2018 10:31 PM
Sure, you can change the code to work around dead numeral buttons on Series 1 and Series 2 Barcos using Communicator, in exactly the same way. It's just this new feature to enter the tamper clear code through Communicator rather than the keypad, that doesn't seem to have been implemented for Series 1 machines.
quote: Steve Guttag
Let's face it, it has been 9 years since the last one came off the line. It wouldn't surprise me if they all stop fooling with them altogether next year for their 10th year past end of production.
However, there are a lot of them still in revenue-earning service, and as long as that situation continues, it would be very bad PR for any of the projector manufacturers to adopt a "we won't even talk to you" approach to supporting these machines. The situation is further complicated by the fact that many of them were installed under VPF or leasing arrangements. I was recently told about an 18-plex full of Series 1 NECs, which were installed under a lease arrangement that the theater is locked into until 2022. This is growing into a major problem for all concerned, because the leasing company is unable to maintain them to an acceptable standard of reliability, because they can't source the parts they need.
To give kudos to Barco where kudos is due, on both of the two occasions I've had to call them for help fixing a Series 1 projector, they were very supportive and helpful. They had to elevate my query to tier 2 support almost immediately, because the helpdesk operator who initially answers the phone doesn't seem to have gone through any high level training on DP1500, 2000 and 3000 projectors. But on both occasions, I have eventually been able to speak to someone who had, and they were able to give me the support I needed to get the projector working again.
The fact that the 1500, 2000 and 3000 use the same model of coolant pump as the B and C series is a very big help, given that faults with the pressurized cooling system are by far the biggest weak point with them, in my (admittedly limited) experience. That was why I was called out to work on the 3000 this afternoon (UV damaged hose had sprung a leak).
| IP: Logged
|
|
|
|
|
|
|
|
|
|
|
|
Leo Enticknap
Film God
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 11-02-2018 10:10 AM
I could have done with it on Tuesday. DP2K-19B in a rabbit hutch enclosure in a Bel-Air Circuit installation (high profile individual, so cannot post a picture for obvious reasons), with literally 2-3 inches between each side of the projector and the side wall of the enclosure. Air bubbles had got into the cooling system, and it needed a flush out and refill.
As if the contortion act needed to get the light engine cover off and attach the hoses to flush and refill the cooling system wasn't bad enough, it took me, literally, 40 minutes to clear the tamper afterwards. I had to feel for the position of the Dallas key reader, and only the left row of numeral buttons was even visible, let alone reachable with a finger. Eventually, and after setting the combo to 333333333 (because that was the only button I stood a vegan in an abattoir's chance chance of getting to and pressing eight times within the timeout limit, after fumbling with the Dallas key), I just managed to do it. If the ability to enter the code on the laptop had been working, I would have saved around half an hour.
| IP: Logged
|
|
|
|
Leo Enticknap
Film God
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 11-22-2018 01:28 PM
Sorry to be a pain, but I've found what might possibly be another bug in 2.7.76. I can't update the ICP software on a projector that is running 2.7.76. The first time it happened (on a DP4K-19B), I thought it was a bad ICP, and Corey advised me to do the ICP recovery procedure. Both using the Barco updater and the TI ICP and Enigma tool, it said error uploading to slot A, and wouldn't let me go any further.
I couldn't do the ICP recovery procedure, because the projector was in an enclosure (the one I mentioned above) that made it impossible to pull the ICP out of the card cage without removing the projector from its enclosure. As I didn't have enough people and ladders to do that safely, I left that ICP on 4.2.
A little while later, I was working in a 'plex with 11 projectors (mix of B and C series, plus one DP3000) that needed upgrading from 2.5.57 to 2.7.76. Some of them still had ICPs on 4.2, and exactly the same problem happened when I tried to upgrade the projector software and then the ICP (on this one, I did do the recovery procedure, and that did enable me to install 4.5 successfully). However, on another projector, I updated the ICP while the projector was still on 2.5.57 without any problem, then updated the projector to 2.7.76 - again without any problem, and both the projector and the ICP were fine afterwards.
Could there be a glitch in 2.7.76 that is preventing ICP updates? Per Meadow's Law, once could be anything, but twice is suspicious.
| IP: Logged
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 3 pages: 1 2 3
|
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.
|
Home
![[Big Grin]](biggrin.gif)
)
Printer-friendly view of this topic