Problem with axis assignement

[nauwa]

Hi Pete,

I'm trying to assign an axis to "send to FSUIPC offset". The axis is connected to a Leo Bodnar joystick interface.

I assign the axis to Offset x66E5 as a word. In the FSUIPC Axis assignment tab everything looks good, moving the axis gives me values from -16383 to +16383, but when I read offset x66E5 I get nothing. Well, i do get some glitches near middle of the axis.

The most strange thing is that it worked perfect for a few minutes in the beginning, but then died without me doing anything.

The hardware is working, perfect stable values from the potentiometer, and I still get perfect values in the "Axis assignment tab", but on the Offset, nothing.

FSUIPC version 4.868

Running SIOC version 4.3 on networked computer via WideFS 6.991 where I try to read offset x66E5

Do you have any idéas?

Regards

Johan

[Pete Dowson]

I'm trying to assign an axis to "send to FSUIPC offset". The axis is connected to a Leo Bodnar joystick interface.

I assign the axis to Offset x66E5 as a word. In the FSUIPC Axis assignment tab everything looks good, moving the axis gives me values from -16383 to +16383, but when I read offset x66E5 I get nothing. Well, i do get some glitches near middle of the axis.

Have you tried using FSUIPC's logging to check what is going on? Monitor offset 66E5 as type S16. You could also set Axis event logging on, and, before loading FS set this in the [General] section of the INI:

Debug=Please

This allows you to set numberical options in the "Extras" edit box in the Logging tab. Set 9 there and it will log the incoming axis value too.

What exact FSUIPC control are you using? Maybe you could show me the [Axes] section from the INI?

Running SIOC version 4.3 on networked computer via WideFS 6.991 where I try to read offset x66E5

I don't know SIOC. Apart from using the Monitor log to check it on the FS PC you can use FSInterrogate (from the SDK) to check it on the client. Is it possibly that SIOC doesn't like WORD (2-byte) values on an odd byte boundary?

Pete

[nauwa]

Thanks for the fast reply Pete!

Well I fired it up today to try to log some data for you, but to my surprise everything worked OK, for a while, then it started to send 65536 or 0, nothing between.

Restarted both computers and tried again. At first all OK, but after about 30 minutes I lost all data on the offset, only receiving 0, no matter how I turn my potentiometer.

Really strange behaviour. I'll continue to test and will log next attempt.

Regards

Johan

[Pete Dowson]

Well I fired it up today to try to log some data for you, but to my surprise everything worked OK, for a while, then it started to send 65536 or 0, nothing between.

Restarted both computers and tried again. At first all OK, but after about 30 minutes I lost all data on the offset, only receiving 0, no matter how I turn my potentiometer.

Really strange behaviour

It sounds like it must be a hardware or wiring problem. Maybe power? How is it connected?

The software isn't going to be deteriorating in any way.

Regards

Pete

[nauwa]

I doubt it would be a hardware problem as when I look at the "axis assignment tab" in FSUIPC, it still works giving me perfect values from -16383 to + 16383, it just don't send it to the offset (or I can't read it from the offset). It might be on the SIOC side, but I don't see the difference from the other offsets I read from FSX via FSUIPC that continues to work when the offset from the axis don't

Well, I'll try more tomorrow with logging ON.

Regards

Johan

[Pete Dowson]

I doubt it would be a hardware problem as when I look at the "axis assignment tab" in FSUIPC, it still works giving me perfect values from -16383 to + 16383, it just don't send it to the offset (or I can't read it from the offset).

Ah, when you said it was varying strangely I assumed you meant when looking directly in the assignments tab.

It might be on the SIOC side, but I don't see the difference from the other offsets I read from FSX via FSUIPC that continues to work when the offset from the axis don't

You need to double check at the SIOC end using FSInterrogate, and at the FS end using the Monitoring facility, as I suggested. It's a waste of time repeatedly talking about odd things happening with no actual information. And as I said, it isn't the software "deteriorating" so it must be related to the link or SIOC. But the checking I suggested will confirm or deny this.

Pete