KNI-DK

Let us say we are going from 3000ft to FL390, if using the FSUICP input "PM MCP Alt Inc 100", one have to turn the knob many many times and keep it running beacause only a few detents are "stored"! (Encoder wired using BU0836x to FSUICP as button assignment) Besides using the "PM MCP Alt Inc 1000" can one do anything to make "PM MCP" or "FSX" or "FSUICP" understand that fast dial or many detents will result in faster increasement of ALT? BR / Kjeld

Hi Pete Got the flu right after the last post and been busy afterwoods regaining the lost time. Haven't tested the LUA yet. But the time doing nothing made me re-consider my approach - and I decided, as you actually advise me at FSweekend, to make a direct wiring from the encoders to FSUICP (bypassing the FSBUS2.2) - which now have been done. BUT now I have another problem (and based on my search at www I am not the only one) using the std. FSUICP assignment "PM MCP HDG INC 1" and "PM MCP HDG DEC 1" (goes as well for SPD, ALT etc) the speed of the bug movement is slow and it takes ageds to dial 180 deg, or go from 6000 ft to FL390. I do not have a dual encoder (could be the case later) and will not use x10 FSUICP inputs (PM MCP HDG INC 10 etc), but as far as I have read it should be possible to let the PM read fast dial as fast and the inc the numbers, but will that require another input (offset)? I have also used both "push" and "release" programming, but for some reason it reads that as 2 "click" even I only feel one at the encoders. Thx BR / Kjeld

Last night I was doing some initial studies at Lua - will go for it in the weekend to assess wether I will do it inside the FSBUS22(CCC logic programming) or go for Lua Thanks Kjeld

Hi Pete YES If I for some reason in my Q made you believe the Q was about how to programme FSBUS I do hope you can accept my apology, this is not the matter of how FSBUS is programmed, but it is/was a Q to help open my eyes to which offset or offsets should be read. Will (maybe this word should be "Can") a single offset give either IAS or MACH (with the different notification (NNN or N.NN)) depending of the mode setting? Or should I keep track of which mode is in work and then read the corresponding offset? Sorry for the incorrect Q - yes I do mean the TL - and your next comment has revealed the answer to this Q Haven't tested it yet, but I do see the picture now - I have used the standard offset for FS to handle the input of inc/dec of QNH, which I now - of course - can see was wrong - I will reprogram with use of INC/DEC QNH for PM (just to be sure x5418 bit 18 and 19) and I will let you know when I have tested it. Many thanks for your answers

Hi Pete Nice meeting you at FSweekend last weekend. :D Hope you are remembering our talk about IAS/MACH - you told me to set Fiddle IAS in the ini file - which I actually had done prior to our conversation - so I still have my problem :shock: I am using FSUICP 4.53 FSX sp 2 PM sw (glass, CDU, MCP and pmSys), newest releases OCs SIOC for annunciators FSBUS22 (the old one) for MCP/EFIS HW (from symulatory) Let me make a introduction to my problem(s) IAS/MACH display 1) IAS is shown and switch automatically to MACH at the set alt in the ini file, which is shown in MCP sw display (pm) and in PFD - can I without any programming (logic) catch this display(the reading) (with an offset) to make my HW display show the same numbers (IAS or MACH)? 1a) I am of course able to read the IAS (04E0) or MACH (04E8) by using the offsets - but do "we" have an (one) offset just mirroring the numbers coming from IAS/MACH reading? temp QNH 2) maybe you are the wrong guy to ask, but I try anyway (if so - pls. kick me to the right place if possible :) ) - when pushing STD (throughpass 49) (and logic (CCC logic in FSBUS) change writing offset from capt. QNH(0330) to Capt temp QNH (5536) the PFD shows below "STD" in white numbers the temp QNH set - so far so good - but how do I write this number as the active QNH, when pushing STD travelling through TA? 2a) Am I in first place using the right Capt. QNH offset (0330)? BR Kjeld

everything is resolved updated FSUICP from 3.7.0 to 3.7.5 thanks for your attension any way Kjeld

HI Peter Having a problem with connection or recognition of Keypress. Simulator and add-ons FS9, SP1 ACtiveSky PMDG etc. (all purchase through official channels) WideServer 6.75 (PC1, with FS9.1 / FSUIPC 3,75) and WideClient 6.75(PC2). Both FSUIPC (feb 2005 and updated) and WideFS (nov 2007) bought on SimMarket. FSUIPC running with no problems, with other applikations (ie. AS6, PMDG etc. those requiring FSUIPC, as far as I remember both AS6/PMDG need at regsitrated FSUIPC to use all applications, correct me if I am wrong). Connection established between Client and Server (at least it said so in the top bar). Implemented KeySend codes as described in WideFS userguide (advance User Guide), inclusive KeyPress assignment in FSUICP. Nothing happens on the Client side (trying the "simplest" test) using the guidelines for PTT solution for TeamSpeak (there is a lot examples out there), so I am confidence I am doing the right thing. I know that You will punish me if I havn't done my homework. :D Investigating User Guides and other threads about the same issue, still not resolving the problem. In a threads I saw that the problem seems could be the keycode was incorrect(old, done by and old keycode generator etc.), is there any way I can do a check if my keycodes a valid? EDITED Tested via PM File Checker: FSUIPC/WideFS found! FSUIPC No Version number Reported! Please Check FSUIPC Installation WideServer Version .002 WideClient Version .002 FSUIPC no version WideFS should be 6.75 Best Reagrds Kjeld