"I think that if you listed what you wanted this "common" computer to
do, the list would be different for 90% of the people on this list."
And that makes so much sense to me!
These small computers today can do all of that! One small package can
handle just about anything you could want to do!
With something like cFS you could load the apps you want on just about
any of these boards and have a low cost/time flight controller. If you
don't need all of it that doesn't matter.
Open source and you could save a lot of time and money doing it.
Use available hardware for IMU, GPS, Comms and Common ground control
software.
You could use it for HPR or go all out and hover a rocket or do
guidance or fly it on a cubesat whatever!
Log data in ways never before possible do telemetry and tracking if you
want. HW and SITL and all that cool stuff. :)
I did find some people working on running cFS on the beagle bone. So I
can't be too far of the mark.
What this computer does is very similar to what the Ardupilot and
Pixhawk do for the UAV community.
All these things are not as important to the amateur rocket community
yet but they are coming I'm pretty sure we can count on that.
I surely don't need the distraction of the flight computer along side
the current engine development I'm undertaking but it is a very
important part of the final goal. Which I can not overcome on my own and
in the time frame I have in mind.
Because it doesn't exists today I have to spend my precious development
time on something I'd rather not do and also does not fit my skill set
very well at all.
Therefore an open source solution with community interest is required.
IF I can get the ball rolling with cFS then a large part of the work
has already started.
If not I need to put my effort into another solution.
I've got a young fella on the PX4 dev team interested in running
something on the PX4 stack rather than the Pixhawk (which is based on
the PX4) based on the Ardupilot code. Perhaps that is the direction I
must go.
Right now it all depends on where I can get the help I need to make an
open source flight controller possible.
Right now I'm wondering why I have to pick all the hard battles.
These things are obvious to me why not anyone else? It seems? Whatever
I guess, I'll just keep on the path I'm on and see where it goes. Maybe
I'll learn enough to do it myself maybe I'll find some help maybe I
won't see it happen at all. I don't know but I'm not veering from this
path.
-------- Original Message --------
Subject: [AR] Re: Flight Computer
From: Paul Breed <paul@xxxxxxxxxx>
Date: Thu, December 24, 2015 7:09 pm
To: arocket@xxxxxxxxxxxxx
I think that if you listed what you wanted this "common" computer to do,
the list would be different for 90% of the people on this list.
I car about keeping an accurate real time PVAT ie position velocity,
attitude and to a lesser extent time.
Keeping this across all flight regimes at all times so one can run some
simple PID loops to do guidance and control.
Others would want reliable recovery deployment, yet others would want it
to manage cameras....
On Thu, Dec 24, 2015 at 4:31 PM, Chris Jones <clj@xxxxxxxxx> wrote:
On 12/24/15 7:20 PM, Monroe L. King Jr. wrote:
The software is the hub IMO :)
The rest of the system is spokes, wheels and tires.
Of course, it all depends on where you're sitting. I still vividly
recall (more than 20 years later) having the power system guy explaining
the power system on a large (designed for over 1000 processors, we
tested around 250) multiprocessor system to me, a software guy who had
to interface with it. He drew a schematic that went into great detail
on the front panel LEDs, the built-in UPS, and the rest of the power
system. The remainder of the system (hundreds of processors, maybe
thousands of disk drives, gigabytes of memory) was denoted as a large
resistive load...