Just a quick back-of-the-envelope calculation, based upon the SU-37 A/P
config...
11 filters at 2 x 128 bits
21 pid controllers at 3 x 128 bits
double the data length for oversight/heads
= 11 x 2 x 256
= 5632 bits
+
21 x 3 x 256
= 63 x 256
= 16128 bits
tot 21960 bits
running at the same def
Ralf Gerlich writes:
> Rob Ratcliff wrote:
> > You could use an event distribution (Pub/Sub) paradigm based on
> > something like the CORBA Notification Service (Event Service), the
> > CORBA property service, the newer Data Distribution Service
> (DDS) or
> > something like the High Level Arch
On Tuesday 13 February 2007 02:21, Martin Spott wrote:
> Did you already find one that matches ?
>
> Martin.
If you want an example:
Designing multimedia applications on real-time systems with SMP architecture
Abstract
Large real-time multimedia systems such as flight simulators have adop
Ralf Gerlich wrote:
>Hi,
>
>Rob Ratcliff wrote:
>
>
>>You could use an event distribution (Pub/Sub) paradigm based on
>>something like the CORBA Notification Service (Event Service), the CORBA
>>property service, the newer Data Distribution Service (DDS) or something
>>like the High Level Arc
Hi,
Curt has pointed out some of the problems in using a non-real time
operating system for real-time simulation but there are
standards,software and hardware for this (see POSIX 1003.1d etc,real
time linux,solaris,vxworks etc) although as has been mentioned
portability is an issue. Also distri
Hi Ralf,
I don't know the deadlines, but I know Doug Schmidt (author of Tao) would.
His email is: [EMAIL PROTECTED]
Malcolm Spence (of OCI that provide commercial support to this free and
open source ORB) would have a good idea as well or could find out.
His email is: [EMAIL PROTECTED]
There
Hi,
Rob Ratcliff wrote:
> You could use an event distribution (Pub/Sub) paradigm based on
> something like the CORBA Notification Service (Event Service), the CORBA
> property service, the newer Data Distribution Service (DDS) or something
> like the High Level Architecture (HLA). A CORBA ORB T
On Monday 12 February 2007 19:10, Curtis Olson wrote:
> On 2/12/07, leee wrote:
> > On Monday 12 February 2007 17:54, Jim Campbell wrote:
> > > Hi,
> > > Curtis has already hinted as to how the following may be done with his
> > > "remote" FDM.
> > > To my mind flightgear can be broken down into di
Curtis Olson wrote:
>
>
> Otherwise you are probably going to be wrestling with a complete
> reachitecting of the entire FlightGear structure. Things like the
> property system work great in a single thread application, but start
> to break down when you split modules off into separate computer
"Ampere K. Hardraade" wrote:
> On Monday 12 February 2007 14:10, Curtis Olson wrote:
> > Otherwise you are probably going to be wrestling with a complete
> > reachitecting of the entire FlightGear structure. Things like the property
> > system work great in a single thread application, but start
On Monday 12 February 2007 14:10, Curtis Olson wrote:
>
>
> Otherwise you are probably going to be wrestling with a complete
> reachitecting of the entire FlightGear structure. Things like the property
> system work great in a single thread application, but start to break down
> when you split mo
leee wrote:
>On Monday 12 February 2007 17:54, Jim Campbell wrote:
>
>
>>Hi,
>>Curtis has already hinted as to how the following may be done with his
>>"remote" FDM.
>>To my mind flightgear can be broken down into distinct plugin
>>"modules". There is the FDM, the "external world" visualisation,
On 2/12/07, leee wrote:
On Monday 12 February 2007 17:54, Jim Campbell wrote:
> Hi,
> Curtis has already hinted as to how the following may be done with his
> "remote" FDM.
> To my mind flightgear can be broken down into distinct plugin
> "modules". There is the FDM, the "external world" visuali
On Monday 12 February 2007 17:54, Jim Campbell wrote:
> Hi,
> Curtis has already hinted as to how the following may be done with his
> "remote" FDM.
> To my mind flightgear can be broken down into distinct plugin
> "modules". There is the FDM, the "external world" visualisation,the
> cockpit input
Hi,
Curtis has already hinted as to how the following may be done with his
"remote" FDM.
To my mind flightgear can be broken down into distinct plugin
"modules". There is the FDM, the "external world" visualisation,the
cockpit input and output (ie joystick,pedals,switches and displays) and
poss
15 matches
Mail list logo
