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

  • Is the accelerometer callback the only function that's not working?  If that is true, then I cannot think of why that would be only callback not being triggered. Also, it does not appear that you put the polledData checking code inside the threa…
  • There is no GPIO pin 9, only 0 - 7.  If you are referring to pin 9 on the pin assignments diagram (https://mbientlab.com/docs/MetaWearPPSv0.6.pdf, section 2.2) then that is GPIO pin 1.  Also, don't forget to change the operating speed to 'FAST' when…
    in NeoPixel Comment by Eric September 2014
  • Forgot to update the thread with the NeoPixel post on our projects page: http://projects.mbientlab.com/metawear-and-neopixels/
  • The Android app doesn't have battery life on there, I will be adding that in the next update.  The iOS API does in the MBLMetaWear interface: https://github.com/mbientlab/Metawear-iOSAPI/blob/master/MetaWear.framework/Versions/A/Headers/MBLMetaWea…
  • Acclerometer data is stored into a temp variable, polledData, which is populated when the metawear is receiving data (receivedDataValue fn).  If no data is being collected then that variable is never fill up.  Trying getting the size of polledData /…
  • You're going to have to provide more information than a log output.  What functions did you call?  In what order did you call them?  What was the sequence of events that led up to the crash?   Second one seems like a firmware issue, the device sh…
  • You can configure the accelerometer through the Android API however, there is no builder class to abstract the byte ordering so you'd have to know the config format.  I will be adding the builder class in the next set of API features. For the time…
  • A reset command can be issued through the ble channel, I will add a button for that on the next Android update (iOS app already has this feature).  As of right now, there is no physical way to reset the device other than cutting the power.
  • Are you referring to the ble GATT service UUID or the advertisement UUID?
  • What firmware and apk versions were you using prior to the update issues?
  • There is a reset command you can issue to the device which will do a hard reset.  The iOS app has a button to do this but I did not add the same button to the Android app.  I will add it in the next app update.
  • We are not releasing the firmware code at this point in time.   If you want to write your own firmware, you will need to purchase your own development kit.  You can check out our firmware guide on docs page: http://mbientlab.com/docs/MetaWearFirm…
  • The stretch goals were retracted on the kickstarter page due to lack of man power and budget.  However, since we have extra time on our hands as the campaign is done, we are going to add the heart rate sensor and have already uploaded the CAD enclos…
  • The current firmware (v0.4.1) does not support changing the device name.  We are planning on adding this feature in a later firmware release.
  • Currently, there is no physical feedback to indicate whether or not the device is on / working.  
  • The MetaWear sample Android app has a panel to control the LED. https://github.com/mbientlab/Metawear-SampleAndroidApp/releases/tag/2.1
  • Android does not support Java 8. 
  • Clearing channel data is embedded in the stop command.  When you send the stop command, you can either just stop the pattern or stop and and clear the pattern.   The current firmware (v0.4.1) does not support clearing individual channels, clearing…
  • The MetaWear app has examples covering most of the functions in the api. https://github.com/mbientlab/Metawear-SampleAndroidApp/blob/2.1/src/com/mbientlab/metawear/app/LEDFragment.java#L157
  • How odd.... the app is compiled for target SDK 19.  I don't see why changing it to 20 would cause build errors. Both DialogFragment and CursorLoader class are using the version from the android.support.v4 package and ArrayFormat is an enum from the …
  • Our accelerometer does support it but we haven't test out the firmware code for it yet.  Our primary focus at the moment has been on the XYZ motion data aspect of the accelerometer. You can checkout the MetaWear accelerometer specs here: http://w…
  • Yes that is correct, first set a color channel then play.  And yes, you can omit channels as they are controlled independently of each other.
  • The LED attributes are set per color channel, which is determined in byte 2 (0 = green, 1 = red, 2 = blue).  This allows you to control each LED color independent of the others. The rest of bytes needed to set an LED channel can be seen in the Jav…
  • the motor and buzzer use the same pins
  • Currently, we don't have any public documentation available on the byte formats.  The closest thing out there is the source code for the Java API on the GitHub page.   Some Java files of interest: https://github.com/mbientlab/Metawear-AndroidA…
  • Try v2.1 of the app: https://github.com/mbientlab/Metawear-SampleAndroidApp/releases/tag/2.1
  • Buzzer pin details are in the preliminary product spec pdf file under section 8, "Typical Application Circuit" https://mbientlab.com/docs/MetaWearPPSv0.6.pdf
  • The service advertisement UUID is the same for all MetaWear boards.  The device UUID is unique,
  • Out of curiosity, are you building the app from the GitHub source code or using the prebuilt apk file?  If you are using the source code, there was a file naming issue stemming from Windows being case insensitive.  The problem is fixed in the latest…
  • Which UUID are you referring to?