Sorry that you're having problems, one difference between newer versions of the Arduino IDE and older ones is the way the board is selected.  Under Tools... Board, make sure "Arduino Pro or Pro Mini" is selected.  Then under Tools... Processor, make sure the Processor is set to "Atmega328 (3.3V, 8MHz). 

Try that and see if it helps.

Thanks,

Ken
TinyCircuits

Hi,

Can you post the actual code for sending this, its difficult to see in just a screenshot.  A few questions - what is BPM and what values can it have?  You are also hardcoding to send just a single byte at time, this should be the size of all the data that being sent in any given transaction.

Thanks,

Ken
TinyCircuits

Hi Jeff,

This is definitely a known problem and sorry that it caused you pain.  It's the big reason that the USB TinyShield now has an option to come out at the top instead of the side, for mechanical conflicts like this.  The top mount USB connector version will work with terminal block board as is (no modifications needed).  The other option is to stick another board in between the USB TinyShield and the terminal block board, but this is not ideal in some cases. 

https://tiny-circuits.com/tinyshield-usb.html

The big issue with a system like there is isn't a perfect universal solution, some of the boards are wider (namely the TinyScreen and the Terminal Block board), while others are long (like Bluetooth, WiFi, etc), so different ones will have different mechanical conflicts.  We are shrinking other boards (like WiFi and Bluetooth), to hopefully make this less of an issue.

Again, sorry for your pain, but you came up with a good solution!

Ken
TinyCircuits

Awesome!  Great to hear.

Ken

Very sorry about this - we have a new app that fixes this that is being tested now, it should be up on github later today (July 20, 2015).

Thanks,

Ken
TinyCircuits

Very sorry about this - we have a new app that fixes this that is being tested now, it should be up on github later today (July 20, 2015).

Thanks,

Ken
TinyCircuits

Unfortunately I don't think this will work well and you'll have quite a bit of screen jitter.  Part of the issue is that you won't be able to buffer up the data in RAM since there isn't enough, so you'll have to write it out to the screen as it comes in, so the refresh rate will be very bad and noticeable.  Also the data for one frame is quite a bit (6144 bytes), with all the radio overhead you will be really limited on how many frames you can send per second.

Thanks,

Ken
TinyCircuits

We have an updated version that fixes this now and we're currently testing it.  We plan to update this to github and our website later today (July 20, 2015).  Thanks for your patience.

Ken
TinyCircuits

Hi Zangetsu,

This is indeed possible, we'd recommend using just the TinyScreen Basic Kit to do this.  When the USB is plugged in, it will attach to the TinyDuino UART lines, and the Raspberry Pi can support the USB Host connection.  There is an example of how to do this here:  http://blog.oscarliang.net/connect-raspberry-pi-and-arduino-usb-cable/

However then you'll need to create you own Arduino sketch to process serial data from the Raspberry Pi and display this on the TinyScreen - you'll also need to create an application on your Pi to send the data you want to display.

Good luck!

Ken
TinyCircuits

Not sure what the problem was, but this is working now. 

Thanks,

Ken
TinyCircuits

Excellent point - we do plan on offering a new GPS option with external antenna in late summer 2015.

Thanks,

Ken
TinyCircuits

Sorry about things being out of stock, we've gotten caught up and most everything is back in stock now.

Ken
TinyCircuits

Thanks for ordering the TinyScreen!  We'll be sending out a new Kickstarter update in the next few days - we are building up units and will begin shipping some later this week.  However we're still waiting on the bulk of the raw OLED modules which should be here in early to mid Feb.  We're shipping out in the order that the orders were received if we have all of the materials needed for the shipment, so if you preorder now, yours should ship in late Feb.

Thanks,

Ken

longs are indeed 32-bit on the AVR architecture, if you only need 16-bit, just change them to int, which would be fine for the accelerometer. 

The microSD card writes are indeed fairly slow, and the SD card library will consume about 1/2K of RAM as well for buffering.  We are working on a SRAM TinyShield which will hopefully be out in early to mid January.

Thanks!

Ken
TinyCircuits

In the Arduino world, the term "pin" is a bit confusing, and doesn't necessary match up with the true physical pin or port on the actual microcontroller.  The TinyDuino uses the same Arduino "pin" mapping as the standard Arduino Uno, so the SPI signals also have pin numbers assigned to them.  SS is pin 10, MOSI is pin 11, MISO is pin 12, and SCK is pin 13. 

Since the LED is connected to SCK, you can toggle this on and off by writing to Arduino pin 13.

Hope that clears it up!

Ken
TinyCircuits