Edwardsj
About
- Username
- Edwardsj
- Joined
- Visits
- 313
- Last Active
- Roles
- Member
Comments
-
@Eric, Thank you. It sounds like what I am working on. So is there any similar projects or other solutions using MetaWear boards that you are aware of?
-
@Eric, That explains a lot. I realized that I pressed the switch on booting up in those cases.
-
@Eric, We defined a macro triggered by pressing the switch, however, it sometimes ends up setting the board in MetaBoot mode. You mentioned in other threads that pressing the switch for a few seconds triggers the MetaBoot macro. Can you specify th…
-
@Eric, I have a question about the iBeacon function. When I enable the iBeacon module, does it only adds payloads to the BTLE packet or it broadcasts additional packet? If it only adds to the BTLE broadcast, which parameters control the broadcasti…
-
@Eric, We've found another issue. Some of the Metawear C sensors cannot be found by both android & iOS device even we replaced the battery. They were running firmware v 1.2.1. However, when I pressed the switch for 2 seconds, they can be …
-
@Eric, I've got the new sensor. Could you keep me posted if your team figure out what was the issue? BTW, what's the difference between hardware design r0.3 and r0.2?
-
@Eric. Here's the compatibility issue. When we upgrade the sensors to 1.2.4/1.2.5, the following code will get a timeout exception after 8500ms when trying to set up a data route. The snippet worked well with 1.2.1. https://gist.github.com/9dd12f0…
-
@Eric, the sensor was worn as a pendant. We only used the sensor to collect accelerations and temperature. I mentioned the case to give you information that the issue is not related to water damage. Sorry for the confusion.
-
We've also tried to set the sensor in MetaBoot mode by pressing the switch for long. However, that doesn't work.
-
@Eric, Is it possible for us to download the firmware bin file? I can only find v1.1.3 and v1.2.1. Sometimes when we found the latest version is not compatible with our application, we would like to roll back to the previous stable version.
-
@Eric, Thank you! I'll definitely look into iBeacon mode. Can you provide some power consumption information of the iBeacon mode? Since it's working over BLE module, does it consume more power compared with the normal BLE broadcasting signals?…
-
@Eric, So, for 2, the question is that when will the following command take effect? setting.configure().setDeviceName("XXX").commit(); Is it on disconnect? Or is it immediate? We discovered that when we execute the macro w/o phone connecti…
-
Do you have a release note for firmware 1.2.5?
-
@Eric, Yes, I've already implemented that in the gist code block. My questions will be: 1. Is it possible for a switch activity handler to call the macro multiple times as configured in the data route? 2. Is the macro which configures the …
-
@Eric, Thank you! I'm using firmware 1.1.3. Does firmware 1.2.1 support the feature you described? If not, I'll try and test on firmware 1.2.4. I'm confused by the third point. Does it mean that by calling Settings.configure().xxxxxx().xxx…
-
@MattThank you very much! It's very helpful!
-
Do you squeeze 4 records in 3 packets or do you leave the remaining 2 bytes empty? Thank you!
-
Thank you, Eric. Can I also have the size of a raw accelerometer record? Is that 4 byte per record?
-
Previously, I am able to set up the timers on some sensors but not the others. So I can see the Timer route ID "2". And those sensors works well. That's why I asked for methods to "reset" the sensors to make sure I can create timers on all the bo…
-
I also tried to reset the board by pulling out the battery for few minutes. After that, I used the latest Metawear sample Android app to connect to each sensor and reset the sensor. After these operations, I started my application and try to conf…
-
@Eric, I've sent you my code snippet via email yesterday. Thank you!
-
I commented out the disconnect and let API handle the connection. Below is my code to 'initialize' the board. I saw that the board disconnected automatically. I think it's the signal indicating the software 'reset' is triggered. …
-
@Eric, Thank you. I'll try that out.
-
In other words, are there ways to 'reset' the device on app start up?
-
Oh.. I checked the sensors today... No luck with resetDevice + MetawearBoard.disconnect. Are there any ways other than tearing them down or serializing the board status?
-
Have tried that out, seemed like working properly.
-
@Eric, in an extreme case, if the phone restarted while the app is running, will resetDevice and then MetawearBoard.disconnect tear down all the routes as well as timers on board?
-
@Eric, a follow-up question: how long will it take for the board to clear its entries if the log module is full?
-
@Eric, I have an initialization phase before I configure the sensors. I removed all my data routes, cleared the timers as well as cleared the log entries. I think resetDevice can help me initializing the board. I will try that out.
-
This only happens to certain sensors. After I took out and put in the battery to reset the board, the data timer is working now. Are there any ways in SDK that can reset the board?