Pete Dowson

Yes. In the FSUIPC.ZIP (get it from http://www.schiratti.com/dowson if you were supplied with only a bare FSUIPC.DLL module) you will find a User Guide, readable in both Word and Acrobat versions. There's a complete section on each of the option pages in FSUIPC, including Visibility. Regards, Pete

Of course AV400 is not actually an NMEA protocol. :wink: Okay, thanks for the update! Regards, Pete

This is all stuff I've virtually forgotten now. but the EPIC95 package with the VXD is still available at http://www.schiratti.com/dowson, where it has always been, and provides not only the VXD but also the registry files to get it all properly entered into the registry. AND documentation! It simply sounds like you've not installed the VXD correctly with the registry additions needed. Go get the ZIP package and check the documentation. After that, I'm sorry but you'll need to contact the EPIC makers, R & R (Ralph Robinson). regards, Pete

I think the registry points to GFconfig. The GFdev.dlll file is in the same folder as GFconfig. Regards, Pete

Not easily. Unless the GoFlight installer made the Registry point to the X-plane folder that older one won't be used. Or overwrite it with the newer one so it doesn't matter? Regards, Pete

I see you have these buttons only enabled for the aircraft "PMDG 737-700". Can you please re-check with a default aircraft instead? You are using FSUIPC 3.45, yes? If not please install that. Then go to the FSUIPC Logging options page. Switch on the Event logging. Test the button again. Switch off the event logging. Look in the log, see if there's a "View Forward" control listed. If the log is short enough, show a bit here (if you are using PMDG it will NOT be short!!). That is also Joystick 0? Or did you pull the first one out? There's nothing really to go wrong with the programming of button release, so I suspect something is interfering with the control instead. Regards, Pete

Further to my last reply, I've looked into this. It is not possible to program a button to send the Print Screen keystroke using the FSUIPC options screen, but you can do it by manually editing the FSUIPC.INI file. The reason is that Windows takes the keypress before FSUIPC can see it, so it can never fill in the box on the Buttons screen. Edit the FSUIPC.INI file and program it there. To make it easy, program your button to make, say, a "space" key press, then close FS and edit FSUIPC.INI. In the [buttons] section look for the line with K32,8 at the end. That will be the sapce. Replace the 32 with 44, the keycode for PrintScreen. This gives you a "normal" print screen -- the whole screen. I've also tried it with ALT (for the current window), K44,24 and this works too, but unfortunately the ALT also brings up the normal FS menu. Other keys which won't be easily displayed by FSUIPC but which may be usable by direct editing include: 19 Pause 20 Caps Lock 27 Escape 144 Num Lock 145 Scroll Lock Hope this helps, Regards, Pete

Yes, that's the problem, which is why it can't be used to program an FS or FSUIPC function. Oh, I see! You actually WANT it to do a Print Screen. Sorry. I thought you were asking whether the key could be used for other things. My misunderstanding. Its list only includes those usable in FS, that's why. I'm not sure if I could make an exception for Button programming (as opposed to Key and Hot Key programming) -- but I'll have a look. If it is easy I'll slip it into the interim test version I am planning to upload here later this week. Watch the announcements. Regards, Pete

Well, the only bottleneck should be the processor on which FS is running. If the "data rate" you are reading is the one displayed in the PM PFD program's graphics display, then, yes, that could depend on the processor on that PC AND on the graphics card there too. But that won't slow down the rest, and it certainly should not slow down the WideFS operations, even on that PC. Your best bet for the PM MCP is still to run it on the same PC as FS. Even more reason to have the PM MCP there. This is with the PM MCP on a Client PC too? There's something odd there then. Are you sure the GoFlight driver (GFdev.dll) is up to date? There's no such symptoms here with any of the GF modules on any system. Check the GF website for a more recent driver package. Regards, Pete

I don't think so -- doesn't Windows see it anyway? Try it and see. Regards, Pete

Well, I don't really know why you persist in misunderstanding (are my messages really so obscure? :( ), but of course you can view it in such a restricted way if you like. You seem to be missing some of the things I mentioned. For example you won't find many of the FS controls listed by FSUIPC actually available in the FS assignments -- as I said there a hundreds there not in FS's list. Of course some don't work and none are obviously documented. FSUIPC gets the list automatically from the FS CONTROLS.DLL which not only includes all those you can assign in FS assignments but also all those that Gauge writers can use in their programming. You did actually use one (Panel Toggle) which is in FSUIPC's list but not in FS's, didn't you? Additionally there are no facilities in FS assignments to, for example, make key assignments different for different aircraft. And of course there are quite a few non-FS controls added by FSUIPC which are actually executed by FSUIPC. You can peruse the FSUIPC user documentation to see those. Regards, Pete

No, not real flying. I did learn to fly for real years back never got a license -- got stopped by my failing eyesight (hereditary retinitis pigmentosa, gradually killing all my rods, or is it cones? Anyway, the peripheral & night vision goes). That's why I do simulation. I'll have a look. Thanks. Regards, Pete

Ah, thanks for the offer -- but I got one straight-away at my usual GPS suppliers! :wink: Does the "Fly" demo come with any maps? Looks like you have to buy a subscription for maps on top? Difficult to tell what sort of European coverage they have from that web site. Regards, Pete

Great! I'm in the UK. I'll see if I can find a source here. Of course, not having the 'a' version, I haven't got any of those, only the road maps (MapSource / City Select). Well, good luck! Let us know when you get anything out of them! Regards, Pete

I have an iQue 3600 (not the 'a' though). It's got a USB sync cable. How do you configure it to send/receive serially as a COM port? I assume its maps and so on are for aviation, and that it comes with some other menu items to set it for NMEA input? Oh, I see. I thought you said you "have the iQue communicating as well."? What was that communicating as/through/to, then? Well, since the socket on the iQue doesn't really have the usual D-type pins 1-9 or 1-25 to "crossover, and since it would be pointless of them to make a cable which connected Receive on the iQue to Receive on the PC, and Transmit on the iQue to Transmit on the PC, it jolly well must be, really. :wink: The only reason I am careful to tell folks to get a null modem or crossover cable is that there are lots of serial cables designed to connect PCs to other devices, and devices which aren't "originators" of signals (DCEs) usually have their serial ports wired as terminals (DTEs), so cables aren't crossed-over. PC to PC links need crossing over because they are both DCEs. (At least I *think* I have these acronyms right -- it's been a long time! :wink: ). Also, many cables which may look right could be designed to be extension cables, and they won't be crossovers either. But a cable with a PC type serial plug at one end and some proprietary thing on the other, as the iQue cable must be, doesn't really have terms like "crossover" applicable to it. Not that I've found. That's why I was asking you -- I assumed it must be something special in the "a" version. The options on the satellite reception screen on mine are only "New location, New Elevation, Preferences, and About". Preferences only contains "WAAS enabled" and "Battery Saver". Maybe yours has more? If Garmin says you can do it, maybe they can tell us how? Regards Pete

Only a few hundred! :wink: (Including the Panel Toggle one, I think!). Also FSUIPC can assign GoFlight buttons, and make both Key and Button programming specific to particular aircraft. And a few other facilities I think, like more key combinations with Tab, Win and Menu used as shifts. :) Regards, Pete

Not arrived yet. Can you re-check? Pete

There's no "toggle panel" control listed. The one which corresponds to the "W" key in FSUIPC's list (and in FS9's CFG files) is "Panel Hud Toggle". This cycles through panel-minipanel-no panel. There are specific panel part toggles, usually mapped to Shift+1 to Shift+9 -- the "main panel" is usually Shift+1, but this relationship is defined in the Panel.CFG files. There is a "Panel Toggle" which toggles the panel on and off without cycling through the minipanel. You are assigning the wrong control. Try using either the FS assignments with "Panel on/off" (which I have just tested and certainly works fine with the Num/ key), or, in FSUIPC, the "Panel Hud Toggle". These are the same controls and both work fine. I don't understand why you are making such complication out of this. Why not just go to FS Options-Controls-Assignments, find the assignment to "W" (against Panels On/Off) and reassign that control? In FS "W" is "Panel On/Off" and will work when assigned to Num/. Why haven't you used FS for this? In FSUIPC it is Panel hud toggle (as, indeed it is inside FS and in the FS9.CFG file), and it will work as well when assigned to Num/. Regards, Pete

Well, you completerly confuse me. Why map one KEY to another KEY? And how on Earth do you do this in FS assignments? What would you want either KEY to do? Surely if you want Num/ to do what W used to do you should simply change the Panel On/Off mapping from W to Num/. What would mapping "W" to anything accomplish? "W" is just a Key on the keyboard. Why do you want it to produce Num/, even assuming FS could do it? You seem to be mixing up keyboard keys and FS controls. The FS control is "Panel On/Off". Keys are those things on your Keyboard. You can assign almost any key to any of the FS controls listed in FS assignments, but you cannot assign a key to a Key! It makes no sense. :( Can you actually explain what you are trying to achieve? What do you want to use the W key for that you have to reassign the Panels On/Off control in any case? Pete

Try the thread entitled ""re: writing active weather to fsuipc from active sky". Sorry i can't post another at present, but there will be an update for wider tests up in an announcement later this week. Regards, Pete

I don't think it's my place to do this, sorry. I have quite a lot to do of my own, and am 100% rooted in MSFS. It is easy enough to find details of the NMEA sentences he would need to produce on the web these days. When I first did GPSout I had to purchase a copy of the NMEA specifcation, a 100 page document, for several hundred dollars. He certainly won't have that sort of problem now! :wink: Regards, Pete

For writing a station the TimeStamp is at C824. What are you doing with CC00? If you meant read the timestamp at C824, then yes. If you are setting a string of stations you would read it in the same Process call as the previous station. Something like this: 1 read timestamp 2 write station 3 Process 4 save timestamp read as "x" 5 read timestamp 6 Process 7 if timestamp changed frm "x"? If not loop to 5 (at next time interval) 8 save new timestamp as 'x' 9 continue at 2 till done all This "timestamp" business is a hand-shaking protocol -- there's only one set of weather data being processed in FSUIPC at a time, so you have to know it's done one before sending the next. For reading weather, not writing. Is that what you are trying to do? If you mean when SETTING stations, then I'm afraid that you will read back what you've just written. It will only get changed to "GLOB" (say) if it's not a WX station. If you are talking about only reading weather, then, yes. In fact once you've set the station and it is accepted it will update every second and the timestamp will change accordingly. But if someone else asks for weather, or the ICAO isn't a listed WX station, you might wait forever, so take precautions. Many programs simply ask for weather by Lat/Lon to get around the problems of WX station lists. Well, I'm confused -- are you asking about READING weather stations, or WRITING them? Your subject line implies writing, but the questions are then a bit, er, skewed. :wink: Regards Pete

Yes. Regards, Pete

No, but I've never noticed it as a problem -- your throttles should have been pulled back to idle of close for the descent in any case. The spooling delays are sufficient for you to "get the feel" for the correct throttle quickly enough. The only other way would be to get a motor drive for the throttle quadrant with some interface for a driver in the PC. Regards, Pete

Yes, it's been reported before in several threads. It's a bug in 3.45 fixed in interim versions attached to one or two replies here already. It only happens if Throttle1 is calibrated in the multiple throttles page of FSUIPC. Apologies for this. You can either check for those mesages with attachments below to get an interim patched version, or wait till about the middle of this week when I'll be posting "official" interim versions for wider testing in the Announcements section above. Regards, Pete