Trouble connecting with sample_bt_agent

[Aravind Nair]

Hi all,

I've been trying to run the sample_bt_agent.c but it doesn't seem to send any data. I get a command like 'Device <bluetooth address> unknown by Bluez' and it stops execution. I read the previous posts about trouble with sample_bt_agent, but since the error was different, wasn't sure it was the same issue. Any insights on this would be much appreciated. I am using Ubuntu 14.04 in Virtualbox for agent and laptop with Ubuntu 14.04 for manager.

I have attached a screenshot of the output window for the agent. PFA.

Thanks & Regards,
Aravind Nair

[Ivan Tumanov]

Have you paired devices before?

воскресенье, 24 апреля 2016 г., 19:35:58 UTC+3 пользователь Aravind Nair написал:

[Aravind Nair]

Hello Ivan,
Thanks for the reply. Yes I paired the two systems first. Then ran healthd and python script in manager and sample_bt_agent in agent system.

Regards,
Aravind Nair

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

[Aravind Nair]

Hi all,

So I've been trying to fix that issue with sample_bt_agent and finally managed to run it and got it till rediscovering of device part. But I am having another trouble. Following is the log I got in the terminal when I run sample_bt_agent.

aravind@aravind-VirtualBox:~/Desktop/antidote-master/apps$ ./sample_bt_agent bpm 38:B1:DB:EC:8A:44

IEE ideaE 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/10681/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/10681/hci0/dev_B4_52_7D_A7_7B_F6
DEBUG   <get_device_addr in plugin_bluez.c:303>     Device address is B4:52:7D:A7:7B:F6
DEBUG   <connect_device_signals in plugin_bluez.c:782> device to be connected: /org/bluez/10681/hci0/dev_38_B1_DB_EC_8A_44
DEBUG   <get_device_addr in plugin_bluez.c:303>     Device address is 38:B1:DB:EC:8A:44
DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_5
*** 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

Any idea what it means or how I can solve this? Any help is really appreciated.

Thanks & Regards,

Aravind Nair

[Ivan Tumanov]

sample_bt_agent must know about health device service on paired devices, it can be possible with start health service before pairing devices

вт, 26 апр. 2016 г. в 19:03, Aravind Nair <mailara...@gmail.com>:

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.

--

Best regards,
Ivan Tumanov

[Aravind Nair]

Hello Ivan,

Thanks for that suggestion. Will try that and get back to you.

Regards,

Aravind

[Aravind Nair]

Hello,

So I've been working on it for the last two days (was busy last couple of weeks hence the delay) and manged to get past that and couple of other errors. But got this 'MCAP instance error' which couple of other guys have also posted in another thread. (https://groups.google.com/forum/#!topic/antidote-lib/whZGpVwmljs). Any idea what it is or how to solve this? MCAP instance comes under Bluetooth HDP which assists in connection creation. There is a brief info about it in Bluetooth HDP whitepaper on 'implementing Bluetooth HDP'. Any ideas or suggestions would be very helpful. The error message is given below:

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/652/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/652/hci0/dev_B4_52_7D_A7_7B_F6

DEBUG   <get_device_addr in plugin_bluez.c:303>     Device address is B4:52:7D:A7:7B:F6

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

DEBUG   <get_device_addr in plugin_bluez.c:303>     Device address is 38:B1:DB:EC:8A:44
DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_5
*** Device rediscovered
Main loop started

DEBUG   <plugin_bluez_connect_cb in plugin_bluez.c:1535> connection initiation error: Mcap instance released

Thanks.

[Joel Reiser]

How did you get past that original error? I always get the same error, no matter what I do... plugin_bluez.c:1535 connection initiation error: Method "CreateChannel" with signature "os" on interface "org.bluez.HealthDevice" doesn't exist. I've tried the most recent version of BlueZ built from source, no change. It triggers at the right time, it just doesn't succeed.

TIA!

Joel R