Sketching in Hardware 2013

1,210 views
1,085 views

Published on

The slides for the presentation at Sketching in Hardware 2013. http://sketching-in-hardware.com

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,210
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Sketching in Hardware 2013

  1. 1. July 18, 2013 Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Shigeru Kobayashi (Institute of Advanced Media Arts and Sciences [IAMAS]) Sketching A New Product Ecosystem Starting with‘Peripheral’Products Sketching in Hardware 2013: PROJECTIONS
  2. 2. How might we sketch new product ecosystems to facilitate mutual understanding between manufacturers and 'makers' to creating innovation? This is the most interesting design challenge for me. Japan is a so called developed country with many highly skilled manufacturers. But there are many restrictions, especially for product liability issues. If we made the relationship between manufacturers and users more flexible, we might be able to facilitate innovation within manufacturers.
  3. 3. Mike Kuniavsky July 20, 2012 Portland, Oregon THE NEW PRODUCT DEVELOPMENT ECOSYSTEM HOW WE WILL SKETCH PRODUCTS AND REINVENT MANUFACTURING IN THE PROCESS Mike Kuniavsky, The New Product Development Ecosystem: How We Will Sketch Products and Reinvent Manufacturing in the Process, Sketching in Hardware 12, 2012 Mike proposed a new product development ecosystem at the last Sketching, consisting of an Amazon like front end and rapid and flexible manufacturing systems as the back end.
  4. 4. Shigeru Kobayashi | Sketching in Hardware 2013 | Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Introduction Case studies • Maker Conference Tokyo 2013 • konashi Make-a-thon I was inspired by the talk. I’d like to introduce two case studies, then talk about a new product ecosystem for ‘peripheral’ products.
  5. 5. Shigeru Kobayashi | Sketching in Hardware 2013 | Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Case 1: KORG’s monotron Maker Conference Tokyo 2013 • A paid conference held at June 15 in Tokyo • About 250 attendees • 5 sponsors including Intel • Keynote talks by Mark Frauenfelder and Eric Pan • Sessions with speakers of manufacturers and makers • Creating maker friendly products • Maker × Maker (Manufacturer) http://makezine.jp/blog/2013/06/nuchack_mct2013.html Maker Conference Tokyo 2013 was a paid conference held at June 15 in Tokyo. There were about 250 attendees. Keynote speakers were Mark Frauenfelder (Make) and Eric Pan (Seeed Studio). I was a PC member and a moderator of two sessions with speakers of manufacturers and makers: ‘Creating maker friendly products’ and ‘Maker × Maker (Manufacturer)’.
  6. 6. Regarding the ‘creating maker friendly products’ session, we invited speakers from Roland D. G. and KORG. The planner of KORG introduced the maker friendly history about ‘monotron’.
  7. 7. monotron is a cheap analogue synthesizer. Initially, the product planner wanted to put synthesizers back into the hands of customers to rediscovery the joy of the synthesizer, since he thought that digital synthesizer have not been as attractive as analogue synthesizers.
  8. 8. In the development process, the hardware designer proposed putting tips on the back of the PCB to let users hack the synthesizers since he felt that monotron is too simple for deep synthesizer lovers like him.
  9. 9. After it's release in April 2010, user immediately understood the developers intent, and hacked the product to create something new.The developers found hacked products at Make: Tokyo Meeting 05 (a Maker Faire in Tokyo in May 2010) and featured the products on their official website in June 2010. http://www.korg.co.jp/Product/Dance/monotron/welove/
  10. 10. Moreover, KORG decided to release the schematic in response to requests from makers in November 2010.
  11. 11. 1 1 2 2 3 3 4 4 D D C C B B A A MODEL TITLE DATE DESIGNED BY 2010.10.13 LM324 12 13 14 IC2D LM324 3 2 1 IC2A LM324 5 6 7 IC2B LM324 1a 9 8 IC2C LM324 411 Va V- IC2E IMX9 Q1 SFW4R-2STE1LF CN1 SN74AHC14 5 6 IC3C SN74AHC14 3 4 IC3B SN74AHC14 1 2 IC3A SN74AHC14 11 1a IC3E SN74AHC14 9 8 IC3D 2SK433 F2 2SK433 F1 2SC4617 Q6 XV09211YNPV20UaNC)1B10K 10K B VR4A SN74AHC14 13 12 IC3F SN74AHC14 147 GND VCC IC3G 2SA1774 Q3 SS-23D03 a6MM KNOB GE) SW1A Bias 1K R17 0.01uC8 1K R34 4.7K R8 820 R2 100 R1 100K R5 VCC VCC RIBBON10KB VCC 100K R13 2.2K R14 0.01u C9 100K R24 0.01u C10 NU R31 1K R26 pitch cuttoff pitch PATCH SELECT cuttoff 330K R42 100K R58 330R62 1uC14 1u C17 XV09211YNPV20U1B10K 10K B VR6A VCC 10K R70 2SK433 F3 VCC 3300pC21 220 R68 4.7K R72 330KR60 1SS355D1 1SS355D2 10u 16V C19 XV09211YNPV20U1B10K 10K B VR7A RK14J11A000G 10K B VR2A audio audio 270KR81 68K R79 22K R77 Headphones TPS61071 1 2 3 4 5 6 SW GND EN VBAT VOUT FB IC1 batteryboxAAAx2 CN2 SLF6028T-4R7M1R6-PF L1 1u C4 1u C1 10u16V C2 820K R3 91K R6 VCC VCC 0.1u C13 0.1uC7 0.1uC18 VCO LFO VCF AMP LFO reset CUTOFF RESONANCE VOLUME +5V 4.7K R35 PITCH LFO RATE XV09211YNPV20U1B10K 10K B VR5A SS-23D03 a6MM KNOB GE) SW1B LFO INT. 100K R61 NUC5 NU C23 100K R39 POWER 2SA1774 Q5 10K R23 27K R10 10K R9 1M R22 TPA6111A2DR 7 2 1 6 IC5A 100pC30 330u6.3V C31 0.01u C26 1u C25 0 R83 0 R65 470 R66 0.1u C27 cw 5.6K R76 XV09211YNPV20U1B10K 10K BVR3A 150K R18 100 R21 0.01u 50V C11 24.49mV@0deg 26.29mV@20deg whole ribbon Vbe offset: 2SC4617 Q8 2SC4617 Q7 2.2K R4 1K R27 47K R37 1KR30 2.2K R64 2.2K R67 2SC4617 Q2 VCO enable 10KR40 10KR38 2.2K R78 LM324 12 13 14 IC4D LM324 411 Va V- IC4E LM324 3 2 1 IC4ALM324 5 6 7 IC4B LM324 1a 9 8 IC4C 2SC4617 Q14 2SC4617 Q13 2SC4617 Q12 VCC 0.01u C20 10K R54 3.3K R53 18K R46 10K R59 27K R57 68KR50 0.1u C28 TPA6111A2DR 84 VDD GND 3 BYPASS 5 SHTDN IC5B VCC 1u C29 10KR44 6.8K R75 10K R56 cuttoff 220K R28 470 R29 10K R25 68K R82 0.1u C6 3300p C22 10K R16 10K R15 VCC 0 R41 10u C15 VA VAVA 330uF 6.3V C3 B2B-ZRaLF)aSN) CN5 100u6.3V C33 23mm 0.2W InternalSpeaker HNS-XXXX LGY2209-0101FC CN3 LGY2209-0101FC CN4 2SC4617 Q10 1K R51 10K R52 0.1u C16 10K R45 100VR1 F-3362S B100OHM-MO 28.08mV@40deg 1K R20 2SC4617 Q9 SML-E12UWT86 LED1 NUR71 NUR69 2SC4617 Q11 47 R48 47 R43 390 R49 1K R33 4.7K R32 10K R55 10K R47 10u 16V C24 100pC32 1K R11 VA VA 1 R12 VA VA CLEARSHAFT NU R19 Bias 10K R73 VA 2SC4617 Q4 47K R80 1K R7 VCC 10K R63 4.7K R74 10K R36 NU C12 VR3B VR6B VR7B VR4B VR5B VR2B SW1C FRAME GROUNDS TP1 pitch TP2 gate TP3 GND TP4 Vbias TP5 VCC TP6 rate TP7 LFO TP8 VCO TP9 cutoff LINE IN VCF gate Any modification to any monotron will immediately void its warranty. Korg or any of its affiliates will not accept responsibility for any damages, personal loss or injury that may result from any modification to the device. SCHEMATIC FOR PUBLIC RELEASEmonotron Details of this schematic are subject to change without notice. TATSUYA TAKAHASHI This is the circuit diagram of monotron. Makers can hack and expand a monotron easily with the aid of the diagram.
  12. 12. About half a year later, monotron nominated at Makey Awards 2011 as the ‘best product documentation’ in June 2011.
  13. 13. A few months later, KORG released derivative products of monotron inspired by hacked products, monotron DELAY and monotron DUO, as answers in November 2011. The hidden concept was 'what if KORG hacked monotron?'.
  14. 14. So far, KORG has been opening products by putting hints and releasing circuit diagrams, with no claims from customers. Since these are not mainstream but ‘peripheral’ products, the developers have been able to major advancements instead of being lead by the voices of established customers or dealers.
  15. 15. Shigeru Kobayashi | Sketching in Hardware 2013 | Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Case 1: KORG’s monotron Lessons learned from monotron • Embedding messages for makers transforms a product into an open platform • The planner thought analogue is the key of putting synthesizers back into the hands of customers, but open platform is the key • Even after opening the circuit diagram, everyone purchased monotron to hack instead of making clones (cost and/or respect?) • Not a simple open components but an attractive and hackable product is the key, and releasing hackable products is an effective way of open innovation Still there are gaps between maker and player communities, but they are trying to approach connecting communities.
  16. 16. Shigeru Kobayashi | Sketching in Hardware 2013 | Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Case 2: konashi Make-a-thon konashi Make-a-thon • Held on June 1 and 22 at OpenCU by loftwork, a global open platform for creative talents, in collaboration with Yukai Engineering, an engineering farm of robots • konashi is a physical computing toolkit to create wireless devices for smartphones and tablets created by Yukai Engineering I was a adviser of the make-a-thon
  17. 17. http://konashi.ux-xu.com/documents/ Technically, konashi is consisting of a Bluetooth Low Energy wireless module and software libraries for Objective-C and JavaScript. But they promote not as BLE evaluation kits but a physical computing toolkit to communicate with designers and artists to expand possibilities of wireless products and services.
  18. 18. There were over 30 participants consist of iOS developers, engineers, web designers, artists and planners. We divided into 6 teams randomly.
  19. 19. http://www.flickr.com/photos/opencu/sets/72157633896214841/ I facilitated idea sketching sessions. As a result, there were over 230 ideas from about 30 participants in 2 hours.
  20. 20. http://www.flickr.com/photos/opencu/sets/72157633896214841/ In addition to the idea sketching sessions, we introduced the software library for Objective-C in 1 hour with the aid of Grove toolkit. A conversion board for konashi and Grove were really useful to let participants try various inputs and outputs in a short period of time.
  21. 21. https://www.facebook.com/CuttingBoxTool Additionally, a student of IAMAS introduced his domain specific design tool to design boxed to be fabricated with a laser cutter.
  22. 22. https://www.facebook.com/CuttingBoxTool
  23. 23. https://www.facebook.com/CuttingBoxTool
  24. 24. https://www.facebook.com/CuttingBoxTool
  25. 25. http://www.flickr.com/photos/opencu/sets/72157633896214841/ At the end of the first day, each team presented what they will make by the end of the 2nd day. Members of each team kept working together online and offline.
  26. 26. 擬人化パッチ(仮) トイレットペーパー編 大塚 翔 平田 孝広 間下 知紀 松川 佳弘 Yuji Miyano 玉城 絵美山岸 昂介巽 孝介 13年6月23日日曜日 http://kakeru.in/e-team/ This is an example of one of the six teams.
  27. 27. 擬人化パッチ 擬人化パッチ(仮) トイレットペーパー編 特攻野郎Eチーム トイレ時間を有効活用 トイペケースを恋人にする トイペケース恋人機能 →使用具合でコミュニ  ケーションをはかる 13年6月23日日曜日 http://kakeru.in/e-team/ The selected idea was a patch to anthropomorphize a toilet paper holder. Usually, a restroom is a public space. But once a person entered a restroom stall, the stall became a personal space. ‘anthropomorphize patch’ is a way to personalize a restroom stall with a smartphone application that plays voices by favorite characters.
  28. 28. 2013年6月1日の夕方 Facebookで特攻野郎Eチーム が集結 13年6月23日日曜日 http://kakeru.in/e-team/ After the end of the first day, they created a Facebook group to communicate online.
  29. 29. 3日後の 2013年6月3日 トイペケースのガラガラ検出に向け、 間下主任が色々なセンサを試しだす 13年6月23日日曜日 http://kakeru.in/e-team/ The engineer evaluated sensors and implemented electronics.
  30. 30. 6日後の 2013年6月6日 皆でトイペとトイペケースについて議論する 13年6月23日日曜日 http://kakeru.in/e-team/ The team members discussed together how to realize the idea.
  31. 31. 8日後の 2013年6月8日 間下主任が実機(トイペケース)で実験開始! 13年6月23日日曜日 http://kakeru.in/e-team/ They made various hardware sketches.
  32. 32. 9日後の 2013年6月9日 擬人化パッドのケースを検討 13年6月23日日曜日 http://kakeru.in/e-team/ And the product designer found a way to realize good enough cases in a short time.
  33. 33. 9日後の 2013年6月9日 擬人化キャラの台詞を検討 恥ずかしい台詞がどんどん出てくる 13年6月23日日曜日 http://kakeru.in/e-team/ They generated ‘embarrassing’ phrases, and iOS developers implemented an iOS application.
  34. 34. 2013年6月16日(日) Eチームが秋葉原に集まる 13年6月23日日曜日 http://kakeru.in/e-team/ They worked together to finish making a prototype. In the end of the second day, all teams presented their prototypes and all participants were really excited.
  35. 35. http://kakeru.in/e-team/ This is the movie of the final prototype demonstrated in the end of the second day.
  36. 36. Another prototype by a different team. If a person drunk too much and feel like throwing up while train ride home, the wearable device displays how deep he is drunk and send a message to his wife in emergencies.
  37. 37. Shigeru Kobayashi | Sketching in Hardware 2013 | Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Case 2: konashi Make-a-thon Why we didn't start with the technology, BLE • Many applications have been proposed by precedent manufacturers already • Starting with technology and constraints will narrow participants vision and they will think like 'what we can make with Bluetooth Low Energy' • Wanted to let participants create ideas of wireless devices and services and make hardware sketches as if it were air
  38. 38. Collaboration with ‘wonderfl’ Shigeru Kobayashi, Online code sharing for ActionScript and physical computing Incentives for web designers and developers, Sketching in Hardware 09, 2009 The toolkit is expanding to attract wider range of audiences. In 2009, I have introduced an online IDE for physical computing in ActionScript in collaboration with KAYAC, ‘physical × wonderfl’, at Sketching 09.
  39. 39. Shigeru Kobayashi | Sketching in Hardware 2013 | Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Case 2: konashi Make-a-thon konashi.js Recently, Yukai Engineering released ‘konashi.js’, an iOS application to be combined with a popular online IDE for JavaScript (also developed by KAYAC).
  40. 40. Shigeru Kobayashi | Sketching in Hardware 2013 | Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Case 2: konashi Make-a-thon Lessons learned from konashi Make-a-thon • Working on a team produces diversity • Sketching wireless devices and applications in hardware is not so difficult anymore • Toolkit enable people realizing‘peripheral’ideas (that can’t survive in planning sessions with PowerPoint presentations) • Still there are gaps between prototypes and products, but toolkit developers can be platforms
  41. 41. How might we sketch new product ecosystems to facilitate mutual understanding between manufacturers and 'makers' to creating innovation? This is the design challenge I’d like to try.
  42. 42. Manufacturers Makers Users (e.g. players) Hackable Products and Components Hacked ProductsNew Product Opportunities New Product Ideas Consumer Products This is a plan of the new product ecosystem between manufacturers, users and makers. Manufacturers produce hackable products with grayscale licenses like the Creative Commons license. Makers make deliberative products and communicate with other communities (e.g. players). The communication ball will make manufactures more flexible and facilitate innovations.
  43. 43. Flexible Warranties Company warrants to return your device to factory defaults by making best efforts to restore original firmware and functionality, subject to any mechanical or electrical damage due to modifications. You Brick it, we’ll restore it: Sunday, July 19, 2009 The Firmware warranty: Tom Igoe, After Sketching: Best Practices for Opening Product Development, Sketching in Hardware 09, 2009 The idea regarding licenses is based on the suggestion by Tom Igoe at Sketching 09 in 2009.
  44. 44. http://opencontent.uct.ac.za/files/siteimages/image/degreesofopenness.jpg What if we have Creative Commons like gray-scaled licenses regarding product liability between 'full warranty' and 'at your own risk’?
  45. 45. Peripheral Products Peripheral Products Main Stream Products It might be difficult to start changing from main stream for manufacturers. But we might be able to start with ‘peripheral’ products such as musical instruments or wearable smart accessories.
  46. 46. I feel signs of ‘peripheral’ products from new hardware projects such as C.24 by Miselu.
  47. 47. July 18, 2013 Xerox Palo Alto Research Center, Palo Alto, California, U.S.A. Shigeru Kobayashi (Institute of Advanced Media Arts and Sciences [IAMAS]) Sketching A New Product Ecosystem Starting with‘Peripheral’Products Sketching in Hardware 2013: PROJECTIONS

×