Wild Thumper T'Rex and ROS

Forum to discuss experiences @ryan

Overview of project

I am interested in finding out what your hardware and software stack is at the moment.

For me, I am using the T’Rex controller with an RPi 1 (model b) as an i2c master, and am working on writing a ROS publisher to send the i2c status data, and a subscriber to receive messages from roslibjs for a web frontend to control the bot. I have been encountering issues with the RPi however, namely with it’s inability to handle repeated start transactions, and am curious if you have encountered the same issue. My longer term solution is likely to ditch the RPi in favor of the odroid-c1+ as it is just an all around better controller for my needs – but I am curious if you found a software fix. (See https://www.robotshop.com/letsmakerobots/trex-controller-i2c-status-request-raspberrypi-master-triggers-shutdown for details)

 

 

I don’t think that the
I don’t think that the Odroid-C1 has that much advantage over an RPi 2.

The ODroid has IIFC three pins for analog input.

I have a different Odroid, but I’ve never tested I2C on this board.

The RPi2 suffers from the

The RPi2 suffers from the same repeated start transactions issue. I don’t really know if odroid will solve that speciifc issue, but the CPU is better performing with similar power consumption. But the analog input is also a nice bonus not available on the RPi.

i am currenty using a T’Rex

i am currenty using a T’Rex controller with  RPi 2 model B. I started off with the Pi 1. I never had any issues with the raspberry pi, I dont really know what you mean when you say repeated start transactions. The only issues I had with the Pi was OS debian and installing all the relavent packages and dependencies. Sorry theres not much help I can give as I used a USB interface for the controller to the raspberry Pi. I never used I2C as I had no experience with it.

 

I would suggest you make an account with ROS Answers and post a detailed question there. They are really helpful if the question is clear. Alterntively look on Github for the issue you are facing.

Would you be willing to

Would you be willing to share the i2c master code you used on the RPi?

I never used I2C, i plugged

I never used I2C, i plugged the controller straight into the raspberry pi and used serial communication?