Visual Productions forum

Author Topic: QuadCore deaths  (Read 626 times)

October 26, 2021, 11:07:41 AM
Read 626 times

ljos

  • Member
  • *
  • Posts: 69
Getting a bit tired of QuadCores and CueCores losing clock/time and then not working.

Several installations that can not be online, so when the cores die, I have to send a guy to update firmware and sync time with PC.

Am I doing something wrong?

October 26, 2021, 11:34:57 AM
Reply #1

Bootsy van der Zande

  • Administrator
  • Member
  • *****
  • Posts: 478
Hi,

I am very sorry to hear that. When you say "die", I think you mean the power of the CueCore2 or QuadCore is out, right? How long does this usually last before it is powered on again?

Which firmware are you running on the devices? There was a range of firmwares that had some issues restoring the time when the device was powered on again. It should be fixed now, I will have to double check from which firmware version it is working properly again.

Greetings,
Bootsy

November 01, 2021, 11:34:58 AM
Reply #2

ljos

  • Member
  • *
  • Posts: 69
Hi, thanks for getting back to me.
A bit unclear in the wording there. When I say "die", I should probably change that to "go into coma".
All units on latest firmware as of installation date or service date.

Most units lose clock time, then just stop working. No function. Need physical reboot.
Last unit this happened with even was on an astro timer for regular reboot, but still lost clock and stopped doing any work.

Project file for one unit attached.
« Last Edit: November 01, 2021, 01:01:56 PM by ljos »

November 03, 2021, 08:31:20 AM
Reply #3

Bootsy van der Zande

  • Administrator
  • Member
  • *****
  • Posts: 478
Hi,

There was an issue with time introduced when working on NTP precision around version 1.33. I believe it was solved in the 1.37 release for QuadCore.

Your backup does not include the settings of the QuadCore, so I can't see what you have for NTP server IP.  It should be displayed in white in the UI. If it is displayed in orange, the QuadCore is unable to connect to the NTP server.

Another note, the NTP server actually only triggers automatically on boot of the device. I usually recommend using a timer in ShowControl to periodically sync the time with the NTP server. To do this, first add a system startup action which starts a timer. Set it to 1 hour or something like that  (If you set it too fast, the NTP server will probably reject) Next, add an action to the timer source, set the Triggerflank to stop, and add the task "TimeServer - Refresh". Also add the task "Timer - Restart" to restart your timer.

Another way would be to add the timeserver refresh to the scheduler.

Let me know if I can help,

Greetings,
Bootsy

November 10, 2021, 11:08:52 AM
Reply #4

ljos

  • Member
  • *
  • Posts: 69
Hi, thanks for the input!

Unfortunately, most of our units are offline and can´t connect to external NTP servers. Safety regulations.

How can we then solve this? As of now, a janitor or other random person has to hook up a PC and set date/time via vManager every few weeks. I´d like to avoid that.


 

SMF spam blocked by CleanTalk