I have started cleaning up the CVS repository for the flight controls code. Part of this includes a re-org of the directory structure and files. Go to
<http://openvtvl.sourceforge.net> and follow instructions for getting the code from CVS. If you want to be added as a developer send me an email and some useful code, I'll add you to the project. For those interested in helping with the code, the design.* files will give you an overview of what is going on. The RTControl directory contains the files that need the most help. The code is well commented with "/*Help, someone!*/" type comments where I need help in doing this stuff (I am not a real software engineer or programmer, I only play one on TV :-) My software dev experience is playing around with some database and mail apps, and writing scripts and wrappers for sysadmin stuff.) For other areas - Code in FCTP compiled once, but I think I broke it sorting out the library functions from the sample/test implementation. The libmath routines are I think essentially complete - and I have compiled test apps that use some of the functions in it. That of course does not mean there are no bugs or serious errors. The code in 'main/' is from the old design, but there is some useful stuff in it, particularly the initialization. The kernel directory has some attempts at A/D driver stuff. I'll be adding the script(s) for creating a RTLinux test enviroment and building the OS/Utilities/Libs for Gizmo/POGO. I think that covers everything. Since the interface between OS and hardware is one of those areas I do not grok: The product manual for the Prometheus PC/104 board with A/D I/O built in can be found at: <http://www.diamondsystems.com/support/techliterature> It's the board we're using for flight controls, the Diamond MM-AT-16 manual can also be used, it is the same A/D. Thanks, Dave _______________________________________________ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
