3.81

[mounty]

Hi Peter,

I am having a couple of problems with using the PMDG 737 macros. I am using a Hagstrom Keyboard Emulator so program FSUIPC with macro keypresses.

What is happening is that for example with the APU Gen 1 & 2 and Eng. Gen 1 & 2 I am using a three position switch - ON/OFF/ON (and only using the center - OFF and one ON pole), and I programme FSUIPC with the Gen ON when pressed and Gen Off when released. This works in that when I use the switch, the on position works the mom switch in PMDG and if I leave the hardware switch in the on position for more than a minute or so, when I switch it off, the PMDG switch does not go to off. If I use the switch within a minute or so, the PMDG switch works correctly.

Also when programming the same switches, FSUIPC does not hold the release part of the macro after exiting FS. I have to reprogram the release side of the macro everytime I reload FS.

I am using a single line code for programming the Hagstrom so that only the press is commanded.

Any help would be greatly appreciated.

Many Thanks

Rob

[Pete Dowson]

What is happening is that for example with the APU Gen 1 & 2 and Eng. Gen 1 & 2 I am using a three position switch - ON/OFF/ON (and only using the center - OFF and one ON pole), and I programme FSUIPC with the Gen ON when pressed and Gen Off when released. This works in that when I use the switch, the on position works the mom switch in PMDG and if I leave the hardware switch in the on position for more than a minute or so, when I switch it off, the PMDG switch does not go to off. If I use the switch within a minute or so, the PMDG switch works correctly.

Sorry, I've no idea what is happening there. I need more information. I have absolutely no idea how a "Hagstrom Keyboard Emulator" works at all.

Since all of the "Keys" assignment facilities in FSUIPC work operate using standard Windows keyboard messaging, please verify what you are assigning these keys to do using a real keyboard first. Let's eliminate the encoder, as if that is behaving differently to a real keyboard you will then need to find out why and presumably deal with Hagstrom support.

Note that there is absolutely no time-related code in FSUIPC regarding how keys are interpreted. The nearest there is would be a little check to prevent FSUIPC sending repeated controls to FS (or in the case of Mouse macros, to a Gauge) faster than they can accept them, generally the frame rate. But that's in terms of milliseconds, so nowhere near your minute -- such a delay there must surely be something to do with the way the encoder is operating.

Also when programming the same switches, FSUIPC does not hold the release part of the macro after exiting FS. I have to reprogram the release side of the macro everytime I reload FS.

Erif you "confirm" the result, it is written to the INI file on OK exit from the Options screen. Please check the INI file. Of course, if you have that set as read-only it will not remember anything, but that sounds pretty unlikely.

I am using a single line code for programming the Hagstrom so that only the press is commanded.

That sounds bad. That presumably would mean Windows only sends me a KEYDOWN message. If there's never a KEYUP message then it cannot see the next KEYDOWN as a new press. It would be the same as having a Key stuck down on your real keyboard. Surely no keyboard emulator should ever leave keys pressed forever? Maybe your "minute" timeout is a safety feature on the Hagstrom to prevent such "stuck" keys?

Any help would be greatly appreciated.

Please try to help yourself first. Two things to do:

1. Program and test everything using a real keyboard only. Only then check it on your encoder. I cannot deal with differences from the way a real keyboard is handled through Windows.

2. Use the Buttons and Keys, and probably also the Event logging facilities in FSUIPC -- see the Logging tab. You can try things and examine the log directly afterwards to see what it happening. (In fact, if you download DebugView from http://www.sysinternals.com , and run it before running FS, you can view the Log in real time, provided you run FS in Windowed mode so you can see the DebugView window).

If you still have problems, or need help interpreting the log, show me. Also show me the relevant Keys section from the FSUIPC.INI file.

Regards

Pete

[mounty]

Hi Peter,

Thanks for your quick response.

When I program FSUIPC I do it from a real keyboard. The Hagstrom Emulator is something like Leo Bodnars BU0836X card, it is just the interface, between the hardware switch and FSUIPC - it converts the switch signal to a set of programmed keypresses. For example the Gen 1 switch is programmed with A as the keypress both in the Hagstrom Emulator and FSUIPC. When I press the switch on, the Hagstrom sends the appropriate A keypress. I am not sure how to find the INI file as there are only files such as FSUIPC.DLL, FSUIPC x 2 files (Config Settings and a text doc), FSUIPC 1. I have set the APU and Eng Gens to both an ON and OFF setting in FSUIPC. However as I said before it doesn't appear to hold the OFF settings aven after I have confirmed the settings it omits them whenever I shut down FS and I have to re-enter them.

The Hagstrom doesn't have any time or safety limits. Before I used 3.81, I was using the Key2Mouse for the overhead and never had the problems I'm having now. I have used the previous FSUIPC version using the Hagstrom without any problems that I can recall.

I have tried to attach the above files but it won't allow me to do so. Is there another address that I can send these files to? I do not understand any of the file content so I cannot help you and I cannot open the INI file as it is an application.

I am thinking of uninstalling FSUIPC and reinstalling it to see if that makes a difference - what's your opinion on trying that?

Many Thanks

Rob

[Pete Dowson]

When I program FSUIPC I do it from a real keyboard.

But do you actually TEST from a real keyboard too? That's the main point.

I am not sure how to find the INI file as there are only files such as FSUIPC.DLL, FSUIPC x 2 files (Config Settings and a text doc), FSUIPC 1.

Those are NOT filenames. You have Windows set to hide real filenames from you! The "Text" document is probably the Log, and the Config file is probably the INI file. There will also be a KEY file with your Registrations: I've no idea how Windows calls that these days. Probably a Settings (confusing it with Registry files).You are supposed to understand that if you have Windows annoyingly converting filenames into its "standard" descriptions!

I have set the APU and Eng Gens to both an ON and OFF setting in FSUIPC. However as I said before it doesn't appear to hold the OFF settings aven after I have confirmed the settings it omits them whenever I shut down FS and I have to re-enter them.

That's why I suggested you check the INI file. There is no way I have any settings being lost here. Something is not right on your setup.

And 3.81 is now out of date. Please download and install 3.82.

The Hagstrom doesn't have any time or safety limits. Before I used 3.81, I was using the Key2Mouse for the overhead and never had the problems I'm having now. I have used the previous FSUIPC version using the Hagstrom without any problems that I can recall.

What previous version had any Mouse Macros? Sorry, this is all meaningless.

Unless you can help me by providing meaningful information, like Logs and INI files, I cannot help you any further. Switch on Buttons and Keys logging (only!) in the Logging tab. And check the INI, as I said.

I have tried to attach the above files but it won't allow me to do so.

Don't attach files. If you do short tests they will be relatively short Text files, both the LOG and INI. You can paste them here. If the files get large I'll give you an email address to send them, but they should not be for some simply Key tests (using the Keyboard).

Is there another address that I can send these files to? I do not understand any of the file content so I cannot help you and I cannot open the INI file as it is an application.

The INI file is most certainly NOT an application, but a normal Text file, like any other standard Windows CFG, INI or settings file. It can be opended in Notepad or any text editor.

I am thinking of uninstalling FSUIPC and reinstalling it to see if that makes a difference - what's your opinion on trying that?

Since "uninstalling" consists of deleting the FSUIPC.DLL, and re-installing consists of putting it back again, it can make not a blind bit of difference. You could delete the INI file (with FS not running) so it reverts to defaults, then start again, if you feel you made some incomprehensible mess somewhere.

I am away from tomorrow morning until late Monday (a long weekend visiting my daughter), so this may have to continue next week.

Pete

[mounty]

Hi Peter,

I have checked FSUIPC and then loaded version 3.82. Deleted the INI file and started over. I programmed a Go Flight switch which was done in the Button Press and seen as a joystick button. Both the On and Off on the APU Generator worked and when I exited and restarted FS, both selections showed up. It looks like the problem might be with the Hagstrom Keyboard Emulator. I have ordered the BU0836X boards from Leo Bodnar so when I wire all the switches, they will show up as joystick buttons.

Problem solved!!!

Many Thanks

Rob