|
|
Author
|
Topic: NEC 2500 series 1 ?
|
|
|
|
|
Leo Enticknap
Film God
![](http://www.film-tech.com/ubbmembers/534a.jpg)
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 09-23-2018 11:44 AM
I have a vague memory that there are some trimpots on the 2500's card cage power supply that allow you to adjust the output voltage (thankfully, it's a year and a half since I've had to go inside one). As the LAN connection doesn't go straight into the TI card, though, I'd have thought that the main input/output board would be a more likely suspect.
However, if you aren't having any other networking problems (e.g. Digital Cinema Commmunicator fails to connect from a PC on the management network occasionally), I'd be surprised if a bus voltage issue turned out to be the cause of your trouble. However, if a direct crossover cable from the server from the projector has not cured the connection problem, that isn't it, either.
I doubt if this is relevant, but is your 2500 on the current software bundle and TI firmware? Should be 2.11 for the software bundle and 15.1 for the TI firmware.
Also, taking a log package from the DSS200, uploading it to Dolby's online log analyzer, and seeing what it tells you can't hurt. The log analyzer will give you a unique URL for the results of your analysis, which you could post here if you like.
| IP: Logged
|
|
Miguel Cruz
Film Handler
Posts: 16
From: Mexico City
Registered: Nov 2012
|
posted 09-23-2018 09:28 PM
Hi David
In fact apparently we have the same issue ,because I had installed a Dolby DSS200 with 4.4 software cith NEC NC1600 , with the same problems " Transport not available " I openeed a ticket with dolby support I sent me 4.8 Software I recommend me "purge" the server , since apparently the server was saving logs , but was still the problema , so they sent me 4.9 software , by schedules I removed the server and replace it with a Doremi , but this week IŽll update the DSS200 and if I see any failure in the playback ( but I donŽt think it happens )IŽll let you know . As Leo mentions you can check the log in http://loganalyzer.dolbycustomer.com/ and open a ticket with dolby support , I share the last thing they commented me:
----------------------------------------------------------------
With the new logs I see more buffer underflows on the 19th, as you mentioned it was reported to you playback stopped:
2018-08-19 16:19:45,762 INFO [TCP server transport connection thread] proxy.ScdProxy$ShowPlayerBufferUnderflowListener - Buffer Underflow Detected 2018-08-19 16:20:02,761 INFO [TCP server transport connection thread] proxy.ScdProxy$ShowPlayerBufferUnderflowListener - Buffer Underflow Detected 2018-08-19 16:20:08,987 INFO [TCP server transport connection thread] proxy.StreamingProxy - streamengine.status.state.value: CONNECTING OldSocketState: true 2018-08-19 16:20:08,987 ERROR [TCP server transport connection thread] proxy.ProxyConnectionStateListener - Lost Socket Connection to ShowPlayer 2018-08-19 16:20:08,987 ERROR [TCP server transport connection thread] proxy.ScdProxy - Detected cat862:showstore-1/192.168.168.21:16161 disconnect
I do also see error message in the Cat.862 logs:
2018-08-19 16:19:53,567629 INFO MainApp;Streaming.StateMachine:Entered Decoding State 2018-08-19 16:20:02,726179 INFO MainApp;Streaming.StateMachine:Video Buffer Underflow 2018-08-19 16:20:02,726448 ERROR MainApp;Streaming.StateMachine:Video Buffer Underflow before end of session 2018-08-19 16:20:02,728781 INFO Supervisor;MicroBlaze:Playback: INFO: Stop Command Received. 2018-08-19 16:20:02,729460 INFO Supervisor;MicroBlaze:Process Interrruption-- 2018-08-19 16:20:02,729878 INFO Supervisor;MicroBlaze:logAllFrameSequences: audioHasLogged=0, videoHasLogged=0 2018-08-19 16:20:02,730265 INFO Supervisor;MicroBlaze:FrameSequenceMonitor::logAllFrameSequences calling Audit Log start 3085 end 3304
And it may mean that the Show Manager is collecting the audit logs which sometimes can cause the Cat.862 to crash. Hopefully updating to 4.9.1.22 will correct this issue. If not, we will have to take the next step.
----------------------------------------------------------------
Regards
Miguel
| IP: Logged
|
|
|
Leo Enticknap
Film God
![](http://www.film-tech.com/ubbmembers/534a.jpg)
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 09-24-2018 07:39 AM
If the underlying problem is software glitches in version 4.7 interacting unhelpfully with your projector and/or TI board, then swapping in a DSS100/DSP100 will likely not help you, because the final software release for it was 4.7.8.7.
Once you get to doing the 4.9 upgrade, if you can live with losing all content, settings and automation cues and having to reconfigure and reingest as necessary, it might be worth doing a clean install as distinct from an upgrade install. You'd need to open a support ticket with Dolby to get the 4.9.1.22 clean install ISO. After running it, you would have (in software terms, at least) a new DSS200, straight out of the factory; meaning that if any software or settings corruption had crept in, that should be guaranteed to nuke it.
| IP: Logged
|
|
|
|
|
|
|
|
|
|
All times are Central (GMT -6:00)
|
|
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.
|