This is topic Server / Projector Random disconnects and comms problems 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=002766

Posted by Gavin Lewarne (Member # 5397) on 07-30-2016, 05:35 AM:
 
Hi All

I have been battling with this issue for a couple weeks now, not really getting anywhere with CinemaNext (DcineX) and Dolby / Barco seem to be at a loss.

Problem:
Random "Disconnected" and "Transport not available" errors on DSS200 server, even during playback.

For a couple weeks now I have seen random "Disconnected" messages on the server when I get to work, not the usual "Transport not available" when the projector is switched off. We leave our server on 24/7 with a weekly reboot. If I see the disconnected message, it will stay there forever regardless if the projector is powered on or off. A server reboot has a 50% chance of getting it back to normal.

Sometimes, I'm seeing a "Transport not available", which is normal, but it remains even when the projector is switched on and left idling for up to an hour. Again, a server reboot has a 50% chance of fixing it.

Twice now, I have had either the show we are playing just randomly stop and the server go "Transport not available", OR, the subtitles (server generated) crap out but playback continue, and on hitting stop again I get a "Transport not available".

Barco advised a ICP replacement, no effect. Dolby advised a Cat862 external link cable replacement, no effect.

I have purged the Cat 862 audit logs, which has made the server much more responsive but has not resolved the issue.

Dolby has since passed on to CinemaNext an issue arising with the Cat862 on the latest software which causes failed communications when the projector is powered off for a period of time, but I cant see how that impacts our failures during playback itself, which occur randomly and on different content.

Server: Dss200, 4.8.8.4
Media Block: Cat862 4.8.5.2
Projector: Barco 12c, firmware 1.13.190, ICP 4.3.448

During all these problems, network connectivity remains functional - my control PC can VNC into the server and Communicator can see the projector just fine. I have replaced the Ethernet cables and switch just in case, no difference. There are no errors or warnings in any of the projector logs and, according to dolby, the server logs seem clean as well.

Does anyone have any idea whats going on?
 
Posted by Magnus Eriksson (Member # 6085) on 07-30-2016, 06:37 AM:
 
Any changes recently? Any new devices on the network??
The tiny blue link cable (data link/Cat 862) continues inside the box. Try opening the server and reseat the internal cable.
/M.E.
 
Posted by Gavin Lewarne (Member # 5397) on 07-30-2016, 06:42 AM:
 
There have been no hardware, software, cabling or network changes now for several months. No new devices on the network. It just started doing it one day a couple weeks ago.

I forgot to mention in my opening post that I also changed the internal Cat862 link cable
 
Posted by Magnus Eriksson (Member # 6085) on 07-30-2016, 06:59 AM:
 
A failing Barco cinema controller board?
Are the DSS200 IP adresses manually configured or is it in 'auto'?
/M.E.
 
Posted by Marco Giustini (Member # 4544) on 07-30-2016, 07:04 AM:
 
I've seen this before and usually required a new 862.
The DISCONNECTED message is the most misleading message on the DSS. It doesn't mean the 862 or the projector are disconnected but the main database is not online (I believe developers use "connectors" to connect to a database, hence the word).
If you have DISCONNECTED, then that tells me the store is crashing.
If you lose communication with 862, that tells me the 862 is crashing/losing communication.

A friend of mine had a similar issue (862 disconnecting and reboot would restore communication 50% of times - also only happened every few months) and in the end he replaced the whole server.

What you can do now is
- replace all the cables
- reinstall the server from scratch (losing all the content)
- full reinstall 862 (check 'reinstall all components' check box)
- isolate system from external network if possible

If the problem stays, I'd replace the 862 next.
 
Posted by Gavin Lewarne (Member # 5397) on 07-30-2016, 07:15 AM:
 
Thanks Marco

I was beginning to suspect Cat862 sheninagins. What you are saying about the disconnected message rings true - when it happens the server is essentially not seeing itself - no available content etc etc

I'm waiting for feedback from CinemaNext and will talk through this with them when I hear back, probably Monday.

Magnus: All IP addressed are manually configured, no DHCP anywhere in the system. I did initially suspect a CCB module issue, but I cant really see how that can be the case if the server craps out, but the communicator software on my control PC can still see and interact with the projector just fine. Ive switched the network port I'm using on the projector as well, made no difference.
 
Posted by Magnus Eriksson (Member # 6085) on 07-30-2016, 07:56 AM:
 
Well, unfortunately this rules out nearly all "cheap" failures and Marco is probably on the right track. The unspecified DISCONNECTED points us in a costly direction [Frown]
A full Cat 862 reinstall might help (I have experienced it), but I wouldn´t hope too much.
/M.E.
 
Posted by Steve Guttag (Member # 268) on 07-30-2016, 09:51 AM:
 
Gavin,

The "Disconnected" problem is software related and what Disconnected means is that the "Show Store" is disconnected. As such, it can't get to the content or much of anything else. The only "fix" for that for now is to reboot the server. STOP weekly reboots until they get this fixed. Dolby is workingn on it and look for a System 4.8.9 to be released with a fix. I hear that they have found one of the two problems causing the issue. That said, plan on MONTHLY reboots (under supervision) because the UI has a memory leak that could cause lockup. Yes, System 4.8.x are not my favorite for stability. I've been yellling pretty loudly about it too and I encourage others to do the same. 4.7 is more stable. Of course, in 4.7 you lose "instant play" and will have to suffer the checking licenses at show start. I hear that once the "Disconnected" problem is solved, that not only 4.8 will be fixed, 4.9 will likely be released shortly thereafter. 4.9 will allow you to save serial, GPIO and Ethernet cues to XML files...yes, you will be able to use the Ethernet port to control stuff, finally.

For the transport not available problem, I'd have to see the logs but I wonder if there are entries showing that the Mediablock link being down or the Auditorium network link being down.

If you actually went into the server to change the CAT862 link cable, you did something I wouldn't have done. What I do and HIGHLY recommend is use a 2-foot cable, remove one of the ISA blanks and run the cable from the CAT862 out through the open slot and then to the Link port on the back of the DSS200. You've left in two potentially bad RJ45 sockets with potential solder issue that could be agrivating the problem. Also, do NOT put that zip tie back on the CAT862. It forces too tight of a bend radius on the cable.

As a rule of thumb, if something goes wonky with a DSS line of server, running the "Install" image is a good idea albiet a PIA since all content, settings, cures, GPIO...etc are lost so always make a back up of your serial cues an/or have you GPIO configuration handy for the reinstall. The CAT862, if it has any issues, is best to reinstall its software and tick the "reinstall all components" Again that will flush out whatever was bad going on with it.
 
Posted by Gavin Lewarne (Member # 5397) on 07-30-2016, 10:19 AM:
 
Steve - I did consider just bypassing the link setup altogether and running a longer cable between the port and the media block, but I have to go by what our VPF NOC (CinemaNext / DcineX) want me to do.

I merely wanted to open the discussion here to see if other peoples thoughts were going along the same line as mine - ie, a Cat862 issue. I will have to wait and see if CinemaNext agree with that assessment and course of action.

So, its looking like I have 2 separate issues - the Disconnected error being a known software issue that will be resolved which is unrelated, but coincidentally happens at the same time as my Cat862 issues which are the main cause of concern.

I will speak to our NOC guy about doing a "full reinstall" of the media block when I speak to him on Monday. After tonight, we are closed for a month so I have plenty of opportunity to get this all sorted without having to worry about things being ready for the daily shows.
 
Posted by Mark Gulbrandsen (Member # 72) on 07-30-2016, 10:32 AM:
 
[Roll Eyes]
 
Posted by Mike Schulz (Member # 4297) on 07-30-2016, 11:46 AM:
 
I know you've got a problem that is beyond this but at one of my venues, we had an issue with random "transport is not available" showing up before/after and during shows. With the DSS-200, it seems to be happy only when the projector is already on and booted up before you boot up the server. Our solution to this problem was to just keep our projector(Christie) on with the lamp off after hours and we keep our server running 24/7 as well. I know the power bill might be an issue by doing this especially in a multiplex but I'd imagine with having the servers already going 24/7 that a projector idle without the lamp on isn't drawing too much power relatively.

I hope you get this sorted soon as I know how frustrating the DSS-200 can be when it decides to be finicky.
 
Posted by Marco Giustini (Member # 4544) on 07-30-2016, 12:01 PM:
 
Steve
Thanks for the heads up. It'd be nice if Dolby shared that info with everybody.

It'd be also nice if Dolby managed to make a working version. It's kind of annoying that the working/fixed version is always the one not yet released. [Frown]
 
Posted by Gavin Lewarne (Member # 5397) on 07-30-2016, 03:04 PM:
 
Marco, the standard reply I seem to get from CinemaNext / Dolby is always "its fixed in the next version". It usually is, but the next version always has something else goofy going on. Such is the way of things. I'm used to it now
 
Posted by Stephan Shelley (Member # 8587) on 07-30-2016, 03:10 PM:
 
When 4.8.9 comes out it is also suppose to fix the problem where the show starts and then freezes at 0:00:00.

I know of a triplex that is plagued with the above. Rolled back to 4.8.2 but then they have the freezing on downloading security logs. That is fixed in 4.8.6 but then the other problem.
 
Posted by Marco Giustini (Member # 4544) on 07-30-2016, 04:27 PM:
 
It's been like that since forever with Dolby.

Don't get me wrong: I like Dolby servers. But think about it: their software must work on 3-4 different systems only. The drivers are fixed. The hardware is fixed. Nobody is going to change a thing of the configuration.
And a D-Cinema server does only ONE thing: ingest and play content.

It's the best case scenario for any software developers but...
 
Posted by Steve Guttag (Member # 268) on 07-30-2016, 07:40 PM:
 
System 4.8 has definately been a mixed bag for me but the version that has the most oddities to it. System 4.7, if you think about it was pretty stable. To me, the biggest thing that changed in 4.8 was the instant play function where it no longer has to check content and licenses when the show starts since it checked them when it selected the show. Intermission was added but that was not a huge feature to me though it may be to others.

Back on topic. I have had exactly ONE CAT862 failure. It failed such that it would not run the movie (time line frozen). Sent it off to Dolby for repairs and it was put back in service and remains so to this day...it was from 2010 so it is now a 6 year old server.

As such, I really don't think you have a hardware issue unless it is an odd bad solder joint or something. As for your NOC...did you offer to him the option of bypassing the double RJ45 thing and he rejected it? I have absolutely had those connectors cause issues. Not many (less than 5) but once I pull that internal cable, I don't replace it with another short cable, it is coming out and a direct cable goes in. What is the downside? The fewer the connections, the higher the relibability.

If you have the opportunity, the next transport not available, try pinging both the projector and the auditorium NIC...see if the response time is less than 1msec. Note too, if it was a CAT862, it would say CAT862 not available (or mediablock if it was just on boot up). The CAT862 is a really reliable piece.
 
Posted by Gavin Lewarne (Member # 5397) on 07-30-2016, 08:00 PM:
 
ah that's a good idea on the Ping test Steve, ill do that.

When I speak to the NOC on Monday I will mention using a single link cable and bypassing the connector, I don't see why they would say no after their request I change the internal one already.
 
Posted by Leo Enticknap (Member # 534) on 07-30-2016, 09:19 PM:
 
I have a sorta similar (though thankfully, nothing like as show-jeopardizing) server/projector interaction issue.

In the Egyptian's little auditorium, we used to have a Doremi DCP2000 with Dolphin media block, connected to a NEC iS8-2K, with link encryption disabled altogether.

We then acquired a second DSS200, and recently replaced the Doremi with it. It connects to the projector via a cat862 and Cinelink I encryption.

The issue is that since installing the DSS200, the iS8-2K Windows control app will not connect to the projector through the network. It would with the Doremi in use, but not the Dolby. When serial or USB is used to connect the laptop to the projector directly, the control app works fine. But not over the network. Both the projector's control and TI IP addresses answer a command line ping from the same laptop, but the dratted app cannot communicate via IP with it.

If I had to guess, it would be that the cat862 is monopolizing a specific function of the connection to the projector's LAN interface (e.g. a port), such that no other device on the network has access to it. I've gone through the DSS200's installation manual looking for any obvious setting, but I can't find one. Communication between the DSS200 and all other network devices works fine (the Dolby Show Manager app running on the same laptop that refuses to control the projector is OK). Cues sent from the DSS200 to the projector also work.

Troubleshooting thoughts gratefully appreciated. It's only a minor pain having to have the laptop and projector connected via a USB wire, but this is one of those irritating little things I'd love to get to the bottom of.
 
Posted by Frank Cox (Member # 6258) on 07-30-2016, 09:31 PM:
 
quote: Steve Guttag
What is the downside?
Dust, since you have now opened another hole into the machine?
 
Posted by Steve Guttag (Member # 268) on 07-30-2016, 11:04 PM:
 
Nope...due to the interal fans, you have positive pressure there.

I really doubt it is the CAT862 that is "monopolizing" the port. The CAT862 doesn't get to talk to your projector directly. It is on its own network. It could be the Auditorium NIC and what it likely does is open the port an keep it open. As a result, if the NEC can only support one connection, it has it. I would find it odd that they didn't give the DCC its own port and let Cinema server have its own port.
 
Posted by Marco Giustini (Member # 4544) on 07-31-2016, 05:10 AM:
 
What Steve said.

When the transport goes, the GUI should tell you why. You'll have a "cannot connect to projector" or "unable to connect to mediablock/cat862" (cannot remember the exact words but something like that).

Indeed ping the projector but also ping the 862 which should be on 169.254.1.2
 
Posted by Leo Enticknap (Member # 534) on 07-31-2016, 01:23 PM:
 
quote: Steve Guttag
I really doubt it is the CAT862 that is "monopolizing" the port. The CAT862 doesn't get to talk to your projector directly. It is on its own network. It could be the Auditorium NIC and what it likely does is open the port an keep it open. As a result, if the NEC can only support one connection, it has it. I would find it odd that they didn't give the DCC its own port and let Cinema server have its own port.
Hmm ... DSS200s and other models of NEC projector work without this glitch, and the Doremi server we used to use works with that model of NEC projector without this glitch, so the cause has to be something to do with the communication between those two specific models. If other NECs can support more than one simultaneous connection, but the iS8-2K can only support one, that would explain it (assuming that the Doremi only uses that connection when it's actually interacting with the projector, and then closes it when each interaction is done). There are actually two Ethernet ports on the side of the projector: I'm going to try connecting the second one to the network switch as well, to see if adding a another physical connection cracks it.
 
Posted by Marco Giustini (Member # 4544) on 07-31-2016, 03:30 PM:
 
Leo

Do *NOT* connect the projector to the switch using two cables! This will create a loop and make your network unstable as the switch doesn't know which port to use!
 
Posted by Gavin Lewarne (Member # 5397) on 08-01-2016, 09:31 AM:
 
Had a more sensible reply from Dolby / CinemaNext today

Seems the server logs indicate problems with downloading the link decryptor logs, and the LD is sometimes severing the connection with the Cat862, even during playback.

They think my LD is hosed, but have asked I run the "downloadallprojectorlogs" script anyway, just to see. If it continues, as they suspect it will, time to replace the Enigma module itself.

I do find it curious as to why the Projector logs and Communicator are not reporting any issues with the LD, but I guess its a start

Will keep the thread updated in case this is helpful to people in the future
 
Posted by Steve Guttag (Member # 268) on 08-01-2016, 02:43 PM:
 
Things to keep in mind on this one. Neither party (CAT862 or Enigma) talk directly to each other. The CAT862 goes through the DSS200's network and then then back out of the Theatre NIC. From there to a network switch (typically though it could go to the projector) from there the projector's internal switch on the Cinema controller, then the signal backplane over to the HDSDI board and finally to the Enigma (link Decryptor). So, as you can see, there are plenty of pitstops that could cause a communication issue.

I would definitely reseat the Cinema Controller, HDSDI board and the Enigma board.

Next to remember, the port number for the log transfers and TLS sessions are not the same as the normal communication so just because one thing isn't reporting an issue does not mean that another function is going to work properly.

If you have another projector I'd do an Enigma swap and see if the problem stays with the either projector. Note, when you swap enigmas you WILL set off the security trigger that will have the Dolby server do the full 8192 log dump (512 at a time for 16 shows).
 
Posted by Gavin Lewarne (Member # 5397) on 08-01-2016, 04:36 PM:
 
Thanks Steve.

We have already ruled out the network cables and hardware (tried multiple different cables and switched, even going direct from auditorium port to projector.

Every board in the projector was re-seated already. We do not have another projector (single screen) so cant do an easy swap out to test stuff. Just have to do it one at a time as and when we eliminate things.
 
Posted by Leo Enticknap (Member # 534) on 08-01-2016, 05:40 PM:
 
Thanks Marco.

Can't understand why the iS8-2K has two LAN ports. I can't see any way you can give them separate IP addresses in the control software (unless the second is exclusively for the TI board). I suspect that this issue is one I'm just going to have to live with.
 
Posted by Marco Giustini (Member # 4544) on 08-02-2016, 11:08 AM:
 
Hello Leo

Those ports are connected to an internal switch. They're there for your convenience. You may want to plug - for example - your 3D unit or your laptop without going back to the main switch (which is always recommended). I find that very helpful particularly when the cabling is a nightmare and you want to connect to the projector network!
 




Powered by Infopop Corporation
UBB.classicTM 6.3.1.2