condor449

Pete, you are perfect :D :D :D Now the calibration can be done with success. Everything works well. Just let me explaine what I`ve done. Both levers are assigned as throttle1 and throttle2 via axis assignment. Note, it is mapped to FSUIPC calibrationen. On page 3 you can see the leverposition and there output value. It is important to set the tickbox "exclude THROTTLEn_SET" If you don`t set the tickbox following will happens... You can see that the lever indicators(the white circles - donuts) are not synchron to the N1 needle. The Wilco need to have the AXIS_THROTTLEn_SET control to set the donuts and the N1. If you also send a THROTTLEn_SET control it will disturb the funktion. If you use only THROTTLEn_SET only the N1 needles will move but not the donuts. Is everything correct the EWD shows following... To make it more transparent here the responsible INI section. For those are familar with axis assignment they will also find the reverser function and the offset setting for autothrust on one of the lever [Axes.Feelthere A320 CFM Condor VA] 0=1X,256,D,9,0,0,0 1=1X,U,9380,11381,65602,0 2=1X,D,9380,11381,65598,0 3=1X,U,11382,12381,65602,0 4=1X,D,11382,12381,65598,0 5=1X,U,12382,13381,65602,0 6=1X,D,12382,13381,65598,0 7=1X,U,13381,14382,65602,0 8=1X,D,13381,14382,65598,0 9=1X,U,14381,15382,65602,0 10=1X,D,14381,15382,65598,0 11=1Y,256,D,10,0,0,0 12=1Y,D,-9340,-8728,x01000810,x00 13=1Y,U,11982,16383,x01000810,x01 14=2Z,256 15=2Z,BR,-16384,-13583,66080,0 16=2Z,B,11941,16383,66079,0 17=3Z,256,D,3,0,0,0 18=16X,R2,F,65763,0,0,0 19=16Y,R2,F,65762,0,0,0 20=18U,R512,D,36,0,0,0 [JoystickCalibration.Feelthere A320 CFM Condor VA] ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Elevator=-16380,0,0,16380/24 Aileron=-16380,0,0,16380/24 Rudder=-16380,-512,512,16380/8 SteeringTiller=-16383,-512,512,16382/24 SlopeSteeringTiller=5 SlopeRudder=6 AllowSuppressForPFCquad=Yes UseAxisControlsForNRZ=Yes Throttle1=-7859,-512,512,16101/48 Throttle2=-7809,-512,512,16139/32 I know, it`s not a normal solution to use the rest of the axis movement for reverser control via assingning a FS control, but it is the only way to realise these funktions together with my hardware. It was not easy for me to explaine Pete what the problem was and many thank`s to you for your patience and the quick solution.

Pete, it`s not only the Wilco, as I know Project Tupolev need to have the full range as well. But they use there own joystick calibration program as a gauge. There is no diffrence if I tick reverser or non reverser option, the N1 needle does not move to the idle position. If I use a single axis for throttle control the needle moves to its idle position after calibration on page one (one axis for both). Normally I has no problems with calibration of both levers but my hardware has it`s idle position not at the end of the potentiometer, it`s still befor on around -7500. And right, the rest of movement will be used for reverser by key assignment on the axis. There is no other way to realise this via reverse axis. Wilco does respond but not correctly displayed on the engine screen. I have tried the joystick gauge from project tupolev and 100% satisfied wit the result, but the gauge interfere with the wilco system gauge and create other problems with the aircraft.

Pete, imagine you need to use AXIS_THROTTLEn_SET for assigning your levers throttle one and two. Each for one of them, because the aircraft does not respont to THROTTLEn_SET funktion. If you are using a single axis for the throttle control and send it via FSUIPC direct to the FS you can calibrate these SINGLE axis on page 1. Where ever the throttle position is - FSUIPC send the full range of movement to the FS. An example, idle is in -7500 and full on 16383. After calibration done the output to FS will be set to 16383 and -16383 but the lever only moves between -7500 and 16383. If you assign each multi thottle controls you can`t use the calibration on page 1 - I know that! Than you can only use the throttle calbration on page 3 - I know that as well! As I explained in the posts before the range of output is not the full movement as the lever moved. As you said between -4000 and 16383 will be generated for forward thrust. But some addons use the full range of control and not stopped at -4000... So the question was is it possible to get the same kind of calibration for multithrottle control in camparision to the kind of calibration on page 1.... Hope that make it more clear.

Pete, here I`m again, I`ve recieved an Product update from Eric Marciano (developer of A320) with multi throttle support. Now I can move both levers exactly by assigning the axis via FS menu and/or FSUIPC AXIS_THROTTLEn_SET (as FS axis). The aircraft system need to have the full range of movement between -16383 and 16383. I must correct the word "donat" - I mentioned "donut" :shock: These are the white indicators on the engine display that shows the actual position of the thrustlever. Until reaching the detents for FLEX or TOGA the N1 needle will move synchron to the white markers and everything works well with a normal joystick with full movement. As I said, the idle position of my thrustlever is around - 7500 and full throttle is on 16383. The calibration function on page one is exactly that what I need. But it is only for the whole axis (AXIS_THROTTLE_SET). It will be perfect to get it as twice. Did you see any possibility to include this for further updates?

Thank`s Pete, that makes it clear. I will look out for an other solution...

Hi all, first let me explaine what I try to do... For my home cockpit I try to separate the morse codes and marker sounds to get them on the headset via a secondary sound device. The environmental sound works on the primary sound devive. I`ve tried that with Esound, but doesn`t get any result until now. So, does Esound be the right tool for that or does I misunderstood anything. All solutions are welcome!

Hi Pete, I havn`t recognised that before. You are right with that. Always read the f.... :?

Hi Peter, I`ve noticed a delay by using the coolyhat on my joystick from a client pc. It starts slow to move the pan view and after a second it will accelerate to normal pan rate. When I switch the views in 2D cockpit there is a delay about 2-3 second until the window will change. As I sayed, the joystich is connected to a client via WideFS 6.78 and is recognised in the button section as "normal" quick response. For test I changed the version back to 3.862 and everything works well. Could you please check that?

Thank`s, now it`s clear! Regards, Frank

Hi Pete, thank`s for reply! A BCD4T is used by FSBus and an internal of this program. You are right, in IPC it is BCD. FSBus use the 4T to display a value of of an offset like BCD 0x2280 to display 12280. This is mainly used for NAVCOM frequenz. The reason for my question is I have programmed a virtual COM3 section with VHF3 in FSBus. To complete the FSBus routine you have to assign a offset for COM3 and COM3STBY like a memory function. These offsets or values should not have any affect to fs because COM3 doesn`t exist in fs. So, with this section I can define company channels to switch Teamspeak to several servers without changing frequenzies on COM 1or 2. Thats a very nice feature and works perfect but I was not sure with the offsets I use. If you mean it is better to use 66C0 - 66FF I will check that. Thank`s and regards, Frank

Hi, does anybody knows for what these offsets are used? In FSInterrogate there are declared as "Unknown". I have set an BCD4T value into these offsets and noticed that the range 5 up and below will be in some parts affected but without any result to FS. Or does anybody know two other not used offsets? Any ideas? Regards, Frank

Pete, "donat" was it called by a good friend and real A330/340 pilot. You never find that in any documentation. That seems to be airline spezific. I found the reason for the problem. As I said wilco uses inputs such as keystrokes or "normal" fs axis. There product is developed without using fsuipc and according to there support forum they never has tested it together. How ever, the problem is the wilco as self. Controlling throttle 1 via fs (without any ipc options) works perfect. Throttle 2 on the same way does not work. The only thing you can notice that the indicator on the display move but N1 of engine 2 is still in idle. That`s the problem. Wilco doesn`t have implemented throttle 2 control in there addon (gauge - what ever). You can map the joystick axis now to fsuipc calibration but the result is an other axis scale. In case of that the needle move, the indicators move too but with a big spread between, thats all! To make that functional it is an item of wilco and not yours. This was only a test to make it compatible with ipc but without success. I hope my english knowledge is good enough to make the description of the problem understandable. Many thank`s for your support, Frank

Hi Pete, The A400 is the new military transporter from Airbus Yes, I have tried both Yes, I have but without any changes That`s Airbus stuff - donats means the white circle on engine indicators where the thrustlever position is shown on it. Increasing throttle will move the white indicators and the trust (N1 needle) will be set exactly to this position. ED is the engine display very similar to Boeing Wilco people say, the A320 needs inputs like axis input via FS or normal key commands Imagine the thrust will be set around 50% by moving the thrustlever. First you will notice that the white indicator (donats) will move synchron to the thrustlever position. After there the thrust increase and will reach with the needles the thrust indicators. The donats shows the actual position of thrustlever independent of the provided thrust. For my understanding wilco use the input range by 16383 to - 16383 to set (show) the thrustlever position and synchron the thrust setting. I hope the definition of "donats" is more clear than before. The thrust lever position is always synchron to the N1 needle on the real bus and by using single throttle control assignment via fs menu as well. 50% thrustlever will set 50% donats and after stabilising the thrust will reach 50% exactly to the donats position at all. This means axis asignment with the option "send direct to FS" and check out both option. I know it is total confusing but that`s what I experienced. By selecting only one it doesn`t work. Both together shows the same result as by selecting "send to fsuipc calibration" without any other asignments. Pete, believe me, I`ve tried each possible combination and the best result was N1 synchron to donats and fully okay and on N2 the donats works, the N2 as well but not synchron. After all these test and experience I don`t believe (as you said) that fsuipc cannot correct this due to the input parameters of wilcos`s A320. You can say wilco a320 can be contolled by 2 throttle but with asyncron indicators on the engine display and that is not acceptable for me. Some CH Throttle users reports there is no problem to use there product on wilco but I can`t believe that due to my own expirience. Please don`t misunderstand me - this is not a problem of fsuips more a problem of the wilco! Regards, Frank

...so, I´ve tried that but without any success. There is no affect to the axis by changing the reverse value. I`ve got some information from the Wilco forum that there is an A400 workaround to make multiple throttle compatible with there products. They recommendet to tick the checkbox "exclude throttle_n_set" and reset the calibration on lever 1 and 2, but that doesn`t work as well. I have experienced following: throttle 1 assignment via fs works throttle 2 assignment via fs set the with lever indicators (donats) on ED but N1 doesn`increase throttle 1 and 2 assignmet via IPC direct to calibration controlls the donats and both N1 needles but the donats are asynchron to the N1 needle - by setting the donats around 50% the N1 increase up to 65-70% ?????? throttle 1 and 2 assignmet via IPC direct to calibration and calibrated via 4 throttle page does not have any affect to the donats and N1 throttle 1 and 2 assignmet via IPC direct to fs you must tick axis_throttle_1/2 and throttle_1/2 otherwise no movement on N1 In summary - now I`m total confused and believe the wilco does not accept throttle 2 control. How ever, I stopped that because it makes no sence to control thrust with asynchron engine indicators. Thanks for your assistance, Frank

Pete, I have recieved some feedback from other Wilco user regarding multiple throttle but without there success. Seems to be a problem or not many simmer use Wilco for cockpit building - I don`t know! But a good tip is to change the reverser value in the aircraft file to 100%. I will try that this evening and will give you feedback. Thank`s, Frank