• Welcome to Theos PowerBasic Museum 2017.

x-IMU API#

Started by Vladimir Shulakov, June 07, 2011, 09:17:14 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Vladimir Shulakov

Hi,

I need to attach x-IMU dll for PB app. (I need to test x-IMU trackir device). It have x-IMU API:
http://www.x-io.co.uk/node/9 in C#, XML API

It use xIMU_API.DLL and API like this:



<?xml version="1.0"?>
<doc>
    <assembly>
        <name>xIMU_API</name>
    </assembly>
    <members>
        <member name="T:xIMU_API.AsyncReadCompletedEventArgs">
            <summary>
            Asynchronous read completed event arguments class.
            </summary>
        </member>
        <!-- Badly formed XML comment ignored for member "M:xIMU_API.AsyncReadCompletedEventArgs.#ctor(xIMU_API.PacketCount,System.Exception,System.Boolean)" -->
        <member name="P:xIMU_API.AsyncReadCompletedEventArgs.PacketCounter">
            <summary>
            Gets <see cref="T:xIMU_API.PacketCount"/> data of read.
            </summary>
        </member>
        <member name="P:xIMU_API.AsyncReadCompletedEventArgs.Error">
            <summary>
            Gets error <see cref="T:System.Exception"/> if occured.
            </summary>
        </member>
        <member name="P:xIMU_API.AsyncReadCompletedEventArgs.Cancelled">
            <summary>
            Gets a value indicating whether the asynchronous scan was cancelled.
            </summary>
        </member>
        <member name="T:xIMU_API.CompatibleFirmwareVersions">
            <summary>
            Compatible firmware versions.  Only major number required.
            </summary>
        </member>
        <member name="T:xIMU_API.PacketHeaders">
            <summary>
            Packet headers.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>
        <member name="T:xIMU_API.ErrorCodes">
            <summary>
            Error codes.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>
        <member name="T:xIMU_API.CommandCodes">
            <summary>
            Command codes.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>
        <member name="T:xIMU_API.Qvals">
            <summary>
            Number of fractional bits used by fixed-point representations.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>
        <member name="T:xIMU_API.RegisterAddresses">
            <summary>
            Register addresses.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>
        <member name="T:xIMU_API.ButtonModes">
            <summary>
            Button mode register values.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>
        <member name="T:xIMU_API.AccelerometerFullScales">
            <summary>
            Accelerometer full-scale register values.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>
        <member name="T:xIMU_API.MagnetometerFullScales">
            <summary>
            Magnetometer full-scale register values.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>
        <member name="T:xIMU_API.AlgorithmModes">
            <summary>
            Algorithm mode register values.
            </summary>
            <remarks>
            A matching enumeration exists in firmware source.
            </remarks>
        </member>


...


Earlier, I have attached successfully a different "trackir" devices via COM or *.h headers API.
But XML API for PB app is incomprehensible.

Maybe, anybody has an experience with it ?

Any ideas?

Regards,
Vladimir


José Roca

It is not an standard DLL, but a .NET assembly.