Spectrum Analyzers: Alternative ways of detecting if an element card is open in DataMiner Cube

Solved624 viewsspectrum analyzer
2
1 Comment

Hi Dojo,

Is it possible for a protocol to detect if an element card is open in DataMiner Cube?

To give some context, I am creating a spectrum analyzer protocol that communicates like a smart-serial device. I would like to disable the polling/retrieval/processing of data if the element card is not open such that it doesn't run in the background, such that it can support multiple sessions.

Is there a reserved parameter or a method to ensure this?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 16th May 2024

2 Answers

0
2.09K 0 Comments

Hi Chian Hao,
The Spectrum component in DataMiner will already act as a layer to manage what you are looking for.

Please have a look here in the docs regarding the behavior of SLSpectrum: Implementation routine | DataMiner Docs

"A client" could represent different things in the concept of spectrum components:

  • either your element-card/view via DM Cube (Spectrum UI)
  • or a trace that gets acquired automatically via spectrum monitors/scripts
  • or an inline Visio shape that displays certain trace data (again via linked monitors)

your protocol need to indeed interface with that Spectrum analyzer only when necessary request have to be made.  But this is what SLSpectrum already handles.

That's one of the greatest advantages of Spectrum management in DataMiner that this is multi-Client by default.

So for every "need" where a client needs new trace updates, the parameter sets will come through in round-robin fashion.  (parameter triggers 64118 & 64116)

Hope this clarifies things and gets you forward!

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 16th May 2024
0
8.86K 2 Comments

Hi Chian,

Every element has a general parameter "[Clients connected]" (ID 65029) which has value Yes=1 when a client is connected, or value No=0 when no clients are connected. Maybe you could use this in your connector.

https://docs.dataminer.services/develop/devguide/Connector/ReservedIDsElementControlProtocol.html

Tom Waterbley [SLC] [DevOps Catalyst] Posted new comment 29th April 2024
Thijs Vanovenacker [SLC] [DevOps Advocate] commented

I think this is less relevant for Spectrum integrations. our Visual overview supports features to show inline trace graphs , this will accept certain “Spectrum monitors” as arguments. In return the spectrum element will need to make sure it can process and request new trace data based on this. So if we block communication based on this 65029 parameter, I don’t think the end goal will be met…
Tom Waterbley [SLC] [DevOps Catalyst] commented

Hi Thijs. I thought the problem was that DataMiner was interfering with users that are working directly with the spectrum analyzer, or another external application. That was not completely clear from the question. But if that is not the case my answer is indeed not really relevant.