Today, we attended a tournament and experienced strange connection and motor issues at the event. we believe this is due to two separate problems, but in actuality, it may be a single problem
Robot Code (See next post [10kchar])
Problem 1: The robot only moves in some instances despite being given full green lights on the joystick. In some instances, the entire robot can be controlled by the joystick, other times it cannot. Under the instance that the robot does connect for an extended period of time, it leads to problem 2
Things we tried:
-Firmware on vexnets and cortex has been updated
-Used tether. Still experienced connection issues
-Used 6 different vexnets. Still experienced spotty connection issues. We used vexnets which consistently runs other robots
-We added a 100ms delay in task user control to see if the CPU was being hogged. No difference in result. We also have a delay in our PID code,
-Vigorously shaking battery connections to the power expander and cortex. Did not affect connection. We do not think loose wiring is the result of connection issues
-Replaced 9v backup battery. No effect. We do not think a lack of a charged back up battery led to connection issues
-Traded joysticks with our 15" robot which we know works. Had no effect on connection issues. Because of this, we don’t think it’s the competition port
-No traces of metal shavings have appeared on the cortex or wiring
Robot Specs
Drivetrain: 4m X-Drive
Shooter: 6m, 35:1, 4.1”, half pound flywheel (Largest sprocket with tank tread, weighed down with screws + nuts) (Shooter Footage: Working on the 24" | By Florida Tech VEX-U | Facebook)
Intake: 2m internally geared for speed, Joe-Johnson Style intake (Footage: Reworked the intake!! | By Florida Tech VEX-U | Facebook)
4 encoders on the drivetrain (1 for each wheel) hooked into digital ports 1-8, and 1 encoder with an arduino hooked up to UART
Problem 2: Robot experienced motor sputtering after about 15 seconds of operating the intake and flywheel from feeding balls from the preloads. Under this scenario, balls do not jam within the intake or shooter.
Things we tried
-We split the current among ports 1-5, 6-10, and a power expander. Breaker ports 1-5 has a y splitter powering 2 motors of the flywheel. Breaker ports 6-10 has another Y splitter powering 2 motors of the shooter. Power expander powers 2 motors for the intake and 2 motors of the shooter on the power expander. Because of this setup, we do not think we are breaking the 4 amp breakers on the cortex or power expander
-Previously, the robot did not use a power expander. Before, we had 3 motors of the flywheel and 1 intake motor on 1 breaker, and another 3 flywheel motors and an intake motor in the second breaker. There was no motor sputtering issue. Because of this, we do not think that this is a current draw problem.
-Previously, the flywheel could be spun by hand and still remain spinning for 15 seconds. Because of this, we do not think this is a current draw problem from excessive friction from the shooter
-Previously, we could feed 2 balls side by side to stress test the intake. There was no motor sputtering problem from the power spike. Because of this, we do not think it is a current draw issue
-We limited PID motor power so the motors do not run in reverse to slow down.
-We minimized the friction of the intake as much as possible. Loosened the bearings to the point that the screws could be turned by hand, but the pillowblocks were still flush to brackets
-We ran the robot without connection to the field prior to matches. We made it shoot 15 balls over the course of about 8 seconds and there was no motor sputtering problem. We placed our robots on the field and let them “cool off” for about a minute. Match started and we ran into sputtering problems after 8 or so shots
-We ran the robot’s flywheel and intake sparingly. We ran the intake to index balls, then ran the flywheel and the intake to shoot. We then shut off the flywheel and used the intake to index more balls then ran the flywheel and intake again to shoot. This time, we could get more shots, but still ran into a motor sputtering problem