Eric
Do not send private messages with technical questions; they will be discarded. All technical questions must be posted publicly on the forum.
About
- Username
- Eric
- Joined
- Visits
- 9,275
- Last Active
- Roles
- Administrator
Comments
-
The MetaWear already behaves as described in this thread.
-
If you need reliable timestamps, you'll have to log the data on-board.
-
The error you quoted is a result of not properly configuring the include paths. If you are building with gcc, you need to configure Gradle to have the same compiler flags as outlined in the Makefile. https://github.com/mbientlab/Metawear-CppAPI/b…
-
Connect is an asynchronous operation. You need to rely on the ConnectionStateHandler class to react to connection attempts. https://mbientlab.com/androiddocs/latest/metawearboard.html#connection-state
-
Figure out what BTLE functions your platform exposes and hook them into the C++ API as outlined in the C++ documentation,
-
Sensor data is not modified on the firmware side. The APIs convert the bytes into the relevant variable types.
-
The entire class is relevant for what you want to do.
-
Yes there is SPI support, we just have not exposed control of the SPI bus to the user. It will be released in the new firmware update.
-
You can use the C++ API to build a PC application to communicate with the board. Once you have the data, you then need to do sensor fusion to combine the acc and gyro data into pitch, yaw, and roll.
-
MetaWear uses Bluetooth Low Energy not classic Bluetooth. There is no serial port profile in the BLE standard.
-
That depends on what you're most comfortable with. If you're not sure, then stick with the original idea of modifying the gpio code.
-
You don't need two apps for this; the same app can handle both uses. Schedule a task to connect, download, then disconnect using the Handler class after you're done setting up the board.
-
Try connecting to the board with the nRF Master Control Panel app. Given what you have described, it looks like the service discovery portion of the API is timing out. Also, what phone and OS are you using?
-
Did you remember to disconnect and reconnect after the changing the connection interval? Also, what Bluetooth adapter is your PC using?
-
Are you filtering by service UUID during your ble scan?
-
Please see my earlier post regarding a general overview on what you need to do. Alternatively, it may be easier to create your own SensorFragment subclass, in the same way done by the BarometerFragment class, and simply having the app configure you…
-
You can mimic an if-else branch by using two passthrough filters (P1, P2) in conditional mode where only one permits data through. Assuming P1 represents no motion, when data passes through, it will disable itself, enable P2, and switch to any moti…
-
Which app are you referring to? Assuming you are using one of the UWP sample projects, try the Android or iOS MetaWear apps to see if the same behavior occurs.
-
I suspect it has to do with the connection interval that Windows uses, see this thread. What you can do is reduce the max connection interval to 7.5ms on the first connect then reconnect the board to your windows device so the two BTLE radios will …
-
You need to be on Windows 10 to use UWP. If you are migrating your development environment to Windows 10, you can follow our UWP tutorial to get started.
-
This goes back to my earlier question of "What does 'startNoMotion' do?" An activity monitor only executes MetaWear specific commands; it is limited in what it can do as the MetaWear is responding to some activity on board, not on your mobile devic…
-
First off, I highly recommend developing on Windows 10 as all of our Windows sample code is built on the Universal Windows Platform. For Windows 8.1, you can refer to the C# Wrapper project for sample code demonstrating how to communicate with t…
-
The error and the appropriate fix is given in the log output: /Users/npstudent/Desktop/SCHOOL/FYP/Metawear-SampleAndroidApp(reference)/app/src/main/java/com/mbientlab/metawear/app/I2cFragment.java Error:(51, 8) error: class I2CFragment is public, s…
-
Writing to the CSV file is handled in the SensorFragment.saveData function. You can look at the SensorFragment child classes to see how different sensors implement it.
-
Which part of the code doesn't work and what does "startNoMotionDetection" do?
-
Because that is not an nmake file.
-
You need to be on Windows 8.1, or preferably 10, to use Bluetooth LE.
-
The RG board has SDA and SCL pins for I2C communication. Check the product specification PDF for the pin location
-
The simplest way to solve your problem is to have other Android devices to handle gyro data from the other boards. There is no getting around the 100Hz data throughput limit as BTLE is not meant for a high volume of data. Unless you log at a lowe…
-
Yes, you can manually write to the command characteristic if you want; that is what the APIs are doing behind the scenes. The C++ API provides some example byte strings in the unit tests.