Topics

1

TinyDuino Processors & TinyShields / Update and Thanks!

« on: December 29, 2015, 12:40:04 PM »

Hi All!

I just wanted to give a little update that I have successfully built out the prototype that I've been working on for the last few weeks (the first version was with a standard Arduino Uno, RedBearLab BLE Shield and a Hall Effect Sensor, and now I'm using TinyDuino (with LiPoly battery)/TinyShield nRF8001/Protoboard/Reed Switch).

There's still more to do, but the basic functionality is there and I'm able to get data back and forth from the TinyDuino/TinyShield BLE device to my iOS app that I'm using to test and it's working GREAT!

Thanks to Ben and all others who have been answering my newbie questions. The answers have all been very helpful and each one has helped move me a little bit forward each time.

Like I said, I still have some more to do (possibly real-time clock and datalogging stuff), but this is the first step!

Thanks Again!

2

TinyDuino Processors & TinyShields / TinyShield BLE nRF8001 20-byte limit?

« on: December 29, 2015, 12:00:39 AM »

Does the nRF8001 BLE Shield have a 20-byte limit per transmission? I thought I saw that in the code but just wanted to verify that.

If that's the case, are there good (or just commonly-used) strategies for breaking up data to send to a Central device if we need to send more than the 20-byte limit will handle?

Thanks!

-Evan

3

TinyDuino Processors & TinyShields / TinyShield BLE - LSBFIRST and MSBFIRST

« on: December 28, 2015, 12:48:12 PM »

Hi!

I noticed that the TinyShield BLE example uses:

Code: [Select]

SPI.setBitOrder(LSBFIRST);
// Do some stuff...
SPI.setBitOrder(MSBFIRST);
Please pardon my ignorance and lack of knowledge in this area (I'm trying to come up to speed, really!!! ), but is there a general rule of thumb as to when this toggling should be done? Are there times at which it should NOT be done?

Thanks in advance!!!

-Evan

4

TinyDuino Processors & TinyShields / Clarification of comment in TinyShield_NRF8001_BLE_Example.ino

« on: December 15, 2015, 01:07:36 PM »

Hi!

I've been working with the TinyShield_NRF8001_BLE_Example project to learn how the TinyShield nRF8001 communicates and I noticed the following comment:

Code: [Select]

//when using this project in the Arduino IDE, delete the following include and rename UART.h to UART.ino

...and I just had some questions:

• Is the intent of the comment to advise us to rename UART.h to UART.ino, and then use that as the basis of future Arduino projects?
• Is there a problem with using TinyShield_NRF8001_BLE_Example.ino as a template for future work?

I was building off the TinyShield_NRF8001_BLE_Example.ino and finally read that comment and I got to wondering, so any advice on that will be appreciated.

Thanks in advance!

-Evan

5

TinyDuino Processors & TinyShields / Basic nRF8001 Advertising Data

« on: December 11, 2015, 08:26:23 PM »

When one uses the basic demo (https://codebender.cc/sketch:91073#TinyShield_NRF8001_BLE_Example.ino) with the TinyShield Nordic, what Service UUIDs does it advertise and are those UUIDs documented anywhere?

Are there default Service and Characteristics that the device is set up with?

I'm using LightBlue on iOS to try to detect the device and I can't really tell if it's in the list.

Additionally, can we use lib_aci_set_local_data() to set/change the name of the device?

Thanks!

6

TinyDuino Processors & TinyShields / Getting Started Tip for those having "programmer is not responding" error

« on: December 03, 2015, 07:09:29 PM »

I just ran into this, being new to TinyCircuits/TinyDuino and thought I would post this just for anyone coming along that might have the same problem...

Basically, I attempted to follow the Getting Started steps (including installing the VCP drivers) and upload the Blink sketch and received a "programmer is not responding... not in sync... problem uploading to board" error:

Arduino: 1.6.3 (Mac OS X), Board: "Arduino Pro or Pro Mini, ATmega328 (3.3V, 8 MHz)"

Sketch uses 1,030 bytes (3%) of program storage space. Maximum is 30,720 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 2,039 bytes for local variables. Maximum is 2,048 bytes.
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00
...

However after a quick email exchange with support, they pointed out that there is a tiny ON/OFF switch on the main microcontroller board, and to toggle it back and forth. (I noticed that mine was actually set to "OFF" which probably didn't help matters.  )

But anyway, after flipping the switch a couple times and leaving it in the ON position, the upload worked just fine -- and I now have a functioning blinking TinyDuino! 

Thanks to the awesome support folks at TinyCircuits!