Pete Dowson

Something is interfering with it. Check your FS Modules folder. All FS9.1 default DLLs should be dated 1st September 2004 (or maybe some other date if it isn't the US/UK edition -- but all the same date). There are 31 of them. Check, see if there are any others apart from FSUIPC. If that checks okay then I can only think there's something else running in your system that specifically affects other programs, like Window Blinds -- that is certainly one which does odd things to FS. Is there an FSUIPC Log file produced? What does it say, if so? Regards, Pete

Great! Well done! Pete

Using KeySend to transmit the signal from FSUIPC to Wideclient should work then. Just encode the keypress you need in the WideClient.ini. Don't forget to set the parameter telling WideClient to expect these things (though if you have the 'normal' PTT working already that should be taken care of). The keypress may need directing to the correct program too -- there are various methods discussed for doing that, the easiest being by getting the program (SB3?) loaded and run by Wideclient in the first place -- then it knows where to send it using the Run reference. Regards, Pete

A float64 is a double. Read it into a double, not a 64 bit fixed point number. The example you are basing it on is not a double at all but a fixed point number!! Pete

Download the FSUIPC SDK from http://www.schiratti.com/dowson and see if the information is listed. Regards, Pete

If it accepts keypresses, program the button to a KeySend in FSUIPC and program the KeySend to do the key press in WideClient.ini. See the WideFS documentation. There are examples for TeamSpeak, I don't know if they'll work for SB3. What you need to do to get keypresses into a program depends on how it is looking for them. I just don't know any of the SB programs I'm afraid. BTW, don't the Squawkbox crew or any of the Virtual Airlines provide any support on this stuff? I would have thought you'd be more likely to get help from those who already use it? Regards, Pete

Really if you don't know why you need it, then you don't need it. Develop things the other way around. Work out what you want to do, then see how you can do it. Then, when you investigate FSUIPC (e.g. through the FSUIPC SDK) you may find it useful, or you may not. But don't start the other way, saying "hmm, everyone uses FSUIPC so I shouldbut why?". Use it perhaps to help solve problems when you know the problems, not the other way around. Fundamentally it is just an interface into FS for other programs. It has grown with the additions over the years of many other facilities, mostly requested by users, but its basic function is a programming interface. That's probably because you are looking at it and trying to see where it fits rather than look at what you want to do and see what you then need to do it. Regards, Pete

Convert N from a range of -16384 - +16383 to N2 with a range 0 - 255. N is a 16-bit integer, N2 is a BYTE (8 bit). Use M as an intermediae 32-bit integer 1. Get everything on the same "base" (i.e. starting from 0): M = N (make sure you have enough room -- i.e. 32 bits) M = N + 16384 (now M runs from 0 to 32767) 2. Scale it down from 32767 max to 255 max 00 i.e 32768 different vales to 256 different values: N2 = M * (256 / 32768) or simpler N2 = M / 128 Now this rounds "off". More accurately you should round to "nearest", which would be by: N2 = (M + 64) / 128 You can do this using shifts instead of division: N2 = (M + 64) >> 7 (where >> means "shift right by"). Regards, Pete

A bit cold for the time of year, but it looks a bit better this morning. More like April than June though. Regards, Pete

I don't know what the difference is between a public PTT and a private one, but if SB3 accepts keystrokes, then just program your button to send that keystroke. Regards, Pete

You need to ask PM about this. There's no PmRjDemo with accredited access. Pete

Have you looked at the SDK? There are examples there, for several languages. Pete

I assume you are writing a program to do this? Download the FSUIPC SDK from http://www.schiratti.com/dowson. Regards, Pete

Delete the FSUIPC.KEY file in the FS Modules folder. I bet it will work then! The difference between 3.40 and later versions is that illegally made FSUIPC keys cause exactly the sort of problems you have found. If you believe your FSUIPC registration is good, send the details to me at petedowson@btconnect.com. If you disagree with any of this, check the FSUIPC.LOG. Run FS and the "traffic view board" or whatever it is, then close FS. Show me the LOG file from the FS Modules folder. Regards, Pete

Something else is wrong then. FSUIPC simply isn't doing anything until and unless it is asked to do so. What programs or add-ons are using it? (Why did you install it?). There are also some by now well known reasons for this -- one is a bug in an earlier version of FSNav. If you have FSNav installed, check that you have the latest update for it. Active Camera also needs an update for FS9.1. There may be others. Regards, Pete

Well, not deliberately sarcastic, more completely and absolutely frustrated because I cannot explain any better how to find the Announcements. They stare you in the face at the top of the forum every time you come here! I cannot understand how you manage to get to see my replies! How do you do that? Tell me how you managed to enter a message here and see my replies, yet still cannot see the list of messages from which to choose? Is this a sort of selective sight resulting from autism? If I understood that then perhaps I could help further! I really cannot see how to help unless I can understand what you are seeing so differently from every one else who visits here. The instructions to get yourself flying were nothing to do with finding a simple announcement. I only referred to the announcements because it is those which tell you what versions of the programs to use. If you know how to find out that simple information then you'd never have the same sort of problem again, so it is my way of helping you work out how to solve your own problems from then on. The only thing you need to do to fly in FS9.1 with FSUIPC is go get the latest FSUIPC from http://www.schiratti.com/dowson and install it into the FS modules folder. This is what I said several days (?) ago, thus: Regards, Pete

Oh dear, this is a first! How can you not see the list of messages in this Forum? How do you find my message in order to reply to it? :roll: I said "Top of this Forum", meaning the first few threads in this Forum. Exit this message and look up the list of messages until you reach the very top. The first three are Announcements and the next four are Sticky -- they are clearly labelled as such in Bold. In particular the third announcement is: Announcement: List of current supported versions [25th April 2005] and this is the one I referred you to, just to find out that the current version of FSUIPC is 3.48! :cry: Pete

That's a real puzzle then. I'm sorry, but I think you have to look to the software in the PDA. Did you prove to yourself that the FS PC end was still sending? That is easy enough with PortMon. No. My abbreviation "RMC" stands for "GPRMC". The GP ones are all the standard NMEA-defined ones -- I just left off the standard "GP" part in the parameter definition for the INI file. The "PGRMZ" one stands for "Proprietary Garmin sentence Z". I don't know the prefixes PFSR, LXWP and so on, only the GP ones and a few of the Garmin ones. Regards, Pete

No, sorry. It is unlikely to be stopping from the FS PC end -- there's no flow control in GPSout, it simply keeps sending stuff. You can check that with "portmon" (a free utility obtainable from http://www.systeminternals.com). Run it before FS. Maybe there's some restriction in the PDA software? What sentences are you selecting in GPSout? If you have too many selected 1 second may not be enough time between them. The 4800 speed works out to 480 characters per second max. You need a good gap between them, so say 400. With an average sentence length of perhaps 60-80 characters that only allows 6-8 different ones. Even then things might get clogged up in the PDA. Try (1) increasing the time from 1000 to 2000 or more, and/or (2) only one or two sentences at a time. Do you know which sentences your software is expecting and needing? Regards, Pete

1. Please turn your Caps Lock off! 2. This IS the Forum! :roll: You are IN the Forum to read my messages and send yours. How else are you doing it? Look up the list of messages and you will see Announcements and other special items of useful information ("Stickies") at the top. Pete

Yes, as per the Read.Me from Microsoft (!) you need to update your very old copy of FSUIPC. Please refer to the announcements at the top of this forum for details of current supported releases. Yours pre-dates the release of the FS9.1 update last September! ("40901" = 1st September 2004, "30612" = 12th June 2003, the original FS2004 release). Regards, Pete

I don't think those signal lines can do that. If they are the wrong way round nothing gets transferred, that's all. Regards, Pete

All that means is that, at the time you looked, the incoming throttle value for FS was 8255 and, because you are not calibrating the throttle in FSUIPC, it is going straight through to FS unchanged, i.e. as 8255. If you move the lever then both values will (should) change -- but they will be the same unless you elect to calibrate in FSUIPC. Again, that's just one value. As you move the throttle lever the values must change -- if they don't the lever isn't working! The values should run through many different values. The 16380 value is just a maximum default used in FSUIPC. Why don't you try calibrating the throttle in FSUIPC? It isn't actually doing anything at all at present. All you are looking at are the values of the throttle figures as they pass through FSUIPC unchanged. Regards, Pete

Just enter ALL three parts of the registration as before. You are making a mistake somewhere. If you kept your FSUIPC.KEY file you could cut and paste from there, or else use the details as originally notified. Regards, Pete

Same place as the programs themselves, inside the exact same ZIP package. Go to http://www.schiratti.com/dowson and download FSUIPC.ZIP and WideFS.ZIP. Regards, Pete