The MinIMU-9 v3 has been discontinued, and the new (pin-compatible) version uses different chips:

https://www.pololu.com/product/2738

Default channel should be -1, we should then look at how many channels in init() call are >= 0 and setup only that many channels.

Integrate the IMU code for the Eth-Bridge

Components

• Etherbotix, with MD-03 motor driver, Mini-IMU v5
• 3 Cliff sensors (GP2Y0D805Z0F) on height adjustable bracket
• Differential drive - QTY2 12v 30:1 200RPM motors
• LD-06 Lidar
• AX-12 servo to tilt lidar (mounted on left side to avoid interfering with the lidar cable)
• 12V, 3Ah battery

Roadmap

• Verify that laser works at high angle of incidence (just use ROS drivers)
• Get laser driver working on Etherbotix, just fill in 360 degree polar map, send over ethernet, visualize on desktop
• Design, 3d print and assemble physical chassis
• Tune PID for motors, make sure we can travel a set distance
• Tune odometry, make sure 90 degree turns are good
• Tune cliff sensors
• Phase 1A - drive straight until cliff sensors trigger, back up, turn 180, repeat
• Add debugging data over ethernet: odometry pose estimate
• Add visualization of debugging data
• Get debugging data over wifi
• Selection of phases using IMU
• Get servo running
• Phase 1B - put control loop around Y error to keep us more centered on the table
• Phase 1C - Use laser to detect cliff ahead of time (so we can go faster)
• Phase 1D - Use laser to detect the width of table and keep robot centered
• Phase 2A - sweep laser and assemble scan
• Phase 2B - find block in laser scan
• Phase 2C - approach block and push off table
• Phase 3A - find box using level laser
• Phase 3B - change block target pose so that we can push block to goal even if it is off to side of table
• Phase 3C - push block into box (behavior is present, but only works well if block is fairly closet to middle of table)
• Physically rotate laser 180 degrees so that we can segment scans for block detection while moving (currently, discontinuity is in the front center, this would put it in the back). Also requires update to transform code in robot and viewer.

Open Issues

• Bootloader won't boot after upload - requires a power cycle? Has gone away after fixing LD06 driver.
• Need to add CRC to LD06 driver
• Odometry is off - Y axis is inverted (we're fixing this by inverting Y in the struct unpack)
• TIM12/PWM seems very off - is this actually up-down counting? That would explain the prescalar issue and also why the "40%" PWM drives laser so slow (check on scope if it is actually 40% or 20%) - nope, it checks out at 40% - no idea why we need to output 70% to get the proper rotation speed
• Won't run without the ethernet cable plugged in

Known Issues

• Can't receive packets bigger than MTU. They show up in Wireshark (which doesn't process checksums) but doesn't show up in python socket.recv() - still exists but packets are now broken up to be smaller than MTU

For instance, TIM1_UP_IRQHandler should be TIM1_UP_TIM10_IRQHandler to match the various ST documentation.

Moved from mikeferguson/robomagellan#2:

It appears the high byte is updated, then table is read out, then low byte is updated. Need to prevent this. This is particularly bad when crossing 0 as the high byte changes from 00 -> ff and vice versa

Example sequence as seen on computer side:

-26, 249, 29

Actual sequence that should be seen:

-26, -7, 29

Plot: