kenny584

Hi Ron. Can you advise me how to access the Jet Aviva charts you mention? I've had a quick look at their site but unsure where to look. Cheers...Ken.

Hi Adrian. EGPH has five arrivals. Only two of them involve the TLA vor and they are both from the west. Coming up from KK you would indeed use the INPIP1E arrival. Scottish control would hand you off to tower who would then vector you by giving you headings to fly to intercept the ILS. That's what I meant by saying you would simply flying a heading to intercept the ILS. The direct entry approach from TLA takes you to EDN which as you say, is the IAF for that procedure. The two plates are not connected. Cheers...Ken.

Hello Adrian. The Arrival into EGPH from EGKK would probably be the INPIP1E arrival. After you complete that phase ATC would vector you for the approach. If you were offline then you would probably just give yourself a heading to intercept the ILS for 24. There is a chart showing a direct arrival from the TLA vor. That is mainly used for arrivals from a more westerly direction. Can you explain further what was wrong with the approach? It is good information for others to know. Do you have the current Navigraph AIRAC cycle for the route? Regards...Ken.

Hello Adrian. Remember that this is a business jet, quite often on charter. It is normal to enter the flight plan bit by bit for each individual flight. The way I enter the plan is to first of all hit the FPL select key and then rotate the inner (small) FMS knob to select the Destination Waypoint screen. Rotate the outer knob again to select the flashing cursor and enter the destination airport by use of the keypad below the MFD then hit ENT to select your destination. The display will revert to the Active Flight Plan screen with the Destination flashing and a Magenta arrow beside it. At this point I now select the PROC key to bring up the Procedures screen. Scroll down by using the outer (larger) FMS knob to SELECT ARRIVAL and hit ENT this action will display the Airport screen with the airport code flashing. Scroll down (outer knob) to the ARRIVAL box and then scroll the inner knob to select your arrival to the airport and hit ENT. You may also have to select a Transition and runway dependant on the selected airport and arrival. The arrival sequence should be showing in the SEQUENCE box. If it is consistant with your arrival chart then scroll to LOAD? and hit ENT. Select PROC again and scroll to DEPARTURE. The airport screen wil show again, this time with your departure airport showing. Scroll down to select your departurre SID and check any runway or transition. The sequence should be as your chart. These sequences are of course dependant on you having an up to date navigation database. They may be different from your charts if out of date. Anyway, if all correct select LOAD? and hit ENT. You will now see the MAP screen with your flight plan showing as a white line. Now, if you wish to enter waypoints or intersections along the route then select the FPL key and the ACTIVE FLIGHT PLAN window will appear. Your Departure will be flashing in white with a magenta arrow going to the first point of your SID. Scroll down to the white ARRIVAL. This is where you enter any intermediate waypoints into the plan. It will be flashing, indicating that it is ready for input. Scroll the small outer wheel\knob and the STARTING WAYPOINT screen will appear with a flashing cyan box. You will need to scroll the outer knob once to select the flashing cursor and then enter the waypoint name and then press ENT to accept it. You can scroll to adjust the altitude or flight level. It will also take you back to the MAP page with the waypoint centred. You have to repeat this procedure until all of your waypoints are selected. By ensuring that you scroll to the flashing ARRIVAL, any new waypoint will be entered in above it. I apologise for the long reply but it works this way. There is a great tutorial in the Forum by Celin101. Best Regards...Ken.

Hello Adrian. I am sorry to read of your problems and know how frustrating this aircraft can appear to be. A lot of people's problems come from not managing their airspeed. There is no autothrottle in the 300. This means that the pilot has to monitor the indicated airspeed and match it to their selected airspeed. It appears that some folks are flying it like an airliner and expecting too much of or not fully understanding the FADEC system. Anyway, Here is what I see and do when changing altitude or flight levels. Initially, on departure, if your SID has a stop altitude of 6000 feet then set that in the Altitude ribbon as normal. Then decide on what seems a sensible VS, say for an example, 2000 feet. I know the aircraft will climb steeper than that but this is just an example. Then select a sensible airspeed, say 220. Set this in the Selected Airspeed box above the speed tape. On departure you should be seeing VS2000FPM (in Green) and ALTS (in White) in the Flight Mode Annunciator (FMA) in the PFD. I am carefull to select CON\CLB for the thrust levers and match the indicated airspeed to that selected. On approaching 6000 feet, both the VS2000FPM and ALTS go off and PIT (in Green) will appear in the FMA. The VS will reduce quite quickly and as you reach 6000 feet PIT goes off and is replaced by ALT (in Green) in the FMA. Be careful then to adjust the thrust to maintain selected airspeed. Let's now say you anticipate a climb to 41000 feet, FL410. Select a sensible airspeed, this will determine your rate of climb. Let's say 250 knts as an example. select 41000 in the Selected Altitude box and adjust the indicated airspeed to match the selected. Then select FLC mode. FLC (in Green) and ALTS (in White) will show in the FMA and the aircraft will pitch up at a VS to maintain 250 knts. You will have to monitor the indicated airspeed and adjust the thrust to match the Selected Airspeed otherwise as the aircraft climbs into thinner air it will start to pitch up and down in an attempt to maintain 250 knts. This is the FADEC system managing the engines. The airspeed may start to fall off as you climb and you then have to decide if you wish to maintain airspeed or VS. Adjust either one to maintain the other if that makes sense. There is a great pdf by Embraer here...http://aircraftstudyapps.com/wp-content/uploads/2019/04/Phenom-300-compressed.pdf Section three covers the Automatic Flight controls. I hope I have not come across as teaching you to suck eggs and perhaps your system is behaving differently from mine but I can honestly say that once you get a grip of the systems this is a beautiful aircraft to fly. I know a lot of people moan about it and say they have problems but I think it all comes down to understanding the routines. Best Regards...Ken.

Emmm...Perhaps I am not doing things correctly but I use FLC mode to change altitude up or down and it works really well. For example, when departing on a SID, I have matched my indicated airspeed to the one I have selected and fly to the STOP altitude on the SID. Prior to getting there I select my preferred enroute FL and select a sensible airspeed. I advance the thrust until my indicated airspeed matches my selected airspeed, this should be within the detent range of CON/CLB, I then select FLC mode and the aircraft smoothly starts an ascent to the selected FL. For a descent, I select my desired airspeed and FL or altitude, then reduce the thrust until my airspeeds closely match and then select FLC wherupon the aircraft will commence a smooth descent. If ATC request a climb or descent then it is better to use the VS mode and adjust thrust to match the selected airspeed. This works well for me. Regards...Ken.

Hello doc-dutch. I fly the 300 in FSX without any problems at all. I do not have P3D so cannot comment on that sim. I can only refer you back to my previous reply in the thread where I said that I had to uninstall and re-install the aircraft and also the Extension pack. I had to do this several times. I have no idea why. It was almost as if the installer was skipping files and it took several tries before they were all in FSX. I know it is weird but that worked for me. It seems as if some pc systems are having issues when others are not. I can make flight plans in the G1000 and fly SIDS and STARS without problems. I do monitor my indicated airspeed and match my selected airspeed before selecting FLC mode. I think that some folks are expecting the FADEC system to do everything. The 300 does not have Autothrottle. I believe that is why some people are complaining about the erratic porpoising behaviour when selecting FLC. They have not manually managed their airspeed.

Hi Folks. Here's what I do and it works for me. I am not a RW pilot but I find that trial and error in the sim is the best way to find out the little foibles of indiviual aircraft in the sim. The weight of the aircraft determines the V speeds, I select an airspeed for the initial climb out and then after gear up and flaps inboard I set the power to climb and check the indicated airspeed. As it approaches the selected airspeed, I activate FLC mode and monitor the trend in the airspeed tape. The aircraft will adjust pitch to aquire the selected airspeed, I have to do my bit as pilot by monitoring the trend indicator and adjust power to match the trend. Once the power setting and pitch angle match the airspeed, I leave well alone and simply monitor. If I am cleared to a new FL or altitude I select an appropriate VS and adjust the power to match my desired airspeed. I find that it is all about power and pitch to match my selected airspeed. There are some very good YT videos by Jesse Flies. He pilots the 300 in and out of various airfields in the US and Mexico. Best Regards...Ken.

Hello Andrew. I am in the same boat as yourself regarding my time frame. My wife and I took some time out for shopping in Livingston and general R&R. I have now progressed quite a bit with LINDA and my FSX actions. I am really quite pleased with my progress, so at the moment there is no real need to get back to me on this. I still have to reload FSUIPC at every start of FSX, both buttons and axes. I'm not sure why but there must be a reason for it. It's not a problem as such, just a slight inconvenience. I am now at the point of taking snippets of code and adding them to a user file for my Duke v2. I am thinking about a button box and switches to give me more scope in LINDA. I am now enjoying this having figured out my earlier mishaps. Warm regards...Ken. p.s. with regard to the windshield switch in my other post, I'm working on it now that I have sussed the tracer and the LUA code. I'll post back later with any result. So again, no need to take up your time with it at present. Cheers.

Hi Folks. After a bit of head scratching and more than a few user errors, I have finally managed to make use of the supplied module for the RealAir Duke albeit the turbine version and I am using the piston V2. I am excited because I now have the Invertor toggle working from my Yoke. Believe me, this is a big step forward for me as I am not really a techie. It take me a few tries before I understand things!! I have made an attempt to use the tracer to locate the Lvar for the windshield heat switch. In the real Duke this acts as another invertor. I see the function and have made a new short code in the user.lua file. However, it does not work. I changed the zero and one numbers around because that is the way it looked to be in the tracer for the ON and OFF positions. Here is my entire user.lua file:- -- Dummy user functions file -- =========================== -- This file is loaded right after main actions.lua script loaded. -- You can use this file to: -- 1. Override any functions or settings in main script -- 2. Execute any desired startup sequence for this aircraft (i.e. your own c&d state macro) -- 3. ... use your imagination -- This file will not be replaced on the aircraft module update, so all of your modifications -- will remain active. Best practice from this moment is DO NOT MAKE ANY CHANGES in original -- actions.lua file. Make all the modifications HERE. -- insert your code below here: -- module 1.1a_KG -- October 2019 -- ################################ -- RealAir Duke Turbine specific functions -- ################################ -- ## Electrics ##################################### function DukeT_Windshield_Heat_on () ipc.writeLvar("L:Duke_Wshield_Heat", (1) DspShow("Heat", "on") end function DukeT_Windshield_Heat_off () ipc.writeLvar("L:Duke_Wshield_Heat", (0) DspShow("Heat", "off") end -- Just a message in console _log("[USER] User's modifications script is loaded...") Please treat me gently as I am a newbie at this...but could someone tell me what I have done wrong and perhaps also what the code should be to make this work? Regards...Ken.

Okay, my mistake. I have now selected the 'yoke' rather than 'other' in the Joysticks setup. In my defence, I have had to uninstall and re-install so many times to get my head around what is happening that I assumed it would have my original selection. Dohh. I am still having to reload the buttons and axes in FSUIPC each time I start the sim though. I still have not worked that one out. Regards...Ken.

Hi Folks. Can anyone explain why the LINDA Joysicks page has started to show the icon with the six buttons and three sliders as my CH Yoke, rather than the Yoke icon that it used to display. I'm assuming that it makes no difference but it should show the Yoke icon. I am using ver. 3.0.12c and FSX-SE Regards...Ken

Hi Folks. It turns out that having to reload FSUIPC after making a change in LINDA is quite normal as the FSUIPC.ini file needs to be updated. That makes sense now that I have had it explained in the FSUIPC forum. I still have no aircraft in LINDA apart from the FSX Default and I am unsure why. I now have the default C172 the way I want it to be with my CH yoke and the shift functions and am wanting to move on to the Duke but it is not in eirther of the Aircraft folders. In fact there are no other aircraft apart from FSX default. Can anyone help please? Regards...Ken.

Okay, I have just about had it with this. LINDA is constantly doing strange things. It stops working altogether and I have no option but to delete the folders and files and then re-install. However, this time it only shows FSX Default aircraft when previously it found the other aircraft in my Aircraft folder. I also still have to reload the Buttons and Switches in FSUIPC after each new button assignment in LINDA. I have not progressed past setting up the default aircraft never mind attempting to make a module for the Duke. Can anyone help at all?

Hi Folks. Can anyone explain why I have to reload the AXIS settings and button settings in FSUIPC 4.974? I have to do this each time I try and set up my CH yoke in LINDA. I am really getting quite confused by it all . I am trying to get the latest version of LINDA 3.0.12 to recognise the basic setup for the FSX default aircraft as per all of the manuals and other online instructions I have read. I am finding it heavy going as LINDA and FSUIPC seem to not like what I am doing. Regards...Ken

Okay, I found a line in the Duke Turbine and the Piston v2 Linda.cfg file that referenced the Parking Brake. After backing up the file I deleted the line and the brake no longer activates on button 2. I'm learning slowly but it's very confusing. Perhaps just a few senior moments on my part. Regards...Ken.

Hello again Folks. I now have LINDA starting with FSX-SE. Not sure what I have actually done but I noticed that there were differences between the FSX and FSX-SE files in both modules folder. I copied and pasted from FSX to FSX-SE and LINDA now starts in steam edition. However, I am still left with the fact that the Parking Brake comes on with a button two press. I have checked several times and there is no obvious mapping for it in FSUIPC version 4.974. I am using LINDA 30.12c. I am in need of some inspiration with this button 2 thing. I am stumped and have run out of ideas. Oh, and LINDA is not recognising my yoke buttons at all. I do have the Duke selected in the sync to sim window and it is showing as enabled and has all the buttons etc but they are not being recognised. I must have fouled up somewhere with all of my efforts at 'fixing' things over the past few nights. Can anyone help? This is in FSX-SE. My FSX boxed edition LINDA recognises the yoke buttons. Oh boy, I'm really confused regarding this!! Regards...Ken.

Hi Folks. I am still finding myself being confused by the actions of LINDA, FSUIPC and FSX. I thought I had it sussed with regard to assigning buttons to switches in my CH yoke and the Duke B60 piston V2. That is until I tried to use the Shifted functions. It may well be that my level of understanding of the relationships between all three programmes is insufficient at present but here is what I am pulling my hair out with... 1) I have deleted all FSX controls and have no buttons and switches assigned in FSUIPC. 2) I have been able to assign the HEADING BUG DEC:0 and HEADING BUG INC:0 to buttons 3 and 4 in the yoke (left/right toggle) LINDA button numbers. Unshifted mode 3) I have been able to assign the Trim ELEVATOR down and Trim ELEVATOR up to buttons 11 and 12 in the yoke (up/down toggle) LINDA button numbers. Unshifted mode 4) I now wish to assign button 2 in the yoke to the SHIFT CYCLE mode in LINDA... However, when I press the yoke button the parking brake in the Duke activates and I get the red sign in FSX (lower left in screen). I used to have this button activate the parking brake but now have the brake mapped to a keypress in FSUIPC and it works. I have no idea why the number two button is still activating the brake as I have unmapped it in FSUIPC and deleted it from the FSX Controls. I really would like to have the number two button activate the SHIFT CYCLE mode in LINDA as I want to assign other functions to the yoke toggles. Namely, the VOR1 OBI inc/dec and the KOHLSMAN inc/dec in SHIFT1 and the VOR2 OBI inc/dec in shift 2. Can anyone point me to a reason why the parking brake is still being activated by button 2 when I have unmapped it in FSUIPC and deleted the yoke assignment in FSX controls? There are no Button assignments in the FSUIPC.ini file in the Modules folder. There must be another location holding the original mapping of the brake to button 2 but I have no idea where or why. I have been trying to figure this out for a few days now. I am using Windows 10 and FSX and the aircraft is the RealAir B60 DUKE piston V2. The Duke is showing in the SYNC to SIM window in LINDA. The strange thing is that in the default aircraft the number two button does not activate the parking brake. It only happens in the Duke. Another strange thing is that LINDA does not start with FSX-SE. I have the appropriate box ticked in LINDA so it should start as it does in FSX but I have no idea as to why it will not start with FSX-SE. Any and all help is appreciated. Best Regards...Ken.

Hello Andrew. Many thanks for your reply and apologies for posting in the wrong thread last evening. It was getting quite late and I was a bit frazzled at my inability to work out what I should be doing. Stinger2K2 has also helped me this afternoon. With his input and your reply to my question, I now have a greater knowledge of what goes where and how to map switches to buttons etc. I am always amazed at what a great hobby we have and the fantastic people who give so freely of their time and knowledge. Warm Regards...Ken.

Hi Folks. I have recently discovered LINDA and have a very basic beginner question. With the help of Stinger2K2 I now have my CH yoke buttons working various switches and knobs in FSX. However, I have now seen various modules and one in particular for the RealAir Duke B60 piston v2. My very basic question is this. What do I do with a module? When I look at the modules I can see the code which at present means very little to me although I can follow through what happens but have no clue as to what the various numbers and symbols mean. That's not quite true, I know about the offset numbers but do not fully know how to use them yet. I would like to know where to place the module and how to make it work. I am interested in assigning a yoke switch to the Duke invertor switch and the Lwindshield switch. There is no FSX event for them but the invertor is in the module but I do not know how to proceed with installing the module into LINDA. I hope this makes sense. I just need a nudge to get going with 'installing' and activating the Duke module. Best Regards...Ken.

Hi Guys. Roman, I'm not too sure what config program you mean. I have activated the Duke B60 Config Panel [Options] but there is no GPS HSI Course. Do you mean the RealAir Duke B60 Config Panel? Mine is marked as Copyrght 2009 and only has options for Ground Steering, GPS Startup, DME Indicator Startup, VC Glass Reflections and on the right hand side of the window there are two other options. Cockpit state on startup and RealView Stall Buffet. I'm thinking that you must have a more up to date version than mine. I have all the options set for Cold and Dark but there is nothing for the GPS HSI. Bert, the only Hotkeys mentioned in the .cfg file are three relating to Camera Definitions. Namely, 0 'Right Seat', 6 'Cabin' and 7 'Rear Window'. I'm thinking that none of these will affect the workings of the Heading Bug and Course Selector but I disabled them anyway. It has just dawned on me that I should have said that I have the Flight1 GTN750 installed into the Duke but unsure whether that would make a difference to activating the toggle. I do not wish to take up a lot of your valuable time but I really would like to get this working. It has become a bit of an obsession now that I cannot think why it is not working. I'll keep looking for ideas online but if you do think of anything else please reply back. Regards...Ken.

Hi spokes and hello again Bert. I never thought to check the Duke options feature. I was thinking that was just for weight and balance and fuel etc. I'll check it out. Bert, thanks for the input, I appreciate it. I'll try that also. I'll do them one at a time and report back with any result. I'm doing my Vatsim P5/ IR in the Duke and using this toggle will save me having to reach for the mouse. Cheers...Ken.

Hello again spokes. Okay, I have looked at the FSUIPC .ini file, the buttons section, and it looks to be okay. I do not have a profile for the Duke. My CH yoke buttons 2 and 3, left/right toggle, will trigger the heading bug in the default Baron and other aircraft but not the Duke!! After a button reset, it will trigger the NAV2 OBS INC and DEC in the Duke but not the NAV1 OBS INC and DEC. It just seems to be locked out somehow and it's driving me nuts. Setting various Key presses will not action it either. I'm stumped. I am wondering why yours works and mine does not. Any other thoughts? Regards...Ken.

Hi spokes. Yeahhh, I'm sure that I have tried those commands, I'll have another go. I have not tried profiles because I mainly fly light GA aircraft and they are pretty much of a muchness. One set of instructions regarding buttons and axes fits all e.g. Gear, Flaps, Trim etc. I have not looked at .ini files either. Again, I'll have an in depth look at these. Both for FSUIPC and the Duke, in fact anywhere!! There is something that I am not seeing and it annoys me because I have been simming for yonks and am usually pretty good with files etc. I dabble in scenery and repaints so I'm not a beginner but this has me stumped. I'll keep you posted and would appreciate further help if required in my investigations. Regards...Ken.

Hi Folks. I have tried for a long time now to figger out why I cannot get the Nav1 OBS heading bug and course selector to move by using a toggle on my CH yoke. The Nav2 OBS responds to my toggle button input and other aircraft will allow me to use a toggle to increase and decrease the heading bug and course selector. However, as I say the Nav1 display in the Duke has me beat. I have tried various options in FSUIPC but not LINDA as I have no experience with it. Can anyone advise if there is something hard coded in the gauge to stop a toggle button from operating it. The mouse will of course operate it but I'd like to use a side to side toggle. I have the up/down toggle working the trim wheel but cannot get the Nav1 OBS to work with the side to side toggle!!! All ideas appreciated...Ken.