movesense

问题 I’ve followed the setup instructions for movesense for windows [1] and run the below cmake command, which seem to work okay. However, when I run the ninja command it fails on step 9/9 complaining that the LTO version doesn’t match the configuration. Any advice? $ cmake -G Ninja -DMOVESENSE_CORE_LIBRARY=../MovesenseCoreLib/ -DCMAKE_TOOLCHAIN_FILE=../MovesenseCoreLib/toolchain/gcc-nrf52.cmake ../samples/blinky_app/ Error: [9/9] Linking CXX executable Movesense FAILED: Movesense cmd.exe /C "cd .

问题 There's already a good answer on the technical details and constraints of timing the gyro measurement: Movesense, timestamp source of imu data, and timing issues in general However, I would like to ask more practical question from the Android app developer perspective working with two sensors and requirement for high accuracy with Gyro measurement timing. What would be the most accurate way to synchronize/consolidate the timestamps from two sensors and put the measurements on the same time

问题 I'm building an app which analysis the step of the person that wears the sensor, and I haven't found and mention in the API or the exapmle apps for what are the unit of measurement (in the linear acceleration and angular velocity). I believe that timestamp is milliseconds (correct me if I'm wrong), but what are the others? Thanks! 回答1: Time Api returns data in uS $ wbcmd --port com9 --op get --path Time { "response": 200, "responsestring": "HTTP_CODE_OK", "operation": "get", "uri": "/net

问题 I have looked trough the "logbook" and "datalogger" APIs and there are no way of telling that the data logger is almost full. I found the API call with the following path "/Mem/Logbook/IsFull". If I have understood it correct this will notify me when log is full and the datalogger has stopped logging. So my question is: Are there a way to know how much of the memmory is currently in use so that I do a cleanup old data (need to do some calculations on them before they are deleted) before the

问题 I'm trying to get the LogBook data over BLE to my App. This works fine for JSON, the data seems accurate. But it takes along time due to the JSON encoding. Getting the SBEM data is way faster. But I can't find any documentation on the encoding. I found out that the "Content" string is Base64 encoded. It starts with SBEM which means, it is uncompressed as stated here: https://bitbucket.org/suunto/movesense-device-lib/src/5bcf0b40644a17d48977cf011ebcf6191650c6f0/MovesenseCoreLib/resources

问题 I am unable to change the Accelerometers sampling rate using the mobile API: I am subscribing using these commands: String strContract = sb.append("{\"Uri\": \"").append(connectedSerial).append(URI_MEAS_ACC_26).append("\"}").toString(); Log.d(LOG_TAG, "subscribeToSensor 1" + strContract); subscribedDeviceSerial = connectedSerial; mdsSubscription = mMds.builder().build(this).subscribe(URI_EVENTLISTENER, strContract, new MdsNotificationListener() { I have tried these strings: static private

问题 Based on the response on this question here: What are The Unit of measurement and extrapolating, it seems that when reading the timestamps from the imu datasource (imu9), the timestamp may not be coming from the base system, but rather from some other source. Is this the case? As an aside, has anyone had any luck syncing the time on the devices to an external device, like an ios or android device? I know the time can be set, but it always seems like I'm about a second off. Would this possibly

问题 Have investigated sample code to subscribe DataLogger to move sensors. https://bitbucket.org/suunto/movesense-mobile-lib/src/master/android/samples/DataLoggerSample/ But failed to subscribe to my own whiteboard resource. As example used jump counter from jump count sample. https://bitbucket.org/suunto/movesense-device-lib/src/master/samples/jumpmeter_app/ WB_RES::LOCAL::SAMPLE_JUMPCOUNTER_JUMPCOUNT::LID And have tried to connect to it by DataLoggerConfig.DataEntry[] entries = {new

问题 I am going through logs done by a sample movesense app and the accelerometer logs contain values like this: { "Body": { "Timestamp": 110033, "ArrayAcc": [{ "x": 0.60114991664886475, "y": 6.7324004173278809, "z": 3.0943653583526611 }, { "x": 0.78317141532897949, "y": 7.0437526702880859, "z": 3.3697926998138428 }] }, "Uri": "ECKIAEBA141A/Meas/Acc/26", "Method": "PUT" } Why the array contains two values from one timestamp? 回答1: Good answers above. To (hopefully) clarify the situation: the reason

问题 I'm looking to integrate logging to the EEPROM in my custom movesense firmware. Reading the docs on the logging service, I've verified that I have the logging system configured with my custom whiteboard objects, and that logging is enabled (logging state is set to 3), with the following code: WB_RES::DataLoggerConfig dConfig; WB_RES::DataEntry dEntry, dEntry1; WB_RES::DataLoggerStateValues::Type dlstate = WB_RES::DataLoggerStateValues::Type::DATALOGGER_LOGGING; dEntry.path = "/App/Object1";