History

Working default tip

2015-03-25, by tntmarket [Wed, 25 Mar 2015 18:11:09 +0000] rev 11

Working

running out of RAM?

2015-03-25, by tntmarket [Wed, 25 Mar 2015 16:36:11 +0000] rev 10

running out of RAM?

Working except for actuator

2015-03-25, by tntmarket [Wed, 25 Mar 2015 14:34:23 +0000] rev 9

Working except for actuator

lift folders

2015-03-25, by tntmarket [Wed, 25 Mar 2015 11:44:05 +0000] rev 8

lift folders

remove dead code

2015-03-25, by tntmarket [Wed, 25 Mar 2015 11:41:22 +0000] rev 7

remove dead code

Kill dead code

2015-03-25, by tntmarket [Wed, 25 Mar 2015 11:40:32 +0000] rev 6

Kill dead code

only imu output

2015-03-25, by tntmarket [Wed, 25 Mar 2015 09:58:50 +0000] rev 5

only imu output

BOTH IMUs WORK NOW. Put them in separate threads. Servo is included.

2015-03-22, by majik [Sun, 22 Mar 2015 06:34:30 +0000] rev 4

BOTH IMUs WORK NOW. Put them in separate threads. Servo is included.

1 IMU, Servo added; -PTD0 is used by something mysterious, so I had to move the servo control line to PTA12

2015-03-22, by majik [Sun, 22 Mar 2015 00:43:42 +0000] rev 3

1 IMU, Servo added; -PTD0 is used by something mysterious, so I had to move the servo control line to PTA12

When we connect 2 IMUs, one of them is laggy and the I2C connection fails after some random interval of time.; We are now only using one IMU.; Possible solution: Put both IMUs on the same I2C bus instead of separate I2C busses.

2015-03-21, by majik [Sat, 21 Mar 2015 22:44:36 +0000] rev 2

When we connect 2 IMUs, one of them is laggy and the I2C connection fails after some random interval of time.; We are now only using one IMU.; Possible solution: Put both IMUs on the same I2C bus instead of separate I2C busses.