the packet format? I suppose that would work in our "fat packet" mode... I
don't know what kind of latency you would have, so maybe only getting 10 or
15 updates a second wouldn't be noticeable, unless your actuators can really
move the***pit around in an instant.
We actually put in a hook for a custom telemetry .DLL into the Heat patch
for some engineering students that are working on a motion base for a
project... one could make a DLL that would translate to any other format
pretty easily, since we send out all the orientation, velocity, rpm, etc
with no latency. It would be nice if this were all standardized, though...
If you want info on this, Mark, feel free to drop me a line.
-Dave Pollatsek
> FYI, x-plane is set up to dump data to motion platform drivers.
> There are standards, I think.
> > Mark,
> > What data port are you talking about? The only port I can imagine is a
> > multiplayer port and this would of course be a seriously limiting way
> > to get at the data since it's not always active and would have a very
> > slow update rate -- relative to the game engine anyway.
> > Am I missing something? Would you care to elaborate further, please.
> > Thanks taking the time ;-)
> > Randy
> > >Randy, in short, you basically intercept the data from the port into
another
> > >computer which is receiving the data. Then you dissect the data in the
> > >packets and determine which data bits are speed, position, altitude,
etc.
> > >Mark
> > >> Mark,
> > >> I'm curious, would you describe how you plan to do this? Not that I'm
> > >> saying you can't, I just wonder how you'd go about it.
> > >> Thanks,
> > >> Randy