HDB++ viewer - TANGO Controls

# 6 years ago
Remotie	HELLO, I have a problem when i add the attribute in hdbviewer nothing is displayed (see the attachments) Attachments:

# 6 years ago
Pascal	Hi Are you sure you have data stored during the specified time ? Edited 6 years ago

# 6 years ago
Remotie	Hi pascal yes i'm sure and i have the Attribute polling period every 3000 milliseconds Attachments:

# 6 years ago
lorenzo	Hi Remotie, from your screenshot it appears you have no archive event threshold, nor archive event period specified. With this configuration no archive event will be sent, unless pushed in the code (like the check button suggests). Have you coded pushing events in your device?

# 6 years ago
Remotie	Hi lorenzo No I don't have coded pushing events in my device What's the solution? Thanks for your help

# 6 years ago
lorenzo	Th easiest thing is to configure the archive event thresholds,. You may want to specify absoulte threshold, that is the minimum chnage in the attribute value that will trigger sending an event, and the period if you want also a periodic archiving (>= polling period). Edited 6 years ago

# 6 years ago
Reynald	Hi, Your problem is due to the fact your Tango attribute mtemp/temperature/10/Temperature is probably not correctly configured to send Tango events. You can see that easily using the HDB++ diagnostics GUI which can be started from the HDBConfigurator GUI (View menu -> HDB++ Diagnostics, or CTRL + D in HDBConfigurator GUI). I guess the GUI will report that your Temperature attribute is not well configured, so no archive events are sent to the HDB++ archiver, so no data was stored in the HDB++ database. Unless your TANGO device is explicitly pushing events by code and the Temperature attribute is configured in a way such as the Tango library does not check for criteria (see POGO screenshot below), you need to configure an absolute change or relative change threshold and/or a period for your attribute archive event configuration. You can refer to this page to get more details about the absolute change, relative change and period archive attribute properties: http://tango-controls.readthedocs.io/en/latest/tools-and-extensions/archiving/HDB++.html?highlight=absolute#rationale Hoping this helps, Reynald Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new. Attachments: 23Kb

# 6 years ago

Reynald

Hi,

Your problem is due to the fact your Tango attribute mtemp/temperature/10/Temperature is probably not correctly configured to send Tango events.

You can see that easily using the HDB++ diagnostics GUI which can be started from the HDBConfigurator GUI (View menu -> HDB++ Diagnostics, or CTRL + D in HDBConfigurator GUI). I guess the GUI will report that your Temperature attribute is not well configured, so no archive events are sent to the HDB++ archiver, so no data was stored in the HDB++ database.

Unless your TANGO device is explicitly pushing events by code and the Temperature attribute is configured in a way such as the Tango library does not check for criteria (see POGO screenshot below), you need to configure an absolute change or relative change threshold and/or a period for your attribute archive event configuration.

You can refer to this page to get more details about the absolute change, relative change and period archive attribute properties:
http://tango-controls.readthedocs.io/en/latest/tools-and-extensions/archiving/HDB++.html?highlight=absolute#rationale

Hoping this helps,
Reynald

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 6 years ago
Remotie	Hi reynald, I configured the events Attribute in pogo but the same problem Attachments:

# 6 years ago
Reynald	It will be difficult to explain in details how the TANGO events are working in this post. So I will try to keep it simple for your use case since you seem to reproduce what you see on the screenshots I posted without understanding the concepts behind. For your use case, what you need is simply to configure an archive absolute change threshold and/or relative change threshold and/or archive period configuration for your attribute Temperature. Your can do that on a live system while your TANGO device mtemp/temperature/10 is running. You can use jive to configure that: `jive &` Then, click on the "Device" tab. Browse the Tango devices until you find mtemp/temperature/10 in the tree. Expand the node and click on Event in the tree. Then, on the right part, select the "Archive" tab, and put for instance "3000" (ms) in the Period field related to the Temperature attribute in order to get an archive event sent every 3 seconds. If you don't want to archive all the time the values of Temperature attribute when this value does not change, you can put "1" in the absolute change archive event field for your Temperature attribute. In this case, archive events will be sent only when the Temperature value changed by more than one degree since the last archive event was sent. Please note that if you precise an absolute threshold and a period, you will get an archive event generated at each period, even if the value didn't change. Hoping this helps a bit, but you still have a lot to learn about TANGO events and its advanced concepts. Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new. Attachments:

# 6 years ago

Reynald

It will be difficult to explain in details how the TANGO events are working in this post.
So I will try to keep it simple for your use case since you seem to reproduce what you see on the screenshots I posted without understanding the concepts behind.

For your use case, what you need is simply to configure an archive absolute change threshold and/or relative change threshold and/or archive period configuration for your attribute Temperature.

Your can do that on a live system while your TANGO device mtemp/temperature/10 is running.
You can use jive to configure that:

jive &

Then, click on the "Device" tab.
Browse the Tango devices until you find mtemp/temperature/10 in the tree.
Expand the node and click on Event in the tree.

Then, on the right part, select the "Archive" tab, and put for instance "3000" (ms) in the Period field related to the Temperature attribute in order to get an archive event sent every 3 seconds.

If you don't want to archive all the time the values of Temperature attribute when this value does not change, you can put "1" in the absolute change archive event field for your Temperature attribute. In this case, archive events will be sent only when the Temperature value changed by more than one degree since the last archive event was sent.
Please note that if you precise an absolute threshold and a period, you will get an archive event generated at each period, even if the value didn't change.

Hoping this helps a bit, but you still have a lot to learn about TANGO events and its advanced concepts.

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 6 years ago
Lize	Hi Remotie May be there is a mis-communication here. You have configured Attribute polling period (3000ms) and have set Events pushed by Code, but you have noted that the code has not implemented pushing archive events, and thus no archive events will be present. The responders were not referring to the Attribute polling period, but rather to the Archive Event Properties - event period (milliseconds) [and/or absolute and relative change] that has to be configured for the TANGO framework to issue archive events. Thus set Archive Event - event period (milliseconds) to 3000ms to get a periodic archive sample each 3s. Lize

# 6 years ago

Lize

Hi Remotie

May be there is a mis-communication here. You have configured Attribute polling period (3000ms) and have set Events pushed by Code, but you have noted that the code has not implemented pushing archive events, and thus no archive events will be present.
The responders were not referring to the Attribute polling period, but rather to the Archive Event Properties - event period (milliseconds) [and/or absolute and relative change] that has to be configured for the TANGO framework to issue archive events.
Thus set Archive Event - event period (milliseconds) to 3000ms to get a periodic archive sample each 3s.
Lize