I2C not initializing

speed3724 · November 19, 2013, 6:06pm

Recently, my team has been having trouble with the integrated motor encoders. We have never had problems up until a few weeks ago, but now the IEM’s wont initialize. We have four encoders chained together, all of which are displaying a solid orange color. We have already tried re-wiring the chain to see if that was the problem, but nothing. We know the encoders work because they were working properly a few weeks ago. We are also running the latest version of RobotC.

Here’s the configuration of our encoders:

#pragma config(I2C_Usage, #pragma config(Sensor, in1, #pragma config(Sensor, in2, #pragma config(Sensor, in3, #pragma config(Sensor, in4, #pragma config(Sensor, in5, #pragma config(Sensor, in6, #pragma config(Sensor, in7, #pragma config(Sensor, in8, #pragma config(Sensor, dgtl1, ArmRight, #pragma config(Sensor, dgtl3, ArmLeft, #pragma config(Sensor, dgtl5, #pragma config(Sensor, dgtl7, #pragma config(Sensor, dgtl9, #pragma config(Sensor, #pragma config(Sensor, I2C_1, DLBIEM, #pragma config(Sensor, I2C_2, LLFIEM, #pragma config(Sensor, I2C_3, LRFIEM, #pragma config(Sensor, I2C_4, DRBIEM, #pragma config(Motor, port1, #pragma config(Motor, port2, #pragma config(Motor, port3, #pragma config(Motor, port4, #pragma config(Motor, port5, #pragma config(Motor, port6, #pragma config(Motor, port7, #pragma config(Motor, port8, #pragma config(Motor, port9, #pragma config(Motor, port10, //!!Code automatically generated by ‘ROBOTC’ configuration wizard I2C1, i2cSensors)
PowerExpander, sensorAnalog)
RightLineFollower, sensorLineFollower)
MiddleLineFollower, sensorLineFollower)
LeftLineFollower, sensorLineFollower)
Gyroscope, sensorGyro)
XAccelerometer, sensorAccelerometer)
YAccelerometer, sensorAccelerometer)
ZAccelerometer, sensorAccelerometer)
sensorQuadEncoder)
sensorQuadEncoder)
SonarLeft, sensorSONAR_inch)
SonarRight, sensorSONAR_inch)
RightPushButton, sensorTouch)
dgtl10, LeftPushButton, sensorTouch)
sensorQuadEncoderOnI2CPort, , AutoAssign)
sensorQuadEncoderOnI2CPort, , AutoAssign)
sensorQuadEncoderOnI2CPort, , AutoAssign)
sensorQuadEncoderOnI2CPort, , AutoAssign)
IntakeLeft, tmotorVex393, openLoop)
DriveRightBack, tmotorVex393, openLoop, encoder, encoderPort, I2C_4, 1000)
DriveLeftBack, tmotorVex393, openLoop, reversed, encoder, encoderPort, I2C_1, 1000)
DriveRightFront, tmotorVex393, openLoop)
DriveLeftFront, tmotorVex393, openLoop, reversed)
LiftRightFront, tmotorVex269, openLoop, encoder, encoderPort, I2C_3, 1000)
LiftRightBack, tmotorVex269, openLoop)
LiftLeftFront, tmotorVex269, openLoop, reversed, encoder, encoderPort, I2C_2, 1000)
LiftLeftBack, tmotorVex269, openLoop, reversed)
IntakeRight, tmotorVex393, openLoop, reversed)
!!//

Any suggestions on what we may be doing wrong or how to initialize the encoders?

corey-ifi · January 15, 2014, 1:12pm

Your ROBOTC configuration looks okay.

To debug the software and hardware, try changing the Configuration software to just one Integrated Encoder and connect just one Integrated Encoder to the Cortex’s I2C port. Verify the cable is not in the UART1 or UART2 port. If one Integrated Encoder works, add a second Integrated Encoder and wiring and software, etc. If the first Encoder and wiring does not work, try a different Integrated Encoder and cable. If neither work, try a different Cortex. If you still have issues, please contact VEX Tech Support at 903-453-0802.

-Corey