Hello,
On server all modules are connected.
Testing FCU Software works over the network.
Any idea?
Printable View
Hello,
On server all modules are connected.
Testing FCU Software works over the network.
Any idea?
Did you try to manually close and restart hardware connect?
Please switch on the log feature in hardware connect (only for the switches), and tell me if there is any answer when you use FDS hardware?
JL
i configured now on client PC1 the FDS Module via IIT_Creator.exe
I defined some buttons for Test and this buttons working via network... (So i guess i do not need the IT Software including to the board enymore?)
But no response to Marcins Profiler Software...
Best Regards! Marco
Hi JL,
some feedback for b25.2:
- the reallly bad lagging on my main machine is gone ... now it's smooth again
- @ Marco: I also use the Marcin FCU: In general the Marcins profiler works with b25.2. But there are some detailed issues which need to be solved. However, I am able to dail speed, HDG... etc. Marcin wanted to provide an update "ASAP". I use profiler 2.1.
- for networking: I can confirm Marcos impression. Its very slow now. The throttle set on EWD move very slowly on client PC. (hardware throttle connected to main server/FSX PC)
- if I have 2 EWDs open (one on server and one on client) the client shows something different. On client is shows HYD B+G LOW PRESSURE with all the flight limits... even HDY is available... the EWD on server shows correct status and NO warnings about HYD.
- since b25.1 all my DUs on my old Pc (except the EWD) remain black??? Any Idea? I guess its my personal problem but do you have any idea what could be the reason that only the EWD is shown on my old client pc? I have tried to start them seperately and without the starter ... without success.
EDIT: I have just removed the complete FMGS "version mix" from my client and reinstalled B25.2. Could it be that the WideFMGS.exe is missing. I can only find the Server in the directory? The WideFMGS.exe is gone...
Regards,
Rob
HI JL,
after some confusion I want to share how I solved my problems:
Sorry for the confusion!!! :(
- first off all, the lagging on the network is gone. Even on my very old machine the throttle is very smooth and not lagging on EWD.
- I think my problem came with one of the last versions you provided: Everytime I installed it on my client, I forgot to deselect ther FMGSserver/AP... etcs. After a clean install as "real" client it works very well after my first impression. Also my black DUs are gone. I will report back after some more testing. but for now forget my last post :)
@ Marco: Still the FCU seems to work. At least the "main things"... Here and there are still some bugs but as I said, Marcins works on it.
Rob
!EDIT!: So after one hour of testing b25.2 I have to say "THUMBS UP, JL!" That's very nice!
No lagging, no blanks, no flashing, no FMA updates... NICE!
Well, I really like the new flight model... thanks again to TOMEK! But I just noticed some significant overshooting of the HDG at lower speeds: i.e. 140, flaps full when AP on. the AC tends to overshoot up +/-20° HDG wrt to target HDG and swings alot before settling to target HDG.
Thanks & regards,
Rob
ahhhh OK thanks for the feedback. Indeed, and for everyone reading this ;) :
DO NOT INSTALL ITEMS THAT ARE NOT REQUIRED!
I really mean it! The software is getting quite complex to run, especially network wise. To make things easy I used the installer feature, but still, care must be taken when installing, otherwise the software gets lost not knowing what it should do.
@Marco: just random thought: do you have wideFS launched on the MCDU PC? (it is required to communicate with FSUIPC, my software does not replace what Peter Dowson created, it was never the point!)
Cheers,
JL
@JL: of course wide FS and FSUIPC are installed as required... that are standards we dont need to talk about...
@AirFan: Did your FCU start working or is there nothing that works? My FCU stays dark and cold and do not start working like in Beta 21 before. All worked before Updating Jehell from Beta 21 to Beta 25.2.
If your FCU is working pls tell me what you have done... Thanks a lot
Regards! Marco
Hello Marco,
As I said the hardware FCU from Marcin is "generally" working with B25.2. And I have not done anything to get it work. It worked with pervious JL versions and still does. Except that since B25 there are some bugs. (read my older posts to B25)
I know Marcins FCU units have changed. I have one of the Plug&Play versions without the I/O board. Its now all included so you only need a usb + power cable to hook it up. If you have an older version it might behaves differently. What I can do is providing you with my FCU profile file for the profiler V2.1. PM me and I will send an email tonight.
But I doubt that it will work with the "old" FCU from Marcin. However, you can try my profile. I recommend to contact Marcin if you cant find anybody who can confirm this dark situation.
Regards,
Rob
@JL:
another one for your list, if you don't have it yet :)
- the ILS mode on ND shows the signs for decel point, top of decent, the runway, selected range values etc...
Regards
Rob
Hi JL,
regarding the mentioned HDG overshoot I can be more precise: It only occurs after an autoland when you do a touch and go. The AC changes to some mode trying to keep the AC on centerline (both APs remain connected). In my case it swings around centerlinewith a huge overshoot ( leaving the runway and the airport :) ). In case you continue flying after autoland the AC also behaves like that back in the air. If you selected a heading it swings left and right around the target HDG... just like on the runway after autoland.
Hope that helps... maybe you can have a look.
Thanks & regards
Rob
Hi,
@Marco: can you give me a detailed info on your system? (number of PCs, what runs on which PC, where hardware is connected,etc...).
There were a few changes in FSUIPC offsets, nothing big but it might affect how Marcin's interpret the power on offset for example. Apparently there are various versions for his hardware, did you ask him about that?
Right now I cannot see why FSUIPC offsets would not work :( Did you try to plug the MCDU on the server PC?
@Rob: I will look at that. This AP mode is not yet perfect, far from it ;)
Regards,
JL