sample_bt_agent and HDP profile

[Kawai Davis]

When I run the sample_bt_agent with the MAC of my manager on a separate machine, this is what I am getting:

IEEE 11073 sample agent

DEBUG   <agent_init in agent.c:133> Agent Initialization

DEBUG   <agent_start in agent.c:369> Agent starting...

DEBUG   <init in plugin_bluez.c:1287> Starting BlueZ link...

DEBUG   <connect_adapter in plugin_bluez.c:876> connecting adapter: /org/bluez/13551/hci0

DEBUG   <connect_adapter in plugin_bluez.c:916> Getting known devices list

DEBUG   <connect_device_signals in plugin_bluez.c:782> device to be connected: /org/bluez/13551/hci0/dev_00_1B_DC_06_AA_13

DEBUG   <get_device_addr in plugin_bluez.c:303>         Device address is 00:1B:DC:06:AA:13

DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_12

*** Device rediscovered

Main loop started

DEBUG   <plugin_bluez_connect_cb in plugin_bluez.c:1535> connection initiation error: Method "CreateChannel" with signature "os" on interface "org.bluez.HealthDevice" doesn't exist

This is the order I am doing this:

1. healthd
2. python test_healthd.py
3. on other machine: sample_bt_agent <server MAC>
4. pair the 2 devices

No matter how many times I retry, I consistently get this error. Any help?

[Lucas Batalha]

Hello!

I think you should pair the devices before all. Am I wrong?

[Kawai Davis]

According to other posts I should have the manager running before I do the pairing. Either way, I have tried both ways.

[Kawai Davis]

More info just in case - Ubuntu 14.04.2 LTS, Dbus 1.6.18, BlueZ 4.101 (all standard packages from Ubuntu). I have tried recompiling BlueZ with the --enable-health command and that didn't make any difference.

[Lucas Batalha]

I don't know how to help, but I've been studying and if I get an answer I'll try to help you.
By the way, if you advance somehow, post here please.

[Ivan Tumanov]

From your words, its strange to launch sample_bt_agent before pairing

вт, 28 апр. 2015 г. в 6:15, Lucas Batalha <lucas...@gmail.com>:

I don't know how to help, but I've been studying and if I get an answer I'll try to help you.
By the way, if you advance somehow, post here please.

--
You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ivan Tumanov]

swap 3 and 4 steps

вт, 28 апр. 2015 г. в 13:10, Ivan Tumanov <i.i.t...@gmail.com>:

[Kawai Davis]

I am still running into the same issue but swapping the steps at least got healthd to show an attempt at connecting. Here is the log from healthd:

DEBUG   <manager_init in manager.c:162> Manager Initialization

DEBUG   <ext_configurations_load_configurations in extconfigurations.c:278> Zero-sized ext config buffer

DEBUG   <manager_start in manager.c:465> Manager starting...

DEBUG   <init in plugin_bluez.c:1287> Starting BlueZ link...

DEBUG   <connect_adapter in plugin_bluez.c:876> connecting adapter: /org/bluez/10630/hci0

DEBUG   <connect_adapter in plugin_bluez.c:916> Getting known devices list

DEBUG   <srv_object_class_init in healthd_ipc_dbus.c:1142>

DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:228> Agent: /com/signove/health/agent/8250

DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:242> Data type: 1004

DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:242> Data type: 1007

DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:242> Data type: 1029

DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:242> Data type: 100f

DEBUG   <get_agent_proxy in healthd_ipc_dbus.c:433> get_agent_proxy

DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_9

DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_10

DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_11

DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_12

DEBUG   <connect_device_signals in plugin_bluez.c:782> device to be connected: /org/bluez/10630/hci0/dev_00_1B_DC_06_A4_CC

DEBUG   <get_device_addr in plugin_bluez.c:303>         Device address is 00:1B:DC:06:A4:CC

DEBUG   <device_created in plugin_bluez.c:822> device created: /org/bluez/10630/hci0/dev_00_1B_DC_06_A4_CC

DEBUG   <disconnect_device_signals in plugin_bluez.c:689> Disconnected device /org/bluez/10630/hci0/dev_00_1B_DC_06_A4_CC

DEBUG   <device_removed in plugin_bluez.c:832> device removed: /org/bluez/10630/hci0/dev_00_1B_DC_06_A4_CC

Here is the sample_bt_agent:

IEEE 11073 sample agent

DEBUG   <agent_init in agent.c:133> Agent Initialization

DEBUG   <agent_start in agent.c:369> Agent starting...

DEBUG   <init in plugin_bluez.c:1287> Starting BlueZ link...

DEBUG   <connect_adapter in plugin_bluez.c:876> connecting adapter: /org/bluez/27960/hci0

DEBUG   <connect_adapter in plugin_bluez.c:916> Getting known devices list

DEBUG   <connect_device_signals in plugin_bluez.c:782> device to be connected: /org/bluez/27960/hci0/dev_00_1B_DC_06_AA_13

DEBUG   <get_device_addr in plugin_bluez.c:303>         Device address is 00:1B:DC:06:AA:13

DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_1

*** Device rediscovered

Main loop started

DEBUG   <plugin_bluez_connect_cb in plugin_bluez.c:1535> connection initiation error: Launch helper exited with unknown return code 1

DEBUG   <connect_adapter in plugin_bluez.c:876> connecting adapter: /org/bluez/29663/hci0

DEBUG   <connect_adapter in plugin_bluez.c:916> Getting known devices list

DEBUG   <connect_device_signals in plugin_bluez.c:782> device to be connected: /org/bluez/29663/hci0/dev_00_1B_DC_06_AA_13

[Ivan Tumanov]

Maybe, try to reinstall bluez. Which linux and bluez version are you running? Antidote is latest from github?

[Kawai Davis]

Ubuntu 14.04.2 LTS, Dbus 1.6.18, BlueZ 4.101 (all standard packages from Ubuntu)

Antidote is latest from github, extracted and compiled from github-master.zip. 

[michaels...@googlemail.com]

I'm facing the same problem. I was trying to execute the sample_bt_agent with Ubuntu 14.04.3 LTS with BlueZ 4.101 (4.101-0ubuntu13.1) and dbus 1.6.18 (1.6.18-0ubuntu4.3) and i'm getting the same error.

I think the problem is founded in some kind of interoperability between antidote and bluez 4.101, so that no HDP profile is offered by bluez. To proof, that HDP is supported by bluez, I tried hdp_oxi_sink from HDPy (Python implementation of HDP profile, https://github.com/signove/hdpy) and it worked out-of-the box, so that the HDP profile is offered by bluez.

For my tests I used the latest version of antidote from github by cloning the repository (There were some warnings during the execution of the autogen.sh script. But from my point of view no serious problems).

aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' 

...

configure.in:6: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.

...

src/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')

My next step will be to have a look at the sourcecode. Perhaps Elvis Pfützenreuter can provides us some help with this topic!?

[michaels...@googlemail.com]

One additional comment: I'm using two pcs both running Ubuntu 14.04.3 LTS. The first is running antidote with healthd and test_healthd.py. The second is running the sample_bt_agent.

[michaels...@googlemail.com]

I have figured out, that the problem is bluez in Ubuntu - it simply doesn't work for HDP since bluez 4.101. Unfortunately till now I could not figure out why. Even the test-health script from the bluez-stack doesn't work in Ubuntu. After that I have tried Ubuntu 5.10 which uses the recent version of bluez (bluez 5.38). The test-health script from the bluez stack doesn't work here too. So I have tried another distro: manjaro. Surprisingly, the test-health script worked here out-of-the box. Another thing I have tried, is to use the recent bluez compiled from source in Ubuntu 15.10. It doesn't work either. So it seems to be some problem of the generic Bluetooth driver in Ubuntu.

 

So for now, I have ported the bluez-plugin of antidote to the recent version 5 of bluez because this works under Manjaro or Debian. But the port does not work anymore with bluez 4.x. I will add eventually a configure-switch to be able to choose between the different bluez-plugin versions. Is someone interested in the port?

[Ryan Yetter]

I would be interested in the port.

[Michael Schmidt]

Hi Ryan,

attached you find my port for bluez5. Just replace the original file in "src/communication/plugin/bluez" with the attached file and compile antidote. Let me know if it works for you or if you are running into problems.

Best regards

Michael

2016-02-04 11:23 GMT+01:00 Ryan Yetter <yet...@yetterprises.com>:

I would be interested in the port.

[Ryan Yetter]

Thanks a lot!  I honestly didn't expect such a fast response - this is a 'weekend project' for me right now so I will keep you posted as I get time to work with it.

-Ryan

[Ryan Yetter]

Hi Michael,

The patch does seem to work as-advertised.  I've used it against a debian 8 install (kernel: 3.16.7-ckt20-1+deb8u3, bluez: 5.23-2+b1) and it works just fine.  I'm going to be doing some more testing over the next week on different Kernel/Bluez combinations so will let you know how it goes.

Thanks again!

-Ryan

On Thursday, February 4, 2016 at 10:47:29 AM UTC-5, Ryan Yetter wrote:

Thanks a lot!  I honestly didn't expect such a fast response - this is a 'weekend project' for me right now so I will keep you posted as I get time to work with it.

-Ryan

On Feb 4, 2016 9:30 AM, "'Michael Schmidt' via Antidote: open-source IEEE 11073 stack" <antido...@googlegroups.com> wrote:

Hi Ryan,

attached you find my port for bluez5. Just replace the original file in "src/communication/plugin/bluez" with the attached file and compile antidote. Let me know if it works for you or if you are running into problems.

Best regards

Michael

2016-02-04 11:23 GMT+01:00 Ryan Yetter <yet...@yetterprises.com>:

I would be interested in the port.

--
You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.

To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.

To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib+unsubscribe@googlegroups.com.

[Ryan Yetter]

For the record, it also works on Ubuntu 15.10, you just have to launch bluetoothd in compatibility mode (in bluetooth.service, add --compat to the Exec line - might have done this on debian too - can't remember now).

On Mon, Feb 8, 2016 at 3:46 PM, Ryan Yetter <yet...@yetterprises.com> wrote:

Hi Michael,

The patch does seem to work as-advertised.  I've used it against a debian 8 install (kernel: 3.16.7-ckt20-1+deb8u3, bluez: 5.23-2+b1) and it works just fine.  I'm going to be doing some more testing over the next week on different Kernel/Bluez combinations so will let you know how it goes.

Thanks again!

-Ryan

On Thursday, February 4, 2016 at 10:47:29 AM UTC-5, Ryan Yetter wrote:

Thanks a lot!  I honestly didn't expect such a fast response - this is a 'weekend project' for me right now so I will keep you posted as I get time to work with it.

-Ryan

On Feb 4, 2016 9:30 AM, "'Michael Schmidt' via Antidote: open-source IEEE 11073 stack" <antido...@googlegroups.com> wrote:

Hi Ryan,

attached you find my port for bluez5. Just replace the original file in "src/communication/plugin/bluez" with the attached file and compile antidote. Let me know if it works for you or if you are running into problems.

Best regards

Michael

2016-02-04 11:23 GMT+01:00 Ryan Yetter <yet...@yetterprises.com>:

I would be interested in the port.

--
You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.

To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.

To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.

To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.

[JONG BUM PARK]

Hi Michael,

I'm working on Antidote.
My devices is raspberrypi3. I compiled antidote with plugin_bluez.c that you've attached.
I got some errors like below.

======================

plugin_bluez.c: In function 'device_connected':

plugin_bluez.c:168:2: error: too many arguments to function 'communication_transport_connect_indication'

  communication_transport_connect_indication(cid, device);

  ^

In file included from plugin_bluez.c:50:0:

../../../../src/communication/communication.h:94:10: note: declared here

 Context *communication_transport_connect_indication(ContextId id);

          ^

plugin_bluez.c: In function 'device_disconnected':

plugin_bluez.c:180:2: error: too many arguments to function 'communication_transport_disconnect_indication'

  communication_transport_disconnect_indication(cid, device);

  ^

In file included from plugin_bluez.c:50:0:

../../../../src/communication/communication.h:96:6: note: declared here

 void communication_transport_disconnect_indication(ContextId id);

      ^

plugin_bluez.c: In function 'data_received':

plugin_bluez.c:1472:4: error: incompatible type for argument 1 of 'communication_read_input_stream'

    communication_read_input_stream(cid);

    ^

In file included from plugin_bluez.c:50:0:

../../../../src/communication/communication.h:104:6: note: expected 'struct Context *' but argument is of type 'ContextId'

 void communication_read_input_stream(Context *ctx);

======================

Could you provide communication.c communication.h sample_bt_agent.c?

Thanks in advance




2016년 2월 4일 목요일 오후 11시 30분 8초 UTC+9, Michael Schmidt 님의 말:

[michaels...@googlemail.com]

Hi Jong,

the files "communication.c communication.h sample_bt_agent.c" you requested are part of the antidote stack. Just use an IDE like eclipse or search for the files in the directory structure of the andidote stack. The errors you are mentioning should not be produced due my changes to the plugin_bluez.c. The changes I made are just affecting the D-Bus calls to the new bluez-D-Bus-API.

Do you have modified some parts of the stack? What linux distribution do you use? What Bluez-Version do you use? Please provide more information in order to help you.

Best regards
Michael

[JONG BUM PARK]

Hi Michael,

Thanks for the quick reply.

I use raspberrypi 3 (Linux raspberrypi 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux)

Bluez Version (5.23-2+rpi2).

I changed some part that you attached because of errors.

I paired the two systems first. Then ran healthd and python script in manager and sample_bt_agent in agent system.

But sample_bt_agent doesn't send any data.

I attached changed plugin_bluez.c that you attached before.

Many thanks in advance.

MANAGER

============================================================

root@manager /home/antidote/antidote-2.0.0/src # hciconfig

hci0: Type: BR/EDR  Bus: UART

BD Address: B8:27:EB:92:CA:49  ACL MTU: 1021:8  SCO MTU: 64:1

UP RUNNING PSCAN 

RX bytes:46029 acl:36 sco:0 events:715 errors:0

TX bytes:5417 acl:36 sco:0 commands:233 errors:0

root@manager /home/antidote/antidote-2.0.0/src # ./healthd 

DEBUG   <srv_object_class_init in healthd_service.c:1760>  

DEBUG   <manager_init in manager.c:158> Manager Initialization

DEBUG   <ext_configurations_load_configurations in extconfigurations.c:274> Zero-sized ext config buffer

DEBUG   <manager_start in manager.c:409> Manager starting...

DEBUG   <init in plugin_bluez.c:1325> Starting BlueZ link...

DEBUG   <connect_adapter in plugin_bluez.c:880> connecting adapter: /org/bluez/hci0

DEBUG   <connect_adapter in plugin_bluez.c:906> Getting known devices list

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_B8_27_EB_F3_B0_54 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_B8_27_EB_F3_B0_54

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is B8:27:EB:F3:B0:54

DEBUG   <srv_configurepassive in healthd_service.c:588> Agent: /com/signove/health/agent/11947

DEBUG   <srv_configurepassive in healthd_service.c:602> Data type: 1004

DEBUG   <srv_configurepassive in healthd_service.c:602> Data type: 1007

DEBUG   <srv_configurepassive in healthd_service.c:602> Data type: 1029

DEBUG   <srv_configurepassive in healthd_service.c:602> Data type: 100f

DEBUG   <get_agent_proxy in healthd_service.c:795> get_agent_proxy

DEBUG   <create_health_application in plugin_bluez.c:1127> Created health application: /org/bluez/health_app_17

DEBUG   <create_health_application in plugin_bluez.c:1127> Created health application: /org/bluez/health_app_18

DEBUG   <create_health_application in plugin_bluez.c:1127> Created health application: /org/bluez/health_app_19

DEBUG   <create_health_application in plugin_bluez.c:1127> Created health application: /org/bluez/health_app_20

============================================================

AGENT

============================================================

root@agent /home/antidote/antidote-2.0.0/src # ./sample_bt_agent B8:27:EB:92:CA:49 

IEEE 11073 sample agent

DEBUG   <agent_init in agent.c:136> Agent Initialization

DEBUG   <agent_start in agent.c:345> Agent starting...

DEBUG   <init in plugin_bluez.c:1325> Starting BlueZ link...

DEBUG   <connect_adapter in plugin_bluez.c:880> connecting adapter: /org/bluez/hci0

DEBUG   <connect_adapter in plugin_bluez.c:906> Getting known devices list

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_56_53_2E_B8_7D_3A and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_56_53_2E_B8_7D_3A

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 56:53:2E:B8:7D:3A

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_52_A7_E6_5A_B3_40 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_52_A7_E6_5A_B3_40

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 52:A7:E6:5A:B3:40

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_78_00_9E_47_5D_0F and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_78_00_9E_47_5D_0F

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 78:00:9E:47:5D:0F

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_7B_5C_A8_19_75_48 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_7B_5C_A8_19_75_48

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 7B:5C:A8:19:75:48

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_00_E0_4C_91_86_0B and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_00_E0_4C_91_86_0B

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 00:E0:4C:91:86:0B

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_73_03_83_90_59_7D and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_73_03_83_90_59_7D

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 73:03:83:90:59:7D

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_5F_9E_66_AA_4B_F5 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_5F_9E_66_AA_4B_F5

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 5F:9E:66:AA:4B:F5

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_78_00_9E_47_67_73 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_78_00_9E_47_67_73

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 78:00:9E:47:67:73

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_70_DC_A4_02_6C_6B and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_70_DC_A4_02_6C_6B

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 70:DC:A4:02:6C:6B

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_6F_41_2F_10_ED_07 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_6F_41_2F_10_ED_07

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 6F:41:2F:10:ED:07

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_78_00_9E_47_5A_D7 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_78_00_9E_47_5A_D7

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 78:00:9E:47:5A:D7

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_78_00_9E_47_4F_31 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_78_00_9E_47_4F_31

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 78:00:9E:47:4F:31

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_D9_27_92_0F_F4_AA and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_D9_27_92_0F_F4_AA

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is D9:27:92:0F:F4:AA

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_57_D6_A4_34_4B_6A and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_57_D6_A4_34_4B_6A

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 57:D6:A4:34:4B:6A

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_5C_E3_0F_D0_F9_53 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_5C_E3_0F_D0_F9_53

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 5C:E3:0F:D0:F9:53

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_04_52_C7_07_7A_68 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_04_52_C7_07_7A_68

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 04:52:C7:07:7A:68

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_40_2C_F4_92_B3_DE and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_40_2C_F4_92_B3_DE

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 40:2C:F4:92:B3:DE

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_B8_27_EB_92_CA_49 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_B8_27_EB_92_CA_49

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is B8:27:EB:92:CA:49

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_14_32_D1_8E_E7_49 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_14_32_D1_8E_E7_49

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 14:32:D1:8E:E7:49

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_00_07_79_0B_77_01 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_00_07_79_0B_77_01

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 00:07:79:0B:77:01

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_71_8E_30_53_C8_E1 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_71_8E_30_53_C8_E1

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 71:8E:30:53:C8:E1

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_8C_08_8B_8A_9B_5C and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_8C_08_8B_8A_9B_5C

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 8C:08:8B:8A:9B:5C

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_CC_3D_82_5B_78_8F and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_CC_3D_82_5B_78_8F

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is CC:3D:82:5B:78:8F

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_76_8C_B9_91_A0_A5 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_76_8C_B9_91_A0_A5

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 76:8C:B9:91:A0:A5

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_73_EA_01_C9_E4_0D and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_73_EA_01_C9_E4_0D

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 73:EA:01:C9:E4:0D

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_88_63_DF_CD_B5_6C and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_88_63_DF_CD_B5_6C

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 88:63:DF:CD:B5:6C

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_72_46_CC_04_69_D2 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_72_46_CC_04_69_D2

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 72:46:CC:04:69:D2

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_00_18_91_75_F4_9E and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_00_18_91_75_F4_9E

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 00:18:91:75:F4:9E

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_D5_E5_84_A7_67_7E and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_D5_E5_84_A7_67_7E

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is D5:E5:84:A7:67:7E

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_A4_E4_B8_6C_09_29 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_A4_E4_B8_6C_09_29

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is A4:E4:B8:6C:09:29

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_58_89_9C_44_17_87 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_58_89_9C_44_17_87

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 58:89:9C:44:17:87

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_4D_DA_18_20_F4_79 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_4D_DA_18_20_F4_79

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 4D:DA:18:20:F4:79

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_7A_3E_28_DC_43_7B and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_7A_3E_28_DC_43_7B

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 7A:3E:28:DC:43:7B

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_1C_48_F9_CB_16_5D and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_1C_48_F9_CB_16_5D

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 1C:48:F9:CB:16:5D

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_F1_BD_DE_B2_95_67 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_F1_BD_DE_B2_95_67

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is F1:BD:DE:B2:95:67

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_FC_A1_DF_2D_E4_43 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_FC_A1_DF_2D_E4_43

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is FC:A1:DF:2D:E4:43

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_5C_31_3E_00_7D_98 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_5C_31_3E_00_7D_98

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 5C:31:3E:00:7D:98

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_00_07_79_0B_77_00 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_00_07_79_0B_77_00

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 00:07:79:0B:77:00

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_00_07_79_0B_76_FF and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_00_07_79_0B_76_FF

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 00:07:79:0B:76:FF

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_00_13_7B_49_3B_BB and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_00_13_7B_49_3B_BB

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 00:13:7B:49:3B:BB

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_7B_CB_D7_0F_5C_50 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_7B_CB_D7_0F_5C_50

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 7B:CB:D7:0F:5C:50

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_6D_86_CE_DD_73_42 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_6D_86_CE_DD_73_42

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 6D:86:CE:DD:73:42

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_60_36_DD_75_EB_11 and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_60_36_DD_75_EB_11

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 60:36:DD:75:EB:11

DEBUG   <connect_adapter in plugin_bluez.c:947> Connecting signals for object /org/bluez/hci0/dev_52_5D_05_4F_32_3D and adapter /org/bluez/hci0

DEBUG   <connect_device_signals in plugin_bluez.c:789> device to be connected: /org/bluez/hci0/dev_52_5D_05_4F_32_3D

DEBUG   <get_device_addr in plugin_bluez.c:310> Device address is 52:5D:05:4F:32:3D

DEBUG   <create_health_application in plugin_bluez.c:1127> Created health application: /org/bluez/health_app_18

Main loop started

DEBUG   <plugin_bluez_connect_cb in plugin_bluez.c:1574> connection initiation error: Method "CreateChannel" with signature "os" on interface "org.bluez.HealthDevice1" doesn't exist

============================================================

2016년 8월 31일 수요일 오후 9시 16분 34초 UTC+9, michaels...@googlemail.com 님의 말:

[michaels...@googlemail.com]

Hi Jong,

the compile errors you mentioned are due to your changes in plugin_bluez.c. I would suggest to revert these changes and concentrate on the main problem, that was:

"connection initiation error: Method "CreateChannel" with signature "os" on interface "org.bluez.HealthDevice1" doesn't exist"

The problem here is, that the agent does not know that the device (to which it is connected) is an HDP supporting device. You must start the manager (healthd and test_healtd.py) before pairing the devices.

Best regards
Michael

[JONG BUM PARK]

Hi Michael.

Thanks for the reply.

Finally I got connection between healthd and sample_bt_agent as you mentioned.

sample_bt_agent is working fine.

But I have another problem with real device AND UA-651BLE.

healthd doesn't respond anything. 

bluetoothctl console gave me 'Device 5C:31:3E:00:7D:98 Connected: yes' message.

I need to check HCI packet later.

Thanks.

Regards.

2016년 9월 1일 목요일 오후 8시 31분 16초 UTC+9, michaels...@googlemail.com 님의 말:

[Michael Schmidt]

Hi Jong,

> sample_bt_agent is working fine.

Perfect! :-)

The device you are mentioning is not compatible to IEEE11073. You can find a list of compatible product here: http://www.continuaalliance.org/products/product-showcase. As I know, IEEE11073 is just possible with Bluetooth (and not with Bluetooth LE/Smart), because Bluetooth LE is using GATT. But there is a whitepaper from the Bleutooth alliance which describes how to convert data. You can find it here: https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=272346. Additionally you should have a look at the signove antidote program guide, you can find here: http://oss.signove.com/images/c/c7/AntidoteProgramGuide.pdf. From interest to you will also be the section which describes the Specializations API of the stack.

I hope this helps. But It think it will be a lot of work to get your device (AND UA-651BLE) running. Please let me know if you managed it :-)

Best regards

Michael

--
You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.

To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib+unsubscribe@googlegroups.com.

[JONG BUM PARK]

Hi Michael.

What a helpful information~!!!

I just checked AND  UA-651BLE is not compatible with IEEE11073.

I used gatttool for measurement data receiving(Change Client Characteristic)

I need to make collector for transcoding unfortunately.

But I think it can not be used in general. 

Thank you so much!
Best regards

JB

2016년 9월 2일 금요일 오후 8시 15분 38초 UTC+9, Michael Schmidt 님의 말:

To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.

[Marko Janković]

Hi Jong,

could you please provide instructions how you installed Antidote to RPi3. I am trying to do it, but make command doesn't work. Did you have to install some addtitional tools? if yes, which ones? I would also like to read data from A&D continua certified devices.

My steps:

./autogen.sh
./configure
make - this is not working for me :/
sudo make install

Thanks in advance.

Best,

Marko

[JONG BUM PARK]

Hi Marko,

Check my blog.

I hope it can be helpful.

http://cafefriend.net/blog/?p=342

2016년 9월 20일 화요일 오후 10시 45분 36초 UTC+9, Marko Janković 님의 말: