Pete Dowson

Are you using Windows 8 by any chance? A lot of folks have problems in Win8 and 8.1, especially with Saitek devices. Check that you haven't got Windows powering off USB connections to "save power". There are solutions around but you'll need to search. I have seen reports that it may be fixed in Win10, so it may be worth upgrading. Win10 is a free upgrade for 12 months. Pete

FSUIPC sees any normal joystick connected without an interfering driver and which has an ID assigned by Windows. Does FS see the throttles? Is the device listed in the [JoyNames] section of the FSUIPC INI file? Please always also state the Version of FSUIPC, and the version of FS -- FS2000, 2002, 2004, FSX, P3D1, P3D2? Pete

Unless you want to write your own driver, you'll need to ask as Pololu Support. FSUIPC doesn't have any hardware support built in at all. It's an interface program for others to write applications and drivers to. I've no idea how the Pololu card interfaces, but if it is a USB or serially connected device then you could actually support it with a Lua plug-in rather than a separate VB, C# or C/C++ driver program. Pete

The Server log is from the 24th July whilst the Client log is from the 27th! The Server log shows some connection but with problems and no actual data transfers, the Client log shows your original firewall type rejection. Since neither WideServer nor WideClient can re-program themselves and change their behaviour between those two dates, something else is changing on your system. I'm afraid I have no way of identifying what that might be. And even though you say "fortunately WideFS on the client stations was finally connected. this happened on friday", from the Friday log you show above there was certainly no data connection, only problems. The Server saw the Client, but no data could be exchanged I still believe that's a firewall or virus checker's protection sort of block. There's no other information which can be gleaned from these logs, and I'm afraid there's no better information which can be obtained from Windows by my programs -- those errors are all it gives. Nevertheless, in future, please show the logs from Server and Client which actually correspond with each other -- i.e. show the same session. Pete

Lua scripts are just text files saved with filetype .lua, that's all. They go into the FS Modules folder, and can then be assigned to keys, buttons or axes in FSUIPC, or if event-driven, run using an [Auto] section in the FSUIPC4.INI file. You'd get more appropriate help from folks who know about your aircraft if you put the main question subject as the title of your thread. "Newbie" is just a non-title altogether. You also need to state which Airbus is it -- Aerosoft or default or what? Please also always post support questions here, in the Support Forum. I moved it from the "User Contributions" subforum -- that place is a repository for solutions found by users, not questions posed. Regards Pete

Sometimes the problem is that FSX closes before WideFS manages to signal this to the Clients. What I do is assign a keypress (I use Ctrl+Shift+E) to the WideServer "ShutdownHotkey". The parameter is in my FSUIP4.INI file in the [WideServer] section, and looks like this: ShutdownHotkey=69,11 This works fine for all my clients. Pete

Version 4.939d is out of date and no longer available or supported. Use the currently supported version. 4.939u, which is the main release available here and on the Schiratti site. Never look for old versions, always use the current version! Also, the latest P3D is build 12946. You are missing a hotfix I think. Pete

WideFS is DIFFERENT to FSUIPC. The parameters are nothing like the same. PLEASE PLEASE refer to documentation! Pete

As indicated in the FSUIPC Offsets Status document (being written in blue) it was new to FSX. It will apply also to FSX-SE and P3D of course, but nothing before FSX. Pete

If you are using WideFS you may like to look at the Lua program I use for my internal cockpit display, which handles both 3380 text (for Radar Contact menus in my case), weather data for the route from ASN, and GSX prompts and menus. Here (line numbers just for reference of course, not part of code): colours = { 0x000, 0xfff, 0xf00, 0x0f0, 0x00f, 0xff0, 0xf0f, 0x0ff } doshow = 1 shown = 2 textset = false menuset = false time2 = 0 time3 = 0 timeclear2 = 0 timeclear3 = 0 w1 = wnd.open("Radar Contact", WND_FIXED, 1280,0,1024,768) wnd.backcol(w1, 0x000) wnd.textcol(w1, 0x0f0) wnd.font(w1, WND_ARIAL, 24, WND_BOLD) w2 = wnd.open("FSX Text", WND_FIXED, 1280,0,1024,100) wnd.backcol(w2, 0xfff) wnd.textcol(w2, 0x000) wnd.font(w2, WND_ARIAL, 17, WND_BOLD) w3 = wnd.open("FSX Menu", WND_FIXED, 1280,100,1024,668) wnd.backcol(w3, 0x88f) wnd.textcol(w3, 0x000) wnd.font(w3, WND_ARIAL, 17, WND_BOLD) ext.state("FSX Menu", EXT_HIDE) ext.state("FSX Text", EXT_HIDE) ext.state("Radar Contact", EXT_NRML) w1text = ipc.readSTR(0x3380,128) ipc.log(w1text) wnd.text(w1, w1text) local function testifclear() doshow = 1 if menuset or textset then doshow = 2 end if doshow ~= shown then if doshow == 1 then ext.state("FSX Text", EXT_HIDE) ext.state("FSX Menu", EXT_HIDE) ext.state("Radar Contact", EXT_NRML) wnd.clear(w1) wnd.text(w1, w1text) ipc.log("Showing RC") else ext.state("Radar Contact", EXT_HIDE) ext.state("FSX Text", EXT_NRML) ext.state("FSX Menu", EXT_NRML) ipc.log("Showing FSX Menus") end shown = doshow end end local function clearw2() wnd.clear(w2) textset = false testifclear() end function clearw3() wnd.clear(w3) menuset = false testifclear() end function textandmenu(mtype, colour, scroll, delay, id, n, msgs) doshow = 1 if mtype == 2 then -- Menu time3 = 0 if n == 0 then wnd.clear(w3) menuset = false testifclear() else menuset = true testifclear() wnd.clear(w3) wnd.text(w3, " " .. msgs[1]) wnd.text(w3, " ") wnd.text(w3, " " .. msgs[2]) wnd.text(w3, " ") i = 3 j = 1 while i <= n do wnd.text(w3, " " .. j .. " - " .. msgs[i]) i = i + 1 j = j + 1 if (j > 9) then j = 0 end end if delay ~= 0 then timeclear3 = delay * 1000 time3 = ipc.elapsedtime() end end else -- Text time2 = 0 if n == 0 then wnd.clear(w2) textset = false testifclear() else textset = true testifclear() wnd.textcol(w2, colours[colour+1]) wnd.backcol(w2, logic.Xor(colours[colour+1], 0xfff)) wnd.text(w2, msgs[1]) if delay then timeclear2 = delay * 1000 time2 = ipc.elapsedtime() end end end end ctr = 0 function time() ctr = ctr + 1 val = ipc.elapsedtime() if time2 ~= 0 and ((val - time2) > timeclear2) then clearw2() time2 = 0 end if time3 ~= 0 and ((val - time3) > timeclear3) then clearw3() time3 = 0 end if (ctr <= 2) then ipc.togglebitsUW(0x32FA,0xffff) elseif (ctr > 10) then ctr = 0 end end function update1(off, val) w1text = ipc.readSTR(0x3380,128) wnd.clear(w1) wnd.text(w1, w1text) end event.textmenu(0, "textandmenu") event.offset(0x3380, "STR", "update1") event.offset(0x32FA, "UW", "update1") event.timer(500, "time") testifclear() Sorry it's so comment-less. I'm not one for commenting my code much. Slows me down! ;-) Pete

No! No! The start and close is in the one line!!! The CLOSE is an option. All Run lines run the program and optionally CLOSE, KILL or DELAY them! Please please please READ the documentation! Just ONE line per program!! I showed you exactly that in my last message! Pete

I assume the Run1 program is different to the Run2 program? Earlier you had: Run1="C:\Program Files\Project Magenta\pmSounds\pmSounds.exe" Run2="C:\Program Files\Project Magenta\pmSystems\pmsystems.exe" So pmSounds then was the first one, not the second. If that is so, you should be trying: Run1=CLOSE,"C:\Program Files\Project Magenta\pmSounds\pmSounds.exe" Run2="C:\Program Files\Project Magenta\pmSystems\pmsystems.exe" The "..." around the program name are needed if it contains spaces, as yours does. I run pmSounds like that, with CLOSE, and it works fine, though some older versions of that program didn't close properly, ever. BTW I don't think those programs will like running in "Program Files", because that folder is protected against being written to, and they write their settings and logs there. You'd need to turn UAC off and maybe even run them "as administrator". If you do that you must run FS "as administrator" too. It all gets very complicated. I suggest you move pmSounds and pmSystems to their own folders OUTSIDE of Program Files. Pete

FSUIPC4 can capture that text and make it available to WideFS. The 3380 offset is only used for text displayed via FSUIPC itself. Details of the way to capture it on a WideFS client PC are found in the Lua documentation, in your FSUIPC documents folder. Check the "event.textmenu" function The same mechanism can also capture the menus from programs like Pro-ATC-X and GSX, but cannot entirely remove those from the FSX screen, only the P3D one. I use these facilities to move the messages and menus to a small screen inside my cockpit. Pete Pete

The logs are okay, though the current ones are incomplete. When posting logs please close FS first, as there is useful information logged at the end, on closure. You don't need to post Logs which don't have the normal name (FSUIPC4.LOG, WideClient.LOG, WideServer.LOG). The ones with another number (1 usually) before the .LOG part are previous copies, saved in case your sim does an auto-restart on a crash (which would else destroy the possibly relevant log). Pete

Well, something is acting as a firewall, because error 10061 is described by Microsoft as: No connection could be made because the target machine actively refused it. Every time this has occurred in the past it has been firewall type protection on the FS PC. I doubt yours is an exception. Check any add-on security software as well as Windows' firewall. Most anti-virus packages also add network protection. The only other thing I know which could actively stop a connection is something already using the port (8002), but that normally gives a different error, like "timed out", because the port owner doesn't recognise WideClient. You could change the port as a test (needs parameters changed in both WideClient.INI and FSUIPC4.INI). FSUIPC doesn't need registering at all for WideFS to work. If WideFS wasn't registered the Server wouldn't start and you'd see this in the FSUIPC options and in the WideServer.LOG. Which reminds me. You've not posted your FSUIPC4.LOG or WideServer.LOG files from the FS PC, have you? Best post them as well just to double check from that end. Pete

Why are you persisting in maintaining two threads on the same subject. Just wasting both our times? Please see my answer in the other one!!! Pete

There's no point doing that. The line is NOT an error, it is just an informative line, in case you did want an initial plug-in to run and had simply spelled the filename incorrectly. Most lines in WideFS and FSUIPC logs are for information, NOT to warn of any problems! The ones telling of problems will say so. Pete

That's almost certainly a firewall problem. You either need to completely disable the firewall on the FS PC, or allow port 8002 and/or WideClient.exe proper entry (never sure which it is you do -- probably depends on the firewall).. I don't use firewalls between the PCs on my Network, only on the Router connecting everything to the outside world. I've always found it a bit of a nightmare trying to get permissions right. BTW, since you aren't using the Broadcasts from the Server, the Client won't know which Protocol it is supposed to use, so you need to set the Protocol parameter in its INI as well as the ServerIPAddr. Pete

Tell me about it -- wait till you get to my age! ;-) Glad you got it sorted. Pete

No no no! You still haven't looked at the documentation! There's no "=yes", just a comma!!! Why not actually look at what it says? Pete

There is no "Close1=yes"..." parameter supported in FSUIPC. You are evidently not looking up the format of the facilities you want. Please refer to page 45 in the FSUIPC4 Advanced Users document, where you will see the defined formats and options available. You have similar problems in your Wideclient.INI. There is no format matching the last line. It is just Close1=Yes Why not refer to the documentation provided, rather than make it up yourself? Pete

What commands and what aircraft? I really cannot help without specifics. What is this "menu" which shows a change? The FS "menu" is the strip along the top, the one which has "Add-Ons" in it which you select to choose FSUIPC. Pete

Please just specify the correct IP address to WideClient. Please read the section in the WideFS User Guide entitled Quote Pete

It's 3367 not 3362. No, they should be identical in this area. The aicraft model interprets the control, though. Are you checking on the same aircraft? If you log "Events" in FSUIPC, you will see that when you write to 3367, fSUIPC simply does what you are doing -- sends the same controls as Shift+E+n does. Compare the two logs from FSX and P3D. Maybe on P3D there's some control getting in between? FSUIPC uses a "macro begin/Macro end" facility provided by SimConnect to ensure the controls stay together. Prepar3D 1.4 is now very old, and if there is a SimConnect problem with it it isn't going to get fixed. Have you considered move onto P3Dv2? It is far superior to 1.4 in every way. Pete

As clearly stated in the FSUIPC User Guide, Mouse macros only work on those very few gauges which are written in strict accordance with the original Microsoft C/C++ Gauge SDK. Fewer and fewer are these days. If, in Mouse Macro making mode you don't get the overlay appearing when clicking on a gauge button it simply means it can't be done. Pete