Hello DM community,
On the Cube, I have multiple Appear TV devices that Dataminer is polling a lot of data from. All my devices' SRT Input Status tables CC Errors flip-flop between N/A and a number exactly every 60 seconds making it very hard to monitor the system health through a dashboard I've built. Because every time I refresh, another devices jumps to the top of the table (CC Errors descending table).
I want to know if it's the normal behavior of the system or it's a glitch that needs fixing.
Best regards,
Satrap
This is very insightful, Alberto. Thanks a lot for sharing it with me. I'll definitely take your advice into consideration as we're still struggling with pinpointing the root cause.
Glad I could be of help, Satrap – I'm a TV lover at heart 😉
N/A looks like a parameter not available at the device side – hence wondering about any micro-sync-loss = or basically, when the TS is not locked yet (bitrate zero) perhaps the device has an N/A
(I would check the behaviour of this Appear TV sw version after locking a stable transport stream and see if the CC gets initialized to 0 – usually the driver in DM follows what the GUI too is presenting)
Hi Satrap Shojaie,
This is definitely not intended behavior and should be addressed. Could you first verify whether you are running the latest available version of the connector? If not, please try again with the latest version to see if the issue persists.
If the behavior persists or you are already on the latest version, would it be possible for you to contact your Skyline technical representative to create a ticket, or report this issue directly to Tech Support? It would be helpful to include the protocol and version when doing so — this way, we can address the behavior with the right priorities and provide a fix in a timely manner.
Kind regards,
This is strange – is there any TS Sync loss on the device?
Otherwise, CC errors would be "0" or higher – on the other hand, you might try to monitor that with a "rate" alarm templated, so that you get an alarm whenever the counter increases – normally, once the counter is incremented this stays constant without affecting the Transport Stream until a new burst of errors happens.
Worth noting: in your screenshot, technically, you are not "monitoring" at all the CC errors column -you're just reading the value via the element (no alarm template / no trend template associated)
In similar cases, I recommend using other parameters as KPIs (such as RTP error rate in conjunction with the TS bitrate)
HTH