Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[DeltaSim]

Hi,

I am currently trying to get my joystic controller to talk to the plane in Outerra. Everything works fine, I just need to re-calibrate before I start. However, I need to do this every time I start Outerra, the calibration data doesn't seem to be stored anywhere. I am using the standard Microsoft driver. Can you help me here?

Cheers, Martin

[cameni]

The calibration data are stored in data directory, in the "devs" folder. Please check if it got created, and attach your eng.log here.

[DeltaSim]

Thanks for the quick reply! I looked at the calibration file and it is there. However, I don't understand what you mean by "attaching" the eng.log there. But I ran into something else: The calibration file says that my joystick has no axes...

product_name = "BU0836 Interface",
vendor_id = 5824,
product_id = 1461,
version_number = 290,

**num_axes = 0,**

num_pots = 1,
num_buttons = 32,
usage_page = 1,
usage = 4,

I'm afraid I didn't quite get it yet...

[cameni]

I didn't want you to attach the eng.log there, but to attach the file to the post here when replying, so we can inspect it

But num axes 0? Looks it doesn't report its capabilities correctly. What kind of joystick it is?

[DeltaSim]

I already thought there would be something very basic that I didn't get...

I attached the log file now, plus the cal. file. The joystik I am using is actually an A/D converter that pretends to be one (http://www.leobodnar.com/products/BU0836/). I use it to feed my force sensor data into JSBSim. It has no driver of it's own. How can I check, whether it reports its capabilities correctly?

[cameni]

Hmm, the log now says something else:

Code: [Select]

INFO: input device: BU0836 Interface
        device: INDEV_HID0
        handle: 1ead0555
        num axis: 2
        num pots: 1
        usage page: 1
        usage: 4
        vendor id: 16c0
        product id: 5b5
        device id: 884663A2DA60756DC3B74846D045B5CE102B5846
        version number: 290
        num buttons: 32
...

Does it change each run?

[DeltaSim]

It stays the same. Here's what I get when I re-run Outerra and close it without calibration:

        device: INDEV_HID0
        handle: 6010d
        num axis: 2
        num pots: 1
        usage page: 1
        usage: 4
        vendor id: 16c0
        product id: 5b5
        device id: 884663A2DA60756DC3B74846D045B5CE102B5846
        version number: 290
        num buttons: 32

[cameni]

How many A/D inputs you are actually using with it?

[DeltaSim]

Right now, I use the first two. The device has however 8 A/D channels.

[cameni]

So it seems to report only the used ones. But apparently it reported 0 before.

Try to delete the devs folder, it's possible it contains a configuration from the time it reported 0 axes, and that doesn't store the calibration data.
Then run the app, calibrate, then exit and check if eng.log reported 2 axes, and if the calibration was preserved in the next run.

[DeltaSim]

I tried it, the log also reports 2 axes. Without calibration the controls are weak (obviusly scaled down), with cal. it's all OK. However, no calibration file is created anymore. Hence I still have to re-calibrate each run.

[cameni]

It should be created at the exit, after you have clicked to calibrate.
Does eng.log contain anything about the writing of the configuration file not being successful?

[DeltaSim]

Not that I found anything. I attached the log file, though. What I did find was the message that it didn't find the confi. file:

INFO: Device configuration file "C:\Users\Martin\Outerra\devs\884663A2DA60756DC3B74846D045B5CE102B5846.cfg" not found using default!

[cameni]

Ok, I'll have to extend the log to indicate when there's a problem.

One more thing - please try to create an empty "devs" dir there, and check if it creates the file now.

[DeltaSim]

Doesn't work either. I am just trying to remember what I did differently yesterday, that the confi. file could be written  .