HDB++ HdbEventSubscriber AttributeStart

# 8 years ago
Sandor	Hi, I've tried to add and start an attribute from the test DS using Jive and receive the following error message: "At least, one signal is faulty Alarm : Value too high for AttributeNokNumber" The attribute is: sys/tg_test/1/short_scalar_ro,1 I found the following syntax among a forum topic entries. The AttributeAdd worked and added the attribute to the AttributeList. With AttributeStatus I can see the following: "Event status : Attribute short_scalar_ro,1 is not supported by device sys/tg_test/1" Although the test DS is in RUNNING state, the short_scalar_ro is visible and is changing frequently in the AtkPanel. What can be the problem? Thank you, Sandor ELI-ALPS HU

# 8 years ago

Hi,

I've tried to add and start an attribute from the test DS using Jive and receive the following error message:
"At least, one signal is faulty
Alarm : Value too high for AttributeNokNumber"

The attribute is: sys/tg_test/1/short_scalar_ro,1

I found the following syntax among a forum topic entries.

The AttributeAdd worked and added the attribute to the AttributeList.

With AttributeStatus I can see the following:
"Event status : Attribute short_scalar_ro,1 is not supported by device sys/tg_test/1"

Although the test DS is in RUNNING state, the short_scalar_ro is visible and is changing frequently in the AtkPanel.

What can be the problem?

Thank you,
Sandor
ELI-ALPS HU

# 8 years ago
Andy	Hi Sandor, I am not sure why short_scalar is not working. Have you tried to configure a long_scalar? Andy

# 8 years ago
Sandor	Hi Andy, thanks for you response. I've tried with sys/tg_test/1/long_scalar,1 and the result is the same. The AttributeAdd is OK, but the AttributeStart fails the same way: "At least, one signal is faulty Alarm : Value too high for AttributeNokNumber" I've tried prefixing with the machine name and with the following, but the result is the same. tango://771eb860bcbc:10000/sys/tg_test/1/long_scalar,1 Additonally I can see the following in the ES console: getaddrinfo: Name or service not known event_Attr: ERROR unknown/sys/tg_test/1/short_scalar_ro,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/sys/tg_test/1/double_scalar,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/sys/tg_test/1/short_scalar_ro,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/sys/tg_test/1/short_scalar_ro,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/sys/tg_test/1/long_scalar,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/sys/tg_test/1/long_scalar,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/771eb860bcbc/sys/tg_test/1/long_scalar,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/sys/tg_test/1/long_scalar,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/771eb860bcbc/sys/tg_test/1/long_scalar,1 NOT FOUND getaddrinfo: Name or service not known event_Attr: ERROR unknown/771eb860bcbc/sys/tg_test/1/long_scalar,1 NOT FOUND add_domain: found domain -> 771eb860bcbc:10000 event_Attr: ERROR 771eb860bcbc:10000/sys/tg_test/1/long_scalar,1 NOT FOUND Sandor Edited 8 years ago

# 8 years ago

Sandor

Hi Andy,

thanks for you response.

I've tried with sys/tg_test/1/long_scalar,1 and the result is the same.
The AttributeAdd is OK, but the AttributeStart fails the same way:
"At least, one signal is faulty
Alarm : Value too high for AttributeNokNumber"

I've tried prefixing with the machine name and with the following, but the result is the same.

tango://771eb860bcbc:10000/sys/tg_test/1/long_scalar,1

Additonally I can see the following in the ES console:
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/sys/tg_test/1/short_scalar_ro,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/sys/tg_test/1/double_scalar,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/sys/tg_test/1/short_scalar_ro,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/sys/tg_test/1/short_scalar_ro,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/sys/tg_test/1/long_scalar,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/sys/tg_test/1/long_scalar,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/771eb860bcbc/sys/tg_test/1/long_scalar,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/sys/tg_test/1/long_scalar,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/771eb860bcbc/sys/tg_test/1/long_scalar,1 NOT FOUND
getaddrinfo: Name or service not known
event_Attr: ERROR unknown/771eb860bcbc/sys/tg_test/1/long_scalar,1 NOT FOUND
add_domain: found domain -> 771eb860bcbc:10000
event_Attr: ERROR 771eb860bcbc:10000/sys/tg_test/1/long_scalar,1 NOT FOUND

Sandor

Edited 8 years ago

# 8 years ago
Andy	Very strange. Have you switched polling on for these attributes? Can you try this on the virtual machine and see if you can reproduce it there. You can find the VM here http://ftp.esrf.fr/pub/cs/tango/tango9-vm.zip and instructions how to use it on this page http://sourceforge.net/projects/tango-cs/files/Tango9_VM.pdf/download Andy

# 8 years ago
Sandor	The polling was not turned on. I've tried it again with turned on polling the result is the same. I can try it with the VM next week. BTW, we try to use HDB++ with Tango 8. Can it be the reason it is 8 and not 9? Sandor

# 8 years ago
Andy	Hi Sandor, just to say I did the same as you - switched on archiving for the attribute short_scalar_ro on the device sys/tg_test/1 on the Tango92 VM and it worked without any problems. The polling was not turned on by default so I specified a polling period when configuring the archiving of the attribute. This will then switch on the polling. I attach a screenshot so you can see what I did. I hope that helps Andy Attachments:

# 8 years ago

Andy

Hi Sandor,

just to say I did the same as you - switched on archiving for the attribute short_scalar_ro on the device sys/tg_test/1 on the Tango92 VM and it worked without any problems. The polling was not turned on by default so I specified a polling period when configuring the archiving of the attribute. This will then switch on the polling. I attach a screenshot so you can see what I did.

I hope that helps

Andy

# 8 years ago
Sandor	Hi Andy, thanks for the hints. With the Tango 9 VM I could achieve the same as you with short_scalar_ro using the HDB++ Configurator. But in case I try to add and start an attribute via the eventsubscriber DS then I get the same error as before, see the attached screenshot and the ulong_scalar. What is strange if I remove the short_scalar_ro with the HDB++ Configurator and add/start it again with the eventsubscriber DS manually then it works perfectly. But with Tango 8 the java_configurator doesn't compile the only way I see to add the attributes is via the AttributeAdd command of the EventSubscriber DS. Could you try to add/start an attribute with the eventsubscriber DS? Thank you, Sandor Attachments:

# 8 years ago

Sandor

Hi Andy,

thanks for the hints.

With the Tango 9 VM I could achieve the same as you with short_scalar_ro using the HDB++ Configurator.
But in case I try to add and start an attribute via the eventsubscriber DS then I get the same error as before, see the attached screenshot and the ulong_scalar.

What is strange if I remove the short_scalar_ro with the HDB++ Configurator and add/start it again with the eventsubscriber DS manually then it works perfectly.

But with Tango 8 the java_configurator doesn't compile the only way I see to add the attributes is via the AttributeAdd command of the EventSubscriber DS.

Could you try to add/start an attribute with the eventsubscriber DS?

Thank you,
Sandor

# 8 years ago
lorenzo	Sandor Hi Andy, thanks for the hints. With the Tango 9 VM I could achieve the same as you with short_scalar_ro using the HDB++ Configurator. But in case I try to add and start an attribute via the eventsubscriber DS then I get the same error as before, see the attached screenshot and the ulong_scalar. What is strange if I remove the short_scalar_ro with the HDB++ Configurator and add/start it again with the eventsubscriber DS manually then it works perfectly. But with Tango 8 the java_configurator doesn't compile the only way I see to add the attributes is via the AttributeAdd command of the EventSubscriber DS. Could you try to add/start an attribute with the eventsubscriber DS? Thank you, Sandor Hi Sandor, the problem is not clear to me; could you please post the AttributeStatus command output for the failing attribute? Please note that if you go for the AttributeAdd command of the EventSubscriber you have to setup the archive event parameters for the desired attribute by hand before executing AttributeStart. Cheers, Lorenzo

# 8 years ago

lorenzo

Sandor
Hi Andy,

thanks for the hints.

With the Tango 9 VM I could achieve the same as you with short_scalar_ro using the HDB++ Configurator.
But in case I try to add and start an attribute via the eventsubscriber DS then I get the same error as before, see the attached screenshot and the ulong_scalar.

What is strange if I remove the short_scalar_ro with the HDB++ Configurator and add/start it again with the eventsubscriber DS manually then it works perfectly.

But with Tango 8 the java_configurator doesn't compile the only way I see to add the attributes is via the AttributeAdd command of the EventSubscriber DS.

Could you try to add/start an attribute with the eventsubscriber DS?

Thank you,
Sandor

Hi Sandor,
the problem is not clear to me; could you please post the AttributeStatus command output for the failing attribute?
Please note that if you go for the AttributeAdd command of the EventSubscriber you have to setup the archive event
parameters for the desired attribute by hand before executing AttributeStart.

Cheers,
Lorenzo

# 8 years ago
Sandor	Hi Lorenzo, the status is the following for ulong_scalar is attached. Could you please give a hint or description how can I setup the archive event parameters for the desired attribute by hand? Thank you, Sandor Attachments:

# 8 years ago
lorenzo	Sandor Hi Lorenzo, the status is the following for ulong_scalar is attached. Could you please give a hint or description how can I setup the archive event parameters for the desired attribute by hand? Thank you, Sandor the attribute is not polled. For each attribute, in order to send events from the source TANGO device server, you need to setup: - the archive event thresholds (absolute and/or relative) and/or the archive event period - the polling, specifying the polling period Cheers, Lorenzo

# 8 years ago

lorenzo

Sandor
Hi Lorenzo,

the status is the following for ulong_scalar is attached.

Could you please give a hint or description how can I setup the archive event parameters for the desired attribute by hand?

Thank you,
Sandor

the attribute is not polled. For each attribute, in order to send events from the source TANGO device
server, you need to setup:
- the archive event thresholds (absolute and/or relative) and/or the archive event period
- the polling, specifying the polling period

Cheers,
Lorenzo