Tango Polling period for the attribute

# 9 years ago
PVincent	Hi Emmanuel, No it doesn't work at all ! You will see in the screenshot attached that there is no zmq as event source, nor periodic event counters moving. What a pain! Best regards, Philippe Attachments: 859Kb

# 9 years ago
Andy	Philippe, strange but true. Is this a new installation? Were events working previously? When last did they work? It sounds like the dreaded hosts problem. Can you send us the exact setting of your TANGO_HOST, your exact client host name (with big and small letters) and the output of the DbGetCSDbServerList command. Andy

# 9 years ago
PVincent	Hi Andy, TANGO_HOST=localhost:20000 My hostname : WIN-O4RJ2OLSPDD DbGetCSDbServerList command output : —————————————————- Command: sys/database/2/DbGetCSDbServerList Duration: 79 msec Output argument(s) : array length: 1 [0] WIN-O4RJ2OLSPDD:20000 I changed TANGO_HOST environment variable to TANGO_HOST=WIN-O4RJ2OLSPDD:20000 : same result. Yes, it's a new installation and I never saw events working before, on this machine or elsewhere. Somme more information on my installation, that perhaps has any importance : Windows 7 x64 Python(x,y) (thus python x86) Tango x86 PyTango x86 MySQL Community Edition (x86) Best regards, Philippe Edited 9 years ago

# 9 years ago

PVincent

Hi Andy,

TANGO_HOST=localhost:20000
My hostname : WIN-O4RJ2OLSPDD

DbGetCSDbServerList command output :

—————————————————-
Command: sys/database/2/DbGetCSDbServerList
Duration: 79 msec
Output argument(s) :
array length: 1
[0] WIN-O4RJ2OLSPDD:20000

I changed TANGO_HOST environment variable to TANGO_HOST=WIN-O4RJ2OLSPDD:20000 : same result.

Yes, it's a new installation and I never saw events working before, on this machine or elsewhere.

Somme more information on my installation, that perhaps has any importance :

Windows 7 x64
Python(x,y) (thus python x86)
Tango x86
PyTango x86
MySQL Community Edition (x86)

Best regards,

Philippe

Edited 9 years ago

# 9 years ago
Andy	I remember there was an issue with Tango 8 and events on systems with hostnames with capital letters. Could you try changing the hostname to small letters. If this is not easy or possible could you try with Tango9? Andy

# 9 years ago
SGara_Nexeya	Hi PVincent, I saw on your screenshot that the host isn't connected to any network. Can you try to connect it to a network and try again.

# 9 years ago
PVincent	Hi Andy, Hi SGara_Nexeya, I tried changing hostname (sidplusdev01, TANGO-HOST=sidplusdev01:20000) without any result, even with a valid network connection. When I installed my machine I followed the tango website how-to tutorial. Is it up to date ? What is especially important during this process ? What could I have done wrong ? Best regards, Philippe Attachments: 956Kb

# 9 years ago
Reynald	Hi Philippe, Can you show us your current event configuration for the device sys/tg_test/1? In one of your previous posts, it seems you polled only the double_scalar attribute. Is this still the case? Is it the only attribute which is polled? If this is the case, what you are observing on the ATK diagnostics window is normal (at least the part we can see on the screenshot). On the screenshot, one can see only other attributes than double_scalar. ATK diagnostic is telling you that the attributes for which you want to receive events should be polled for the events to work properly. Can you please show the polling and event configuration for the device sys/tg_test/1, as well as the ATKDiagnostic window showing sys/tg_test/1/double_scalar? Please note that there was a typo in your last post. I guess it was only in the post. The environment variable is named TANGO_HOST, not TANGO-HOST. Hoping this helps a bit 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.

# 9 years ago

Reynald

Hi Philippe,

Can you show us your current event configuration for the device sys/tg_test/1?
In one of your previous posts, it seems you polled only the double_scalar attribute.
Is this still the case?
Is it the only attribute which is polled?
If this is the case, what you are observing on the ATK diagnostics window is normal (at least the part we can see on the screenshot).
On the screenshot, one can see only other attributes than double_scalar.
ATK diagnostic is telling you that the attributes for which you want to receive events should be polled for the events to work properly.

Can you please show the polling and event configuration for the device sys/tg_test/1, as well as the ATKDiagnostic window showing sys/tg_test/1/double_scalar?

Please note that there was a typo in your last post. I guess it was only in the post. smile

The environment variable is named TANGO_HOST, not TANGO-HOST.

Hoping this helps a bit

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.

# 9 years ago
PVincent	Hi Reynald, Hi all, Reynald, you will find enclosed the requested screenshots. You were right, there was a mistake in the TANGO_HOST, but fortunately just in my post. Somme more questions : What piece of software is in charge of zmq operations (exe, dll, service, …) ? I saw that with notifd you have to launch start-notifd, is there something similar for zmq ? Is there some option at install time I could have missed ? Thanks a lot for all the answers you will send. Best regards, Philippe Edited 9 years ago Attachments: 96Kb 96Kb

# 9 years ago

PVincent

Hi Reynald, Hi all,

Reynald, you will find enclosed the requested screenshots.
You were right, there was a mistake in the TANGO_HOST, but fortunately just in my post.

Somme more questions :

What piece of software is in charge of zmq operations (exe, dll, service, …) ?
I saw that with notifd you have to launch start-notifd, is there something similar for zmq ?
Is there some option at install time I could have missed ?

Thanks a lot for all the answers you will send.

Best regards,

Philippe

Edited 9 years ago

# 9 years ago
Reynald	Hi Philippe, Maybe you missed this step which is explained in the README file to receive events from JAVA applications. NOTES ON EVENT USAGE ——————– Tango 8 has a new event system based on ZMQ. It is used only between processes which are all using Tango 8. If one of your processes receiving/sending events uses Tango 7, start the old event system (using notifd process). To receive Tango 8 events in Java application, you need to have in jzmq.dll library in your PATH environment variable. This DLL is included in this distribution in %TANGO_ROOT%\win64\liv\vc10_dll So adding %TANGO_ROOT%\win64\liv\vc10_dll in your PATH should solve your problem, at least for the Java part… Maybe for the Taurus GUI part as well? Replace %TANGO_ROOT% with its absolute path to be sure it will work. 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.

# 9 years ago

Reynald

Hi Philippe,

Maybe you missed this step which is explained in the README file to receive events from JAVA applications.

NOTES ON EVENT USAGE
——————–

Tango 8 has a new event system based on ZMQ. It is used only between processes which are all using Tango 8.
If one of your processes receiving/sending events uses Tango 7, start the old event system (using notifd process).
To receive Tango 8 events in Java application, you need to have in jzmq.dll library in your PATH environment variable.
This DLL is included in this distribution in %TANGO_ROOT%\win64\liv\vc10_dll

So adding %TANGO_ROOT%\win64\liv\vc10_dll in your PATH should solve your problem, at least for the Java part…
Maybe for the Taurus GUI part as well?
Replace %TANGO_ROOT% with its absolute path to be sure it will work.

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.

# 9 years ago
PVincent	Hi All, Events are now working on my system ! yesssss ! Andy was right, the hostname must be in lowercase. That was the only reason why events were not working with PyTango/Taurus. I never succeeded with TangoTest and ATKPanel like suggested by Emmanuel, even with the path modifications suggested by Reynald. I still have some problems or misunderstandings : I have 2 DS written in Python (DS_Server & DS_Client) and a GUI written with Taurus. DS_Server send data_ready events associated with its attribute and DS_Client subscribe to these events handled through a callback. DS_Server poll a PLC every 500ms and send events if data have changed (10 attributes, non polled). DS_Client creates 2 instances of its class, handles events, update its own boolean attributes (50 attributes, polled at 1000ms). The GUI shows led indicators for each boolean attributes of DS_Client. I have a lot of API_PollThreadOutOfSync error on the GUI side. I tried to make some adjustment and I would like to understand (no answer found in all the document read) : I saw that PER_DEVICE was the default serialization model. Does this mean that each device is operated by a separate thread ? I saw also that you can add threads to polling thread pool through jive or astor. You can also set the size of polling threads pool in the server code. What is the correct use of all these features ? I would like to detect a communication loss to the DS_Server in the DS_Client, how can I do that ? (I've read some information about a KeepAliveThread ?!) Thanks a lot for your help. Best regards, Philippe

# 9 years ago

PVincent

Hi All,

Events are now working on my system ! yesssss !

Andy was right, the hostname must be in lowercase.
That was the only reason why events were not working with PyTango/Taurus.
I never succeeded with TangoTest and ATKPanel like suggested by Emmanuel, even with the path modifications suggested by Reynald.

I still have some problems or misunderstandings :

I have 2 DS written in Python (DS_Server & DS_Client) and a GUI written with Taurus.
DS_Server send data_ready events associated with its attribute and DS_Client subscribe to these events handled through a callback.
DS_Server poll a PLC every 500ms and send events if data have changed (10 attributes, non polled).
DS_Client creates 2 instances of its class, handles events, update its own boolean attributes (50 attributes, polled at 1000ms).
The GUI shows led indicators for each boolean attributes of DS_Client.

I have a lot of API_PollThreadOutOfSync error on the GUI side.

I tried to make some adjustment and I would like to understand (no answer found in all the document read) :

I saw that PER_DEVICE was the default serialization model. Does this mean that each device is operated by a separate thread ?
I saw also that you can add threads to polling thread pool through jive or astor. You can also set the size of polling threads pool in the server code. What is the correct use of all these features ?
I would like to detect a communication loss to the DS_Server in the DS_Client, how can I do that ? (I've read some information about a KeepAliveThread ?!)

Thanks a lot for your help.

Best regards,

Philippe