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

  • There is no macro being used in your code block? You can try the sample route in the Android Docs for LED debugging:https://mbientlab.com/androiddocs/#dr-monitor
  • The point of returning a byte array is so the user doesn't know anything about the internal formatting.  If someday, a more compact serialization format is needed, it does not affect the user as all they see is a byte array rather than expecting a f…
  • At this point, I'm not sure what could be wrong.  You can take a look at one of our demo projects we are doing as a tutorial to compare against your project, link here.
  • You need to eliminate as many variables as possible.   * Is orientation detection working? * Does the activity handler properly trigger other events i.e. turn on led?
  • Is your support library package up to date?  The app uses appcompat-v7 now instead of support-v4.
  • Again, I am asking if "mwBoard.isConnected()" returns true when you are calling "getModule".  If you see the error message in the logger, then accelModule is not being assigned a value, therefore is still null when you press the button.
  • What do you mean by "program the ADC reference" ?  If you are trying to read the ADC ratio, then use AnalogReadMode.ADC.
  • Both boards support orientation, we have not yet tested all the configuration options on the RG chip so the Android and iOS libraries have not exposed them for now. The byte string enables orientation on the R board.  If the windows library does n…
  • Actually...which board do you have?  R or RG/Pro?
  • For orientation, you need to enable the detection, configure the sensor, and then enable notifications: 0x03 - 0x08 - 0x01 0x03 - 0x09 - 0x00 - 0xc0 - 0x0a - 0x00 - 0x00 0x03 - 0x0a - 0x01 Once you've done that, you write [0x03 - 0x01 - 0…
  • ///< When you serialize mma8452qModule.routeData().fromOrientation().log("orientation_log").commit()     .onComplete(new CompletionHandler() {         @Override         public void success(RouteManager result) {             ///< save this…
  • You can serialize the board's internal state and store it to your device's filesystem.  When you restart your app, you can restore the board's state. MetaWearBoard.serializeState() MetaWearBoard.deserializeState(byte[])
  • I believe this can be done with the activity handler.  You would monitor motion detection, shake detection, and a temp -> comparison filter.  Each activity handler would set the Ibeacon minor  * Attach a monitor to motion, shake, and  temp -&g…
  • The Windows API creator has not been active on these forums in 9 months.  We do not officially support a Windows API so your best bet would be to contact the author directly.
  • Yes, which is why I am asking if "mwBoard.isConnected()" returns true when you are calling "getModule" if (!mwBoard.isConnected()) {   Log.e("Test", "Device is not connected to a MetaWear board"); } else {   accelModule= mwBoard.getModule(Accel…
  • How are you getting to this activity (or fragment)?  The only way I can see you running into a null pointer exception is that you are not connected to the board when you call getModule.  So, to make sure, does mwBoard.isConnected() return true on bo…
  • You will need to provide some more information about your code flow.  What happens between retrieving an accelerometer module and calling setOutputDataRate?
  • Maintaining an active connection, combined with live streaming, draws a greater amount of power from the battery than letting it operate on its own.  I would go with the IBeacon approach for getting some information on what's happened and use the lo…
  • Eric Leigh hasn't been active on the forums since December of last year.  You may not get an answer unless you contact him directly.
  • You need to have an active ble connection before calling getModule. https://mbientlab.com/androiddocs/#m-modules
  • * The key passed into setLogMessageHandler and the log method must match, same with subscribe/unsubscribe and stream.  In your code, you are using different keys. * Log sends data to the internal logger * What Android version are you using? * Call…
  • Yes, 2.0.0 has breaking changes all across the board including reorganizing the package structure; you will need to update your API usage to reflect the new changes. https://mbientlab.com/androiddocs/index.html#library
  • The app currently does not support the new sensors.  This release updates the code support R PRo and RG with existing app features. Gyro documentation is on the docs page: https://mbientlab.com/androiddocs/index.html#bmi160-gyro
  • The temperature sensor from the SOC picks up heat from the chip which causes it to report slightly higher temperatures.  If you are using an R Pro (or RG), you can read temperature from the internal thermistor  to get a more accurate reading.
  • A simple way is to use USB debugging to view the system logs in Logcat.  Check the status codes of the gatt connection attempts and the visible devices listed from a BLE scan.
  • The LED module is pretty straightforward, like the haptic module, in that all the code does underneath is properly place the respective parameters in a byte array.  An implementation of the Led interface is provided in the DefaultMetaWearBoard class…
    in Python API? Comment by Eric August 2015
  • No, the USB port only provides power, nothing more.
  • What are the specs for the devices?  Sounds like the second device does not support Bluetooth LE.
  • DIsconnecting immediately after writing a command could result in the command being dropped.  It's possible the stop command was never sent due to closing the connection too quickly.
  • Here's some steps you can take to debug the board.  First, use your coworker's IPhone 6 to update the board to the latest firmware (v1.0.4).  After that, see if the Nordic Master Control Panel app on your Android phone can connect to the board. …