weyes blog

10th flight simulator conference

noreply@blogger.com (Alessandro Caproni) — Thu, 19 Apr 2012 10:08:00 +0000

I have been at the 10th flight simulator conference, held in Germany on saturday, March the 24th. Sorry if I am writing this report with a huge delay...

The first report have been written in one of my posts in the VoloVirtuale forum so what you read below is more or less a plain translation from italian to english.

There were a lots of exhibitors and between them VATSIM, IVAO, AEROSOFT, Saitek, VRinsight just to name some of them. And there was also a lot of people, actually much more then I expected. The conference has been held inside the Deutsche Musuem of Aviation.

Aerosoft was selling all of its products and had a virtual cockpit that people could enjoy. The cockpit seems a real replica based on XPlane and having a big flat screen The queue for playing was really huge!

Also Saitek and VRInsight were present with a lot of products. VRInsight was offering an interesting 20% discount. But the most interesting things was to see and touch the hardware they produce.

VRInsight was selling a 737 header panel for 1600€ but to be honest I did not like so much because it looked like little game instead of a serious device for flying.

Very interesting instead the gadwet produced by Saitek for altutude, speed and so on... unfortunately I read some comment saying that suck widgets are very useful for the standard FS planes but less interesting for liners like the LevelD or PMDG. I still believe that they could help creating a good home cockpit in a short time.

Due to the lack of time, I followed only 2 talks: the presentation of XPlane and PMDG.

Almost all the stands run XPlane, FSX was used in a very limited places while Prepare3D was absolutely missing.

XPlane

The first coming product is DC3 for the lovers of vintage planes.The graphic details of the cockpit and the interiors comes from around 6000 photos.

XPlane and his future developments have been presented in an interesting talk. The was a lot of people following the talk and they had a lot of questions. Unfortunately the talk was in german so I could understand only part of the presentation and almost nothing of the questions...

With XP10, Laminar tried to develop what they called a reasonable world not a 100% reproduction of the reality.

In XP10 there are different type of roads like highways, one way, normal streets and so on. These different types come from OpenStreetMap. There are also different types of residential areas like cities, villages, industrial, business.

The autogen, the ATC, the rendering engine, the lighting and the textures have been rewritten or greatly imprioved from version 9. Actually, a lot of very amazing screenshots have been presented especially regarding the lighting system.

For the future, Laminar wants to focus on big liners that they called "High Fidelity Aircraft Addons" by adding FMS data (from Navigraph that at the present is the only one available), idraulic system, electric system, high resolution textures and visrtual cockpit.

Laminar XPlane 10 releases LFMN, ELDP, LPFR, EGLL, LFPO, EDDF. LSZH in collaboration with Aerosoft.

Apart of airports, XPlane 10 has severla new common objects avalable for scenery designers like hangars and water towers among the others.

PMDG

Randazzo presented the new products from PMDG in a 30 minutes talk with a great series of screenshots . His complete presentation, in english, is available in you tube.

The second product is the 777 . Randazzo showed the level of detail of the instrumentation that arrice to reproduce the dust of the original planes from which PMDG took the pictures..The cockpit of the 777 was turned off because the stem did not work 100% yet in fat, in the only active instrument, there were chinese chars that they don't know from where they come from.

Randazzo also announced that PMDG will develop a 747 whose release date is foreseen between 4 and 6 months after the 777.

Randazzo spent quite some time talking about the 737 'HUD. It is now widely used but was a real technological challenge for PMDG.

The selling of the MD11 was not as good as expected. People buys the plane that sees in the airport regarding if it is a good produt.

He believes that 'MD11 is a wonderful plane both in reality and simulated.

Randazzo reaffirmed that there is no interes in PMDG to develop airbus birds.

PMDG is developing a plane for XP but he did not tell us which one because they could change along the way depending on the diffuclties they have to afford. According to Randazzo, it is not a project to sell but to investigate XP potentiality and estimate the porting effort so it will not be a new product but the porting of an existing one.

Home cockpit builders were a little bit upset for the lack of SDk but it seems that PMDg is going to change its policy. Apparently, the SDK released by PMDG for the 737 are not good enough because the software houses found some glitches and functions not implemented as they should.

FMC installed - final review of the device

noreply@blogger.com (Alessandro Caproni) — Tue, 28 Feb 2012 09:36:00 +0000

The FMC has four LEDs already connected on the grren board and the manual from OpenCockpits describes very well how they are wired. The cables to light the LEDs are available in the 40 pins connector: the ground is common and there is one wire available for each of the four LEDs (However in the picture of the manual there is an error in the way the holes of the 40 pins connector are numbered....)

I preferred not to scrape the gumi of the cables but instead to put another thin cable in the hole before inserting the 40 pins connector in the socket.

Actually, I ended connecting in this way only the LED for the MSG and preferred to wire the EXEC in a different way. The reason is that for the EXEC I had to put a LED with a resistor and, at least for me, there is not enough space for that. I suggest to use a LED with a incorporated resistor for the EXEC. They costs a little bit more but for this specific case I think they are of a great help to reduce the cabling and the space needed for the resistor. I did 2 new holes in the board just below the black BRT pin, as you can see in the following picture of the rear side of the board:

There is enough room for one of the holes but for the second one it is a little bit risky.... As you can see at the bottom of the right big hole there are 2 little holes one close to the other. They are the holes supposed to to be used for this LED and that are wired in the 40 pins connector of the board. The reason I did not use them is because I need to mount the LED in the frame, then put the keys in place and only in the final step to close the box. I need the LED to be moveable and to be able to turn left and right the frame before closing. It might be that I am not skilled enough ;-)

Note that the LED must be connected to a master card or to an output card to be lighted because the FMC as an OpenCockpits key card that has no output lines.

Pay special attention to the position of the keys because is very boring to dismantle the device only for that. And pay attention to the keys also. Each key is composed of two parts: the black upper side with the engraved letter and a transparent squared frame at the bottom. They are simply glued and in my case the glue went banana on its own and I had to fix the pieces again... I hope these pieces are glued well because it is a lot of time to dismantle the device, glue and remount!

I put the FMC into a box. The cable run out of the box from the bottom. The box itself has been fixed on the left side of the monitor. As I said, unfortunately I have no room to build a pedestal. The following picture shows the FMC in its final position:

Theis shows part of the cockpit during a flight:

And the last one shows the FMC during a flight:

As you can see the quality of the image is quite good and the written are placed exactly in front of the left and right keys. Some light comes out of the upper side I have to better seal the frame): it is produced by the screen of the FMC.

Flying a liner with the FMC improves the feeling of the reality so I really suggest you to have one in your home cockpit. The feeling of the OpenCockpits one is quite good. I mean the screen is very good and if I press a key the reaction time is very good.

But is is not perfect. As I said the glue of one of the keys failed without having done anything. The keys are too loose; this is not a problem normally unless you mount the device in a vertical position as I did.

Very good to have the lines to connect the LEDs but why are they in the 40 pins connector together with all the other wires? It would be better to have a dedicated connector considering that they must be connected to an external board.

Finally a couple of words about the missing EXEC LED. IMO the other LEDs are not very important. In the 767LD for example there is an annunciator in the cockpit showing that there is a message in the FMC. But the EXEC LED is really important because it is used very often and it is the only way to know that the FMC is waiting for you to press the relative key.

I consider a big lack the absence of such LED. I appreciate the wiring in the board (even if I preferred not to use).. But where one is supposed to put the LED? And IMO it is very complicated to wire....

Why don't have the LED in the place of the BRT black pin? It is a fake and useles... The best solution would be to have the LED incorporated in the key of course...

We must take into account have to consider the price that is very low compared with other similar devices on the market.

OpenCockpits FMC

noreply@blogger.com (Alessandro Caproni) — Thu, 16 Feb 2012 09:14:00 +0000

Few days ago I received the FMC from OpenCokpits and I am going to write down here my first impression.

The box was very well sealed and the FMC was packed with soft paper to protect from damages.

When I saw the new toy I was surprised to find it much bigger then expected. The upper panel is 100% plastic and the keys move slightly in their holes. To be honest the first impression was not good. It really looks like a cheap toy for kids.

The sides of the FMC are not covered and show the electronics that drive the FMC. The bottom side, showed in the next picture has a connector for the power supply, in yellow, and for the USB (in white). Note that the connector of the power supply offers a socket in the rear side (in black at the right of the yellow inlet) that can be used to back light the device. The black cable is for the TV out.

The lateral view: the display is on the right side; the rear side of the FMC is on the left of the picture.

The keyboard is fixed to the electronic by means of screws so it is quite easy to remove the upper side and check how the keyboard is done internally.

The keys are simply put on top of micro switches and three brown plastics frames, one on top of the other, hold them in position. That's the reason why they moves slightly. However pressing the keys is smooth and they emit a nice sound of click.

There are 4 LEDS, 2 on the left side (on top in the picture) and 2 white at the right side (better visible in the next picture). They correspond to the 4 alerts that the FCM can show during a fly. I am particularly interested in the led on the right upper side of the device that lights when the FMC shows a message.

The EXEC button instead has no light and that's really a pity because we need that otherwise we have to remember when the FMC expects us to press EXEC. There is also no available place to fix a LED in the EXEC button. What I plan to do is to remove the BRT black plastic of the mask and put a LED there. Note that the BRT does not work in this version and the black plastic item is simple a place holder. I took this idea looking at Nico's pedestal.

The following picture shows the keyboard of the FMC with 2 of the three frames in position on top of the keys. You can hardly see a hole in the plexiglass on the right side of the EXEC key. It corresponds to the BRT black plastic pin. It really seems to have been planned for housing the LED for the EXEC after removing the BRT pin.

Before closing the the device I removed the BRT pin. Now I need to find the best way to fit a LED there and also the way to light the for LEDS in the green board.

After looking at the inside of the device I changed my opinion. I think it is well done and ready for being back lighted. There is the place for the LED of the EXEC and four LEDS ready for being lighted.

What I completely miss is the documentation on how to turn on/off the LEDS. Are they available already or do I have to connect them by myself to the master card?

Lekseecon provides variable to light the MSG and the EXEC. And I will ask Nico how he configured his device.

The connection to the PC has been easier then I thought. To avoid problems I bought from opencockpits the VGA to video converter. I guess it was overpriced but at least it worked immediately.

I needed to add a new screen to my PC and I could use the onboard video device of my ASUS P67 pro. I set the screen resolution to 800x600 and started the 767LD.

It took me quite some time to position the window inside the new screen. I had to hack the panel.cfg to find the right parameters. The trick has been that to set the size of the widget as fixed and then the classical trial and error procedure. It took me quite some time but finally I had the green written in the display in the right position.

To test the device I had initially to move my SIOC from one single file to multiple files configuration. I splitted my config file in 2 files, one for the light panel and one for the master switch. It worked immediately.

Finally I added the FMC config file provided by lekseecon after setting the opencockit device in the SIOC config file.

Unbelievable it worked immediately with no intervention from my side. I really did not touch Nico's config file and everything worked in the first shot.

It is really great to interact with this device. It is smooth and I like the click when I press a button.

I will add more picture the next time I connect the device to the 767LD.

Now I need to connect and light the 2 LEDS I mentioned before and build a wooden frame to suite the device. I will hold it in the wall at the left side of my home cockpit. As I said I have no room to replicate a real 767 cockpit so for the time being I have to arrange the devices where I can.

Bought the FMC

noreply@blogger.com (Alessandro Caproni) — Wed, 01 Feb 2012 11:40:00 +0000

It is a long time that I want to have a FMC for flying the 767 because the device is essential and one of the most used device during the simulation.

There are several items on sold from a pletora of producers. I started surveying the products long time ago and ended with 2 devices. One is the B747 FMC from FlyEngravity. It is quite expansive, at the present it costs aroubnd 1200€. It is fully compatible with the 767LD and easy to connect as it uses only one USB cable and a power connector.
The second interesting product is the OpenCockpits FMC that costs around 350€ plus taxes. It requires a USB connectr, a video out and the power. The problem is that I already have 2 monitors connected to me PC.

After a long time I decided for OpenCockpits FMC especially because I am afraid that the FlyEngravity one is too tight to the 767LD and FSX.
The market is in a transition phase right now. Flight seems not to be good enough for simmers. XPlane 10 seems quite interesting but sttill not supported by the software houses. Prepare3D is very interesting and expansive but I am afraid that LevelD will never port there the 767 or will do but only in a very far future. Sad to say but LevelD is very slow releasing products. They promised the 757 years ago and still nothing is moving. I asked the official forum about P3D and they replied that they are aware of this simulator. Difficult to say what it means exactly.

So, for the first time since long time, I am not anymore 100% sure to stay with the 767LD and FSX. This is the main reason I preferred the Opencockpits FMC. To be free of using it with other planes simply changing the SIOC script.
If I will switch to another plane, it will be a 737 because it is much more easier to find cockpit's stuff for that model. PMDG 737 seems very promising so it is worth to wait for its SDK. It will be compatible with my CPFlight modules that are designed for the 737 and I will customize my hardware for that plane.
In this moment, I believe that it is better to stay quiet and see what the software houses will do.

Having bought the OpenCockpits FMC, I need a video out connector. I am thinking to add a new graphic card to my PC. It could as well be USB. But I prefer to have the device at home and think better about the connector. I bought also the VGA to video converter sold by OpenCockpit. I believe that I can found a cheapest one on the market but I do not want to have problem for a connector if possible.

Given that the FMC was cheaper then the other (that I was very close to buy to be honest), I bought some other interesting stuff. Especially the flaps indicator. This is again for the 737 but I will customize for the 767. The number of flaps positions differs between the two planes.

I received the MCP from CPflight. They changed the knobs and returned the item in a very short time. I will never get tired to repeat that CPFlight support is quite good.
The MCP works well and I connected also the TOGA button but it seems useless unfortunately.
I upgraded the firmware to the last 3.05 version but I have a problem now. I have an out of memory when launching the connection to FSX. I have to restart the connection and seems ok apart that it does not iconize. Ok not a big deal! I warned the support just in case it is the symptom of an underlying problem that could arise while flying.

Unfortunately the power supply I built for the electronics stopped working yesterday. I discover that I can avoid a power supply if I take the power out of the USB expansion card. I will use that as a temporary solution but I believe that a separate power supply is better. And I will probably need it for the backlit of the FMC and maybe for the bar of leds of the landing gear.
On the other hand, if it works well then it is not the case to add the complexity of another power supply to the system...

Logitech G940 review

noreply@blogger.com (Alessandro Caproni) — Sun, 22 Jan 2012 10:55:00 +0000

The device is very well packed and all the items have their envelope to protect from water and humidity. The box contains the pedals, the throttle, the joystick and the power supply.

Cabling is quite easy. The main device is the joystick that has the USB cable to connect to a free port of the PC. It has also 2 DSUB9 ports where the throttles and the pedals have to be connected. Cables are long enough at least for my setup. Close to these connectors there is also the connector for the power supply. Neither the DSUB9 not the power supply connectors have screws to lock the cable. I think that a device so expansive should have better connectors especially the DSUB should be different between pedals and throttles to avoid to connect a device to a wrong socket. The missing of the screws is also a lack for me. At least in my setup I will have to connect and disconnect the devices every time I flight so I am afraid the the connectors could brake with the time.

All the devices are plastic made but they lock very solid and heavy. The joy and the throttle device have holes that allow to screw them to the table. However they have gum below and never move even without locking. Pedals have gum below and some locking when used with carpet. They also never moved but I wonder why they do not have any locking mechanism that I find more useful for this device then for the others.

Installation proceed as usual: launch the setup of the CD and connect the device when requested. When the G940 is powered the buttons in the throttles lit up first in red then in green then off. The joystick wake up and the lever goes to the center. The software loads up a profile manager from which it is possible to select a specific profile for the flight simulator. Note that at the present there is no support to light the buttons of the throttle. It is a pity as it would be nice to have them working. I think for example to have red/green color for the landing gear and so on.

The profile manager resembles other profile manager like for example that of the saytek joystick. It is possible to select the device, a button of the device and then associate a key or a macro (i.e. a sequence of key to press). In the case of the Flight Simulator, the profiler shows a list of commands. Thrusting the default profile for flight simulator I started the sim and tested the device. I had to configure the axis from the controls tab of the simulator. Some of them has to be inverted, like the rudder, but it has been quite easy. I used one of the saved situation of the 767LD for that purpose so my sim started with the pane powered at the parking.

In my case this simple configuration did not work, The plane had the brakes always on and crashed during the taxi or was impossible to take off. I never understood the reason as there was nothing assigned to the brakes. I configured the pedals with the differential brakes and no assignation for the brakes (the dot of the keyboard) and nothing for the parking brakes. When I released/set the parking brakes everything seemed to work well but as soon as I touched and released the pedals the brakes engaged and was not possible to release. I spent quite some time with this issue but no solution. Another problem I noticed was related to the spoilers:: the lever moved constantly from released to around middle range.
After spending some hour, I gave up and get rid of the profiler by selecting an new, empty profile. I deleted all the assignation to the devices in the flight sim. and start from scratch. What is annoying in this phase is that in order to save the settings in the flight simulator you have to exit the program. It seems that FSX only saves the settings during shut down. Note that to get rid of all the assignation, I had to select the right device in the settings tab. SO the same operation had to be repeated for all the three devices. FSX assigned to each devices some command/axes by default. But this assignation is not clever enough so that there were more device controls assigned to the same axis or keyboard command. I guess this, together with the profiler settings, could have been the reason of the problems.
I resasigned all the axes and commands to the buttons as I liked and after that everything works well. However this operation has been very time consuming and for awhile a thought to have a problem in the G940 too.
The profiler has now an empty profile. I tried to assign some commands from the profiler but it does not work anymore. First when I select a button it does not offer the list of FSK commands as it was doing before. And even if I assign a command, nothing happens in the simulator. So I guess that now the link between the simulator and the profiler is broken. I also guess that there is a way to fix but I am not really interested as I think that the profiler is useless unless it allows me to do something I can't achieve with the setting of the simulator that is not the case.

G940 is plenty of joysticks and buttons, hats and sliders and all of them easily configurable with FSX. In my case I used only controls for the landing gear, flaps, trim, one to engage the spoilers for landing and a hat for the view in 3D cockpit. So in my case there are more controls then what I need. What I would like to have is the possibility to invert the axis of the throttle to simulate the reverse. It should work in this way: when landing move the throttle back to idle; press a button (or better switch the configuration button from position 1 to 3, this button is in the throttle lever) this button inverts the axis so when I accelerate the throttles the reverse is applied. When finished with the revers, move back the throttle, press the button and the axis return normal for taxiing. Not sure if it can be done with the profiler. That would be a good reason to resuscitate the profiler.

The pedals are quite solid. Even if they are plastic made, I am not afraid to put my heavy shoes on it and move them. Instinctively I do not apply big forces on them but there is no need as they react immediately and smoothly. I found taxing and landing a new experience. The pedals add a lot of realism. Differential brakes together with the 2 throttle levers greatly improves maneuvering. Differential brakes are progressive so it is not a process all/nothing but it is easy to modulate the amount of brake to apply to the left and side side.

The throttles are easy to control with he 2 levers. Very useful during taxi and maneuvering and to experiment single engine fly without turning off one of the engines. The levers do not move smoothly along all the range. There are 2 points where they offer some resistance. For me it is not disturbing but for a three-hundred-euro device they should be better IMO. The throttle has to be put on the left side while I hoped to use them on the right side because this is the position of the throttle in respect to the captain seat. The levers have an inclination and the button in one side of the lever so that their position is the right side.
For my way of control the throttles, the button in the pad are disturbing. I am used to lie my left arm on the pad and in this way it presses the buttons in the pad. This is my fault of course. I solved by setting buttons that I do not press by mistake with the arm. Fortunately the device is full of buttons...

The joystick is really great to control the plane. It is very smooth, really nice to move. The hand fits quite well. This device must be controlled by the right hand. Same consideration I did for the throttle...
The lever is quite big and to press some button or use the topmost hat I have to release the lever, move the hand and operate the control. This is again not a big deal because there are buttons and a hat I can control without releasing the lever. There are so many controls that it is very easy to customize.
I almost can't feel the force feedback. It has been activated in the simulator and I also increased from 100% to 110% but up to now almost can't feel it. I should feel some vibration during taxi, landing and moving up and down the gear but nothing. I would also expect the force to be applied when the plane needs trim. But nothing or very little force. I have to investigate more. What I can say is that I had an old microsoft side winder years ago and when the plane needed trim it was quite hard to handle the lever of the joystick. I have to experiment more probably.

To close this long review, just few words about the centering of the devices. It has to be done with the standard windows controls, the same we are used to use for the other joysticks. This is easy and familiar but surprising for the throttle as the 2 throttles are seen by the system as a 2 axis joystick so both the levers must be moved while centering.

The following picture shows my little home cockpit as it appears today (pedals at the bottom are not visible).

G940 is just in front. Behind almost invisible the keyboard and the mouse in the right side. The lighted instruments are CPFlight (MCP, EFIS, XPNDR, NAV, ADF, COM). On the right side of the MCP, the master caution button I built starting from two pieces of aluminium. In the top right side the light panel.

I took this picture flying on IVAO with the 767LD. The right monitors shows the FMC and IVAE.

Below the monitor on the right side, there is the wooden frame for the next panel. I am planning to put there the landing gear and other controls, not sure yet which ones.

And I am also planning to put on top of the monitor in the left side, a set of annunciators. Probably the ones in the overhead and maybe those in the glare shield.

Last saturday I sent the MCP to CPFlight for maintenance. The knobs for the heading and the altitude do not work (consumed). But talking with CPFlight support, I found that there is wire connector in the back side of the MCP for the TOGA button and it works with the 767LD. I will probably add a button close to the master caution for engaging the TOGA. In this way I save one input line of the master device and the cabling should be very easy.

Logitech G940

noreply@blogger.com (Alessandro Caproni) — Mon, 09 Jan 2012 19:43:00 +0000

One of the thing I mostly missed while simulating is the throttle for a twin jet engine like the 767 I always fly. There are several alternatives in the shops and I believe that the most used throttle comes from the saitek. Saitek in fact sells the Pro flight throttle quadrant that can be customized for a twin jet, for the flaps. IMO these lever are so ugly that nobody should really buy them. But I know this is my opinion and someone could prefer a ugly device if it works well.

Walking in a shop I found the Logitech G940, a gaming device composed of a 2-axis force feedback joystick, throttle for a twin engine plane and the pedals. I looked for info on the net and found a very interesting review that convinced me to buy the device.

I am well aware that such a device does not match with a 767 home cockpit. So why I decided to buy it?

The reason is that my home cockpit is not intended to be a replica of a 767 cockpit because I do not have enough room at home. My goal is instead to fly without the keyboard and this device gives a lot in this sense: 2 throttles, a set of configurable buttons. And i gain much more realism with the pedals.

Is the force feedback joy adding something to the realism? I don' t really believe as I have already had the Microsoft Sidewinder. If it does not add any realism, it adds a good feeling while flying because it transfer to the hand some of the forces that act to the plane surfaces. I could feel the bumping of the plane in the asphalt, the force in the wings to counter act with the trims and so one.

The logitech G940 is meant for a twin engine jet fighter. It is not the only one alternative on the market. Saitek is also offering something very similar at an higher price, the X-65F. This last product can or cannot be better, I don't know. And the price play a role in my choice because I don't really know, at the present, if I will build the pedestal at a certain point. But the pedestal is a very complex piece of hardware and even if I will build (or buy) it, it will require long time before being ready. The G940 will help from the time being.

I will write my own review after installing and testing G940.

Designing new panels

noreply@blogger.com (Alessandro Caproni) — Fri, 06 Jan 2012 11:23:00 +0000

Finally I setup FSX and connected all the hardware and could fly online at IVAO.
The good news is that FSX never blocked and it is running at an average speed od 25fps, good enough for flying smoothly.
I have an error from time to time in the 3D view that make all the instruments unreadable but does not compromise the fly.

Unfortunately I have lost all the setup of the hardware and a lot of things changed in the last 2 years. SIOC is at version 4 with support for multiple files and lekseecon has also been largely improved. The good news is that it was so easy to use Niko's library and I wrote again the SIOC script in less then one hour.
The following is the script to control the lights in my panel:

/////////
/// Master Switch (MS)
/////////

// HW variables definition

// Master switch push button
Var 266 Static Link IOCARD_SW Input 41 Type P

// Lekseecon var to check the state of the lights of
// the Master switch button
Var 739 Static
{
&O_MSWarning = TESTBIT v739 0
&O_MSCaution = TESTBIT v739 1
}

// SIOC - MS Red led - Warning
Var 9001 name O_MSWarning Link IOCARD_OUT Output 11

// SIOC -MS Yellow led - Caution
Var 9002 name O_MSCaution Link IOCARD_OUT Output 12

/////////
/// Panel flood lights
/////////

// Panel & MCP Flood
Var 246 Static Link IOCARD_SW input 29 Type I

// SIOC - Overhead light led out
var 9008 name O_OvdLT Link IOCARD_OUT Output 49

// Overhead lighting -- NOT SIMULATED!!!
Var 247 name PanelFlood Static Link IOCARD_SW input 27 Type P

// Glare shields

/////////
/// Taxiing lights
/////////

// Taxi
Var 260 Static Link IOCARD_SW input 28 Type I

// Left runway turnoff
Var 261 Static Link IOCARD_SW input 34 Type I

// Right runway turnoff
Var 262 Static Link IOCARD_SW input 26 Type I

/////////
/// Landing lights
/////////

// Left wing landing
Var 263 Static Link IOCARD_SW input 25 Type I

// Right wing landing
Var 264 Static Link IOCARD_SW input 21 Type I

// Mose landing
Var 265 Static Link IOCARD_SW input 23 Type I

/////////
/// Extern lights
/////////

// Pos. Lights
Var 255 name PosLight Static Link IOCARD_SW input 22 Type P

// SIOC - POS led out
Var 9003 name O_Pos Link IOCARD_OUT Output 51

// Anti collision RED
Var 256 name Red Static Link IOCARD_SW input 24 Type P

// SIOC - Anti collision red led out
Var 9004 name O_Red Link IOCARD_OUT Output 50

// Anti collision White
Var 257 name White Static Link IOCARD_SW input 20 Type P

// SIOC - Anti collision white led out
Var 9005 name O_White Link IOCARD_OUT Output 54

// Wing lights
Var 258 name Wing Static Link IOCARD_SW input 18 Type P

// SIOC - Wing led out
Var 9006 name O_Wing Link IOCARD_OUT Output 53

// Logo lights
Var 259 name Logo Static Link IOCARD_SW input 19 Type P

// SIOC - Log led out
Var 9007 name O_Logo Link IOCARD_OUT Output 52

// Lekseecon var to check the state of the lights of
// the lights panel
Var 737 Static
{
&O_OvdLT = TESTBIT v737 0
&O_Pos = TESTBIT v737 1
&O_Red = TESTBIT v737 2
&O_White = TESTBIT v737 3
&O_Wing = TESTBIT v737 4
&O_Logo = TESTBIT v737 5
}

One of the botton in the light panel is not implemented in 767LD/FSX so I could in principle reuse it for something else. It is a ON/OFF switch. Times ago I used it for the parking brakes.

I am already designing my next panel but I have not yet decided what to put there. For sure the gear lever but together with other controls.

I have to decide if I still want to copy the glare shield or if it is time to put there the most used commands for enjoying the flight.The problem is that now with the situation of flight simulation I do not yet know what to do. I can stil fly with FSX and the 767LD of course but there is also a chance to switch to Flight or XPlane with a 737 and in that case all the panels for the 767 will be mostly unusable.

I have already built the woodden frame and start thinking on the electronic componets. I will add more comments as soon as I take the final decision.

I will also build a the annunciators for the overhead panel and those in the glare shield. The former will be with a white led because I don't want to have them signaling errors. I double checked that those are implemented in lekseecon.

The annunciators in the glare shield will have a orange high performant LED. These are not implemented in lekseecon and the logic has to be retrieved from FSUIPC.

i am also planning to put something close to the master switch button. Probably other annunciators not prenset in any oter place like for example a stall warning. There could also be one or two buttons. i am still in the design phase...

I have been elected as a Flight beta tester from Microsoft. For being correct, I will never write any comments on the flight simulators until my role terminates.

Back in Germany

noreply@blogger.com (Alessandro Caproni) — Mon, 14 Nov 2011 11:13:00 +0000

I definitely left Chile the 31st of October and I am back in Garching since last saturday the 5th and back at work since monday the 7th.

Now that I am back in Garching it is time to set up the system to flight.

My old PC is really too old... it was already very old and slow a couple of years ago but now I found almost impossible to work with it. It is a P4 Fujitzu Siemens and I have to say that it never stopped working. The only failure in so many years has been an hard disk! I am now evaluating if it is the case to use the PC for some background not expansive task or to definitely retires it.

After a survey in the internet and in the shops in Munich, I bought a new machine from csl-computer. It has the components that I would have chosen by myself. In short: Intel Core i7 3.4Mhz, 16Gb RAM, 2Tb HD, NVIDIA GeForce® GTX 550 Ti with 4096 MB, Motherboard ASUS P8H67 Pro, USB 3.0,...

I am a little bit concerned about the graphic card. In principle it is a good one with its 4Gb RAM but I need to see it in action with the flight simulator. However, in my opinion, the graphic card is the only one component that is worst to upgrade in a couple of years to increase the performance of the whole machine. After it is usually better to change the computer itself.

The network is also on the way. I choose a DSL with 6.000 kbit/s. It was enough in the past so it will hopefully be now again.

Knowing germany, I will probably have the PC and the network during this week or the first days of next week.

Back to Europe

noreply@blogger.com (Alessandro Caproni) — Wed, 19 Oct 2011 13:31:00 +0000

At the end of October I will come back to Europe after a wonderful period I spent in Chile.

Chile is a wonderful place that I suggest everybody to visit. The country offers a lot of special places for hiking, exploring, walking and whatever you like. The climate ranges from the cold south and its glaciers to the warm and dry desert of the northern part.

Talking about Chile is not in the scope of this blog of course but if you're curious take a look to some of the pictures I took in this 2 years looking at my albums.

From a personal point of view the time I spent here is invaluable. The experiences I did working at the observatory, the places I visited and especially the persons I meet here will be part of my life forever.

XPlane first tests

noreply@blogger.com (Alessandro Caproni) — Fri, 05 Nov 2010 23:53:00 +0000

The first challenge is to find good liners for XPlane. For good liners I mean liners complex enough to be close (or, better, that I believe are close) to the real plane, with a good FMC for flying online and a good flight model.

After some browsing on the net, it seems that there are basically only 2 good liners: a 737 and A320. Unfortunately both of them come with no FMC even if it is possible to add but both of them are for free.

I have tested the 737 that seems quite interesting even if it is not comparable to FSX version of 737. But it is 100% free and as far as I recall there are no such good products available for FSX for free.

The flight model for this plane seems quite good. It was initially very nervous but after setting up my joystick it responds quite well.

The biggest problem is the lack of an FMC. It is possible to buy an FMC from the same site that delivers the plane but until now I tested only a freely available FMC: X-FMC.

X-FMC is generic in the sense that it is customizable for a lot of planes like the 737 or the FMC. It is quite complete with initialization pages, performances pages, routes, SIDs and STARs.

However the route is quite unrealistic, not smoothed at all and the plane does not follow it 100%. In the 737 this FMC is not well integrated in the sense that it works by setting the HDG and the appropriate vertical mode instead of VNAV and LNAV. This is enough for me to say that it is not acceptable as it is quite far from a good simulation of the systems.

But I kindly suggest this FMC as a chep solution and for flying offline.

Next step will to buy and test the x737FMC that claims to be 100% integrated in the x737. With the incoming version of X-Plane, I prefer to wait before buying.

XPlane 9 arrived

noreply@blogger.com (Alessandro Caproni) — Sat, 25 Sep 2010 13:00:00 +0000

I bought XPlane 9.xx from the Laminar Reserach web site and arrived a few days ago.

I was surprised to receive the software in a so short time.

I was expecting a box but it was an envelope with the DVDs inside. I have to say that one of the DVD, the number 4, was missing. I contacted the support and they provide for sending me the DVD (not yet arrived).

The installation procedure is quite easy on windows. What I liked is that it is clean in the sense that does not write tons of things in the registry: it creates only a folder with all the software, libraries and so on inside.

I could not install all the sceneries for Europe as they are right in the 4th DVD. :-(

There are a lot of planes ready to fly. The Piaggio P180 seems to be one of the best but it is very nervous and difficult to fly. i have to say that a new version of this plane has been published a few days ago.

Looking for a serious plane to fly I downloaded a B737 and an A320. They comes with a lot of liveries.

The plane did not work and I discovered that the my XP was quite old, something like v9.22 instead of the last one (9.60 at this moment). It was quite surprising but after installing the planes worked and I liked it considering that they are freely available, especially the 737.

I am looking for a plane to fly on IVAO and to use for my home cockpit too.

Return date postponed again

noreply@blogger.com (Alessandro Caproni) — Fri, 30 Jul 2010 02:20:00 +0000

It seems that my temporary transfer in Chile lasts longer then expected: at the present the return date has been postponed to may 2011.
I have no chance to bring the simulator and the cockpit in Chile because there is no point in organizing a removal for a few months only.

In the mean time I am thinking about the future of the simulation because Microsoft flight simulator seems stuck since long time and there are no rumours of any future development.
I am planning to buy and test X-Plane that seems the only valid alternative. Since september 2009, CPFlight supports X-Plane and there are libraries to interface SIOC to this simulator too.
I will report after the testing.

Temporary stop

noreply@blogger.com (Alessandro Caproni) — Tue, 19 Jan 2010 22:22:00 +0000

Due to a temporary transfer in Chile, my home cockpit is not progressing.

I will resume the work as soon as I come back in Germany (forseen date is May the 1st).

AeroPlayer53 follow up on my blue light

noreply@blogger.com (Alessandro Caproni) — Thu, 14 May 2009 07:30:00 +0000

This period I do not have so much time for the cockpit: a new digital camera, the Nikon D300, the sunny weather and a lot of work keep me well far away from the simulator.

Riccardo just added a thread in the italian forum I follow describing the progresses of his home cockpit. As he said, the work started from the description of blue light of my home cockpit in the Cockpit light post of this blog. I found his proposal very interesting: he used strips of blue LEDs to lighten the instruments instead of the whole cockpit. He fixed the LEDs below aluminium arms fixed on top of the instruments.

For my taste, the arms are too far over the instruments and can interfere with the movements during the flight. But having the LEDs almost in contact with the panel could lead to a very good result. The reflexions, especially against a plexiglas cover, should be taken into account.

I wish to thank Riccardo, AeroPlayer53, for reading my blog and sharing his experience in the forum.

In the mean time I have received the landing gear and a new master card from opencockpits. The landing gear seems to be good and smooth even if not as smooth as I expected.

Master caution button complete!

noreply@blogger.com (Alessandro Caproni) — Tue, 17 Mar 2009 20:55:00 +0000

It took me something around four months for designing and building but the button is now complete. It seems a lot of time but you have to think that:

I don't have a CNC machine (and I don't want to buy one because is very expansive)
I wanted to spend as few as possible (what I have found on the net was around 30EUR)
I wanted to use only COTS

I spent most of the time finding the right components to use and made a design. The initial design was published in a post in december. When the project was ready, I bought the two aluminum squared pipes and started building the button with my dremel. A picture was shown in another post in february.

The button at this stage looked very ugly with the 2 big springs and it was also very hard to press because the springs were very hard. But it did its wok. You have to keep in mind that the only visible part is the upper side.
However, at the moment I had to put the leds I discover that there were not enough room in the upper side. Initially I wanted to put the LEDs in the little pipe while the moving pipe is only the big one. This solution was not suitable because the light would have passed from the holes between the pipe making a very noisy reflection. I had no other choice then rework the bigger pipe leaving more room for the LEDs:

As you can see the upper side is now longer. I have also mounted the switch: when the user presses the button, the bigger pipe shift down and presses the switch closing the contact. At this point I made an extraordinary discover: the switch is enough to move the biggest pipe in the original position when I don't press over the big pipe so the two springs are not needed anymore. The movement of the big pipe is very smoot and when the switched is cliked it emits a very nice sound. Unbelievable but is much better then I expected.
I have put screws in the upper side to hold the support for the LEDs. The support is composed of a shape piece of wood divided in 2 horizonthal lines each of which contains an array of 2 LEDs. The red line is at the top and the red at the bottom. After some investigation I have discovered that an output line of the master card can feed 2 LEDs connected in serial without resistance:

The handles in the upper side will hold the button against the frame in the cockpit.
For covering the LEDs, I have bought some white slides to print with my inkjet printer. I have printed the label in dark black leaving the written to appear in negative :

The written has been covered by a piece of plexiglas that protects the label agains my fingers.

I have finally connected the electronics to the master card and made some test to be sure that everything is working. At this point I have mounted the button in the cockpit. This is the view from the rear (internal) side of the cockpit:

And this is how the button appear in my cockpit:
In my opinion the final result is quite good. The movement is very smooth and the sound when I click the button is wonderful. The yellow LEDs are perfect but I would prefer the red ones to be stronger. However the final result is much better then expected.

Finally the cost. I think it cost a total of 12EUR more or less. I still have along piece of the sqaured pipes that I can use for other button. For example the 767 annunciator as a very similar button for the G/S Inhibit button. The same strategy could be used for korry switches but this implementation nedds a lot of space in the back side of the cockpit so it could be difficult to put two of this button enough close one to the other.

There are a lot of technical issues that I did not talk about in this post of course. If you are interested in the project, want the exact measurement or any other clarification feel free to send me an email or post a comment in the blog.

A picture of the Master Caution

noreply@blogger.com (Alessandro Caproni) — Sun, 22 Feb 2009 18:08:00 +0000

As I promised a few days ago, this is a picture of the MC.

You can see the two squared pipes, one inside the other. The upper handles will be fixed to the cockpit frame. The two springs at the bottom keep the two pipes in the right position and allow to press the button. A switch at the bottom left side catches the pressure of the button.

Now the difficult part is to fit the leds in the upper side. I have already shaped a little holes card to fit in the big pipe. The card will be hold by a set of screws in order to keep the leds upon the hole and avoiding the lights to pass through the holes of the pipes.
At the present I plan to put 4 red and 4 yellow leds in the holes. Over the card of leds, I put the plexi and over it a little piece of white paper with the written.

I hope the final result will not be so bad. As I said, at the present I have the impression that the movement of the button is not as smooth as I hoped at least compared to an electronic switch. I will go ahead building that button but I am still not 100% that this tool will never be part of my cockpit.

in fact last week I went to conrad and bought a squared button where it is possible to fit one led. I am investigating if it is possible to fit two colored leds inside the button and if I succeed I will probably choose this second solution even if the button is not as big as I wish.

Master caution again

noreply@blogger.com (Alessandro Caproni) — Mon, 16 Feb 2009 08:33:00 +0000

The master cation frame is finally ready, I will post a few pictures one of these days.

The final version is slightly different from the original design, in fact the two springs had to be put between the two lower brackets. It means that the two springs push the brackets away one from the other instead of pulling. I have tested the movement of the button and it works even if it is not as smooth as I wish. I guesst I have to put some oil between the two pieces of aluminium but it can never be as smooth as an electronic switch.

There is also another problem due to the windows made in the outer windows to let the upper brackets pass outside of the pipe to fix the button to the cockpit frame. The windows will be a problem when the leds are on because the light will pass also throught the windows creating an undesired game of lights. I have thought to two possible solutions and I will probably adopt both of them:

mount the button in such a way the window will always be below the frame (in this way I guess the light will be much less because the wood will naturally stop it; I should probably add a fisical protection like a piece of dark gumi)
try to mount the led in the upper most side of the outer pipe with a dark gumi in the back (for this implementation I should investigate the usage of special very little leds like those used to light handy phones; the light will probably be inserted into the plexi; particular caution must be applied while cabling the leds because they move together with the outer pipe whenever the button is pressed or released)

In the mean time I think it is time to start designing the right side of the cockpit. I have to put there more commands usually found in the upper side of the real cockpit like fior example the trust control, the gear lever and so on. I have submitted yesterady an order to opencockpits getting a new master card a few switches and the gear lever of the 737 (I had found a 767 model too but was really too expansive).

Master caution button project

noreply@blogger.com (Alessandro Caproni) — Fri, 26 Dec 2008 20:01:00 +0000

Here below you can see a picture of the master caution button project.

The green box is the bigger squared pipe. The litle pipe, inside the green box, is represented by a black box.
The big green box moves up and down around the blue supports (there are 2 holes in the big pipe and the supports, screwed in the little pipe, will pass through such holes).
Two springs kee the button in the upper position. When the user presses the button, a switch is closed activating a line in the SIOC software.

The blue supports in the upper side are screwd to the panel and fix the button in the right position. The other 4 supports, at the bottom of the 2 pipes are needed to blck the switch and the screws. You can imagine a hole in a pipe whenever a support is fixed in the other squared pipe.

Plexi has to be fixed very carefully because it needs to support user pressures that could be quite strong. The plexi will have a written but the caution/warning message will be distinguished by the color of the leds (yellow for warning and red for alert).

The picture has no sizes but if someone is interested I could write down a better project with measures. However, the little squared pipe is 7cm long and the biggest is 6cm. I have bought such pipes in a workshop for around 3EUR each.

At the present I have cutted the two pipes and made the holes in the biggest one. The holse still needs to be refined. and I ma still thinking which is the best way to do that.

The design is quite clear for me. But there are a lt of techinical issues that i don´t know yet how to address. For example how to fix the springs and the switch. And even which type of switch to mount.
Another point is the plexi that should have the same level of the surface of the pipe but fixed somehow to allow the user to press it without bracking or moving.
Finally, until the whole button will be ready I don´t know if the bissgets pipe will move smoothly enough inside the little one.

As usual, I will post some picture in the blog.

Master caution button design

noreply@blogger.com (Alessandro Caproni) — Fri, 26 Dec 2008 18:28:00 +0000

After browsing the web I have found that master caution buttons ready to use are quite expansive (something like 50EUR or more). I found that price so unbeliavable for a single button that Ideide to try to build one from scratch.

I bought two squared pipes with a very similar size in such a way the biggest one surround the little one leaving a very little space. I will put the leds into the little one while the bigger one moves forward and backward. When in backward position it will press a switch in order to clear the warning.

I kno that what I said is not clear enough. If I have enough time I will draw the project and put here an image.
I still have some concern about this idea but I found it a very interesting challenge.

That´s it for now. Merry Christmas and happy new year to everybody!

Cockpit light

noreply@blogger.com (Alessandro Caproni) — Thu, 20 Nov 2008 09:04:00 +0000

If you fly by night you know that it is very dificult to see the landscape outside of the windows. You can trick the monitor but the result is always bad looking. To enhance the situation you can think of turning off all the light and fly in a dark room. This strategy works of course but it is very difficult to find the keys of the keyboard or, even worst, you can't write down notes while flying online. Well, I don't know you but I have to write down al least metars, radio frequencies and take off clearances.

I agree that the problem of the lighting is temporary because when all the controls will be implemented at hardware it will not be needed anymore to find the keys of the keyboard. But what until then?

I thought about this problem for a long time and arrived to the following conclusion. I need a light that can be turned on and off independently of the simulator and maybe later on integrated with the 767 light switch. The light should be strong enough to allow writing notes and reading the keyboard but not too strong to reduce the visibility of landscape details flying by night.

I bought a couple of blue led strips and positioned in the upper right and left side of the closet. They are turned on and off by an apposite switch positioned below the table.

The following picture shows the environment while flying:

You might easily find it kitsch but for me the final effect is quite good: no artificial light reflected in the two screens, lightning is soft and relaxing but strong enough to read the keyboard or write down notes.

A possible next step could be that of integrating the lighting to the 767 cockpit. The two 24 leds strips needs 12V power that I already have in the power supply. The SIOC software already catch the events of the cabin light switch but up to now it only sends the command to the simulator. It would be possible to close a 5V output line that in turn powers on the leds with the help of a raleigh or something like that. It is something I will think about...

Last but not least the price. I payed the two strips of 24 blueleds, a 12V dedicated power supply, cables and the switch around 50 EUR. Half an afternon was the time to mount the hardware in the closet.

New radio and MCP panel

noreply@blogger.com (Alessandro Caproni) — Thu, 13 Nov 2008 09:02:00 +0000

The refactoring the radio and MCP panelsis finally completed. You can see a snapshot of the previous situation in this post. The radios were in the left side in two white wodden frames. The MCP and the EFIS were below the two monitors in a very big wodden box bought from Ikea a lot of time ago.

The idea was to have a new box with the EFIS and the MCP in the upper side and the radios at the bottom.The new panel is shown by the following picture.

As you can see the new panel is much more compact. The little screwed panel in the upper left side is intended to contain some buttons controlled via opencockpit. That panel is not as wide as I hoped so I think I will put there not more then 4 buttons. For sure it will contain the master switch and the toga.

Just behind the webcam there is the power switch and another switch to close the contacts of the dip switches of the CPFlight MCP for upgrading the firmware.

The wood is painted with a water paint and the color is RAL7043. The new CPFlight radios have almost the same color of the panel while the old ones, the MCP and the EFIS, are quite different. However the final result is not bad and for sure much better then the original situation.

Yesterday night I made my first flight with the new panel, from EHAM to LIMC. I took this photo while climbing to final FL310 under Brussel CTR:

You can see the panel back lighted. In the left screen the VC and in the rigth monitor IVAP, the FMC and the radio panel. Most of the time, I use the left monitor to browse the charts.

Just upon the rigth screen you can see the three leds of the cabin light, the read and white beacons from the opencockpits light panel.

Work in progress with MCP and radios

noreply@blogger.com (Alessandro Caproni) — Mon, 27 Oct 2008 09:21:00 +0000

Last weekend I began the building of the new panel with MCP, EFIS and radios I bought from CPFlight.

The panel is composed of a box of 64x17 cm to be positioned below the left monitor. In the upper side of the box there will be the EFIS then the MCP. At the bottom, from left to righ, XPNDR, COM, ADF VOR.

At the present the scheleton of box is completed and the elictrical components are in place. There will be one button for turning ON/OFF the electronics and a two poles switch button for upgarding the firmaware without insering the 2 dip switches in the rear side of the MCP by hand. In this way the firmaware can be upgraded without moving the panel.

At the right upper side of the front panel there is less space then I initially supposed: only a 8x6 cm little panel. I will put there the master switch, the GA and the button to switch between auto and manual setting of the VOR for the capitain.

In the first step this panel will be empty but ready for the replacement with the panel with the buttons.

For the GA button I have found at conrad a little squared button that can be reasonably used. It has no led on board and so it can't be back lighted.

The master switch is the most complex button because it has more then one led, at least a red and a yellow one for caution and warning. Till now I have found no button like that on the market. Of course it is sold by specialised web sites but it is very expansive.

The button to switch between manual and automatic VOR tuning can be one of the button (with a green led) I have already used for the light panel.

I am currently investigating the way to build the master switch and korry buttons. I subscribed to mycockpit forum and ther I have found some interesting solution. I will create a new post later with some good solution.

Refactoring of the MCP/EFIS/RADIOS panels

noreply@blogger.com (Alessandro Caproni) — Tue, 21 Oct 2008 08:29:00 +0000

It seems that next week I have to put all my stuff out of the shelf :(

I'll take the chance to fix the not working button of the light panel. At the same time I want to change the setup of the MCP, EFIS and radios. Current setup was in fact a temporary solution that is in place for more then one year.

The idea is to create a wodden frame having the MCP and the EFIS in the upper side and the 4 radio modules at the bottom. If I have enought space, I will insert some controls in the upper side of the panel. I am thinking of the master switch and GA button or the annunciators or something else. The new panel, painted in RAL 7043, will be placed below the 2 monitors, where the MCP and EFIS are at the present. Giving that I already have at home all the wood I need, i guess that this remake will last for some days only.

At the end, I will have the left side free for new panels and space on the left for e new panel that I am designing right now.

My idea for this new panel and for the following is to be modular. I mean that frame of the panel will be fixed and sub-panels will be mounted. In this way it will be possible to unmount a sub panel for upgrading or fixing without the need of open everything. Actually, this is nothing new...

Beside this refactoring, I am thinking of a new panel to put on the right side of the MCP/radios panel. I ahve thought a little bit on what controls I have to put in and I am now focused on the engines startup, the gera lever and myabe the flap. I have brosed the net for componets and I have found a gera for the 767 for 280EUR. It is crazy so I am going to build my gear level from scratch and depending on the result I will build a flap lever too.

I am quite disappointed fro the prices of hardware components on the net. Specialised web sites have crazy prices and I am probably not the best to browse electorinc web sites...

IVAP moved in the laptop

noreply@blogger.com (Alessandro Caproni) — Tue, 07 Oct 2008 12:41:00 +0000

Excited by having the hardware connected to the laptop, yesterday I moved IVAP from my desktop in the laptop. Just to be a little more clear (and repetitive): I run FSX in the desktop while opencockpit hardware (the light panel for instance) is connected to a Dell laptop.

The installation went quite smoothly apart that I had to install SimConnects in the laptop. But even this step was quite easy and automatic.
Initially I decided to have all the IVAP subprocesses running in the laptop but the connection with IVAO did not respond. I ended up having in the desktop only the GUI and the IVAO connection while all the rest runs in the laptop.

Surprisingly the IVAO traffic was immediately there, all the hardware (OpenCockpit and CPFlight) worked as usual as well as TeamSpeak for voice communications.

I still have to try with a full online flight to double check if the engine weather works well. By turning the encoders of CPFlight MCP it seems that it now reacts much better.
What is not satisfatory is that the online traffic that is not smooth enough: I have to check connecting the laptop through an RJ45 instead of the wireless.

Moens, the author of IVAP, does not warranty about increasing of performances having IVAP running in a separate windows box in connection with FSX. From this point of view my PC is too old and slow to give definite results but if my CPFlight hardware is more responsive than it means that the performances are better then before.

In place

noreply@blogger.com (Alessandro Caproni) — Mon, 22 Sep 2008 18:56:00 +0000

The panel is in place just on top of the right screen.

These are 2 shots of my flight simulator setup (without the 2 peices of my saitek X45 joy):