net.cpp AND what on earth is vector<string>::const_ite - Printable Version

+- Forums (
+-- Forum: Project (
+--- Forum: Development (
+--- Thread: net.cpp AND what on earth is vector<string>::const_ite (/showthread.php?tid=235)

Pages: 1 2

- nael - 06-14-2006

Its a cockpit mounted ontop of a Moog 6DoF platform. 6 ppl can sit inside, but we are thinking of removing one row of chairs and just making it fit 4 instead. Theres one screen inside, but we are mounting 1 or 2 more for a wider view. There will be two joysticks and a yolk and paddle connected inside as well to play the simulations. Right now its running FlightGear flight sim, and I am working on having Vdrift work in there as well. There are 4 machines on the network, one with a 64 bit AMD processor and a high-end Nvidia card that will produce all the graphics and display them on the screens. This is easily done with Flight Gear as their command line options are more developed than vdrift. They allow for the phsysics engine to be run on one machine and the graphics produced by another while both communicate to run the simulation. I am programming similar abilities for the Vdrift command line.

Rather mucking around with networking code, we are using DTK Diverse to manage shared memory. It comes with lots of tools and libraries that allow writing to a DTK shared memory on one machine, and sharing it with any number of machines on the network. So I write accelerations in all 6 dimensions to the shared memory, and read them from another computer that will control the platform. These accelerations are mapped to a range between -1 and 1 and sent to the Moog onboard computer to control the platform.

So to sum up, one graphics computer, one physics engine computer. the on board Moog computer and another operator/monitor computer outside to oversee the operation. I developed an interface using FLTK that can be used to start/stop and test the platform. The FLTK library is used by the programs that come with DTK Diverse. These are very usefull for test purposes as they come with scopes and other displays that visually show you whats happening in the shared memory. The really neat thing is what they call GnomeDisplay and its a 3D axis and when you run it with the shared memory it starts moving according to whatever is written to it - so you can see whats the platform supposed to do.

I am not sure how hard its going to be to split vamos from the rest of the vdrift but the professor I am working with wants one computer to just deal with the graphics.

I still didnt get a chance to see the platform in motion, as the university engineers are taking their sweet time to connect electricity to the room with the simulator..I think it will be ready next week and I can start testing.