Yes, solutions of the future are built as mashup. Assembling building blocks.
Some months ago I purchased the Google Voice Kit and I assembled it.
I have also used it for some demo at work. It is a very nice and cost effective way to show how you can build custom solutions using Google Assistant Technology, Speech-to-Text (STT) and Text-to-Speech (TTS).
Now, the idea is: why not to run the OBDII python code on the Google Voice AIY kit?
It should be possible and easy: we have an RPI 3, and Python SDK from Google.
Therefore, this is MY Next Big Thing: my OBDII Python Code running on this:
If you want more details, see older posts and have a look at the MY Connected Car Project
Last but not the least: my idea of playing with "cars" started from a suggestion, and work we did together, from one great collegues and friend: Fabrizio Marini. Thanks guy!
Showing posts with label Google. Show all posts
Showing posts with label Google. Show all posts
Wednesday, January 3, 2018
Friday, April 28, 2017
My AndroidThings 2
One quick update, things are rapidly happening in AndroidThings Space: Intel has announced a porting of its MRAA and UPM libraries to AndroidThings. Have a look here
Obviously it is only a starting point: you'll only drivers for few sensors.
As soon as I have time, I'll try with my LCD display, coming from my Grove kit.
Obviously it is only a starting point: you'll only drivers for few sensors.
As soon as I have time, I'll try with my LCD display, coming from my Grove kit.
Thursday, April 27, 2017
TensorFlow and Image Recognition
How much easy is to do Image Recognition with TensorFlow:
The model is Inception-V3 and it is already pre-trained. Only 200 MB of space on disk and.. it is done.
The language used is Python.
The model is Inception-V3 and it is already pre-trained. Only 200 MB of space on disk and.. it is done.
The language used is Python.
My Android Things
![]() |
| AndroidThings |
Android Things is the new name that Google has adopted for its OS for Internet of Things. Before, the code name was “Brillo”.
Google has made available Android Things to developers, as a
developer preview, at the end of 2016.
At the beginning of April 2017 (06/04), Google has released the DP3, adding for example BLE support, and it has been generally made available.
See the announcement here:
At the beginning of April 2017 (06/04), Google has released the DP3, adding for example BLE support, and it has been generally made available.
See the announcement here:
What is interesting is that it
can be installed on a set of prototyping boards, such as Raspberry PI 3 (RPI3) and Intel Edison
and therefore you can easily test it (obviously if you have one of these boards
available).
Labels:
AndroidThings,
Eclipse,
Google,
Intel,
iot,
Java,
Machine Learning,
MQTT
Subscribe to:
Posts (Atom)
