oshug

oshug@oshug.org

2 participants
433 discussions

Re: [oshug] Talks for November OSHUG.
by Paul Tanner 12 Oct '11

12 Oct '11

Hi all. I think this would be a good topic. Maybe several people who've done different things with Jeenodes and home-made ones and a discussion of protocols used or desired. I would appreciate discussion of Zigbee too but that might be too much for one session (or cut into drinking time). Regards, Paul At 09:54 PM 10/10/2011, you wrote: >There has been suggestion of "wireless" as a theme for the OSHUG >meeting on Thursday 24th November. So, this could be licence free >short-range/low power, e.g. 433 MHz and 868MHz and wireless sensor >nodes etc. Perhaps someone has done something interesting with >JeeNodes or EZ430/OpenChronos. Or perhaps something on the radio >amateur side... Any offers of wireless talks? Or failing that, another >theme or general suggestions? Paul Tanner - Virtual Technologies - http://www.virtual-techno.com Tel: +44 1494 581979 Mob: +44 7973 223239 mailto:paul@virtual-techno.com

1 0

Talks for November OSHUG.
by Andrew Back 10 Oct '11

10 Oct '11

Hello, There has been suggestion of "wireless" as a theme for the OSHUG meeting on Thursday 24th November. So, this could be licence free short-range/low power, e.g. 433 MHz and 868MHz and wireless sensor nodes etc. Perhaps someone has done something interesting with JeeNodes or EZ430/OpenChronos. Or perhaps something on the radio amateur side... Any offers of wireless talks? Or failing that, another theme or general suggestions? Cheers, Andrew

1 0

Open Source at Embedded Masterclass, 5 October
by Jeremy Bennett 04 Oct '11

04 Oct '11

I shall be running a session on "Open Source in Embedded System Development" (3:45-4:30) at this year's Embedded Masterclass in Cambridge tomorrow. I should be delighted to meet any OSHUG members who are attending. More details at http://www.embedded-masterclass.com/. Registration for the exhibition and presentations is free. Best wishes, Jeremy -- Tel: +44 (1590) 610184 Cell: +44 (7970) 676050 SkypeID: jeremybennett Email: jeremy.bennett(a)embecosm.com Web: www.embecosm.com

1 0

Re: [oshug] [OH Updates] the issue of patents
by Bryan Bishop 03 Oct '11

03 Oct '11

On Mon, Oct 3, 2011 at 3:23 PM, Mike Hord <mike.hord(a)gmail.com> wrote: > A patent is really (AIUI) just a license to sue an infringing party. A > patent won't be > granted if prior art on the matter exists; OSHW is, by it's very nature, > prior art. > That means Mega-corp, LLC, can't file a patent on a design released by > SparkFun > and then sue SparkFun, since SparkFun's release of the design into the OSHW > community is pretty solid prior art. > Not precisely. It's my understanding that the litigation can still occur even in situations of prior art. There's also a process to invalidate a patent by submitting prior art (I think), but then again some people choose to invalidate patents through the defense litigation process or something? It's more complicated than just "yo dude, prior art" because- even if there is prior art- the patent is still in effect, even if some of the claims might seem invalid, etc. IANAL. - Bryan http://heybryan.org/ 1 512 203 0507

1 0

Thursday reminder.
by Andrew Back 27 Sep '11

27 Sep '11

Hello, Just a reminder that OSHUG #12 will be taking place in a couple of days time. If you plan to attend but haven't registered already: http://oshug.org/event/12 Cheers, Andrew -- Andrew Back mailto:arback@computer.org

1 0

Fwd: Official Google Blog - ANdroid in Spaaace
by Paul Tanner 02 Sep '11

02 Sep '11

Sorry, Dave, we can't let you do that. As it suggests, next is Arduino in space. >Date: Fri, 02 Sep 2011 16:20:17 +0000 >Subject: Official Google Blog >From: The Official Google Blog <FeedTrack(a)gmail.com> > > > ><http://googleblog.blogspot.com/>Official Google Blog ><http://fusion.google.com/add?source=atgs&feedurl=http://feeds.feedburner.co…> >[] ><http://fusion.google.com/add?source=atgs&feedurl=http://feeds.feedburner.co…> > > > > > >---------- >Android in spaaaace! (Part 2) > >Posted: 01 Sep 2011 10:16 AM PDT >Back in December, ><http://googlemobile.blogspot.com/2010/12/android-in-spaaaace.html>Android >ventured into near space, thanks to a weekend of >DIY work, a couple of Nexus S phones, some >weather balloons and the help of ><http://www.youtube.com/watch?v=mSoPJevJyeE&feature=player_embedded>this >little guy. After this first adventure, we knew >it was only a matter of time before Android went further into space. > >On the last manned space shuttle, Atlantis, NASA >sent two Nexus S phones along for the ride as >part of the STS-135 mission. The goal is to use >Nexus S on the International Space Station to >explore how robots can help humans experiment >and live in space more efficiently. > > > >NASA is using Nexus S phones to upgrade a trio >of volleyball-sized SPHERES (Synchronized >Position Hold, Engage, Reorient, Experimental >Satellites), originally developed by MIT. The >phones help the robotic satellites perform tasks >the astronauts used to do, like recording sensor >data and capturing video footage. In the future, >the phones will control and maneuver the SPHERES >using the IOIO board and possibly the ><http://android-developers.blogspot.com/2011/05/bright-idea-android-open-acc…>Android >Open Accessory Development Kit (ADK). > >A couple of our engineers built an open source >sensor logging app that NASA decided was perfect >for running diagnostics with the SPHERES. You >can download the same app yourself from ><https://market.android.com/details?id=com.cellbots.logger>Android >Market. NASA was interested in Android because >itâs an open source platform, which makes it >easy to customize the software on the phone to >meet the specifications required to fly in space >and work with the SPHERES. Nexus S was also a >good fit because of its various sensors and >low-powered, but high-performing, processor. > >You can learn more about the project ><http://www.nasa.gov/mission_pages/station/main/spheres_smartphone.html>on >NASAâs website. We loved being a part of the >final Space Shuttle mission and working to bring >the power of the Android platform to space exploration. > >Posted by Thor Lewis, Creative Lead, and Charles Chen, Software Engineer ><http://feeds.feedburner.com/~ff/blogspot/MKuf?a=Q3Dhf4ts15I:FfFfDDuSDRc:yIl…> >[] > ><http://feeds.feedburner.com/~ff/blogspot/MKuf?a=Q3Dhf4ts15I:FfFfDDuSDRc:-BT…> >[] > ><http://feeds.feedburner.com/~ff/blogspot/MKuf?a=Q3Dhf4ts15I:FfFfDDuSDRc:V_s…> >[] > >You are subscribed to email updates from ><http://googleblog.blogspot.com/>The Official Google Blog >To stop receiving these emails, you may ><http://feedburner.google.com/fb/a/mailunsubscribe?k=4Pjffpq9l2gMyxNvv4bju0W…>unsubscribe >now. Email delivery powered by Google >Google Inc., 20 West Kinzie, Chicago IL USA 60610 Paul Tanner - Virtual Technologies - http://www.virtual-techno.com Tel: +44 1494 581979 Mob: +44 7973 223239 mailto:paul@virtual-techno.com

1 0

Android Accessory Development Kit (ADK - Arduino-based)
by Paul Tanner 02 Sep '11

02 Sep '11

Hi, http://developer.android.com/guide/topics/usb/adk.html This was announced some months ago but few people seem to have engaged with it. Some of us want to get started and we thought that it might be good to identify a few people who would like to come on this journey. Please reply if you have begun any ADK development or plan to do so in the near future. If there are a few of us it might make sense to have a short meetup to share some of what we know. Thx. Regards, Paul Paul Tanner - Virtual Technologies - http://www.virtual-techno.com Tel: +44 1494 581979 Mob: +44 7973 223239 mailto:paul@virtual-techno.com

1 0

Re: [oshug] A fine example
by Paul Tanner 20 Aug '11

20 Aug '11

Thx for this post. Anyone have a link for the electric-motor-assisted open source trail bike I heard mention of? Or was that in my dreams? A page with links like this would come in handy. Maybe there is one already? Paul At 08:02 AM 8/20/2011, you wrote: >Of OSHW in action: > >http://www.kickstarter.com/projects/jkg/quadshot-an-aerobatic-blend-of-rc-h… > >Awesome... > >Chris > >-- >@putt1ck >putt1ck.blogspot.com >skype: putt1ck > >Opinions in this email are my own and may not reflect that of my >clients, past employers, associates, friends, family, pets etc.. > >Documents attached to this email may be in ISO 26300 format: >http://iso26300.info > >_______________________________________________ >oshug mailing list >oshug(a)oshug.org >http://oshug.org/cgi-bin/mailman/listinfo/oshug Paul Tanner - Virtual Technologies - http://www.virtual-techno.com Tel: +44 1494 581979 Mob: +44 7973 223239 mailto:paul@virtual-techno.com

1 0

A fine example
by Chris Puttick 20 Aug '11

20 Aug '11

Of OSHW in action: http://www.kickstarter.com/projects/jkg/quadshot-an-aerobatic-blend-of-rc-h… Awesome... Chris -- @putt1ck putt1ck.blogspot.com skype: putt1ck Opinions in this email are my own and may not reflect that of my clients, past employers, associates, friends, family, pets etc.. Documents attached to this email may be in ISO 26300 format: http://iso26300.info

1 0

Re: [oshug] Open (Source?) Hardware.
by Andrew Katz 19 Aug '11

19 Aug '11

I definitely prefer Open Source Hardware On 19 Aug 2011, at 08:58, Paul Tanner wrote: > I don't think I know what "Open Hardware" is so I'm definitely for OSH. Paul FWIW, I consider Open Source Hardware to be hardware which comes with the recipe/blueprints/source code whatever so that you can reproduce it yourself, and Open Hardware to be hardware that comes with complete specifications so that you can interface to it without any nasty surprises and without necessarily knowing what goes on inside. Open Source is better, but open is definitely a step in the right direction. Open Source hardware almost inevitably relies on open hardware: for example, you can have all the specs to a 555 timer, but you don't need to have the information necessary to build one. Or for even harder hardware, you may have the specs of a bolt (thread pitch, length, tensile strength, general resistance to corrosion etc) but you're unlikely to know the exact makeup of the alloy used to make it, or how it was tempered etc. So most simple electronic components will be open hardware. The only thing you have to be a bit careful about when talking about open source hardware is that it's more difficult to draw the boundary between source and object than it is with software. For example, I'd say an open source car is still an open source car if the complete design docs are available, even if the motors are individual proprietary units and you don't have the source for them, so long as the specification of the motors is sufficient for you to do what you want with them and they do what they are expected to do with no nasty surprises. If you take a maximalist approach, and want instructions sufficient to enable you to synthesise a car from a bunch of atoms, then you will spend most of your life sadly disappointed. It's lucky there is no one like this in the open source software (sorry, free software) world :) Best Andrew

1 0

← Newer
1
...
33
34
35
36
37
38
39
...
44
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

oshug