Hi,
I am trying to configure a new alarm in Elettra Alarm server by passing the below string as input argument:
"alarmtest-srv/01/01/Alarm_test (alarmtest-srv/01/01/Alarm_test != false) 0 log -1 gr_tmc \"PS_Alarm_test\";"
But I am getting an error (Refer attachment for details).
Can somebody please suggest how to resolve it?
-Lochan
Update: I tried to configure alarm on different device server which does not contain special character in its name. This time the error is different. Now it displays that it cannot subscribe to the attribute. Please check the attachment for details.
Any help will be appreciated.
Indeed, the dash ‘-’ better to be avoided in device names. Concerning the second error, it seems that the AlarmHandler device failed to subscribe to the change event on the
Testclass/01/01/attr1 device…
You may want to check that polling and change event thresold(s) are configured for the attr1 Attribute (otherwise TANGO will not generate events, and trying to subscribe is going to fail…).
Lorenzo
A dash in a device name is perfectly valid in the Tango world.
We have many devices having a dash in their name in our control system.
But we are not using the Elettra alarm system so this case is maybe not yet well handled.
For the subscription error, you should probably check testclass/01/01/attr1 event configuration (polling if it is not pushing events by code and change event attribute properties (rel_change, abs_change)).
Is testclass/01/01 up and running?
Hi, in some old version of the Elettra Elarm Server dash in the device name was not supported, but at some point the bug was fixed.
The version available in http://www.tango-controls.org/developers/front-end/#alarm-system should work with that.
[quote=“lorenzo”]Indeed, the dash ‘-’ better to be avoided in device names. Concerning the second error, it seems that the AlarmHandler device failed to subscribe to the change event on the
Testclass/01/01/attr1 device…
You may want to check that polling and change event thresold(s) are configured for the attr1 Attribute (otherwise TANGO will not generate events, and trying to subscribe is going to fail…).
Lorenzo
[/quote]
[quote=“Reynald”]A dash in a device name is perfectly valid in the Tango world.
We have many devices having a dash in their name in our control system.
But we are not using the Elettra alarm system so this case is maybe not yet well handled.
For the subscription error, you should probably check testclass/01/01/attr1 event configuration (polling if it is not pushing events by code and change event attribute properties (rel_change, abs_change)).
Is testclass/01/01 up and running?[/quote]
Yes the testclass is running. I could successfully configure the alarm without dash. I had not configured polling and change events. Thanks for your guidance.
[quote=“gscalamera”]Hi, in some old version of the Elettra Elarm Server dash in the device name was not supported, but at some point the bug was fixed.
The version available in http://www.tango-controls.org/developers/front-end/#alarm-system should work with that.
[/quote]
As per the offline mail trail yesterday, I built the latest code from git repo. Now I am facing error while loading alarm string in the newer version. Its failing while parsing the alarm string. Please check the attachment for details. Is there any change in alarm string format in newer version? The string I am passing is:
"testdevice/01/01/myalarm2 (testdevice/01/01/attr2 = false) 0 log -1 gr_tmc \"PS_Alarm_test_MyAlarm2\""
[quote=“Lochan”]Yes the testclass is running. I could successfully configure the alarm without dash. I had not configured polling and change events. Thanks for your guidance.
[/quote]
That’s a bit strange. I’d expect the AlarmHandler will fail subscribing to the event then. Unless your testclass device is pushing change event in the code.
Seem to remember some significant changes in the alarm string format because of the latest developments. Graziano, can you provide the latest syntax…?
Hi Graziano, can you please provide the syntax?