{"action":"created","issue":{"url":"https://api.github.com/repos/machinekit/machinekit/issues/968","repository_url":"https://api.github.com/repos/machinekit/machinekit","labels_url":"https://api.github.com/repos/machinekit/machinekit/issues/968/labels{/name}","comments_url":"https://api.github.com/repos/machinekit/machinekit/issues/968/comments","events_url":"https://api.github.com/repos/machinekit/machinekit/issues/968/events","html_url":"https://github.com/machinekit/machinekit/issues/968","id":160053058,"number":968,"title":"client call MT_HALRCOMMAND_DESCRIBE to haltalk breaks haltalk operation","user":{"login":"zhivko","id":3688966,"avatar_url":"https://avatars.githubusercontent.com/u/3688966?v=3","gravatar_id":"","url":"https://api.github.com/users/zhivko","html_url":"https://github.com/zhivko","followers_url":"https://api.github.com/users/zhivko/followers","following_url":"https://api.github.com/users/zhivko/following{/other_user}","gists_url":"https://api.github.com/users/zhivko/gists{/gist_id}","starred_url":"https://api.github.com/users/zhivko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zhivko/subscriptions","organizations_url":"https://api.github.com/users/zhivko/orgs","repos_url":"https://api.github.com/users/zhivko/repos","events_url":"https://api.github.com/users/zhivko/events{/privacy}","received_events_url":"https://api.github.com/users/zhivko/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":31,"created_at":"2016-06-13T21:49:51Z","updated_at":"2016-06-17T20:17:57Z","closed_at":"2016-06-15T22:34:31Z","body":"I expect I could use ZMQ and MT_HALRCOMMAND_DESCRIBE to retrieve hal status (pin values, and other hal related values), but weirdly it seems that MT_HALRCOMMAND_DESCRIBE breaks haltalk operation.\r\n\r\nIt breaks it in a way that also MT_PING from client doesn't ẁork anymore ( MT_PING_ACKNOWLEDGE is not received back anymore).\r\n\r\nMy scenario is as follows:\r\n\r\n1. I have ZMQ client with dealer socket.\r\n2. I issue MT_PING request to haltalk and I get MT_PING_ACKNOWLEDGE back to client.\r\n3. In same code I only change line:\r\nbuilder.setType(ContainerType.MT_PING);\r\nto\r\nbuilder.setType(ContainerType.MT_HALRCOMMAND_DESCRIBE);\r\n4. Start client again and make MT_HALRCOMMAND_DESCRIBE call to haltalk - from that point on - I don't get any reply back.\r\n5. In same code I change type of container again:\r\nbuilder.setType(ContainerType.MT_HALRCOMMAND_DESCRIBE);\r\nto\r\nbuilder.setType(ContainerType.MT_PING);\r\n4. I dont get MT_PING_ACKNOWLEDGE back anymore. I can also see that enumerating services on BBB where haltalk is running doesn't show this 3 services anymore (in start of test they were up and running):\r\nHAL Rcommand service on beaglebone tcp://beaglebone.local.:49155/\r\nHAL Rcomp service on beaglebone tcp://beaglebone.local.:49154/\r\nHAL Group service on beaglebone tcp://beaglebone.local.:49153/\r\n\r\nWhat could be the reason?\r\n\r\nmy dpkg show this:\r\n```\r\nmachinekit@beaglebone:~$ dpkg --list | grep machinekit\r\nii  machinekit                              0.1.1450479237-1mk.travis.master.git0b8ec05d~1wheezy armhf        PC based motion controller for real-time Linux\r\nii  machinekit-build-deps                   1.0                                                  all          build-dependencies for machinekit\r\nii  machinekit-xenomai                      0.1.1450479237-1mk.travis.master.git0b8ec05d~1wheezy armhf        PC based motion controller for real-time Linux\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/machinekit/machinekit/issues/comments/226871283","html_url":"https://github.com/machinekit/machinekit/issues/968#issuecomment-226871283","issue_url":"https://api.github.com/repos/machinekit/machinekit/issues/968","id":226871283,"user":{"login":"strahlex","id":1467368,"avatar_url":"https://avatars.githubusercontent.com/u/1467368?v=3","gravatar_id":"","url":"https://api.github.com/users/strahlex","html_url":"https://github.com/strahlex","followers_url":"https://api.github.com/users/strahlex/followers","following_url":"https://api.github.com/users/strahlex/following{/other_user}","gists_url":"https://api.github.com/users/strahlex/gists{/gist_id}","starred_url":"https://api.github.com/users/strahlex/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/strahlex/subscriptions","organizations_url":"https://api.github.com/users/strahlex/orgs","repos_url":"https://api.github.com/users/strahlex/repos","events_url":"https://api.github.com/users/strahlex/events{/privacy}","received_events_url":"https://api.github.com/users/strahlex/received_events","type":"User","site_admin":false},"created_at":"2016-06-17T20:17:57Z","updated_at":"2016-06-17T20:17:57Z","body":"Here is another test to trigger the problem: https://github.com/strahlex/machinetalk-test"}}
{"actor":{"display_login":"strahlex"}}