Thursday, December 19, 2013
Maker Yellow Pages...
We just start debating the possibility of the creation of some kind of "yellow pages" for the Maker Movement... a metadata about projects, code, diagrams, makers, makerspaces, etc...
A simple database but very useful for all levels of knowledge...
Friday, December 13, 2013
PSClub "Danuts Hour" Event...
Prezados,
queria convidar a todos pra um chat-evento online (ou áudio ou vídeo). Assuntos
em torno de RaspberryPIs, Arduinos e Microcontroladores... estaremos tentando
fazer 1 mini-evento por mês ou a cada 15 dias... esta já é nossa segunda
tentativa, SÁBADO 14/DEZ, 10:30hs AM, horário de Brasília.
Texto chat,
ou áudio ou vídeo...
A
iniciativa faz parte de nosso “PSClub” (fizemos num outro post)... postaremos
aqui o link pra quem tiver um tempinho...
Abraços a
todos.
Saturday, December 7, 2013
Saturday, November 30, 2013
Tuesday, November 26, 2013
Sunday, November 17, 2013
Scratch + Micro PC I/O - enorme potencial
Após baixar mais material e ler mais sobre o Scratch e o CodeClub, estou ainda mais convencido de que o Scratch e o CodeClub são parceiros IDEAIS para o nosso USB Micro PC I/O (dispositivo geral USB para controlar e interagir com a realidade física)...
O site do Scratch lista os 3 exemplos existentes de interação entre Scratch e realidade física:
http://www.makeymakey.com/
http://info.scratch.mit.edu/WeDo
https://www.sparkfun.com/products/10311
Estarei estudando mais em detalhes estes (citados) para definir melhor o escopo de uma interface entre o Scratch e o Micro PC I/O, e desde já, percebo o ENORME POTENCIAL que existe em um dispositivo assim interfaceando com o Scratch e que sejam ao mesmo tempo SIMPLES e de BAIXO CUSTO...
Scratch e o Mundo Físico...
Após ler e analisar o material disponível do Projeto CodeClub, surgiu a idéia de usar o Projeto do dispositivo Micro PC I/O em conjunto com este, afinal ambos partilham objetivos comuns: ajudar no ensino de conceitos básicos de programação.
No caso do CodeClub e alvo é o PC e crianças, e no caso do nosso Micro PC I/O o alvo incluem tb crianças e um dos nossos objetivos é prover material para que pessoas leigas aprendam os fundamentos do SOFTWARE FÍSICO e seus conceitos de programação básicos...
Na figura, o gato Felix é o logo da linguagem Scratch, utilizada no projeto CodeClub para ensinar crianças os primeiros passos da interação com computadores... o dispositivo do meio é nosso projeto USB Micro PC I/O, que é um meio bem simples e barato de conectar o PC ao mundo físico através de USB, permitindo que o usuário consiga controlar coisas no mundo material através de comandos no PC... até o momento estávamos usando C e Python, e ontem eu testei pela primeira vez a possibilidade de usar o Scratch, e logo de início os testes mostram que não haverá muita dificuldades pra fazer ambos funcionarem em conjunto...
Informações e códigos estão sendo disponibilizados aqui:
https://sites.google.com/site/scratchfisico/home
Agora, ao fazer o download de mais material e ler mais sobre o projeto CodeClub, fico muito mais motivado com a possibilidade de usar o Micro PC I/O em conjunto com o Scratch e em possível cooperação com o projeto CodeClub...
Eu já conhecia o Scratch, desde anos atrás quando conhecí o Google APP INVENTOR, que tb tem inspiração no Scratch. Além disso, o RaspberryPI traz em sua instalação original (RaspBian) instalado o Scratch, pois este tb almeja servir de instrumento de aprendizado para crianças...
No momento estou analisando todas informações a respeito dos projetos citados, com o intuito de definir uma forma de interação entre o PC I/O e o Scratch, que seja útil para os iniciantes aprenderem a programar...
No caso do CodeClub e alvo é o PC e crianças, e no caso do nosso Micro PC I/O o alvo incluem tb crianças e um dos nossos objetivos é prover material para que pessoas leigas aprendam os fundamentos do SOFTWARE FÍSICO e seus conceitos de programação básicos...
Na figura, o gato Felix é o logo da linguagem Scratch, utilizada no projeto CodeClub para ensinar crianças os primeiros passos da interação com computadores... o dispositivo do meio é nosso projeto USB Micro PC I/O, que é um meio bem simples e barato de conectar o PC ao mundo físico através de USB, permitindo que o usuário consiga controlar coisas no mundo material através de comandos no PC... até o momento estávamos usando C e Python, e ontem eu testei pela primeira vez a possibilidade de usar o Scratch, e logo de início os testes mostram que não haverá muita dificuldades pra fazer ambos funcionarem em conjunto...
Informações e códigos estão sendo disponibilizados aqui:
https://sites.google.com/site/scratchfisico/home
Agora, ao fazer o download de mais material e ler mais sobre o projeto CodeClub, fico muito mais motivado com a possibilidade de usar o Micro PC I/O em conjunto com o Scratch e em possível cooperação com o projeto CodeClub...
Eu já conhecia o Scratch, desde anos atrás quando conhecí o Google APP INVENTOR, que tb tem inspiração no Scratch. Além disso, o RaspberryPI traz em sua instalação original (RaspBian) instalado o Scratch, pois este tb almeja servir de instrumento de aprendizado para crianças...
No momento estou analisando todas informações a respeito dos projetos citados, com o intuito de definir uma forma de interação entre o PC I/O e o Scratch, que seja útil para os iniciantes aprenderem a programar...
Saturday, October 5, 2013
Open Royalties Power...
This week I think that 2 related announcements CONFIRM how powerful is the idea of a "Open Royalties" Model...
Arduino Team just announce 2 powerful cooperation around 2 projects: THE ARDUINO TRE and the Intel Galileo...
We did talk about it few months ago here...
http://physicalsoftware.blogspot.jp/2013/07/openroyalties.html
I think that this can be a "proof" that, by having a good "Open Royalties" Model, you can enjoy a lot of business cooperation, sometimes from powerful partners like Intel and Texas Instruments, and this will make your own business better...
The Arduino TRE
The Intel Galileo
Congratulations to the Arduino Team.... the courage to pursue the innovation now is paying back...
Arduino Team just announce 2 powerful cooperation around 2 projects: THE ARDUINO TRE and the Intel Galileo...
We did talk about it few months ago here...
http://physicalsoftware.blogspot.jp/2013/07/openroyalties.html
I think that this can be a "proof" that, by having a good "Open Royalties" Model, you can enjoy a lot of business cooperation, sometimes from powerful partners like Intel and Texas Instruments, and this will make your own business better...
The Arduino TRE
The Intel Galileo
Congratulations to the Arduino Team.... the courage to pursue the innovation now is paying back...
Sunday, September 22, 2013
Micro PIC Burner...
Tested with Daniel Perron "burnLV" Python and Giorgio Vazzana "RPP" C...
First prototype working... very slow...
Just completed some low level routines to make it speed up... not tested yet fully... the new routines works individually and
succeed with "bulk erase" the chip and "read device id"...
Excited about this new device...
Site is here (still writing it):
https://sites.google.com/site/micropicburner/
Valter
First prototype working... very slow...
Just completed some low level routines to make it speed up... not tested yet fully... the new routines works individually and
succeed with "bulk erase" the chip and "read device id"...
Excited about this new device...
Site is here (still writing it):
https://sites.google.com/site/micropicburner/
Valter
Sunday, September 15, 2013
Molec (PIC) Low Voltage Programming...
Daniel Perron showed me
Daniel Perron showed me his RaspberryPI PIC Low Voltage Programming... he pointed it as the another way to program Moleculines... quite nice...
Here is the post (forum) where he announced it:
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=37&t=41245
I did test, works nice...
Also, I tested it using a hardware interface for higher voltage and the same DC Voltage Converter I am using with ArdPicProg and RPP... it also works fine with HIGH VOLTAGE PROGRAMMING (with few modifications)...
The good news is that it is written in PYTHON, so, it is more easy for the average RasPI user to look and change the code...
I will put information and code (already there) in the following link:
https://sites.google.com/site/kit2pic/
Daniel Perron showed me his RaspberryPI PIC Low Voltage Programming... he pointed it as the another way to program Moleculines... quite nice...
Here is the post (forum) where he announced it:
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=37&t=41245
I did test, works nice...
Also, I tested it using a hardware interface for higher voltage and the same DC Voltage Converter I am using with ArdPicProg and RPP... it also works fine with HIGH VOLTAGE PROGRAMMING (with few modifications)...
The good news is that it is written in PYTHON, so, it is more easy for the average RasPI user to look and change the code...
I will put information and code (already there) in the following link:
https://sites.google.com/site/kit2pic/
Saturday, September 7, 2013
Friday, September 6, 2013
Saturday, August 31, 2013
OpenRoyalties = Diff + Patch
For me, a working and stable "OpenRoyalties" standand will be the equivalent of the "diff & patch" commands and its role for the open source code...
The current stage of "open hardware" is the equivalent to have open source code out there, but no mechanism to allow its practical application (adoption)...
open code + (diff & patch) = open code "goes" to a new level (growth = LIFE)...
open hardware + openroyalties = the design can display "life" on its own... growth and partnerships...
The current stage of "open hardware" is the equivalent to have open source code out there, but no mechanism to allow its practical application (adoption)...
open code + (diff & patch) = open code "goes" to a new level (growth = LIFE)...
open hardware + openroyalties = the design can display "life" on its own... growth and partnerships...
A logo for the OpenRoyalties idea...
Just playing around the idea for a “logo” for the OpenRoyalties… after 3 sketches I did one that may be useful...
Here is the a quick “about”, for the open_royalties_logo_3 (draft 3 below).
The arch is in the same style as in the Open Source and Open Hardware logos.
Text Font Name: Ubuntu, meaning “elevating humankind to a higher level by means of behavior”
The “=” (equal sign) stands for “treat others designs the equal way you want others to treat your own design”, which in turn is the Maker’s version of ‘Do unto others as you would have them do unto you’.
The idea here is to promote growth, which should be the natural way to think about good designs, and the goal is to “attach” this factor to every design we can do, so others can benefit from it and at the same time cooperate with its growth, and on the opposite side we can use others people designs and kickback authors, helping to promote the design growth.
The stronger the design (from others) I am using inside my product/service, the strong my own product/service can be, so paying royalties “works for my product” as a consequence.
Personally, I believe it is a POWERFUL mechanism to achieve growth and reliability into products/services, by adopting STRONG and RELIABLE designs when building (Making) something, and the open royalties mechanism can help to achieve this level of designs.
Also, it is crucial to have a CLEAR and TRANSPARENT relationship between cooperating designs, otherwise the resulting product (of the relationship) will tend to be somewhat artificial and short lived.
Finally, “why use others people design instead of doing it yourself?”, can be a great question… and I already have an answer to this question but it is another subject and will make the text too much long if I try to write it here, so, I just like to say that by “cooperating work” we can achieve, TODAY, END RESULTS much more powerful and reliable than we can, ourselves, achieve alone tomorrow...
If you want a copy or may want to try to improve, feel free to get your own copy on the following links...
[get your copy here, gDrive - share URL logo_1]
[get your copy here, gDrive - share URL logo_2]
[get your copy here, gDrive - share URL logo_3]
draft 1
draft 2
draft 3 (a temporary "logo" for the idea of OpenRoyalties)
Tindie is already working with the concept (https://www.tindie.com/about/
Disclosure: this is not any kind of "official proposition" for the logo, I just like the idea and want a symbol to use when talking about it.... I did it because the idea of OpenRoyalties will be playing an important role inside the project I am doing, the Molec Project (https://sites.google.com/site/softwarephysical/), and I want a picture to use when talking about it...
Monday, August 26, 2013
"Open Royalties" = Kickback...
Looks like I am not alone when thinking about "royalties" to designers (authors), when we, create projects using their work...
This blog post from Tindie (Tech Indie Crowdfunding) deals with more or less the same idea...
http://blog.tindie.com/tindie-launches-open-designs-and-kickbacks.html
This blog post from Tindie (Tech Indie Crowdfunding) deals with more or less the same idea...
http://blog.tindie.com/tindie-launches-open-designs-and-kickbacks.html
Sunday, August 18, 2013
Compiling and Using JAL V2 Under RaspberryPI
Get the JAL v2 compiler compiled under Raspberry PI also...
Works fine!
[How to compile]
https://sites.google.com/site/jalraspberrypi/
Works fine!
[How to compile]
https://sites.google.com/site/jalraspberrypi/
Molec on Linux
YES, we also have a software-package for everyone to try Molecs using Linux from a USB PenDrive... so that there is NO NEED to install, just plug-boot-and-run...
1) Molec Uploader (TinyBootUpLoaderLinux)
2) ArdPicProg (to build Molecs from Scratch)
3) JAL and JALLIB Compiler
4) Files to build again (the same package)
5) Of course, 8GB Flash Drive
https://sites.google.com/site/moleconlinux/
1) Molec Uploader (TinyBootUpLoaderLinux)
2) ArdPicProg (to build Molecs from Scratch)
3) JAL and JALLIB Compiler
4) Files to build again (the same package)
5) Of course, 8GB Flash Drive
https://sites.google.com/site/moleconlinux/
Friday, August 16, 2013
Molec Proto 3
A Platform for makers to put "intelligence" into all 3D Printed Object...
A way for home users to change (programming) behavior of all home appliances...
A "computer" for any kind of physical stuff, so that it can have its own needed "intelligence"...
A way for home users to change (programming) behavior of all home appliances...
A "computer" for any kind of physical stuff, so that it can have its own needed "intelligence"...
Molecs evolving...
The old PIC18F14K50 Prototype looks very "big" compared to the 12F1822... lol...
Thursday, August 15, 2013
Social Soft and Physical Software are the "hot things", according to the "CROWD"...
This is "good news" for the Moleculine Project, it shows that the "CROWD" is rewarding "social software" and "physical software" as the "hot things" out there...
https://sites.google.com/site/softwarephysical/
https://sites.google.com/site/softwarephysical/
Tuesday, August 13, 2013
100x Easier Software - Quantum Leap
From time to time a “jump” can happen into productivity of
ideas and simplicity of usage (new paradigm), and this is exactly what is
happening within the “fusion” of electronics and software, a creating of
something higher than both, easier than both and will allows us to THINK AND DO
beyond the both universes together… IT IS THE PHYSICAL SOFTWARE PARADIGM SHIFT!
The combination of the PC Paradigm Shift, the Smartphone
Paradigm Shift and the Physical Software Paradigm Shift creates a NEW UNIVERSE
of “software”, a quantum leap compared to the traditional software. Also, it is
a “jump” of productivity and simplicity over the traditional electronics…
The difference is not about an improvement, it is about a
real “jump”, equivalent to the electrons quantum leap in the atoms…
The social and economic impact of the current level of
evolution will be, of course, greater than the previous ones…
*Disclosure: the background of this picture is from a website... don't remember the link... I'm hoping to find it in some old backup and credit it here...
Found it: http://paneandov.com/connecting-the-dots/
Tuesday, August 6, 2013
Wednesday, July 31, 2013
Physical Soft and Moleculine Presentation Doc...
Did a quick PDF Presentation around the Concept of Physical Software and Moleculine...
PDF Download here:
https://sites.google.com/site/softwarephysical/home/PS_Quick_Presentation-v0.1.pdf?attredirects=0&d=1
New Website will be here:
https://sites.google.com/site/softwarephysical/home
PDF Download here:
https://sites.google.com/site/softwarephysical/home/PS_Quick_Presentation-v0.1.pdf?attredirects=0&d=1
New Website will be here:
https://sites.google.com/site/softwarephysical/home
More parts... (for Kits)
At least for this first (small) batch, around 80% of parts are Made In Japan, then remaining majority are Made In Taiwan... not sure about all the PICs, some are from Thailand... Trimmers are from HongKong (China?)...
Tuesday, July 30, 2013
Building the "kits"...
Order a small batch of parts for the Molec Ardu-Factory and Raspi-Factory...
Here are some of the parts...
Here are some of the parts...
Monday, July 22, 2013
SeeedStudio Royalties
I ask SeeedStudio about their "Royalties Method" and here is the answer:
"The royalties are varied among products. Normally, you get $7.00 to $8.00 from $10.00"
Nice.
"The royalties are varied among products. Normally, you get $7.00 to $8.00 from $10.00"
Nice.
Saturday, July 20, 2013
OpenRoyalties
Finally, after years thinking that "it is possible, it can be achieved, it can be done", I think I've found a financial model to serve as basis for all OpenSourceSoftware and OpenHardware activities... one that promotes less conflict between free-software and commercial initiatives...
When I build a product using someone else design (open design), how much should be the distribution of the profits, how much should go to the author and how much should I keep to myself?
In my mind, I was looking for something that represent the MOST STABLE POSSIBLE values, bringing the best benefit for all parties on the equation. There MUST be something that the author feels compensate and the producer (the ones that build and sell the commercial product) feels stimulated to work with...
For years I was looking at the subject and feeling that it represents a barrier for the progress of the OpenSource Movement, and a tremendous waste for businesses...
Yesterday, FINALLY, I believe I had reach the "light" on the subject...
Brave pioneers are opening news territories and testing ideas about how to do it... like:
Kindle offer 70% to authors and keep 30% for itself...
Apple offer 70% for developers and keep 30% for itself...
Quirky offer 30% to authors of ideas, manufacture, sells and keep 70% for itself...
And, for OpenHardware (and I think OpenSource Software too) the Winner Is...
It maybe in front of your eyes all the time: ARDUINO ROYALTIES MODEL...
The following worksheet on Google Docs I describe the Arduino 10% Royalties Model, and you can test different values there to see how much percent it will give you, depending on the profitability model that you chooses...
https://docs.google.com/spreadsheet/
The worksheet uses Chris Anderson Rule of 50% Profitability Model, as expressed in his book, Makers - The Next Industrial Revolution... (you can test others values to see how much it impact distribution of values), in combination with the Arduino Royalties Model...
By choosing to use Anderson's 50% Profit Rule, you end up keeping 70% of the profit on the sales for yourself, and paying the other 30% to the author of the design you are using...
Using Richard Kock's thinking, Arduino Royalties Model is something like a GOOD BUSINESS GENS...
And this is the way I believe we can go and seek for success, by adopting Arduino Royalties Model in the "genetics" of good products and services that uses OpenSoftware and OpenHardware as tools...
I think that this model is a solid and tested foundation to build upon, adapting it if necessary to particular circumstances...
After all, this is, I think, the correct thinking; "it is not success that will allow you to build good gens, but the use of good gens that will generate success". (Richard Dawkins).
So, when using others people design or when someone else wants to use my design, this Arduino Royalties Model with Chris Anderson Profitability Rule can be a strong candidate for a rule to follow...
Valter
You can find more about Quirky Model here:
http://www.quirky.com/home/terms
When I build a product using someone else design (open design), how much should be the distribution of the profits, how much should go to the author and how much should I keep to myself?
In my mind, I was looking for something that represent the MOST STABLE POSSIBLE values, bringing the best benefit for all parties on the equation. There MUST be something that the author feels compensate and the producer (the ones that build and sell the commercial product) feels stimulated to work with...
For years I was looking at the subject and feeling that it represents a barrier for the progress of the OpenSource Movement, and a tremendous waste for businesses...
Yesterday, FINALLY, I believe I had reach the "light" on the subject...
Brave pioneers are opening news territories and testing ideas about how to do it... like:
Kindle offer 70% to authors and keep 30% for itself...
Apple offer 70% for developers and keep 30% for itself...
Quirky offer 30% to authors of ideas, manufacture, sells and keep 70% for itself...
And, for OpenHardware (and I think OpenSource Software too) the Winner Is...
It maybe in front of your eyes all the time: ARDUINO ROYALTIES MODEL...
The following worksheet on Google Docs I describe the Arduino 10% Royalties Model, and you can test different values there to see how much percent it will give you, depending on the profitability model that you chooses...
https://docs.google.com/spreadsheet/
The worksheet uses Chris Anderson Rule of 50% Profitability Model, as expressed in his book, Makers - The Next Industrial Revolution... (you can test others values to see how much it impact distribution of values), in combination with the Arduino Royalties Model...
By choosing to use Anderson's 50% Profit Rule, you end up keeping 70% of the profit on the sales for yourself, and paying the other 30% to the author of the design you are using...
Using Richard Kock's thinking, Arduino Royalties Model is something like a GOOD BUSINESS GENS...
And this is the way I believe we can go and seek for success, by adopting Arduino Royalties Model in the "genetics" of good products and services that uses OpenSoftware and OpenHardware as tools...
I think that this model is a solid and tested foundation to build upon, adapting it if necessary to particular circumstances...
After all, this is, I think, the correct thinking; "it is not success that will allow you to build good gens, but the use of good gens that will generate success". (Richard Dawkins).
So, when using others people design or when someone else wants to use my design, this Arduino Royalties Model with Chris Anderson Profitability Rule can be a strong candidate for a rule to follow...
Valter
You can find more about Quirky Model here:
http://www.quirky.com/home/terms
Subscribe to:
Posts (Atom)