What more information on RIO

I'm thinking of purchasing the RIO w/AHRS.
My questions are:

-When connecting the RIO board to the Pi, Does the Pi have to be configured in some way?
-If the RIO is connected to a motor controller How many inputs/outputs are free for sensors.
also, can the RIO?
-Can the RIO programming perform all function to an robot for autonomous or does the Pi programming perform all the functions?

The datasheet contains the pinout connections and software installation to make your Pi work with our Rio boards.

dev.roboteq.com/dev1/index.php/products/...ters/rio-ahrs-detail

Do you all have any code examples for RIO & Pi?

If I was to purchase the RIO, Is there support for the software to configure it?

We will support the library needed to talk to the I/O on the board. For general programming and Linux
question, you will have to go to Raspberry PI forums.

I have the RIO running and delivering AHRS information to the RPI. Is there documentation somewhere on how to interpret the AHRS data in terms of units of measure and/or conversion to standard scales? Alternatively, can the component(s) for this function be disclosed so that we can lookup the datasheets ourselves if necessary?

Thanks!

@talgbal
I'm thinking about purchasing the RIO. But I don't have a lot of details about it.
Can you give me some insight? Such as Does the Pi have to be programmed in some way? How is the RIO board itself programmed?
if I purchase it I would like to connect it to the controller and program it for a robot.

The datasheet is good in terms of basic information. I wasn't able to open it on the site for some reason, but I was able to download it and then open it.

dev.roboteq.com/dev1/index.php/docman/ri...1-rio-datasheet/file

Roboteq supplies a c library and test programs that run on the Pi and access the RIO data. It was fairly easy to get that part going. The basic architecture is that the Pi runs a daemon, also supplied by Roboteq, that constantly updates a memory map on the Pi with data from/to the RIO. The functions in the library interact with the shared memory and your app on the Pi, and the daemon interacts with the shared memory and the RIO. Note that the latency between the Pi memory map and the actual pins on the RIO can be about 2ms.

Alternatively, the RIO can be accessed via various serial ports using command sequences similar (conceptually) to the ones used with Roboteq motor controllers. The RIO also supports Roboteq Microbasic, however I find the documentation less than adequate for that unless I've missed something. There does not seem to be a user manual for the RIO, but I hope I've just not found it yet. The best way to program the RIO in microbasic is using the PC config utility on a separate computer connected to the serial port exposed on the 40 pin connector on the RIO. Of course, the microbasic program can be flashed onto the RIO and made to run at startup. At that point, the PC is no longer required, and you can further interact with the RIO from the Pi.

Thank you for your reply. That kinda put things in prospective.

As of current, the datasheet is the only piece of documentation we have available. We do have a small video in the resources tab in the link below just after the block diagram..

dev.roboteq.com/dev1/index.php/products/...hrs-detail#resources