Juzzer

https://www.ghielect...d=19617&page=1?

Martin and I would like to take the lid off some ongoing work - the Radius Wearables Core and Radius Reference Hardware. This work is still in its early days and will continue to evolve, but here's an early peek...

The Radius Wearables Core (RWC) is a .Net Micro Framework codebase and accompanying Windows, Windows Phone, Android and iOS companion apps, all written in managed code. The idea behind the RWC is to create an integrated software framework for connected wearables - watches, pendants, and all manner of headless devices too.

The RWC software is free and open-source for non-commercial uses. Commercial use requires a separate license. Distribution of the mobile phone companion apps through app stores involves a separate approval process through Microsoft, Apple and/or Google, though it is intended that the default app (which we will publish) will accomodate custom wearable devices you might create. The RWC software is tested on the Radius, Molecule, IoT Dx Blue, GHI hardware and Netduino.

The Radius Watch reference hardware v1, includes:

• STM32F401 - 82Mhz 512kb Flash 96kb ram or STM32F411 - 96Mhz 512kb Flash 128kb ram
• 1.26inch Sunlight readable Sharp MemoryLCD
• BLE113 Bluetooth LE with separate vreg
• MPU-9150 9 DOF sensor
• MPR121 Capacitive touch sensor 
• Battery backed up RTC
• 8mb External SPI flash
• Buzzer
• Lipo power with charge circuit
• 3 User buttons
• Power on/off push button

The Radius Wearables Core software features include :

• Mobile-phone companion apps for all major mobile platforms
• Installable Radius apps (requires filesystem - apps are managed from your PC or mobile device)
• Notification routing and display
• Radius app sandboxing and resource-management
• Structured messaging over any serial channel (e.g., BLE on the Radius Reference Hardware)
• Support for private host-app-to-Radius-app messaging (create your own app protocols)
• Support for mobile device control (call management, media controls, volume, messaging, etc.)
• Support for headless devices (annunciators and sensors)
• Support for multiple Radius-compatible devices attached to a single host (mobile device or PC)
• A touch or button driven navigation framework

And on the Radius Hardware, includes default apps for:
App Menu, Watch, Notifications and a touch-gesture navigation framework

The source code is available at : https://github.com/M...leDotNet/Radius

Demo video is upcoming...

Yes that module can be used.

I am building a similar device over the coming weeks running NETMF so if your interested drop me an email.

That is showing free ram - the other 92kb has been gobbled up by starting up TinyCLR

This can be reduced by removing features from the firmware, for instance a base STM firmware is only using about 40kb

true forces the GC to run and release memory.

You want Debug.Print(Debug.GC(false).ToSting());

The 1MB flash contains TinyBooter, TinyCLR and your user program.

RAM is seperate.

What strikes me so odd, is that we all thrive to build IOT DEVICES, whilst most vendors (RP, Netduino, GS, Intel etc.) do not add the INTERNET component as simple as possible. In IOT the bridge to to I is through the wifi - not through a cable.

 

I know we are in the early days, but spending hours and $$ on Building basic drivers does not drive value for my customers. They need a device that quickly deploy, seamless integrate with their existing infrastructure and cobe without any concern.

 

I love the N+ series. Yes there are gaps. But missing WIFI across the vendor stack is a big surprise!

How about one of these

 Boards.jpg   138.15KB   9 downloads

@Mario - i posted this picture yesterday that Chris deleted after a few hours...

Lets see how long it lasts this time 

The problem isn't Netduino, but MS which almost dropped the MF project. That's a big blame, at least in my opinion.

Also an over enthusiastic admin who deletes posts and has an interesting marketing perspective....

Mint! - glad my fell Kiwis are jumping in with both feet, i will have to check it out and lucky for me i land in AKL next Friday 

ST port..

STM32F427 - 2mb Flash, 256kb ram running NETMF 4.3.1

Bulegiga BLE113 module in xBee form factor

Yes i wrote all the code using VS2013 - all pretty vanilla stuff, very easy to do.

Quick write up here: http://www.ingenuity...ble-on-wp8.aspx

Couldn't help myself so the Zumo got a quick make over

An just cause i know a few of your guys are wondering... i got my Galileo yesterday