pdpo

Hi Peter, I was trying out LUA and made a script called Initial.LUA in the widefs directory. Reading only the parking brake offset for 100 times and then stopping the lua script. Between each read action I wait 500msecs. I expect 32767 for the value but I read 0 for the first 20 seconds. After this 20 secs the value is 32767. Is it normal it takes soo long? I handled it for now by putting a while loop which ends when the FS day of year is different to 0 (offset 0x23E). Greetz Peter

Hi Pete, I thought I had enough info send to you but it seems I need be more specific. Well, its FS9, qnd I made the capital mistake that I thought to lower the framerate in order to free CPU for widefs but by doing that I actually worsened the problem because I read that wideserver is sending the info on FS frame speed. So now I did the opposite, I increase the framerate in FS and i see also the data rate that project magenta PFD is receiving going up. PFD of PM is making its framerate double the data receive rate from wideclient. Also my FSCOMMUNICATOR PC now also receives higher data rate from FS. So I will proceed with lower FS settings yielding higher framerates. Thanks anyway Peter Belgium

Hi Pete, My FS PC is a P4 3hz with hyperthreading. I got several widefs clients on somewhat lower end PC´s like celeron 2.66Ghz. I noticed there that the clients get only about 10 times per second data from widefs and I cannot get this higher. I checked the network traffic and this is rather low 0.01..0.05% . I checked the CPU usage on the clients, around 20% so not that high. The FS PC, I have removed the hyperthreading, stopped all processes which are really needed for FS, set the target framerate of FS to only 10 frames per second (while around 25 is reached when I set no limit) in order to reduce the load of FS itself. But all to no use, in the clients I see the same rate of data receival of 10 times per second. Even I connect only one client, no improvement. Any idea or is this normal and somewhere a limit of widefs? Any ideas how to improve this? Greetz Peter Depoortere Belgium

Hi Pete, I tried last week some things with the conditional button assigments. Im at work now so I dont remember the exact offsets I was using. Anyway following is what I liked to accomplish : offset for external view (xxxx) value 1 = outside view value 4 = spot plane view So I put in the fsuipc.ini for the same button press two lines the first line : when value on offset xxxx is 1 -> change it to 4 the 2nd line : when value on offset xxxx is 4 -> change it to 1 but this did not workwhen it was 4 and I pressed the button it went to 1 when it was 1 and I pressed the button it went to 1 the reason : I think that when it is one fsuipc matches the first line and executed but then it matches with the new value also the second line and sets it back to 1 Greetz Peter

Hi Pete, just leave that at this 5 sec. You never know another appl needs also some time to shut down and after all what is 5 secs when you want your PC to shut anyway. For me is more important the PC shuts, so when I close FS all my cockpit PCs shut themselves nicely and I dont find one of them still on the next day :-) For the buttons i'll keep an eye on it for the coming days. Its quite important it works consistently since one of the buttons is the push to talk and like some days before I was talking to the controller but he wasnt responding to me. After some time I saw in the teamspeak that this wasnt sending since the PTT was not seen. But I have now put 2 buttons to change the view so I verify here first if its working. Ready for the next problem/question? Maybe better a new thread? Greetz Peter

Hi Pete, you've done it somehow.... I tried only onestonight there will be more trials... Now my buttons were working from the first time. Anyway, i'll remove those lines with the protocol and the serverip in order to avoid any further occurences of this. When I shut down the FS, I saw on the remote computer fscommunicator closing down and then wideclient stayed up for some time and eventually the wideclient closed down followed by the computer... Greetz Peter

HI Pete, I think the latest update is not good. The button case is still there. Do not see the joystick buttons again. Added to the first two lines in the ini file Protocol=UDP ServerIPAddr=10.0.0.5. The shutdown is completely messed up I think. When I shut my FS PC I see on the remote PC FSCOMMUNICATOR being closed and started again iso closing, I think. Anyway, for sure I see it starting again since I see again the opening page appearing. Then some short time later, as well the window for wideserver closes as the fscommunicator but the PC does not shut down. The idea you put forward to contact the chap from fscommunicator will be difficult since he stopped any development on his program some time ago (due to hackers who craked his code and spread out an older version of his software for free on the net) However if you insist to him and pay some money he gives you the needed keys for activate the licenses of the latest version. If you like I can send you the latest version (without keys of course). Then you can start and use the program (full version) but after one hour it closes down and needs to be restarted. So to get serious support (like you provide us) from him will be difficult I guess. Of course we can always try but then we need to know exactly what wideclient is sending to the process. To start and stop I got the following lines: [uSER] AllowShutDown=yes RUNREADY1=c:\FCOM\FSCOM.EXE CLOSEREADY1=Yes Greetz Peter (PS tonight I can check with spy++ what exactly you are sending in the new version)

Hi Pete, we are making progress....I have removed wideclient.ini and started the client, then I started the FS. Buttons were seenas you also see it Then I checked the differences between the newly created wideclient.ini and my settings. First impression, no many differences. Then i added the [user] section where I start the fscommunicator. Retested it, buttons seen immediately. Then I added two lines to the wideclient.ini : protocol=UDP and ServerName=10.0.0.5 (ip address of my FS PC). after adding those two lines I retested it and the buttons were not seen again. So there lies the clue...how to link this to what we see...thats up to you... For the moment its now Ok with me since the wideclient connects also without those two lines. -> update : for the problem written below I was reading the document and I noticed the the serverName should have a name rather then the ipaddr So I changed it to ServerIPAddr=10.0.0.5 and then tested the buttons again but buttons are not seen again I got only one remaining problem now. It must be related to fscommunicator I think because it started only when I started using that. Before this PC was used for the project magenta PFD/ND and when I shut my FS PC this PC also shut down. Now that I put fscommunicator wideclient shut the fscommunicator program and itself but it does not shut the PC anymore. Any idea? -> update1 : if I close fscommunicator by hand and then shut FS2004 then the remote computer shuts down nicely -> update2 : when I close FS2004 (FS communicator still running) then the computer does not shut down and I notice on the taskbar that it takes longer to close fscommunicator then wideclient itself -> update 3 : there is already another post in this forum about this called computer not shutting down using wideFS and its also related to FS Communicator is it difficult to introduce the same timeout as DelayReady1 after each close of an application to try. I mean with RUNREADY1=xxxx and DELAYREADY1=y the program will wait some seconds after it started this appl then move on to the next. Can this wait also be done after each CLOSEREADY entry? Greetz Peter PS : if you still want to test something for this , just keep this thread going..i´ll be checking it daily

Hi Pete, all my PC's (4 of them) are starting wideclient at startup and then start the needed applications when the FS (wideserver) is ready. Never had any issue. I also never used buttons on a remotely connected joystick. Its only since last week I started using fscommunicator which made me move my joystick to that remote PC and have my buttons of my joystick being connected to a wideclient connected PC. When FS is ready the wideclient is getting connected nicely and fscommunicator starts up (via runready in wideclient.ini) exchanging data with the server. Its purely these buttons which show some problem. Sorry, if I caused extra work. I dont know how wideserver/wideclient do their communication but I assumed that the joystick buttons also are just like transfering data and this transfer never showed any problem if wideclient started first, waiting for the server. Since it was working when I closed wideclient and start it back up I assumed it had something to do with starting it at startup of the PC. Overlooking the fact that at that moment also FS was running already. Greetz Peter

Hi Pete, tried lots of things this night, also your new version which is not the solution. It all boiled down to the same situation where my buttons do not get seen in FSUIPC and that is when the wideclient is started before the wideserver is ready. Whatever I do in my client PC (delay start of wideclient with 20secs after start, dont start fscommunicator, start wideclient manually) if FS is not running yet. The client goes to waiting for connection and then I start my FSbuttons not seen. When I start my FS first and only start the PC with the client afterwards (when FS has started) there is no issue. On my FS PC I also start automatically project magenta FCU and AST server software via the intif lines in fsuipc.ini. Thats it... Greetz Peter PS time to dig into the code? :-) Im off to sleep

Pete, I will try to see this USB power managment for sure I have found some program on internet where I can specify delays for startup of programs after windows has loaded, will see what that does When FS comes Ok and fscommunicator starts up it can read the joystick axes and button while the other buttons are not seen in fsuipc Greetz Peter I'll keep you informed

Hi Pete, the joystick is a USB device FSCOMMUNICATOR is a program that reads the joystick axes and buttons and implements a very detailed airbus fly by wire system. You can connect in this way two joysticks and let them work like the sidesticks of an airbus with priority function. This program reads my joystick axes and I have set it up for one button for the priority switch. The other buttons on the joystick are defined in FSUIPC for braking, PTT, outside view, plane view. I will try tonight to remove the autostart of fscommunicator to see if it would be related to this. But I guess not, since when I close it and then I close wideclient, then open wideclient again (fscommunicator is also started automatically) it works again and my buttons are seen in fsuipc. Strange not. Anyway, i'll try it and let you know. The only difference I see is that in the case that it doesnt work, wideclient waits first for wideserver to be up and then starts fscommunicator. in the case that it works I start wideclient when wideserver is already running, and FS is running. We'll see.... Peter

Hi Pete, I got an issue with my joystick button assignments. I assigned in FSUIPC some joystick buttons from a ajoystick physically connected on a second computer linked via wideFS. All is working well. Then I copied the wideclient link into the startup folder on the 2nd PC so wideclient starts up after boot and then waits for the connection of the FS PC. When this FS PC is ready (wideserver ready) the wideclient starts FSCOMMUNICATOR. Now what happens is that my defined joystick buttons dont work after startup. Fsuipc does not see any button pressed on that remote joystick. When I close fscommunicator and wideclient on that remote PC and start wideclient back up however it works again. Any ideas? I guess it could have something to do with the fact the wideclient starts very fast after the PC comes online and the joystick driver is not ready at that moment? Functionally it works because if I dont start wideclient during startup but I start it manually, the buttons do get seen in fsuipc and everything works. The problem is I would like to remove the screen from that PC, so it should all start automatically when I switch on the PC thanks Peter

Also checked during lunch on XP home.... Working also They reconnect when FS starts up Greetz Peter Depoortere

Pete, I tested it with winXp Pro and there it was OK with the latest version and it was faulty with the previous version (as above) Tonight I'll put it also on my other PCs with XP home. But it looks better now since on the XP Pro I saw also the disconnection in the logfile as on the XP home ones. Greetz Peter Belgium PS : send also as Private Mail

Peter, to test a possible solution to this I'dd be happy to assist. The current workaround is to start first FS and position the plane on the gate then I start the client PCs and this gives no problems I'll continue for now this way in order not to change all the ini files so if you got something regarding this to test it doesn't take me much to do so. If there is anything else you needjust send me mail at peter(dot)depoortere(add)skynet.be and peter(dot)depoortere(add)alcatel.be the last address is being checked very often since it in my work but i got from work no access to my PCs at home Greetz Peter Belgium

Pete, I am using winXP (I think I updated to SP2 on all of them) I forgot also to mention that I installed yesterday the latest wideclient on an older computer (WinMe) that I use to develop my hardware scripts and there I did not have this problem!!! Greetz Peter

Just made some checks and here is a logfile. For some reason when FS starts up it send a shutdown code to the client PC When FS is running already the connection is made instantly ********* WideClient Log [version 6.598] Class=FS98MAIN ********* Date (dmy): 15/05/06, Time 21:25:28.170: Client name is MCDUDISPLAY 625 Attempting to connect now 656 Trying UDP/IP host "10.0.0.5" port 8002 ... 656Okay, IP Address = 10.0.0.5 656 UDP connectionless mode set up okay! 875 Error on recv() [Error=10054] Connection reset by peer 875 Attempting to connect now 875 UDP connectionless mode set up okay! 875 Received shutdown offset code = ADBC 875 FS closing down (param=ADBC), disconnecting 875 ********* Interim performance summary ********* 875 Total time connected so far = 0 seconds 875 Reception maximum so far: 0 frames/sec, 0 bytes/sec 875 Transmission maximum so far: 0 frames/sec, 0 bytes/sec 875 Max receive buffer = 0, Max send depth = 1, Send frames lost = 0 875 ***********************************************

Well Peter, you're rightit was late last night. I have installed also the latest widefs version found on the forum and the change to UDP was in the light of this new version. I use a switch for my network connection. Anyway when I start first the Fs running PC, start FS and sit somewhere on the tarmac, then I start the client PC -> I have no problems with this new version and with an ethereal application I see the UDP messages going back and forth. However, when I start first a wideclient while the FS is not running yet, then I start the FS then the client stays in waiting for connection and it doesn't connect. When in this state I stop the wideclient and restart is (now server is running) I got no problem and the connection start immediately. Will make some logs when I got time .... I was thinking maybe there is a change since UDP is connection less while TCP is connection oriented and will retry until the server comes up Greetz Peter Belgium

Hi Peter, Installed the latest 3.601 on my PCs and I have put in the clients the serverName=ipaddr in each ini file and put the protocol= UDP Everything seemed to work as before at first glance. However after starting up all my PCs today I found the following. Normally I start all my PCs at ones and the PC running FS is the fastest but the slowest in booting. So all PCs are running wideclient before FS starts. WHen it finally comes online the client see this and start there applications. This doesnt happen anymore they stay without connection. If I shut the wideclient and start it up again (server is running already) everything is OK Greetz Peter Belgium