Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

JS41 Engine start - no rpm

Featured Replies

Well I uninstalled the J41, reinstalled it went through the normal process and it started like a dream. Just completed my first FSPassengers flight with it and all the passengers were happy :( :( Don't know why it wouldn't start before but I've now got a saved flight with everything started and ready to taxi (just in case it happens again) and another flight after it's been shutdown completely, ready for a fresh start next time round. :( Fingers crossed for next time.BadgerPS: I too had followed the start up instructions to the letter and had them engrained in my brain but I couldn't start the second engine (whichever one I started first, the other wouldn't start) until I uninstalled and started again. Latest update. Loaded up FSX and tried to start a new flight but the same old problem arose. It seems like the props are feathering again after I have started one engine so what I've done is leave the throttle in full reverse whilst I've started each engine and when the first engine has stabilised I put that one back to the neutral position (the other one stays in full reverse). I then start the other engine and when that's stabilised, press F1 and away we go. Seems to work for me and avoids the apparent refeathering after starting one engine. I don't know if this will help anyone but thought I'd explain how I got around this in case anyone else has this problem.

  • Author

Hi,just to be sure - a quick and dirty start for the engines needs only??!!1. Battery and GPU on2. Fuel Pumps on3. Props unfeathered and locked4. Starter 5. StartbuttonEngines won't ignite!! No movement of the props.That's the way for me to test quick or do I have to go through the whole tutorial?Tom

  • Author

...finally got it to work.The problem were the goflight push-button-module.I configured it for engine starter before.I have read that pmdg do not support these modules. So it don't come to my mind to push the starter button at the hardware. I alwayspushed it in the vc.Well what shoudl I say. I tried today to start with the goflightand finally it worked.Lucky me.Thanks for your help.Tom

That is great. I couldn't figure out why it wasn't working... but then you didn't add the extra hardware into the equation either.

Dan Downs KCRP

That is great. I couldn't figure out why it wasn't working... but then you didn't add the extra hardware into the equation either.
Good time for a reminder... (no flame intended) :( To provide expeditious assistance, it is important when posting problems that we get a list of everything that is interacting with FS. All add-ons, all hardware, all software, etc. Also, to isolate the problem when troubleshooting its best to start with the basic airplane and then one by one add things back. Many issues end as this post has with the problem being caused by something external to the PMDG product and not mentioned in the original post. We are here to help but it makes it much easier when we have the complete picture. :(

George Morris

 

Boeing777_Banner_BetaTeam.jpg

  • Author

Of course you're right.Sorry from here.Tom

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.