Matt
About
- Username
- Matt
- Joined
- Visits
- 350
- Last Active
- Roles
- Administrator
Comments
-
@fryjs The MetaMotionR hardware has the battery charge status pin connected to its processor, no soldering required. It also has a new signal connected to the USB 5V line, so that it knows when it is plugged in. The battery charger only indicate…
-
@didlich For a SPI bus you need to connect four signals: * Slave Select (SS) on MetaWear to the Chip Select (CS) of the target chip * Master Out Slave In on MW to the input of the target chip * Master In Slave Out on MW to the output of the target…
-
@didlich The simplest option would be to switch to the SPI bus for communication. The protocol they are using is really meant for a UART and poorly adapted for I2C and SPI. It should work with our SPI API which handles more raw operations which …
-
@didlich I could only look briefly at the spec for the NFC chip. They seem to have tunneled a custom protocol through i2c in an unconventional manner. The big difference between your node code and the MetaWear API code, is that the MetaWear API R…
-
@alessandromontanari The SDK is more bound to the softdevice versions than the chip revisions, because the APIs change with each soft device revision. Generally, if the softdevice release says that is compatible with rev2 silicon, then you should…
-
@alessandromontanari Are you running the MetaWear firmware or custom firmware? Reusing fixed function pins generally will not work with the way GPIOs are exposed to the APIs in firmware. On the MetaWear C base model, you can use SDA and SCL a…
-
@Alex Regarding correlating a specific Accelerometer and Gyroscope sample, I would recommend using the timestamps received with the responses from the OS. There is a feature of BLE which will make it work quite nicely. The radio communicates on a…
-
@obiwahn A number of logistic reasons. The BMX160 is a new multi die package, and not yet available through distributors. MetaMotionR has been in development for some time and BMX was not an option when it began. We prefer the performance of the…
-
@Edwardsj BLE is default unencrypted. When a device is paired with a central, the BLE spec has provisions to run AES CCM mode. We have considered possibilities for firmware encryption of the MetaWear protocol, but there is a penalty to energy…
-
@alessandromontanari All R series devices past and present are on nRF51 revision 2 silicon. C series devices may have revision 2 or 3 depending on when they were ordered. The nRF51 revision can be identified by the laser marking on the certified r…
-
@biofeedbackuwa That larger pancake motor would work with MetaWear. The typical way to connect the motor is via the 3V pin next to the high current driver. The other important constraint for a motor is the drive current -- the default battery we …
-
@Christopher The coin cell holder is made of nickel plated phosphor bronze and is non magnetic. There may be ferrous material in the EMI shield on the radio module, or there may be residual polarization in the battery. For best results an AC type…
-
@Alex What kind of demagnetizer are you using? Fixed magnet demagnetizers do not sufficiently depolarize the ferromagnetic materials in the coin cell battery. An AC type demagnetizer can completely nullify the magnetic polarization. Here is an e…
-
@kspeng There is no built in current measurement output on any of our products. I recommend using an external 3V power supply, with a fast sampling Ammeter inline. If you really want to measure on a scope, you will need to get a current sense ampl…
-
@Oferorgal A "Scan Response" has special meaning in BLE terminology. It is essentially an extended 2nd advertisement so a device can communicate more about itself before being connected to. From the context of your call back it seems that it wi…
-
@mamaj The bluetooth protocol stack which is loaded on MetaWear supports slave mode only, and has no capability to scan ad packets. This might be a capability we can support in future revisions of MetaWear.
-
@KingTalullah The HCD driver is setup as "open-drain" and only provides a pull down to sink the current of an attached high current peripheral. In order to drive a piezo buzzer, an additional resistor needs to be added in parallel with the buzzer t…
-
@KingTalullah I have a MetaWearC r0.3 device set up in the lab running the latest release firmware and it is generating the HCD signal as expected. Could you provide more details about how you are testing -- what is connected to the pin, which…
-
Hi @wsuite, we're glad you figured out what was wrong. Let us know if you have any other issues!
-
Hi @northCountry If you desire the servo motors to be synchronized you could wire the control signal in parallel. At present there can only be one channel for a servo motor -- the nRF51 supports up to four hardware PWM channels using its built…
-
@alanhortz If you can wire two CR2016 in parallel that would work well as a power source. Both batteries should be fresh when installed, because lithium coin cells do not tolerate reverse current well -- which the weaker of the two would receive if…
-
Hi @mclean2016 Presently this mode is not supported in iOS. BLE privacy depends on pairing device with a phone and using it only with that one phone. Most users are using the sensors anonymously, and the MAC address is used (especially in Androi…
-
@Bram : On the MetaWearC model the battery voltage and SoC supply voltage are equivalent. The nRF51822 ADC can be configured measure the supply pin against the internal voltage reference to measure the battery voltage.
-
@kspeng The high discharge required to stream accelerometer data will tend to droop the battery voltage and battery level reading. When disconnecting the load is reduced and the battery is able to recover. Using the throttling settings to reduce…
-
@gtx77 The MetaWear i2c implementation follows the typical i2c convention of using read and write register addresses immediately following the device address. This chip is a little different but it should not be a problem. When doing an i2c w…
-
@jhurley : Pin definitions look good. The only thing that seems out of place is the SPI_MODE -- We are using mode 3 compared to your mode 1. If that does not help, I would trace through the code to make sure all of the pins are configured into the…
-
@jhurley Simply attach a debug header to the MetaWearC, and connect it to the "Debug Out" connector on the nRF51 DK with a 10 pin cable as shown here: You will need to have the battery in the device and the DK should pick it up. Make sure …
-
@seamus : No problem. Hmm, yeah they must have meant to say "isn't" in that comment. My C++ is a bit rusty, so I was not even aware you could overload member functions like that. Cheers.
-
Looks like they are using OPERATION_MODE_NDOF by default in their class header: bool begin ( adafruit_bno055_opmode_t mode = OPERATION_MODE_NDOF );
-
@seamus : For test purposes I would advise a minimum delay of 100-200 ms. Delays less than 40-50ms in the Android thread may still result in BLE commands being issued in the same connection period, which would undo the delay. That being said, if y…