kneighbour

Excellent suggestions! Will amend my procedure/checklist. I have been trying to find details on many of the aircraft procedures, but so far no luck. Pretty much trial and error.

A more up to date printable checklist - Sat 4 Jul 2015 Checklist 340A.rar

Sorry, slip of the tongue on my part. The commands OBS_HSI_down/OBS_HSI_up do work just fine, but I will check out the commands you suggest. While they work, and DO adjust the CRS value (exactly the same as the CRS1 knob does), the HSI course needle does not change. My observation was that while these commands change the CRS value, they are not sensed by the Course popup display. I would not worry about the the popup display as usually the HSI needle changes. If I enter a Direct To point in the GPS, then the HSI moves and points to the DTK. This saves you using the CRS1 adjustment to do the same thing, so a nice touch. So if there is any issue here, it is perhaps that the HSI is not picking up the DTK sometimes. Also, by automatically moving the HSI needle, and not the CRS setting, the MSG screen on the GPS is not cleared. here is another example... I loaded a new flight plan. The HSI correctly showed the first DTK. I then stepped through the flight plan segments, activating each and it correctly showed the first couple of legs, but the last one failed. It should be 105 degrees, but shows 62. The GPS MSG screen says to set CRS to 105. If I move the CRS1 knob, the popup shows the CRS settings at some random setting (259 in my case). The 62 does not seem to be related to anything. The three segments in this plan are 113, 032 and 105. In the GPS I move to each segment and then Activate that segment using the Menu button. If I go to each segment and then press the Direct To, then the HSI will adjust correctly each time. I use the HSI on other aircraft all the time. I usually fly using the GPS and the HSI, so I know how it works generally and with most other aircraft. In fact it was why I waited to buy this version of the 340A. I needed the GPS functionality. And on other a/c, HSI needle certainly moves with CRS adjustment in this mode. The 340A seems to be different, and if that is as designed, fine. I have noticed this issue a bit as I have been using long flight plans, and often the HSI needle is not pointing to where I am flying. The aircraft still flies the flight plan ok and the autopilot tracks correctly. The deviation indicator on the HSI also seems to be working ok.

thanks for those 'tweaks'. I have adjusted/fixed a few things myself. Will upload an updated list at one point. I am trying to work things out from the performance charts, and am getting there.

This all worked just fine in V1.2 as far as I can recall. Funny things are happening in V1.3. Set Nav selector to NAV S L. Set EHSI to ROSE mode I setup a flight plan in the GPS and use the CDI button set it to GPS mode. The EHSI correctly goes to LRN1. The distance shown is correct. The DTK on the GPS is 233 degrees. The MSG error comes up on the GPS, telling you to adjust the CRS to 233, The NAV Course pointer on the EHSI is showing 245 degrees and the digital bearing reading is 245 degrees as well. This is all fine - usually what you do next is adjust the CRS1 control to move the NAV Course pointer to the GPS DTK - 233 in this case. When you adjust the CRS now (either with the CRS1 control on the pedestal, or with my hardware control), the CRS does change. When the Course is at 233, the MSG warning on the GPS goes out. As you are doing this, the Course 1 Selection popup adjusts as you move the CRS1 knob on the pedestal. It does not move if I use my hardware switches connected to the OBS_HSI_down/OBS_HSI_up commands. But these commands do actually change the Course, it is just not indicated. The problem is that the NAV Course pointer on the EHSI never moves. It remains at 245 degrees the whole time. It is not indicating the CRS. If I change the active leg on the flight plan, the NAV Course pointer does move, but to what seems like a very random direction. No idea what the relation is to the direct track, but as far as I can see, there is no correlation. If I put the GPS in GPS and OBS mode, the deviation indicator on the HSI works as normal - although it is perhaps a bit too sensitive. But it looks basically correct. The Course 1 Selection popup displays correctly for the CRS1 control, but not the X-Plane commands. If I put the GPS in VLOC mode, the NAV Course pointer moves with the CRS1 control, and also the two X-Plane commands. The Course 1 Selection popup displays correctly for both X-Plane command control and CRS1 control. So this is all as expected. If it is a problem (ie not as designed), then it seems to be the same on NAV S L or NAV S R.

Good to hear that other users having the same/similar problem. I don't feel quite so stupid! Usually when it happens to me, neither engine will start once one fails to start. But now I know not to bother - I know i have to do a reload, so perhaps sometimes the other engine will start sometimes. Not sure what you mean here. How do you stop the start procedure? One of my issues is that the engine will stay in motoring mode for ever. I have had the battery down to 10V and dropping. I have even turned both batteries off then on again - the motoring continues unabated. This is with no external power.

Yep - that is what I plan to do.

I was not even intimating that there was anything wrong with the systems (except for the fact that once it starts motoring, it goes until doomsday). I fully agree it is something I am doing. Using Autostart will not help in diagnosing that. I don't think it is a checklist item as they are all pretty much digital - ie I either do them or I do not. And I do them. My current hypothesis is that I am not accurately lining up the Condition levers. They certainly LOOK like they are lined up, but will try to play with slight misalignments and see if that is the issue. Did 3 starts yesterday, no problems.

Only a couple of times. Worked each time. But have not used it enough to build up a history. Yep - that is what I do. Probably even a bit longer. Ok. Since that noise I hear on a good start is combustion firing up, that makes sense. I originally thought it was lack of fuel causing the problem, because when it goes into start sequence, the fuel gauges turn off. But that is just the gauges turning off. I certainly have the Condition levers on the indent. Also have enough fuel. So not sure what else to check. Oh - one thing there - I always put BOTH condition levers on the Start line, plus the throttles on Idle. If one engine does this, the other engine will be the same. ie neither will start. If nothing else, surely the engines should not motor on forever? Is there not a timeout function in the startup sequencer? Having to reload the aircraft seems a bit extreme.

There are a couple of checklist items that say to CHECK an item. Not sure what I am to check for. Before Engine Start Hydraulics (CHKD) - check for what? Climb T/O Inhibit (OUT) - the light is out, is that what you check? Approach HP Valves (SET) - to what? Landing Hydraulics (CHKD) - check for what? That is all - nothing critical or anything. I am still flying around without knowing these things, so am guessing they are not too important!

I mentioned in another thread that sometimes the engines will not start. Best to start a new post, I thought. Tonight I did 3 starts, 2 on external power and 1 on battery. The first one on ground power failed. The other two worked just fine. I all cases I used the checklist and to the best of my knowledge did not miss any steps. But it is possible. One thing I have noticed. When you press the START switch, the engine starts to motor up. The Temp goes to about 29 degrees and stays there and the RPM goes to 20% and stays there (forever). Also, within a few seconds you hear a pretty strong blast of air (if it is going to work). I don't know where this air comes from, or indeed if it is an air blast at all. If the engines are not going to start, this 'air blast' does not occur. You then have to reload the aircraft (with all that entails). I know it is not much to go on, and it does not happen very often, but perhaps other users are seeing this as well and have noticed something I have not? And by 'not often' - it has happened perhaps 3 or 4 times in the last 10-15 starts. V1.3 in Windows x64. XP 10.36.

Brilliant, if you ask me. I doubt very few people would even do a battery start, let alone know about battery temperatures if they did.

I'm impressed that it is modelled at all. Very impressive minor detail that few would notice, I am guessing. Is there a solution to the case where the engine starts motoring. but never stops? Even if batteries turned off, then on again? Even if batteries down to 10v?

I followed your battery start procedure and it worked perfectly. I don't know what I did the first time. The only small issue is that the batteries take a fair time to cool down after a battery start. Perhaps being a simulator, I am not keen to hang around while they cool! But they cooled down ok once I was in the air, so no problem. They charged very quickly - a few minutes. Anyway, got that bit all worked out now. Did a few very nice touch and goes tonight. It drops like a rock on finals if you don't watch it, but that is fine. Just need to finesse the technique there a bit! Once you get used to it, it is very nice to fly.

Good to know. Thanks.

This is not a problem in any sense of the word. I just recently noticed that there are no height warnings on landing. No voice announcements anywhere, as far as I can tell. I just want to check that I do not have a setting turned off or something.

Of course! Stupid me...I should have thought of the clearances, required, etc. Good - all cleared up. Thanks again.

Yes, I see why you would turn the Avionics OFF before engine start. Just cannot see why you would turn them ON at the very start. They would hardly have had time to warm up before you have to turn them off again. Thanks for the bleed air description. Love this level of detail....

Excellent information! Just what I am looking for. Thanks for that. It is interesting that you put the Condition lever in the 'Start and feather' position. Not the Start bit obviously, but that the thing is feathered. It is obvious when you say it - just never thought of it that way before. I am trying to document an Engine Start Procedure, so the more information I can work out the better. If I can trouble you for two other small questions I had in this area? 1. The Checklist (and the start video I watched, frame by frame) puts this step R BLD VALVE - move to reset and then AUTO (or left of course) BEFORE starting the engine. It does not seem to do anything at this time as there is no bleed air. It makes more sense to me to place this operation AFTER the engine has started and stabilised. Which is correct? 2. The start video I watched turns on L AVION and R AVION just after connecting external power and turning on the batteries. Then, just before starting the engines, it gets you to turn them off again. I am not sure why this is done or even if it should be done. I see why ESS AVION is turned and left on (to show the fuel gauges for one thing). But cannot see the point of turning on the Avionics for such a short period of time. Thanks for any information. It would be lovely if I could get my hand on a POH or similar!

It seems possible to start the engines on battery - the thing is to put them in series and not parallel. The manual mentions the Series/Parallel Relay (pg 61) but it does not mention how to set this relay. How do we start just using the battery? I tried - by simply not plugging in External Power. This does something funny that I hope there is an answer for. You hit the START switch and one engine starts to rotate, but I guess it does not go fast enough to trip the ignition system or something. The thing is it will do this now forever. I currently have the battery down to 10V and it is still turning! I can even turn the batteries off and then on, and it is still turning! Is there anyway to stop this? I ask - not just in this situation - but a few times a start has not worked and I can see no way of getting out of it except to reload the aircraft. I just did a night landing and was surprised to see that there were no landing lights - made things a bit awkward! Only later did I work out that you only get landing lights if you have HDR turned on (which I can't)....

i assign a joystick button to the command - LES/CMD/CW/button/AP_disconnect. That seems to work just fine.

Very much appreciated! If not too much trouble, would also appreciate the Engine Start procedure....

On my last flight I lost one engine. Not sure why - first I knew was the Fuel warning light came on and then noticed one engine had died. There was plenty of fuel and in fact kept flying the rest of the flight on the one remaining engine. I attempted a midair restart on the dead engine, but nothing seemed to work. Since I do not know the procedure to restart in flight, perhaps I messed that up. In the end I turned on Autocoarsen and that seemed to help feather the dead engine. Speed dropped, but continued the flight. Actually, the Tutorial Flight in the manual. I guess I should have turned back.... Anyway, was wondering if anyone knows the proper procedure to restart an engine in flight, and failing that, to shut it down? I could have missed that section in the manual, if so would appreciate someone pointing it out to me if that is the case. Thanks.

Not me. I fly almost exclusively in FSE. I tend to fly the same (or very similar) routes over and over again, kind of emulating what pilots do in real life. So it becomes very routine, and I like to make every flight as accurate and smooth as possible. It is better if you do everything by the numbers, so then every flight is duplicated exactly. Sounds boring when you say it that way, I guess, but I pride myself on getting everything just right and not spilling any passenger coffee. ie smooth NAV intercepts, that sort of thing. And of course no RL pilot would ever just fly without any on type training...same here.

I think a lot of it is wrong, which is why I posted it here. I will see if I can flesh it out by doing a lot more flying. Hopefully more experienced pilots on type can give some pointers. Already I can see some errors.