IOIO board for SN10 to Samsung Galaxy Note 4

On Saturday, May 9, 2015 at 4:42:25 PM UTC-5, Sean Fidler wrote:
Thanks Robert. Great info. Soldering iron warming up...

Sean, this is EXACTLY why many of us prefer the Oudie to building a "supposedly" superior system out of more "up to date" technology and software.

Buy it, hook it up, configure the displays to your liking (or use the defaults if you are really lazy or computer-challenged) and go fly. Oudie does that, at a fraction of the cost of the higher end systems.

Myself, I'll probably stick to my SN10+Oudie2+PF setup until something significantly better is available (and I don't see XCsoar as "significantly better" than SYM, in the ways I use my moving map). Right now, what I'm watching is the evolution of iGlide and the sunlight readability of the big iPhones - when they meet my personal criteria of features and cost-effectiveness, then I might retire my Oudie. My SN10, OTOH, stays until it dies, I like it so much...

And, as a big believer in redundancy - I would never want my primary nav display to also be my retrieve phone, etc. That's just asking for Murphy to have a go!

Meanwhile, have fun with your science project and keep us posted!

Kirk
66

Kirk - I'm not sure I understand your point here. Are you saying that choosing to "roll our own" custom HW interface solution is a negative? If someone either doesn't have the skills or simply doesn't want the hassle then they can purchase any one of a number of pre-built cables and interface solutions that will work with XCSoar. This is no different than hooking an Oudie up to instrumentation - you can "roll you own" or buy a pre-made cable and interface kit. Maybe I missed the point...

On Monday, May 11, 2015 at 12:31:34 PM UTC-5, kirk.stant wrote:
On Saturday, May 9, 2015 at 4:42:25 PM UTC-5, Sean Fidler wrote:
Thanks Robert. Great info. Soldering iron warming up...

Sean, this is EXACTLY why many of us prefer the Oudie to building a "supposedly" superior system out of more "up to date" technology and software.

Buy it, hook it up, configure the displays to your liking (or use the defaults if you are really lazy or computer-challenged) and go fly. Oudie does that, at a fraction of the cost of the higher end systems.

Myself, I'll probably stick to my SN10+Oudie2+PF setup until something significantly better is available (and I don't see XCsoar as "significantly better" than SYM, in the ways I use my moving map). Right now, what I'm watching is the evolution of iGlide and the sunlight readability of the big iPhones - when they meet my personal criteria of features and cost-effectiveness, then I might retire my Oudie. My SN10, OTOH, stays until it dies, I like it so much...

And, as a big believer in redundancy - I would never want my primary nav display to also be my retrieve phone, etc. That's just asking for Murphy to have a go!

Meanwhile, have fun with your science project and keep us posted!

Kirk
66

On Monday, May 11, 2015 at 6:31:13 PM UTC-5, wrote:
Kirk - I'm not sure I understand your point here. Are you saying that choosing to "roll our own" custom HW interface solution is a negative? If someone either doesn't have the skills or simply doesn't want the hassle then they can purchase any one of a number of pre-built cables and interface solutions that will work with XCSoar. This is no different than hooking an Oudie up to instrumentation - you can "roll you own" or buy a pre-made cable and interface kit. Maybe I missed the point...

Robert, perhaps I didn't make myself clear enough. I think it's great that you guys are putting together systems to integrate new displays with new software in interesting ways - but please go back and look at your previous post; to most of the glider owners in my club it would be totally incomprehensible! For them (and me, largely because I'm not interested in spending the time putting together a custom made system) even as simple a system as the Oudie seems too complicated. So when Sean makes long statements about how superior his custom approach is to something like the Oudie, he doesn't realize that for many, his approach is totally out of the question.

I personally like SYM because I can customize it to do exactly what I want. I'm sure XCsoar can be setup equally well, but I'm not interested in learning a whole new UI for no real performance difference. TopHat looks interesting on a Kobo mini eink tablet as a stand-alone device for club ships. I've used WinPilot (OK) and tried StePla (too "german"!); even looked at LK8000 (too many numbers that I really don't care about) - but keep coming back to SYM because I'm used to it.

iGlide looks really interesting...

Anyway - whatever a person uses is fine if it makes the soaring experience more fun and safer!

Cheers,

Kirk
66

LK8000 on Mio and cabled to Power Flarm and V7.

Pros: Forum support that is excellent, beautiful interface, easy task declaration to Flarm, fully utilizes pitot, barometric sensor, etc of V7/Flarm. Handles Turn area tasks and MATS easily. Simulator for PC

Cons: Requires some "hacking" of chosen device. Requires windows based platform. Only source of MIO compatable cables (my device) is glidertools. Requires home study to fully understand and configure many options

Lane
XF

Well, you're certainly right that my original post is generally incomprehensible to anyone who is not already familiar with an IOIO interface. But, in my defense, the post was not really meant to describe how to actually build one - its pretty clear that Sean was already experienced with it.

This gets me thinking, though, how many people may actually be interested in putting an Android XCSoar device in their cockpit, connect it to their 302 or Flarm, etc. but are afraid to do so because of a lack of very detailed instructions. I wonder if there would be much interest in an article in Soaring Magazine that shows in detail how to build and use an IOIO based solution? Anyone out there want to read such an article?

Robert


On Tuesday, May 12, 2015 at 11:53:27 AM UTC-5, kirk.stant wrote:
On Monday, May 11, 2015 at 6:31:13 PM UTC-5, wrote:
Kirk - I'm not sure I understand your point here. Are you saying that choosing to "roll our own" custom HW interface solution is a negative? If someone either doesn't have the skills or simply doesn't want the hassle then they can purchase any one of a number of pre-built cables and interface solutions that will work with XCSoar. This is no different than hooking an Oudie up to instrumentation - you can "roll you own" or buy a pre-made cable and interface kit. Maybe I missed the point...

Robert, perhaps I didn't make myself clear enough. I think it's great that you guys are putting together systems to integrate new displays with new software in interesting ways - but please go back and look at your previous post; to most of the glider owners in my club it would be totally incomprehensible! For them (and me, largely because I'm not interested in spending the time putting together a custom made system) even as simple a system as the Oudie seems too complicated. So when Sean makes long statements about how superior his custom approach is to something like the Oudie, he doesn't realize that for many, his approach is totally out of the question.

I personally like SYM because I can customize it to do exactly what I want. I'm sure XCsoar can be setup equally well, but I'm not interested in learning a whole new UI for no real performance difference. TopHat looks interesting on a Kobo mini eink tablet as a stand-alone device for club ships. I've used WinPilot (OK) and tried StePla (too "german"!); even looked at LK8000 (too many numbers that I really don't care about) - but keep coming back to SYM because I'm used to it.

iGlide looks really interesting...

Anyway - whatever a person uses is fine if it makes the soaring experience more fun and safer!

Cheers,

Kirk
66

Yep

On Tuesday, May 12, 2015 at 7:42:24 PM UTC-4, wrote:
Well, you're certainly right that my original post is generally incomprehensible to anyone who is not already familiar with an IOIO interface. But, in my defense, the post was not really meant to describe how to actually build one - its pretty clear that Sean was already experienced with it.

This gets me thinking, though, how many people may actually be interested in putting an Android XCSoar device in their cockpit, connect it to their 302 or Flarm, etc. but are afraid to do so because of a lack of very detailed instructions. I wonder if there would be much interest in an article in Soaring Magazine that shows in detail how to build and use an IOIO based solution? Anyone out there want to read such an article?

Robert


On Tuesday, May 12, 2015 at 11:53:27 AM UTC-5, kirk.stant wrote:
On Monday, May 11, 2015 at 6:31:13 PM UTC-5, wrote:
Kirk - I'm not sure I understand your point here. Are you saying that choosing to "roll our own" custom HW interface solution is a negative? If someone either doesn't have the skills or simply doesn't want the hassle then they can purchase any one of a number of pre-built cables and interface solutions that will work with XCSoar. This is no different than hooking an Oudie up to instrumentation - you can "roll you own" or buy a pre-made cable and interface kit. Maybe I missed the point...

Robert, perhaps I didn't make myself clear enough. I think it's great that you guys are putting together systems to integrate new displays with new software in interesting ways - but please go back and look at your previous post; to most of the glider owners in my club it would be totally incomprehensible! For them (and me, largely because I'm not interested in spending the time putting together a custom made system) even as simple a system as the Oudie seems too complicated. So when Sean makes long statements about how superior his custom approach is to something like the Oudie, he doesn't realize that for many, his approach is totally out of the question.

I personally like SYM because I can customize it to do exactly what I want. I'm sure XCsoar can be setup equally well, but I'm not interested in learning a whole new UI for no real performance difference. TopHat looks interesting on a Kobo mini eink tablet as a stand-alone device for club ships.. I've used WinPilot (OK) and tried StePla (too "german"!); even looked at LK8000 (too many numbers that I really don't care about) - but keep coming back to SYM because I'm used to it.

iGlide looks really interesting...

Anyway - whatever a person uses is fine if it makes the soaring experience more fun and safer!

Cheers,

Kirk
66

I wonder if there would be much interest in an article in Soaring Magazine that shows in detail how to build and use an IOIO based solution? Anyone out there want to read such an article?

Absolutely!

I'm going to put a video up of the process from my end. I'm estimating an hour or so of actual work to get this running. We will see how that estimate works out. Parts are on route.

There are serial to Bluetooth converters and multiplexers out there to
buy off the shelf. No need to build anything. Simply plug the
converter into your computer and connect your moving map via Bluetooth.

On 5/12/2015 5:42 PM, wrote:
Well, you're certainly right that my original post is generally incomprehensible to anyone who is not already familiar with an IOIO interface. But, in my defense, the post was not really meant to describe how to actually build one - its pretty clear that Sean was already experienced with it.

This gets me thinking, though, how many people may actually be interested in putting an Android XCSoar device in their cockpit, connect it to their 302 or Flarm, etc. but are afraid to do so because of a lack of very detailed instructions. I wonder if there would be much interest in an article in Soaring Magazine that shows in detail how to build and use an IOIO based solution? Anyone out there want to read such an article?

Robert


On Tuesday, May 12, 2015 at 11:53:27 AM UTC-5, kirk.stant wrote:
On Monday, May 11, 2015 at 6:31:13 PM UTC-5, wrote:
Kirk - I'm not sure I understand your point here. Are you saying that choosing to "roll our own" custom HW interface solution is a negative? If someone either doesn't have the skills or simply doesn't want the hassle then they can purchase any one of a number of pre-built cables and interface solutions that will work with XCSoar. This is no different than hooking an Oudie up to instrumentation - you can "roll you own" or buy a pre-made cable and interface kit. Maybe I missed the point...
Robert, perhaps I didn't make myself clear enough. I think it's great that you guys are putting together systems to integrate new displays with new software in interesting ways - but please go back and look at your previous post; to most of the glider owners in my club it would be totally incomprehensible! For them (and me, largely because I'm not interested in spending the time putting together a custom made system) even as simple a system as the Oudie seems too complicated. So when Sean makes long statements about how superior his custom approach is to something like the Oudie, he doesn't realize that for many, his approach is totally out of the question.

I personally like SYM because I can customize it to do exactly what I want. I'm sure XCsoar can be setup equally well, but I'm not interested in learning a whole new UI for no real performance difference. TopHat looks interesting on a Kobo mini eink tablet as a stand-alone device for club ships. I've used WinPilot (OK) and tried StePla (too "german"!); even looked at LK8000 (too many numbers that I really don't care about) - but keep coming back to SYM because I'm used to it.

iGlide looks really interesting...

Anyway - whatever a person uses is fine if it makes the soaring experience more fun and safer!

Cheers,

Kirk
66

--
Dan Marotta

I'll post a quick demo in the morning...