Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Peter,

I'm trying to get a couple of Rotaries to talk to PM MCP via EPICINFO and the MCP_xxx_VAR variables.

I have set up two virtual Axes Z and Rx on what I think is windows joystick 3. It is the 4th joystick to appear in the windows list.

I have added the lines MCP_HDG_VAR=3,3 and MCP_ALT_VAR=3,4 to

the EPICINFO.cfg file.

The values show correctly for each of the joystick axes when

I calibrate them in windows.

However I get no response from the PM MCP and the EpicInfo.log shows this at the end :

***********************************************************

550093 AxisAction 'MCP_HDG_VAR' actioned: J3,2, was=0014, now=0013

550093 AxisAction 'MCP_ALT_VAR' actioned: J3,3, was=0001, now=0002

550984 AxisAction 'MCP_ALT_VAR' actioned: J3,3, was=0002, now=0001

560797 Joy 3 for Axes got error 167!

560859 Joy 3 Axes okay now 0!

570500 AxisAction 'MCP_HDG_VAR' actioned: J3,2, was=0013, now=0014

570500 AxisAction 'MCP_ALT_VAR' actioned: J3,3, was=0001, now=0002

570625 AxisAction 'MCP_ALT_VAR' actioned: J3,3, was=0002, now=0001

585140 Joy 3 for Axes got error 167!

585203 Joy 3 Axes okay now 0!

*********************************************************

Got any idea what's going wrong ? What is the error 167 ?

Hope you can help,

Posted

I'm trying to get a couple of Rotaries to talk to PM MCP via EPICINFO and the MCP_xxx_VAR variables.

Phew! I had to dig out my EPICINFO document just to understand what you were talking about. I'm sorry, but I haven't used EPIC for several years.

I have set up two virtual Axes Z and Rx on what I think is windows joystick 3. It is the 4th joystick to appear in the windows list.

Hmmm. That doesn't necessarily follow I'm afraid. I seem to recall I never knew how to identify them exactly except by trial and error. I did once actually edit the Registry, giving each of the EPIC joysticks a different name, so I could tell. That worked for a while, but it is very messy and dangerous to do. I did ask Ralph Robinson (R&R) if he couldn't install them all with different names, but I don't think he ever got around to it.

However I get no response from the PM MCP and the EpicInfo.log shows this at the end :

Well, this shows something changing, slightly, in the axes. Not enough to notice I suppose. Random jitter perhaps?

Got any idea what's going wrong ? What is the error 167 ?

According to my Microsoft jostick API refernces it means "joystick unplugged".

Most likely thing is that you've got the wrong joystick number. Try using the JoyView program (from Thrustmaster) -- if you can find it still. If not, I may have it buried somewhere in my archives. It has always proven very useful when trying to sort EPIC axes and things out.

You can monitor what's being changed in the PM MCP using FSUIPC's Monitor facilities. The offsets you need to monitor are listed in the PM offsets document (on the PM documentation site). They are all 16 bit words (U16 or S16) at offset 5406 onwards.

Regards,

Pete

Posted

With regard to joystick errors reported in the EPICINFO.log file, could you tell me what error 165 signifies please ?

I'll have to go search the Microsoft documentation again. Hang on, I'll give you the whole list:

JOYERR_PARMS 165 bad parameters

JOYERR_NOCANDO 166 request not completed

JOYERR_UNPLUGGED 167 joystick is unplugged

That's all that appears to be listed. Looking up their meanings further only gives:

165 = The specified joystick identifier is invalid.

166 no other mention? Presumably a timeout someplace.

167 = The specified joystick is not connected to the system.

Regards,

Pete

Posted

Oooh ! Sounds pretty grim.

Sounds like a job for Ralph Richardson this one!

Thanks for the whole list.... Couldn't find it on the web.

Maybe I blinked whilst I was searching.

Thanks anyway Pete.

cheers

Rick

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.