On Thu, 2003-10-02 at 20:12, John Carmack wrote:
> I would strongly urge ERPS to adopt the same software organization that I 
> settled on for Armadillo (after a couple early generational changes).  It 
> has been a completely positive arrangement.
> 
> There are two major components: 
<snip>

So far this is very similar to what I am doing. The three of us that
have laptops, IT backgrounds (i.e. can do some programming), and are
actually working on this stuff all have Linux on our laptops. So both
the flight computer and ground computer are Linux. I hadn't thought
about doing a "computer thinks this is its orientation" display on the
ground computer, but I can see where this could be a definite advantage
and will be adding it soon.

> This is a Very Very useful arrangement of code, and you need to write 90% 
> of it for normal vehicle operations anyway.  Doing a simulation in matlab 
> or any other external product will not give the same benefits.

I think the biggest advantage of doing a Matlab/Simulink simulator is
that none of us have much experience doing simulations of any sort.
Since Matlab/Simulink does much of the tedious and complex stuff in the
Aerospace blockset, we can get the simulator going quickly and use that
as a 'design document' to help us in creating our own simulator. Sort of
a rapid application development tool.

Also, we were actually thinking of making the simulator a seperate unit
such that there is only a connection between the A/D and D/A boards. Our
thinking is that we can test the actual flight code, all of it, from
reading the sensor data off the A/D to communicating with the ground
computer to spitting out the motor data through the D/A. Of course since
I have the joyous task have writing the interface for the simulator I'll
be doing it such that it does not particularly care whether it is
writing to a network, IPC, or A/D board.

Thanks,
Dave

-- 
David Masten <[EMAIL PROTECTED]>
_______________________________________________
ERPS-list mailing list
[EMAIL PROTECTED]
http://lists.erps.org/mailman/listinfo/erps-list

Reply via email to