Laura
About
- Username
- Laura
- Joined
- Visits
- 3,668
- Last Active
- Roles
- Administrator
Comments
-
But I don't understand, it already does this for you in my Xcode example on Github?
-
makefile? for mac? I am confused. What are you talking about specifically?
-
thanks for the update @DylanMach1
-
Very feasible, just follow some examples from Google to push the CSV file to your drive. You could even have the local drive linked to your device and have the MetaWear or MetaBase app changed (since the source code is available) to dump automatica…
-
Found a dumb error in the code. Will push update shortly.
-
Not enough information.
-
When the SDK is initialized, a bunch of additional stuff happens in the background where the code reads information about the hardware on the board using our own protocol over BLE (we have the metawear characteristic that we use to send info using a…
-
Still working on it.
-
Why not use the LED that is already on board?
-
Maybe it is an issue with ble caching on android.
-
@ericf, Awesome, you are already on your way to becoming a debug pro!
-
Thanks @jjm345 for the update.
-
This isn't a metawear related questions. This is a UI question. Here the App is looking for a Fragment by ID which is some kind of UI (probably an Activity wheel or similar). What is happening? What is the offense? This is not very helpful at al…
-
Oh are you using Windows 10 MetaBase? Because that App doesn't work and is no longer supported (hasn't been for 2 years). I removed it from the store because it is confusing many people. Please confirm and use iOS or Android MetaBase only.
-
Well this is a thread for metawear and not generic coding. As you pointed out, it's running just fine from the command line or the icon so it's not really a metawear related issue. This means that your crontab is wrong. Probably the cron is no…
-
Well it does tell you the issue. The type is not int for libmetawear.mbl_mw_gyro_bmi160_set_range(s.device.board, 2000.0); It's (according to the CPP docs) mbl_mw_gyro_bmi160_set_range (MblMwMetaWearBoard *board, MblMwGyroBoschRange range)…
-
Please factor your code correctly in this thread and take a screenshot of the issue when you run the script. I cannot follow anything in your comment.
-
So if it's in the diagnostic but not working in your code, then the issue is with your code syntax. The module info does get populated when the SDK initializes (right after a connection is secured).
-
HI @ericf, I don't understand your setup at all. It sounds like you may be going over the BLE specs here.
-
No one has mentioned issues with the BMP280 on this forum. Maybe you can check the datasheet and bosch forum?
-
Worst case though, keep them in the charger.
-
Best is to keep them in sleep mode and charge them for 2 hours ever 2-3 months. Keep them at a good ambient temperature with minimal temperature fluctuations.
-
Its probably an issue with your actual coding syntax.
-
What does the diagnostic say from the MetaBase App?
-
Does your sensor have a bmi160 or a bmi270? You are using the bmi160 calls.
-
Ok I checked today and the MetaWear.mbl_mw_led_stop_and_clear(device.board); function was working very well for me. var MetaWear = require('../index'); MetaWear.discoverByAddress('c8:4b:aa:97:50:05', function(device) { console.log("DISCOVER BY…
-
I don't think you are running the script correctly, you need to be in the right folder for one.
-
@ericf, Based on your description, it seems more likely one of the sensors had some extra leftover data in the memory that it needed to download.
-
I have 0 information to comment on this. What script? Which metabase? our image? pi4? is the executable working? Does it work without your script? What are you trying to do?????? I will close this thread if not proper info is provided.
-
I just updated the MetaHub App. You can do a git pull on the MetaBase-Node folder. https://github.com/mbientlab/MetaBase-Hub