Jump to content

N1 going down when advancing thrust


admiralaspen

Recommended Posts

Hi I searched the forums for a few days to see if anyone else encountered this issue.

 

When I start to taxi the aircraft I advanced the throttles just a nudge forward to start taxi, then I get a drop in N1 from 21.1% down to 19.9% for a second or two then the thrust increases.

Same goes when reducing thrust from say 30% to idle I see a jump up to about 35% and then a drop towards idle.

Maybe this is how the aircraft works in real life? But from videos I've seen I've not seen this issue and it's only present in sub 50% N1.

 

First I thought that maybe fsuipc was doing something spooky here but now when I remapped the throttle through P3D Controls it's still the same, infact if I use just one press of F3 I see the drop of N1 to 19.9%.

 

CRJ Version: Latest 1.0.2.0

Simulator: P3D v4.1

OS: Windows 10 x64

Throttle Quadrant: Thrustmaster Warthog HOTAS

Link to comment
Share on other sites

Yepp. I have it as well.


Not a big deal for me since its remedied quickly but since Mathijs asked :)

 

I should add that I have exactly the same specs as the OP wrote. Maybe that is a lead...?

Link to comment
Share on other sites

To update some on my issue.

Last night I had this issue happening >50% N1 while in the descent.

 

What I noticed is that the issue gets worse the smaller the throttle changes that I do. I've started logging FSUIPC axis inputs to look for abnormals but it all looks fine, I tried every configuration alternative for throttles.

I've tried disabling different applications such as AV, Process Lasso etc. but no luck.

Tonight I will enable logging in the CRJ manager to see what input the CRJ gets from throttle positions, a question there which logging level should I use (1, 2 or 3)?

 

Edit: Also noticed that if I slam the throttles forward into any detent, CLB, TOGA or MAX, the issue isn't there.

Link to comment
Share on other sites

1 hour ago, Mathijs Kok said:

The only logical reason is spikes in the signals from the controllers.

I would think so as well if other aircrafts had issues, but it's only the CRJ that has issues. Anyway will continue to try a few things tonight.

 

Edit: The raw data from the controllers are fine without any spikes anywhere.

Edit 2: Also the issue is there even when I press F1, F2 and F3 to move the throttles as well as when I move them in the VC by using the mouse. So something else is fishy here

Link to comment
Share on other sites

  • 3 weeks later...
3 hours ago, Mathijs Kok said:

Well is an almost 100% sure sign of noisy potmeters. Have you activated the option in DAVE that might help with that?

I would agree if I hadn't tried to unplug my TQ and use F1-F4 keys and still experience the issue. Is there some way to provide you with additional logs or anything?

Link to comment
Share on other sites

  • 2 months later...

Hello!

 

Another update on this issue. Still present in 1.0.5.0 and I did notice that issue only appears when both engines are started. With only one engine started N1 behaves normally against throttle input.

So after seeing this I tried to disable N1 sync but nothing changed. I've even gone so far as to reinstall my P3D v4.

 

Best regards, Kristoffer

Link to comment
Share on other sites

5 minutes ago, Hans Hartmann said:

I've been watching out for this all the time since I first read about it here. However, I haven't seen it yet. What do you use to control the throttle?

One axis on my warthog TQ setup through FSUIPC as Throttle axis. Have tried setting this up in all three ways supported by the CRJ (P3D standard controls, FSUIPC and FSUIPC advanced throttle setup)

Weird part is that it doesn't matter if I use the standard Keyboard shortcuts (F1-F4) to control the thrust, more specifically F3 to increase in small increments, or if I use the mouse in the VC to move the thrust levers. I still get the same result.
I've tried disconnecting all my controllers as well and only use keyboard/mouse controls but still the same issue.

Link to comment
Share on other sites

  • 2 months later...

Hello,

 

Just to update on this issue.
Yesterday I tried out different settings, more specifically "Sensitivty"-slider in P3D. I found a sweetspot of 110 sensitivity but this remove the upper part of the throttle quadrant.
I started thinking that it seems like the idle detent in the cockpit is not in sync with idle input from the throttle lever (When sensitivty is set to 127)

So a workaround could be:

  1. Create profile in FSUIPC for the CRJ (livery dependant)
  2. Assign throttle axis through FSUIPC and calibrate axis
  3. Edit fsuipc.ini and find the profile for CRJ
  4. Find the row with throttle axis calibration and change the "lower" number to an even lower one (Some expermimentation required to find a sweetspot)
  5. Reload assignments in FSUIPC

I have not tested the above it's just a thesis.

Link to comment
Share on other sites

I have the same issue. When you advance power (and my joystick/htrottle has 0 spikes as all other aircraft work fine) the N1 first drops then rises.

Link to comment
Share on other sites

On 2018-05-07 at 9:48 AM, admiralaspen said:

Hello,

 

Just to update on this issue.
Yesterday I tried out different settings, more specifically "Sensitivty"-slider in P3D. I found a sweetspot of 110 sensitivity but this remove the upper part of the throttle quadrant.
I started thinking that it seems like the idle detent in the cockpit is not in sync with idle input from the throttle lever (When sensitivty is set to 127)

So a workaround could be:

  1. Create profile in FSUIPC for the CRJ (livery dependant)
  2. Assign throttle axis through FSUIPC and calibrate axis
  3. Edit fsuipc.ini and find the profile for CRJ
  4. Find the row with throttle axis calibration and change the "lower" number to an even lower one (Some expermimentation required to find a sweetspot)
  5. Reload assignments in FSUIPC

I have not tested the above it's just a thesis.

Quoting myself just to say that I tried this but didn't work because I couldn't find a good setting where idle input matched idle in the CRJ.
Best I got was 22,4% N1 which made it impossible to shutdown engines.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use