AferoCE / beetle

Afero Bluetooth daemon
MIT License
0 stars 0 forks source link

How to verify beetle function? #2

Open Peter-Lin opened 6 years ago

Peter-Lin commented 6 years ago

Hi I want to verify beetle function. But my bluetooth chip don't have Afero firmware devices on it now, may I verify beetle function without Afero firmware devices ?

Is there any test ap or test commands? thanks~ Daniel

afjgeorge commented 6 years ago

Hi Daniel,

We have some beetle connection test documentation that you can use without having any Afero devices. As long as your board supports BLE, you can set up beetle on two hosts, one will act as a host and one will act as a peripheral, and you can test basic beetle functionality that way.

Please see the documentation at https://github.com/AferoCE/beetle/blob/master/docs/connectiontest.md

Please check that out and let me know if you have any questions and I'll be happy to help!

Thank you,

Joe

Peter-Lin commented 6 years ago

Hi Joe How do I verify the beetle function if I have an Afero device with Afero firmware? see https://github.com/AferoCE/beetle/blob/master/docs/devicetest.md? beetle will auto run if I have an Afero device with Afero firmware? Or how to enable it? thanks~

Daniel

afjgeorge commented 6 years ago

Hi Daniel,

If you have an Afero device, you can use the instructions in "devicetest.md" to manually communicate between an Afero device and the beetle daemon. In a complete hub environment, if beetle and the hub daemon ("hubby") are started at boot, they will auto-connect to Afero devices and establish communication to the Afero cloud, but in this instance for testing, the instructions in devicetest.md will allow you to force communications between beetle and the Afero device to establish it's working.

Thank you,

Joe

Peter-Lin commented 6 years ago

Hi Joe

In a complete hub environment, if beetle and the hub daemon ("hubby") are started at boot<=Do I have to do anything to start hubby and beetle or the two apps will auto start? thanks~

Daniel

afjgeorge commented 6 years ago

Hi Daniel,

The two apps don’t have any ability to auto-start themselves. In Linux environments you would need to have some type of startup script to launch them at boot and restart them if they die. For more modern Linux OSes you can use systemd, I think Android supports traditionalUnix /etc/init.d/ scripts which will also work on many smaller embedded Linux OSes as well.

Joe

On Oct 1, 2017, at 6:53 PM, Peter-Lin notifications@github.com wrote:

Hi Joe

In a complete hub environment, if beetle and the hub daemon ("hubby") are started at boot<=Do I have to do anything to start hubby and beetle or the two apps will auto start? thanks~

Daniel

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/AferoCE/beetle/issues/2#issuecomment-333424521, or mute the thread https://github.com/notifications/unsubscribe-auth/AQB98jiMS6-FOR9EaNntq2i6XMBZ1IBQks5soEILgaJpZM4PlJmo.

Peter-Lin commented 6 years ago

Hi Joe

What is the command to start beetle an hubby in a complete hub environment? May I start beetle by the command "sudo beetle -m cen" in a complete hub environment? Is hubby in the Afero firmware? Do I still have to start it? Thanks

Daniel

afjgeorge commented 6 years ago

Hi Daniel,

At boot you just need to call “beetle” - the central mode is the default. The hubby software we provide to you in binary form (I believe we put this up for you a couple of weeks ago at this point). To launch it at boot you only need to call “hubby” as well - no command line switches needed.

For reference, these are the systemd service descriptions we use to start these daemons for the current upgrade to the Developer Hub I’m working on. They simply call the daemons at boot and relaunch them if they are killed. This translates to a pretty simple init.d type script if you need init.d for your system.

Cheers,

Joe

beetle.service [Unit] Description=Afero BTLE Daemon Documentation=man:beetle Requires=network.target After=network.target

[Service]

Type=forking

ExecStart=/usr/bin/beetle Restart=always RestartSec=1

[Install] WantedBy=multi-user.target

hubby.service [Unit] Description=Afero Hub Daemon Documentation=man:hubby Requires=beetle.service After=beetle.service

[Service]

Type=forking

ExecStart=/usr/bin/hubby Restart=always RestartSec=1

[Install] WantedBy=multi-user.target

Alias=hubby.service

On Oct 2, 2017, at 6:42 PM, Peter-Lin notifications@github.com wrote:

Hi Joe

What is the command to start beetle an hubby in a complete hub environment? May I start beetle by the command "sudo beetle -m cen" in a complete hub environment? Is hubby in the Afero firmware? Do I still have to start it? Thanks

Daniel

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/AferoCE/beetle/issues/2#issuecomment-333714808, or mute the thread https://github.com/notifications/unsubscribe-auth/AQB98g_1-IRSdWQ5ZGFymbGr1HxQ2RJOks5soZDtgaJpZM4PlJmo.

Peter-Lin commented 6 years ago

Hi Joe

My colleague doesn't have the hubby software. Do you remember who had received it? Could you give me again? daniel_yc_cheng@wistron.com thanks

Daniel

afjgeorge commented 6 years ago

Hi Daniel,

The Afero binaries that we supply to you are at https://github.com/AferoCE/wistron-binaries https://github.com/AferoCE/wistron-binaries

hubby, afsecd, and provision. hubby requires afsecd to launch at boot before hubby does, provision is just a diagnostic tool to read the Afero data out of the ATECC508A chip and can be used to verify the 508 on your board.

Cheers,

Joe

On Oct 4, 2017, at 8:01 PM, Peter-Lin notifications@github.com wrote:

Hi Joe

My colleague doesn't have the hubby software. Do you remember who had received it? Could you give me again? daniel_yc_cheng@wistron.com mailto:daniel_yc_cheng@wistron.com thanks

Daniel

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/AferoCE/beetle/issues/2#issuecomment-334345638, or mute the thread https://github.com/notifications/unsubscribe-auth/AQB98utShFVRuxzYUOe9TRHbyecNi5HYks5spEaBgaJpZM4PlJmo.