Announcement

Collapse
No announcement yet.

IMB time/date error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • IMB time/date error

    Hi all,

    I have a gdc sx3000 that is having issues, I don't have the money to replace it.
    I do though have some spare doremi/showvaults lying about that Dolby was kind enough to send me certificate extensions for.
    I tried swapping back to the doremi and they could play a dcp (unencrtypted) but the date and time are way off (they think they are in 2008)
    I changed the boot up bios system clock that did not help. (didn't think it would ...but i tried

    In the date/time settings there is no way to adjust date time, obviously because of dci compliance. There is a place there to put in the NTP server info, but when I put in a valid one on our network it says it's "invalid".

    What is the best way to get the time/date issue fixed ?
    Until I can get it fixed i'm stuck with the defective gdc imb which likes to randomly reboot itself during movies.

    Thanks !!!


    Armand

  • #2
    On the SX-3000 network settings, you have to set the IP address of the time server, usually your TMS system. GDC is also able to remote in and do it if you have that external access. You can call their tech support and ask them. But again, be sure your server is accessible by using standard remote software such as Team viewer..

    Comment


    • #3
      Armand - are you sure the Doremi certificate extension software has been installed properly? Are you sure the IMBs have not lost their time and date due to a drained battery?

      When you open diagnostic manager, can you post a screenshot of the Doremi software version and certificate expiration date?

      It would be interesting to create an encrypted Test-DCP with a timeframe that matches your Doremis actual time, and see if the Doremi can play this encrypted DCP.
      Doremi used to have a patch that allowed to correct the secure clock in a 'one-time' fashion. I don't know if Dolby still supplies it.

      Comment


      • #4
        This is an issue that they have a recovery process for, I'm trying to attach a pdf for it. You will need a DLM for the SM software back dated to 2008, not the one on the ftp site: ask Dolby for that.
        Attached Files

        Comment


        • #5
          Originally posted by Mark Gulbrandsen View Post
          On the SX-3000 network settings, you have to set the IP address of the time server, usually your TMS system. GDC is also able to remote in and do it if you have that external access. You can call their tech support and ask them. But again, be sure your server is accessible by using standard remote software such as Team viewer..
          Thank you Mark, but the gdc doesn't have the time issue, its what i'm using currently, i'm replacing it with a doremi I have sitting on a shelf because the gdc keeps rebooting itself randomly. Its the doremi that has the time issue.

          Comment


          • #6
            Originally posted by Carsten Kurz View Post
            Armand - are you sure the Doremi certificate extension software has been installed properly? Are you sure the IMBs have not lost their time and date due to a drained battery?

            When you open diagnostic manager, can you post a screenshot of the Doremi software version and certificate expiration date?

            It would be interesting to create an encrypted Test-DCP with a timeframe that matches your Doremis actual time, and see if the Doremi can play this encrypted DCP.
            Doremi used to have a patch that allowed to correct the secure clock in a 'one-time' fashion. I don't know if Dolby still supplies it.
            Dolby sent the cert extensions, they have not been applied yet. I figured i'd investigate the time issue first.... And it certainly could be a drained battery issue.....

            Comment


            • #7
              Yes, A clock battery could be very low or dead. I only installed a handful of Doremi servers, and those were before Dolby took them over. Since I retired, I started repairing DSLR cameras. Almost all of those have clock batteries in them. Some, Nikon, are soldered in. While everyone else uses socketed batteries. And on certain models, if the clock battery dies, the camera won't even turn on. So that could certainly be something I'd check first.

              Comment


              • #8
                You need to apply the critical updates from 2023. It sounds like you're not at software 2.8.52 (and the associated security manager and firmware versions). There was a bug in the older versions that sent those servers back in time on Jan 1 2024. Follow the Y2K24 instructions Dave posted and then you can run content and update the certificates.

                Comment


                • #9
                  If you boot the showvault into the bios, what time is shown there? There are really two clocks involved, the system bios is maintained by the motherboard battery.

                  Then there is the secure clock battery, which is the one that will brick things if it dies or is swapped without a suitable charge on the maintenance capacitors

                  You can try making any change in the bios, if the change is not preserved after a cold shutdown then you know the bios battery is shot. At least that part is an easy fix.

                  would be good to know when the secure clock battery was last replaced, or meter it in situ. That is probably worth addressing before you make the full effort to put this unit in service and attempt the time correction patch and time server sync, and any other pending patches/updates.

                  But End of November is your deadline on the cert extension patch. Don’t shelve the project for too long!

                  Comment


                  • #10
                    Ohh and on the NTP server subject. Was it a stratum 1 time server? Not just any time-server is accepted as a valid sync source... such as your local office NTP.

                    Stratum 1 Time Servers explained:
                    https://timetoolsltd.com/ntp/what-is...1-time-server/

                    Here is a perhaps incomplete list of stratum 1 public time servers organized by country:
                    https://www.advtimesync.com/docs/manual/stratum1.html

                    If you prefer one hosted internally, so your servers don't need internet access, there are ways to build one with a raspberry pi and GPS hat:
                    https://forum.netgate.com/topic/1437...g-raspberry-pi
                    Last edited by Ryan Gallagher; 03-13-2025, 10:58 AM.

                    Comment


                    • #11
                      Originally posted by Armand Daiguillon View Post

                      Dolby sent the cert extensions, they have not been applied yet. I figured i'd investigate the time issue first.... And it certainly could be a drained battery issue.....
                      Armand - again, start diagnostic manager on the ShowVault and post a screen shot here. Before we know what software and firmware is active, no one can help you with this issue.

                      Did you get full instructions on how to install the cert extension software? It is a multistage process, and you need to follow it properly.

                      Comment


                      • #12
                        I spent the day on this - turns out the imb did have some issues itself, I swapped to a different one and ran into the 2008 date issue, but Dolby sent me the patch to fix that along with a software update and the cert extension. Once I swapped to another spare imb all the patches worked and we're good to go now.

                        Thanks everybody !

                        Comment

                        Working...
                        X