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
-
Sounds like the battery is defective or not properly attached. We will fix the board free of charge, send us an email to "hello at mbientlab dot com" with your problem and order #.
-
Part of the memory allocated for a log entry is for a timestamp and an identifier. I suppose a timestamp is unnecessary if the user is collecting data at a fixed rate and knows either the start or end time. It's something worth considering.
-
What is the full code for your logged sample processor? I logged a sample processor and downloaded it without running into any problems. // Using a MetaWear RPro multiTempModule.routeData().fromSource(multiTempModule.getSources().get(1)).process…
-
Sorry, I had left out some bits of information in the previous post. Processors are executed in the order they are added. In the first example, the processors in order are: 1) counter 2) maths. So, the counter will execute first, trigger the acti…
-
Some offhand thoughts about the proposed filters: * The sample filter (erroneously described in the Android docs, need to fix that) partially does what you are looking for. It will not allow data through until it has received X samples however, t…
-
Ok I see what you are doing. Modifying a processor will always occur before the processor handles the next piece of data. So, your counter will trigger the modification of processor X, then processor X will deal with the data from the counter proc…
-
I think you have the wrong idea of what a monitor does. The commands inside a monitor are only executed in response to activity on its producer, i.e. when data is created, not when the Java code handles the monitor function. If I am interpreting y…
-
Processors are added to the MetaWear in the same order as in the code. Streaming, logging, and monitoring are handled after all processors are added. Assuming your As and Bs are all processors, they will be send to the metawear in this order: …
-
@Matt Unfortunately the screenshots are too small for me to see any code. It seems that you have stopped at part 2 of the guide. You should go through part 3 of the tutorial so you can become experience with creating a MetaWear app from scr…
-
No, data from each sensor is separate from each other. Any sort of data joining or splitting needs to be handled on the mobile device.
-
@jgummeson There is not way to check the result of the write. That information is not available to the API.
-
How far along are you in the "Getting Started" guide? You will have a working MetaWear app at the end of guide so I would follow the guide til the end. When you are done with the guide, you should checkout the iOS docs on the MbientLab website: ht…
-
No, metawear boards cannot communicate directly with each other.
-
Yes, that json file is what the iOS API uses for the firmware check.
-
Most devices can maintain multiple BTLE connections so you can have several MetaWears communicate to each other through 1 mobile device.
-
Presently there is no function to do a firmware check with the Android API. Firmware updates are not frequently released so it is not a high priority item for now.
-
Code snippet is available on the Android docs page:https://mbientlab.com/androiddocs/#settings. You can also change the device name with the MetaWear App using the "Settings" panel.
-
You can read up on the GPIO class on the iOS docs: https://mbientlab.com/iosdocs/#gpio. The documentation has code snippets for the various GPIO features.
-
Yup, this is a bug. I've fixed the issue and it will be in the next release.
-
The macro system is for storing commands on board. What you need is a signal monitor: https://mbientlab.com/androiddocs/#dr-monitor. Unless you need your Android device to be alerted of free fall events live, you should replace the stream componen…
-
You use the Settings module to change the advertisement parameters, and the Macro module to make the change permanent.
-
Yes, this is a feature we have on our TODO list. Currently, there is no way to do this with the MetaWear API until the firmware is updated to support the disconnect event.
-
Hrm, I'm not quite sure what could be wrong. The sample app implements auto reconnect using the disconnect and failure callback functions as well. https://github.com/mbientlab/Metawear-SampleAndroidApp/blob/3.1.0/app/src/main/java/com/mbientlab/m…
-
@fblais Please send an email to to 'hello at mbientlab dot com' about the situation with your order number.
-
Hrm, it looks like your Android device can establish a connection to the board but it does not complete the MetaWear service discovery. Just to be sure, can your Android device connect to the board with the MetaWear app?
-
Since you have the battery disconnected, try holding the button down when inserting the USB cable. This will force the board into bootloader mode. If the board still does not show up then, its possible it is defective / dead. We can replace the b…
-
You can try using a bigger battery, such as a 200mAh battery. However, running two sensors in addition to the LED draws a huge amount of current, possibly more than the lithium battery can provide.
-
What does the stack trace of the error object show in the failure function?
-
The app requires a minimum of Android 4.3 to run. As far as I know, Bluetooth LE is only on Android 4.3 and higher. Unless there is a strong reason for you to stay on 4.2.2, you should upgrade to at minimum Android 4.4.
-
I am not sure what could be wrong. We put the metawear inside a nerf football and threw it around in the streets not problem. I'll ask Laura to see if she might have any insight.