toktiny

Hi Pete In June 2014 I ran into a problem and sought your most appreciated advice and as a result you advised me on the course to take ,which I did, and it worked perfectly for me with all gauges working with no problem. It is impossible for you to remember the thousands of most valuable help that you very kindly offer to us all on the forum. In case it might help below is a copy of our exchange ; FROM TONI For this to work can I assume that is it obligatory to have the same Windows OS in the older second PC and the main FS PC or could you have XP in the older one and Windows 7 in the main PC? FROM PETE Any version of Windows from XP SP1 onwards works with the current WideClient. The only thing to watch is that XP uses a different default network workgroup name to Win7, so you should change one to match the other for WideFS to link automatically. (Or you can always link inany case by giving the Client the IP address or name of the FS PC). For my cockpit I have the main FSX PC using Win7 64bit, and 5 other PCs on WinXP. FROM TONI That is great news because I still have my older PC with XP which is compatible with the TRC gauges and has the relative boards etc. at its disposal . My understanding is that WideFS will pick up the relative info. for the gauges from the old PC and being attached through a network to the new main FS PC, which is using Win7 64Bit, will work in tandem between the two ? The first thing I have to do is set up the most simple network I can find between two computers . I take it there is no specific type of network essential. Thank you for your guidance. FROM PETE As far as I recall (I did have a number of TRC gauges, and so used their driver, some time ago), it will all work through WideFS perfectly well. The difference between Win 7 and Win XP is easily resolved in one of the two ways I mentioned in my last reply. A network is a network is a ... If you have an Internet router it is usually easiest just to connect them both to that. If your two cockpit PCs are separate altogether, you can network them with a special PC-to-PC "crossover" Ethernet cable, not a normal type. Now as I have said above I followed your directions and all worked perfectly. I was using it for about 18 months until late '15 when unfortunately due to medical reasons I was out of action until just a few weeks ago and when I switched on my computers and cockpit for the first time to find that my current problem had arrived. I will add here that my wife and I live alone, as all the family are up and gone, and my wife does not use a computer let alone a cockpit so that I was the last one to switch it on or off. Pete this is what puzzles me completely, you switch something off after it has worked without a hitch for eighteen months and you switch it back on and I have outlined for you what has happened. I will experiment with your two programs, "TrafficLook" and "Weatherset2" that you suggested and I will mail you after you get back on 20th. and let you know if we have had any luck. Again my sincere thanks to you for all your help as down through the years I would be lost without it. Toni

Hi Pete Many thanks for your explanation which I now fully understand. On your suggestion to try not loading the three TRC programs and to see if WideClient stays connected without them the answer is yes it does.Also if I try loading the programs the WideClient will still show "Connected" on the XP computer but the WideServer will close and show the "error" which we have shown in previous mail. On your question regarding using UDP and Broadcast mode I omitted letting you know that I have tried this, my apologies, but I am afraid exactly the same results as we have got in prior tests. I attach below the WideClient.log and WideServer.log which I got when I tried this change in case you maybe able to detect something. You asked if I was using a wireless connection .No I do not. The two computers are connected to an Internet Router and all connections are by wire as I have said I dont use wireless connections at all. This may be totally Irrelevant, if so please ignore, but the company that provides my broadband service are now providing a Fiber Broadband and some time ago updated my Router. Many thanks Toni WideClient Log ********* WideClient Log [version 6.999n] Class=FS98MAIN ********* Date (dmy): 13/06/17, Time 11:40:47.203: Client name is ALPINE-UK 63 c:\program files\trc development\the real cockpit 63 C:\Program Files\TRC Development\The Real Cockpit\TRCLink.exe 10063 c:\program files\trc development\multi controller 10063 C:\Program Files\TRC Development\Multi Controller\MCLink.exe 20063 c:\program files\trc development\multi controller 20063 C:\Program Files\TRC Development\Multi Controller\MCLink.exe 30063 LUA: "C:\Program Files\TRC Development\The Real Cockpit\Initial.LUA": not found 30063 Attempting to connect now 30063 Trying to locate server: IP protocol needs ServerName or IP address! 30063 Failed to connect: waiting to try again 30063 New Client Application: "MCLink" (Id=2808) 30063 New Client Application: "TRCLink" (Id=2280) 30125 New Client Application: "MCLink" (Id=3984) 31078 Attempting to connect now 52078 Trying to locate server: IP protocol needs ServerName or IP address! 192078 Server = OWNER-PC 192094 Trying UDP/IP host "OWNER-PC" port 8002 ... 192094 ... Okay, IP Address = 192.168.1.1 192094 UDP connectionless mode set up okay! 192250 Using "C:\Program Files\TRC Development\The Real Cockpit\GFDEV.DLL", version 2.2.1.0 192313 Connection made: receiving okay! WideServer Log ********* WideServer.DLL Log [version 7.934] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 13/06/17, Time 11:37:10.938: Server name is OWNER-PC 15725 Initialising TCP/IP server 15740 Initialising UDP/IP server 16115 Broadcasting service every 1000 mSecs 16115 Preferred protocol = UDP 18330 Connected to computer "ALPINE-UK" running WideClient version 6.999 (IP=192.168.1.6) UDP 18330 Broadcasts will be used for this UDP Client

Hi Pete To answer your question regarding did I check both PC's and got the same response yes that is correct just the same return as I have outlined in earlier mail from both. One thing that keeps going through my mind and I do not know the answer but perhaps you could put it to rest for me. WideClient in Computer 2 ( XP ) with the aid of WideClient.ini runs 3 TRC programs and transfers them to a combination of FSWide and FSUIPC in Main Computer ( Windows 7) which contains FSX Now as I read it the 3 TRC programs are accepted in Computer 2 ( XP ) and then transferred to Main Computer ( Windows 7) where both computers recognize and accept each other until such time as the 3 TRC programs are about to be loaded and then immediatly after it gives the message 1.Connected all communication is cut. This seems that even though the connection took place to accept the first TRC program ,even that first TRC program was never loaded. Now what goes through my mind is there any possibility that the server goes through the process until it rejects the TRC programs for some reason or another ? My sincere thanks for your opinion. Toni

Hi Pete and Thomas I am afraid I did not have any luck with the alternative suggestion to the server name. I tried it several times an it would not even show a connection XP client. I resorted back to our previous server name "owner-pc" and got "Connected" showing on Computer 2 and "awaiting clients" followed by "1.Connected" on FSX . Pete on your comment regarding some sort of Firewall block I decided to make sure to try and clear any Firewalls that I know about. I had already disabled all window firewalls in XP and windows 7.and checked to make sure that they were still inoperative and they were. The only other Firewall that I am aware of in XP was in a program called AVG. I had disabled it but found that it was still up and running after a computer restart.I decided to remove the program completely and after about two hours with help from the internet got every last file out. I thought this might have helped but it did not make one change or bit of difference in the results. At this point I might add that I have little or no programs in the Main (Windows 7) computer as I have confined it to the cockpit (FSX) programs only. I then removed and reloaded all the TRC Multicontroller Board and two TRC Controller Boards files just to make sure that they were not the cause of the problem. To no avail I am afraid everything remained exactly the same. One thing I did find was that in XP computer the GFDef.dll in the GoFlight Folder was Version 2.2.1.1. ( Which is also included in the "The Real Cockpit" folder where "WideClient.exe and "WideClient.ini" are kept. In the Modules Folder of FSX the GFDef.dll was Version 2.1.10.1. I thought I might be on a winner here and copied the same Version into both computers. I tried both Versions but I am afraid to no avail. Pete ,was ether of these the version you used in your setup many moons ago ? I am afraid I have no more ideas to try . Toni

Thomas I am afraid it has taken me a while to understand your last mail as it was well over my head I will have to admit. I can understand that Error=10013 means that access permission has been denied to the client to provide information to the server. Is that correct ? If so this would prevent the server from receiving clients. I did eventually get the Network address and subnet mask of both the Server and Client and they are as follows ; Server: ID=192.168.1.1 Subnet: 255.255.255.0 Client: ID=192.168.1.6 Subnet: 255.255.255.0 The readings I hope mean something to you, as for me I am lost ! If these readings need to be changed and your direction "Network address and subnet mask correct set manually and not automatic on both PC's" is what has to be done, could you let me know the procedure of how it is done and what they should be changed to ? Again many thanks for your help which is much appreciated. Toni

Many thanks for your prompt reply Thomas. I double checked to make sure that Firewall on both computers are disabled and I confirm that both on Widows 7 and Windows XP they are. I remember Pete telling me on initial setup that this was most important. I also double checked the basic settings for Windows network e.g. computer names and computer Workgroups and I am afraid these were correct also. Below you will find a few files that might indicate something further. Toni I COPY OF WideClient.ini ; ===================================================== [Config] Port=8002 Window=-32000,-32000,160,26 Visible=Min ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ServerName=owner-pc Protocol=TCP ; ----------------------------------------------- [User] Log=Errors+ Run1=C:\Program Files\TRC Development\The Real Cockpit\TRCLink.exe Delay1=10 Run2=C:\Program Files\TRC Development\Multi Controller\MCLink.exe Delay2=10 Run3=C:\Program Files\TRC Development\Multi Controller\MCLink.exe Delay3=10 ; Run4=C:\FSX Flight Plans\6.Flight Plan Menu.exe ; =============================================== [Sounds] Path=C:\Program Files\TRC Development\The Real Cockpit\Sound\ Device1=Primary Sound Driver Device2=SB Audigy 4 [EC00] COPY OF WideServer.log ; ===================================================== ********* WideServer.DLL Log [version 7.934] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 11/06/17, Time 11:25:19.758: Server name is OWNER-PC 15803 Initialising TCP/IP server 15818 Initialising UDP/IP server 16099 Broadcasting service every 1000 mSecs 18689 Incoming connection Accepted ok (skt=9064) TCP 18923 Connected to computer "ALPINE-UK" running WideClient version 6.999 (skt=9064) TCP 132289 Restarting service due to zero reception! 170899 Incoming connection Accepted ok (skt=3724) TCP 171133 Connected to computer "ALPINE-UK" running WideClient version 6.999 (skt=3724) TCP 2864989 Auto send stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP COPY OF WideServer.0log ; ===================================================== ********* WideServer.DLL Log [version 7.934] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 09/06/17, Time 20:05:37.073: Server name is OWNER-PC 15179 Initialising TCP/IP server 15179 Initialising UDP/IP server 16115 Broadcasting service every 1000 mSecs 27862 Incoming connection Accepted ok (skt=9040) TCP 27909 Restarting service due to zero reception! 27924 Incoming connection Accepted ok (skt=5340) TCP 28190 Connected to computer "ALPINE-UK" running WideClient version 6.999 (skt=5340) TCP 1967969 Auto send stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP 1974552 Close signalled to clients 1975706 Closing down now ... Memory managed: Offset records: 1048 alloc, 1047 free Read buffer usage: 30861 alloc, 30861 free, max in session: 1 Write buffer usage: 125304 alloc, 125304 free, max in session: 1 Throughput maximum achieved: 31 frames/sec, 5843 bytes/sec Throughput average achieved for complete session: 13 frames/sec, 1545 bytes/sec Average receive rate from "ALPINE-UK": 15 frames/sec, 2394 bytes/sec ********* Log file closed ********* COPY OF FSUIPC.log ; ===================================================== ********* FSUIPC4, Version 4.934 by Pete Dowson ********* Reading options from "C:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=645B0000 User Name="Toni OKelly" User Addr="tok@iol.ie" FSUIPC4 Key is provided WideFS7 Key is provided 32 System time = 11/06/2017 11:23:42 47 FLT UNC path = "\\OWNER-PC\Users\Owner\Documents\Flight Simulator X Files\" 812 Trying to connect to SimConnect Acc/SP2 Oct07 ... 843 FS UNC path = "C:\FSX\" 1139 LogOptions=00000000 00000001 1139 SIM1 Frictions access gained 1139 Wind smoothing fix is fully installed 1139 G3D.DLL fix attempt installed ok 1139 SimConnect_Open succeeded: waiting to check version okay 1139 Trying to use SimConnect Acc/SP2 Oct07 1139 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1139 Initialising SimConnect data requests now 1139 FSUIPC Menu entry added 1248 \\OWNER-PC\Users\Owner\Documents\Flight Simulator X Files\Default Flight.FLT 1248 C:\FSX\SimObjects\Airplanes\X J2 B737-800\aia_737_NG.AIR 9813 System time = 11/06/2017 11:23:52, Simulator time = 09:00:00 (08:00Z) 9969 Aircraft="WoA_AIA_B738_W_RYR-Ryanair_2" 96924 Starting everything now ... 96955 Using "C:\GoFlight\GFDEV.DLL", version 2.1.0.1 96955 GoFlight GF45 detected: 2 devices 96955 GoFlight GFP8 detected: 4 devices 96955 GoFlight GFT8 detected: 1 device 96955 GoFlight GFMCP detected: 1 device 96955 GoFlight GFRP48 detected: 1 device 98094 Advanced Weather Interface Enabled 2953957 Sim stopped: average frame rate for last 2863 secs = 32.8 fps COPY OF FSUIPC.ini ; ===================================================== [General] History=YRXVSJPDKXMZ3JN02WPA0 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No WeatherReadFactor=2 WeatherRewriteSeconds=1 SimConnectStallTime=1 MouseWheelTrim=No MouseWheelTrimSpeed=1 FixControlAccel=No FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No ZapSound=firework ShortAircraftNameOk=Substring UpdatedByVersion=4934 SmoothBySimTime=No SaveDataWithFlights=No UseProfiles=Yes CustomWeatherModify=No Console=No JoystickTimeout=20 BrakeReleaseThreshold=75 DontResetAxes=No PollGFTQ6=Yes BlankDisplays=No MouseWheelMove=No DeleteVehiclesForAES=Yes AutoScanDevices=Yes EnableMouseLook=No AxesWrongRange=No InitDelay=0 GetNearestAirports=Yes LuaRerunDelay=66 InitDelayDevicesToo=No UseMidMouseBtn=Yes OOMcheck=Yes UseSystemTime=No NewInterceptTextMenu=No DelayedMouseLookZoom=No FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [GPSout] Port=<none set> Speed=4800 Interval=1000 PosTo6Decimal=Yes Sentences= GPSoutEnabled=No [AutoSave] AutoSaveEnabled=No Next=1 Interval=60 Files=10 SaveOnGround=No [JoyNames] AutoAssignLetters=No 0=CH THROTTLE QUADRANT 0.GUID={8E53A2E0-D1F7-11E3-8001-444553540000} 2=Saitek Pro Flight Rudder Pedals 2.GUID={8E53A2E0-D1F7-11E3-8003-444553540000} 1=CH FLIGHT SIM YOKE USB 1.GUID={8E53A2E0-D1F7-11E3-8002-444553540000} 3=BU0836X Interface 3.GUID={55143C90-D43D-11E3-800C-444553540000} 4=BU0836X Interface 4.GUID={1C451F30-ED77-11E3-8001-444553540000} [Buttons] ButtonRepeat=20,10 3=P3,0,C66239,0 8=P3,31,C66300,1 9=U3,31,C66300,0 26=P3,29,C66302,1 27=U3,29,C66302,0 28=P3,28,C66303,1 29=U3,28,C66303,0 30=P3,26,C66495,1 31=U3,26,C66495,0 32=P3,25,C66496,1 33=U3,25,C66496,0 34=P3,24,C66497,1 35=U3,24,C66497,0 36=P3,19,C66224,1 37=U3,19,C66224,0 38=P3,18,C66531,1 39=U3,18,C66531,0 40=P3,17,K74,10 41=U3,17,K74,10 44=P3,14,K189,8 46=P3,13,K65,8 48=P3,12,K187,8 51=P3,22,C66293,1 52=P3,23,C66241,1 53=U3,23,C66241,0 54=U3,22,C66293,0 55=P3,16,K191,8 56=U3,16,K191,8 62=P3,11,C65895,0 63=P3,10,C65894,0 66=P1,13,CL4:R,0 74=P3,9,C65917,1 76=P3,8,C65916,1 78=U3,9,C65917,0 79=U3,8,C65916,0 80=P3,27,C66494,1 84=P3,5,C66240,0 86=U3,27,C66494,0 88=P101,14,C66482,0 89=P101,12,C66477,0 90=P101,21,K80,9 91=P101,22,K49,8 92=P101,20,K50,8 93=P101,23,K69,9 94=P101,24,K89,8 95=P101,25,K81,8 96=P101,26,K112,8 97=P101,27,K113,8 98=R101,28,K81,10 99=R101,29,K81,11 100=P101,31,K90,9 102=P3,6,C66376,0 103=P3,7,C66579,0 105=P101,30,K121,9 106=P101,13,C66390,0 107=P2,7,K123,8 108=P2,6,K120,8 109=P3,4,C65751,0 110=P3,3,C66379,0 111=P3,2,C65560,0 112=P149,2,C65915,0 113=P3,21,C66651,1 114=U3,21,C66651,0 115=P3,20,C66493,1 116=P3,15,C65567,1 117=P0,23,C66241,0 118=P0,22,C66701,0 119=U3,0,C66239,0 120=P4,27,C66494,0 121=U4,27,C66494,0 122=P4,26,C66495,0 123=U4,26,C66495,0 124=P4,25,C66496,0 125=U4,25,C66496,0 126=P4,24,C66497,0 127=U4,24,C66497,0 128=P4,31,C66300,0 129=U4,31,C66300,0 130=P4,30,C66301,0 131=U4,30,C66301,0 132=P4,29,C66302,0 133=U4,29,C66302,0 134=P4,28,C66303,0 135=U4,28,C66303,0 136=P1,11,C66241,0 137=U1,11,C66241,0 138=P4,23,C66241,0 139=U4,23,C66241,0 153=P4,3,C65842,0 154=U4,3,CM5:2,0 155=P4,13,K65,8 157=P4,15,C65567,0 159=P4,14,C65656,0 160=U4,14,C65656,0 161=P4,12,C65655,0 162=U4,12,C65655,0 163=P4,5,C66452,0 164=R4,4,C66446,0 167=P4,22,C66293,0 168=U4,22,C66293,0 170=U4,21,C66651,0 171=P4,19,C66224,0 172=U4,19,C66224,0 173=P4,18,C66531,0 174=U4,18,C66531,0 175=P4,17,C66695,0 176=U4,17,C66695,0 177=P4,16,C65589,0 178=U4,16,C65589,0 179=P3,1,C65750,0 180=U3,1,C65750,0 181=U3,2,C65560,0 182=U3,3,C66379,0 183=U3,4,C65751,0 184=U3,5,C66240,0 185=U3,6,C66376,0 187=U3,7,C66579,0 188=P4,10,C65894,0 189=U4,10,C65894,0 190=P4,8,C1021,0 191=U4,8,C1021,0 192=P4,9,C1020,0 193=U4,9,C1020,0 194=P4,11,C65895,0 195=U4,11,C65895,0 196=P4,20,C66493,0 198=U4,20,C66493,0 199=P0,9,C66080,0 200=P0,8,C66079,0 201=P4,6,C66448,0 202=R4,7,C66445,0 205=P4,2,C65846,0 206=P4,21,C66448,0 [GPSout2] GPSoutEnabled=No [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=No 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=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Throttle=-16380,16380 Throttle1=-16384,-5756,639,16383 Throttle2=-16384,-13653,-8601,16383 Throttle3=-16384,-12086,-10878,16383 Throttle4=-16384,-15291,-9011,16383 UseAxisControlsForNRZ=No [MacroFiles] 1=747 OHD 2=APchart 3=PFD 4=King 5=Eicas 1-2 [LuaFiles] 1=MenuDemo 2=TripleUse 3=PMDG_JS41_CD 4=log lvars [Keys] 2=77,11,M3:1,0 5=88,14,M4:1,0 7=90,14,M4:2,0 9=90,11,M3:1,0 15=80,15,M3:1,0 17=49,11,M3:1,0 19=51,11,M3:2,0 21=81,9,66391,0 [Sounds] Path=C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Primary Sound Driver Device2=SB Audigy 4 [EC00] [Axes] RangeRepeatRate=10 0=0Y,256,D,9,0,0,0 1=0Z,256,D,10,0,0,0 2=0U,256,D,11,0,0,0 3=0V,256,D,12,0,0,0 4=1X,256,D,0,10,0,0 [ClientNames] 1=ALPINE-UK

I have a generick cockpit which I have built up over the years.I am using two computers to feed this cockpit.The main computer contains OS Windows 7 (64) which runs FSX and the second computer contains OS Windows XP. I use the second cpmputer to feed TRC gauges operated from a TRC Multicontroller Board and two TRC Controller Boards on an O/H panel. The reason for this is that the TRC gauges are not compatable with the main computer, OS Windows 7 (64) which runs FSX. With help from Pete a few years ago he directed me to use WideFS through FSUIPC which I did and everything worked perfectly, however, due to medical reasons over the last two years I have not been able to use my cockpit. A few weeks ago I was delighted to get going again but I found that a problem had occurred in getting my gauges to load from Computer 2 to the main FSX Computer. When it goes through the loading procedure Computer 2 will show “Awiating Connection” and the Main Computer will show “FSX with WideServer waiting for Clients” .Then Computer 2 will show “Connected” and the Main Computer will show “FSX with WideServer ; 1 Connected” FSUIPC in Main Computer will show both FSUIPC and WideFS are registered. FSUIPC in Second Computer will show FSUIPC is registered and WideFS is not. Checked that the TRC Boards have been loaded with the required software into the CCU. Checked Wide Client.exe and WideClient.ini in Computer 2 Checked that all appropriate folders and files are in place both in Main Computer and Computer 2. I can not find any change in files from the time that all was up and running and I have not added any new software to ether computer so I am afraid it has me puzzled. The only conclusion that I can come to is that some file has become corrupt or that in my time away from my cockpit that I have forgotten or am doing something silly. Please find below a copy of WideClient.log which may help. My sincere thanks for any help to get things back working again. TokTiny ********* WideClient Log [version 6.999n] Class=FS98MAIN ********* Date (dmy): 09/06/17, Time 20:06:31.937: Client name is ALPINE-UK 469 c:\program files\trc development\the real cockpit 469 C:\Program Files\TRC Development\The Real Cockpit\TRCLink.exe 10656 c:\program files\trc development\multi controller 10656 C:\Program Files\TRC Development\Multi Controller\MCLink.exe 20672 c:\program files\trc development\multi controller 20672 C:\Program Files\TRC Development\Multi Controller\MCLink.exe 30672 Attempting to connect now 30672 LUA: "C:\Program Files\TRC Development\The Real Cockpit\Initial.LUA": not found 30672 New Client Application: "MCLink" (Id=4384) 30672 New Client Application: "MCLink" (Id=2352) 30703 Trying TCP/IP host "owner-pc" port 8002 ... 30703 ... Okay, IP Address = 192.168.1.1 30735 New Client Application: "TRCLink" (Id=4104) 51735 Error on client pre-Connection Select() [Error=10060] Connection timed out 51735 Ready to try connection again 52735 Attempting to connect now 96922 Trying TCP/IP host "owner-pc" port 8002 ... 96922 ... Okay, IP Address = 192.168.1.1 162985 Trying TCP/IP host "owner-pc" port 8002 ... 162985 ... Okay, IP Address = 192.168.1.1 229422 Trying TCP/IP host "owner-pc" port 8002 ... 229422 ... Okay, IP Address = 192.168.1.1 295985 Trying TCP/IP host "owner-pc" port 8002 ... 295985 ... Okay, IP Address = 192.168.1.1 340547 Connection made okay! 340594 Connection closed by server! 340594 Attempting to connect now 340594 Connection made okay! 340938 Using "C:\Program Files\GoFlight\GFDEV.DLL", version 2.2.1.0 2280641 Received shutdown offset code = ADBC 2280641 FS closing down (param=ADBC), disconnecting 2280641 ********* Interim performance summary ********* 2280641 Total time connected so far = 1940 seconds 2280641 Reception maximum so far: 31 frames/sec, 5668 bytes/sec 2280641 Reception average whilst connected so far: 26 frames/sec, 932 bytes/sec 2280641 Transmission maximum so far: 23 frames/sec, 3310 bytes/sec 2280641 Transmission average whilst connected so far: 21 frames/sec, 190 bytes/sec 2280641 Max receive buffer = 713, Max send depth = 5, Send frames lost = 0 2280641 **************** Individual client application activity **************** 2280641 Client 4384 requests: 29192 (Ave 15/sec), Data: 58706728 bytes (30261/sec), Average 2011 bytes/Process 2280641 Client 2352 requests: 43199 (Ave 22/sec), Data: 22639640 bytes (11669/sec), Average 524 bytes/Process 2280641 Client 4104 requests: 43215 (Ave 22/sec), Data: 4380772 bytes (2258/sec), Average 101 bytes/Process 2280641 *********************************************** 2280766 Received shutdown offset code = ADBC 2288391 Connection closed by server! 2288391 Attempting to connect now 2288391 Trying TCP/IP host "owner-pc" port 8002 ... 2288391 ... Okay, IP Address = 192.168.1.1 2354656 Trying TCP/IP host "owner-pc" port 8002 ... 2354656 ... Okay, IP Address = 192.168.1.1 2420969 Trying TCP/IP host "owner-pc" port 8002 ... 2420969 ... Okay, IP Address = 192.168.1.1 2435313 ****** End of session performance summary ****** 2435313 Total time connected = 1940 seconds 2435313 Reception maximum: 31 frames/sec, 5668 bytes/sec 2435313 Reception average whilst connected: 26 frames/sec, 932 bytes/sec 2435313 Transmission maximum: 23 frames/sec, 3310 bytes/sec 2435313 Transmission average whilst connected: 21 frames/sec, 190 bytes/sec 2435313 Max receive buffer = 713, Max send depth = 5, Send frames lost = 1 2435313 **************** Individual client application activity **************** 2435313 Client 4384 requests: 30925 (Ave 15/sec), Data: 62425746 bytes (32178/sec), Average 2018 bytes/Process 2435313 Client 2352 requests: 45592 (Ave 23/sec), Data: 23946218 bytes (12343/sec), Average 525 bytes/Process 2435313 Client 4104 requests: 44412 (Ave 22/sec), Data: 4505260 bytes (2322/sec), Average 101 bytes/Process 2435313 ********* Log file closed (Buffers: MaxUsed 6, Alloc 173231 Freed 173231 Refused 0) *********

That is great news because I still have my older PC with XP which is compatible with the TRC gauges and has the relative boards etc. at its disposal . My understanding is that WideFS will pick up the relative info. for the gauges from the old PC and being attached through a network to the new main FS PC, which is using Win7 64Bit, will work in tandem between the two ? The first thing I have to do is set up the most simple network I can find between two computers . I take it there is no specific type of network essential. Thank you for your guidance.

Quote ; "BTW if you had an older PC running XP, you could have connected it to the FS one in a Network and used WideFS to link up your TRC gauges and so forth. I'm using several small PCs running XP in my cockpit for the gauges and displays, and for most of the switches and so on. Only the main control axes are connected directly to the FS PC." For this to work can I assume that is it obligatory to have the same Windows OS in the older second PC and the main FS PC or could you have XP in the older one and Windows 7 in the main PC?

Just for the record I have a printed copy of all of your updated manuals (I do not just read them on the monitor ,I bring them to bed with me ! ! ) and I have a printed text of all of the working examples of the Lua files which I got from the Zip file so I am doing my best to get to grips with this part of FSUIPC which I have not used before.

Many thanks for your help . I will follow up what you suggest getting on to the My Cockpit site regarding a suitable input/output board and I will let you know how I get on further down the line. As regards my "MenuDemo" adventure please forget it as it was not of any importance to sorting out my problem and I dont want to waste your time on it , just curiosity on my part to try and learn a little more about Lua.

I am afraid you are quite right , the GF-DIO board is way too expensive just to provide me with 9 lights. I looked into the GoFlight WP6 with 6 warning lights and found that other people in various sites had a lot of difficulty with it using Windows 7 (64) as an OS. It also states in Goflights details of same that ; “Can only be programmed for any flight sim key-stroke function” .I don’t know if that would also present a problem for me for what I want it to provide. I checked Leo Bodnar’s site and as far as I can see he does not produce any board for output/display control ,they seem to be all geared for joystick control . Analysing the information that you have kindly provided me with I seem to be in a situation where I am halfway up a tree with two options. 1. Stay where I am and be happy or 2. Graduate to using Lua and progress from there. I have downloaded and installed Lua last night out of curiosity more than intent and will see how it goes from there. One last thing ,when I had Lua up and running I wanted to see your “MenuDemo” in operation. I checked and by default you have it on the Lua list in FSUIPC4.ini so that was fine. I loaded up FSX ,went to FSUIPC4 – Buttons and switches, selected a switch to open your lua file, filled in “Lua MenuDemo” in both sections where it says “Control sent when button pressed” and pressed OK. I flew the aircraft, toggled the selected switch but I am afraid –No Menu. What I did get were two options on the main FSUIPC4 main bar menu ; 1. “End Menu Test” or 2. “Add a Submenu” Not being sure if I had selected the correct entry for the file I then tried entering “Lua Toggle MenuDemo” and also “Lua Value MenuDemo” and “ Lua Set MenuDemo” but I am afraid I got the same results as above with no menu showing on screen. What am I doing wrong ?

On looking further into my problem and using the information that you provided I now realise that I was approaching same as you put it “backwards”. I now understand, as you explained, that I would have to; 1. Read the value of the offsets 2. Use the result to write to the HARDWARE and carry out the actions necessary. This could be done using a Lua file cottoned in the Module folder and adjusting the FSUIPC4 ini file to include same. I emphasised “hardware” above for as I have explained I have had to remove all my three TRC boards due to incompatibility with Windows 7 (64) which means I would have to find a replacement of one of these, compatible with my OS, to accommodate the directions of the Lua file. Is this correct ? If so what would you recommend. As I explained in my previous mail I have removed, between TRC gauges and GoFlight modules, fifteen units from my cockpit (which broke my heart) and have replaced same with three extra monitors that now through software are showing all my gauges. With the aid of three BU0836X and your FSUIPC4 are taking care of buttons, switches and macros. The only item that I have not replaced in my cockpit is this small O/Head with about nine warning lights, nothing else. I guess I will have to decide whether to go ahead with procedure outlined above or sacrifice my warning lights. Many thanks for your help and I might add that down through the years I have found your software invaluable.

Many thanks for your mail. Please allow me a little time to digest your comments and I will reply.

I have a generick cockpit which I have built over the years but I am afraid that I have run into a problem when I updated to Windows 7 (64). Up to now I have used a TRC Multicontroller board and two TRC Controller Boards to feed TRC Gauges and provide info for O/Head panels. All of these I have had to remove due to none compatability between my new OS and TRC. I am endeavouring to provide gauges etc.etc . through additional monitors and software. Where I have come to a bit of a holdup is in trying to replace one of my O/Head panels which I used for aircraft lights and warning lights such as ; Out Marker ,Mid Marker , In Marker, Overspeed, Doors Open, Stall, Gear Busy, Gear Up, Gear Down, Nose Wheel on Ground, Left Wheel on Ground, Right Wheel on Ground, Low Fuel and Low RPM. I have no problem with aircraft lights as these can be provided by FSUIPC4 version 4.911 with the use of buttons, switches and rotary encoders, however, the warning lights which I thought would not be a problem are proofing the most difficult to perform. It had been my intention to use the FSUIPC4 Offsets for FSX and after reading all I could find on the internet regarding this I understood that for this to be accomplished within FSX one had to select offsets, go to “FSUIPC Options and Settings / Buttons and Switches” press the appropriate button or switch you wish to use ( I should mention that I am using Leo Bodnor’s Universal Joystick Controller BU0836X to do this ). Then fill in the details of "Offset byte set", or "Offset word set" (etc) controls, specifying the offset (x....) and parameter of an offset and there you have it , the selected offset such as “Out Marker” would perform. I have tried every combination of available options but I am afraid with no luck. I am aware that in order to use offsets which are going to make changes to the variables in the origional offset this would require the use of the Lua program but I understood that for certain preset offsets this was not nessessary. The warning signals that I am trying to provide as far as I know have fixed settings and should only require a “True or False” reading. I have gone through the FSUIPC Offset list and selected the following which I feel may be the ones that would fit into “Defined Offsets” and would not require using Lua as I don’t want to go down this road; 0BAC ; Inner Marker: activated when TRUE 0BAE ; Middle Marker: activated when TRUE 0BB0 ; Outer Marker: activated when TRUE 0894 ; Engine 1 combustion flag (TRUE if engine firing) 092C ; Engine 2 combustion flag (TRUE if engine firing) 09C4 ; Engine 3 combustion flag (TRUE if engine firing) 0A5C ; Engine 4 combustion flag (TRUE if engine firing) 036C ; Stall warning (0=no, 1=stall) 036D ; Overspeed warning (0=no, 1=overspeed) 077C ; Stall horn available 0BE8 ; Gear control: 0=Up, 16383=Down 0BEC ; Gear position (nose): 0=full up, 16383=full down 0BF0 ; Gear position (right): 0=full up, 16383=full down 0BF4 ; Gear position (left): 0=full up, 16383=full down 0BCA ; Braking indicator: brake applied if non-zero(1=Left, 2=Right, 3=both 3367 ; This byte shows doors that are open, one bit per door: 3366 ; This byte reflects the FS2004 “Engine on Fire” flags. To put it in a nutshell I am not being over selective in which warning signals it may be possible to provide in the manner outlined .What I wish to do is to try and replace some signals on my O/Head panel which I have lost for reasons explained above and to do this using the offset feature in FSUIPC4. I would be most grateful for any help that can be provided . I feel that I am not reading or perhaps understanding the best way to provide what I am trying to achieve. Sincere thanks in anticipation.