AP_SPD_VAR_SET in epicinfo.cfg

[joeymars]

I'm having problems trying to send values from epic to fs using virtual axes. I've debugged the joystick values and they're accurate. My epicinfo.cfg looks like the following. Any info is greatly appreciated.

[All]

ReSend=0

Log=3

AxisReads=Both

AP_SPD_VAR_SET=P0

HEADING_BUG_SET=P1

[Default]

Sets=CP,MCP,TR1,KR1,NAV

;Sets=All

Thank you,

Sam Llorca

[Pete Dowson]

I'm having problems trying to send values from epic to fs using virtual axes. I've debugged the joystick values and they're accurate. My epicinfo.cfg looks like the following.

I don't know what you mean when you say you've "debugged the joystick values".

Values "Px" are not virtual axes, in the sense I understand, but POVs ("Points Of View" controls).

You don't say whether you are using FS98, FS2000, FS2002 or FS2004.

You don't say whether you are using ISA EPIC or USB EPIC.

I also need the EPICINFO version number, and the FSUIPC version number.

But first, please help yourself by using the logging facilities in EPICINFO as documented. The log should show you what is going on.

Regards,

Pete

[joeymars]

FS2004

EPIC USB

EPICINFO 4.22

FSUIPC 3.1.3.5 (registered)

By debuging values, i mean i've read the raw data from the directx axis.

I've set the pov values from EPL. I've also tried virtual axis X4-Z4, which i understand is Joystick 5.

----

I've looking in the log file and i found the following error.

167313 Joy 0 for DisAxes got error 167!

167313 Joy 0 for DisAxes okay now

How does the log ouput a change in the Axis Value?

I've also tried

FSUIPC_WRITE_1=X4,1,07E2

Thank you,

Sam Llorca

[Pete Dowson]

By debuging values, i mean i've read the raw data from the directx axis.

Where and how? Sorry, the terms "raw" and "directx" don't really go together as far as I've found.

I've also tried virtual axis X4-Z4, which i understand is Joystick 5.

Depends whether you count from 0 or 1. :)

I've looking in the log file and i found the following error.

167313 Joy 0 for DisAxes got error 167!

167313 Joy 0 for DisAxes okay now

That's an error returned by EPICIO.DLL (part of the USB Epic package), but as it corrected itself immediately afterwards I wouldn't worry about it. Maybe it's an initialisation state.

How does the log ouput a change in the Axis Value?

It logs the axes and the values. With Log=3 if changes were seen on your programmed axes at all they'd be logged. If there's nothing like that in the log then the changes aren't being seen. I noticed you have "AxisReads=Both", so it seems the changes aren't getting through either the Windows route or the EPICIO.DLL routine.

I really think you'll need to check things with the EPIC folks, unless someone else here can jump in. It sounds like something related to the way you've defined things in the EPL, but I'm afraid I get puzzled by all that stuff too. I've not programmed EPIC seriously since the new EPL was invented.

Regards,

Pete