Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Amarino Toolkit
Home
+ new post
About this group
Join this group
Amarino with Custom Communication Pins
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Free Beachler  
View profile  
 More options Sep 7 2012, 1:48 am
From: Free Beachler <fbeach...@gmail.com>
Date: Thu, 6 Sep 2012 23:48:11 -0600
Local: Fri, Sep 7 2012 1:48 am
Subject: Amarino with Custom Communication Pins
Print | Individual message | Show original | Report this message | Find messages by this author

Last spring I published a project named "Open Bluetooth Intents" (OBI).
 It's a bluetooth library that works with Amarino-Embed -- which eventually
will be consumed into OBI.

Right now the only code it contains is firmware for Amarino-like
communication at https://github.com/tenaciousRas/open-bluetooth-intents.
 The firmware allows for Amarino sketches that use pins besides the default
0/1 (TX/RX).

The firmware is derived from Amarino but does _not_ extend the Print class.
 It *compiles* for the example sketches that accompany the code, but with
one caveat (below).  The firmware should work on Arduino 022 and lower, if
necessary, but that's not tested.  It even has a "HelloAmarinoWorld"
example.

The caveat is:  the examples _only work_ if I wrestle with having
SoftwareSerial.h on the $PATH (unix).  I just verified this and pushed an
update.  That's where I could use some help to get this across the finish
line -- fix the #include path problem and help with testing and/or bugfixes.

Would anybody be able to test the firmware, or offer suggestions as to why
I have to wrestle with the include path?  Right now it's hardcoded for an
Arduino 1.0.1 installation on OS X.  I've already tried the usual C-style
"include-path-fixes", I think.  Would anybody be interested in forming a
Github team to collaborate on the project?  As stated in a recent post, I
have a roadmap that includes the Android side of things and much more.

Best Regards,
Free Beachler
Boulder, CO


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google