Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Geoff Chapman <geoff.chapman@mmbresearch.com>
Cc: Stefan Schmidt <stefan@osg.samsung.com>,
	Alexander Aring <alex.aring@gmail.com>,
	linux-wpan@vger.kernel.org
Subject: Re: atusb availability
Date: Wed, 27 May 2015 09:00:33 -0400	[thread overview]
Message-ID: <11929.1432731633@sandelman.ca> (raw)
In-Reply-To: <CAHwW5636ELxe1FU+pf5GjnvsgV3hAWqiYgSLmf4OSgi4SMW+CA@mail.gmail.com>


Geoff Chapman <geoff.chapman@mmbresearch.com> wrote:
    > Hi Stefan,

    >> Nice, that you used the same schematics and build your boards!

    >> Do you by any chance have the infrastructure to handle a bigger run of
    >>these? We often get asked about such a device >for easy hacking with
    >>ieee802154 from a laptop or desktop without any SPI connections
    >>available.

    > This is exactly the reason I am interested in the device.  I want to
    > set up a simple 6LoWPAN network, but do not have any SPI connections.

I also want to be able to speak 15.4 from a laptop system for diagnostics
and ease-of-coding purposes.  It did take me awhile to figure out that the
atusb was not a product I could buy... I too would be interested.

    >> The run Werner did was around 100 - 120 pieces for atusb IIRC. My best
    >>guess would be that there could be interest for another 50-100
    >>depending on the promotions.

    > So-far, we have only built two atusb modules.  We are in the process
    > of loading the firmware and testing, so I am not sure if the boards
    > are functional yet.  At this time, we are not set up to produce
    > numbers in the 50-100 range.   This may change once we successfully
    > test the boards.

Put it on kickstarter?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


  parent reply	other threads:[~2015-05-27 13:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 15:55 atusb availability Geoff Chapman
2015-04-23  8:30 ` Alexander Aring
2015-05-13 17:24   ` Geoff Chapman
2015-05-13 20:05     ` Alexander Aring
2015-05-22 13:05     ` Stefan Schmidt
2015-05-26 18:29       ` Geoff Chapman
2015-05-27  9:06         ` Stefan Schmidt
2015-05-27 13:00         ` Michael Richardson [this message]
2015-05-27 13:18           ` Stefan Schmidt
2015-05-27 13:29           ` Ralph Droms (rdroms)
2015-05-27 13:32             ` Stefan Schmidt
2015-05-27 13:47               ` Alexander Aring
2015-05-27 16:04                 ` Ralph Droms (rdroms)
2015-06-02 16:03                   ` Alexander Aring
2015-05-27 16:06               ` Ralph Droms (rdroms)
2015-05-27 16:36                 ` Stefan Schmidt
2015-05-27 14:00             ` Michael Richardson
2015-05-27 16:07               ` Ralph Droms (rdroms)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11929.1432731633@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=alex.aring@gmail.com \
    --cc=geoff.chapman@mmbresearch.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=stefan@osg.samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox