frc1076/robotkitlib issues and pull requests

#87 - PRACTICE: Write an auton routine that drives the robot forwards 10 feet

Issue - State: open - Opened by VeeBallbach about 4 years ago
Labels: Practice

#86 - Voltage, Code Communications fail if joystick not plugged in

Issue - State: closed - Opened by EmilyRobotics about 4 years ago
Labels: bug

#85 - PRACTICE: Write a more complicated auton routine

Issue - State: open - Opened by VeeBallbach about 4 years ago
Labels: Practice

#84 - Fix autononomous init being run before robot is enabled

Issue - State: open - Opened by EmilyRobotics about 4 years ago

#83 - PRACTICE: Add a simple auton routine to the robot

Issue - State: open - Opened by VeeBallbach about 4 years ago - 2 comments
Labels: Practice

#82 - PRACTICE: Add a brake to the robot

Issue - State: open - Opened by VeeBallbach about 4 years ago
Labels: Practice

#81 - Eli drivefixes

Pull Request - State: closed - Opened by EmilyRobotics about 4 years ago

#80 - BUG: After deploying new code, you currently have to unselect and reselect both enable and teleop to drive

Issue - State: open - Opened by EmilyRobotics about 4 years ago
Labels: bug, Driverstation

#79 - Newly added pikitlib files do not get properly deployed.

Issue - State: closed - Opened by mcolinj about 4 years ago - 1 comment

#78 - Revert built in deployer, todo: make it work better in the future

Issue - State: closed - Opened by EmilyRobotics about 4 years ago

#77 - CHALLENGE: Random Robot

Issue - State: open - Opened by EmilyRobotics about 4 years ago
Labels: CHALLENGE

#76 - CHALLENGE: Py4E Python Training

Issue - State: open - Opened by numerator about 4 years ago
Labels: CHALLENGE

#75 - Mecanum drive

Pull Request - State: open - Opened by EmilyRobotics about 4 years ago

#74 - merge in new changes

Pull Request - State: closed - Opened by EmilyRobotics about 4 years ago

#73 - A few more suggestions for the new deploy

Issue - State: closed - Opened by amylieb about 4 years ago

#72 - robot_setup.py doesn't extract tar into RobotCode directory

Issue - State: closed - Opened by amylieb about 4 years ago

#71 - Reorganize files and deploying code

Pull Request - State: closed - Opened by EmilyRobotics about 4 years ago

#70 - Issue with git bash not installed/not working

Issue - State: closed - Opened by EmilyRobotics about 4 years ago - 1 comment

#69 - Reorganize the files in the repository

Issue - State: closed - Opened by mcolinj about 4 years ago

#68 - Test everything fully

Issue - State: open - Opened by VeeBallbach about 4 years ago
Labels: ongoing

#67 - Make sure that everything can be done manually

Issue - State: open - Opened by VeeBallbach about 4 years ago
Labels: ongoing

#66 - Add version info to driverstation and robot

Issue - State: closed - Opened by VeeBallbach about 4 years ago - 1 comment

#65 - merge main changes into ultrasonic branch

Pull Request - State: closed - Opened by EmilyRobotics about 4 years ago

#64 - ultrasonic object created in pikitlib!

Pull Request - State: open - Opened by sorenfnt about 4 years ago

#63 - Logging and catching code errors

Issue - State: open - Opened by EmilyRobotics about 4 years ago

#62 - Remove .vscode directory from source control

Issue - State: closed - Opened by numerator about 4 years ago

#61 - Error establishing connection

Issue - State: closed - Opened by MrRSquared about 4 years ago - 3 comments

#60 - Added mecanumdrive file with two driveCartesian options

Pull Request - State: closed - Opened by IngmarNT about 4 years ago - 3 comments

#59 - differentialdrive is not calling the RobotDriveBase initializer.

Issue - State: closed - Opened by IngmarNT about 4 years ago - 2 comments

#58 - Driverstation crashing on connect

Issue - State: closed - Opened by MrRSquared about 4 years ago - 8 comments
Labels: bug

#57 - Make the readme more up to date

Issue - State: closed - Opened by EmilyRobotics about 4 years ago

#56 - Look into issue where battery wouldnt connect but still be able to drive the robot

Issue - State: closed - Opened by EmilyRobotics about 4 years ago - 1 comment
Labels: bug

#56 - Look into issue where battery wouldnt connect but still be able to drive the robot

Issue - State: closed - Opened by EmilyRobotics about 4 years ago - 1 comment
Labels: bug

#55 - Create more logging for the driverstation

Issue - State: open - Opened by EmilyRobotics about 4 years ago - 1 comment
Labels: Driverstation

#54 - Add "gamedata" feature to the driverstation

Issue - State: open - Opened by EmilyRobotics about 4 years ago
Labels: Driverstation

#53 - Add visual battery indicator in addition to existing text indicator

Issue - State: open - Opened by EmilyRobotics about 4 years ago
Labels: Driverstation

#52 - Add a timer to the driverstation

Issue - State: open - Opened by EmilyRobotics about 4 years ago
Labels: Driverstation

#51 - Consider adding a "reverse motors" button to the driverstation

Issue - State: open - Opened by EmilyRobotics about 4 years ago
Labels: Driverstation

#50 - Create windows version for uploading code

Issue - State: closed - Opened by EmilyRobotics about 4 years ago - 1 comment

#49 - Create program to deploy code to robot

Pull Request - State: closed - Opened by EmilyRobotics about 4 years ago - 3 comments

#48 - Uploading code to the robot

Issue - State: closed - Opened by EmilyRobotics about 4 years ago - 1 comment

#47 - Remove estop button, instead use spacebar

Issue - State: closed - Opened by EmilyRobotics about 4 years ago

#46 - Rewrite/create battery monitor class

Issue - State: open - Opened by EmilyRobotics about 4 years ago - 3 comments

#45 - Clean up analog input class

Issue - State: open - Opened by EmilyRobotics about 4 years ago - 2 comments

#44 - Allow driverstation to run without controller plugged in

Issue - State: closed - Opened by EmilyRobotics about 4 years ago

#43 - Rework GUI, add various notifications

Pull Request - State: closed - Opened by EmilyRobotics about 4 years ago - 1 comment

#42 - Fix issue where close button doesnt actually close driverstation

Issue - State: closed - Opened by EmilyRobotics about 4 years ago
Labels: bug

#41 - Add E-Stop button to driverstation

Issue - State: closed - Opened by EmilyRobotics about 4 years ago

#40 - robot code is slipping

Issue - State: closed - Opened by MrRSquared about 4 years ago - 5 comments

#39 - Fix xboxcontroller getY() and getX() being reversed in some instances

Issue - State: closed - Opened by EmilyRobotics about 4 years ago
Labels: bug

#38 - Fix driving and some threading errors

Pull Request - State: closed - Opened by EmilyRobotics about 4 years ago

#37 - Distributed software image on SD card should contain all necessary contents

Issue - State: open - Opened by mcolinj about 4 years ago - 1 comment

#36 - Create the documentation on how to bring the Freenove robot to life

Issue - State: open - Opened by mcolinj about 4 years ago - 7 comments
Labels: High Priority

#35 - Set up the pi so that run.py (robot) starts up automatically on reboot

Issue - State: closed - Opened by mcolinj about 4 years ago - 6 comments
Labels: Medium Priority

#34 - Add a feature to the run.py that will "advertise" the robot IP address using the neopixel lights

Issue - State: open - Opened by mcolinj about 4 years ago

#33 - Create the mecanum drivetrain

Issue - State: open - Opened by mcolinj about 4 years ago - 6 comments
Labels: enhancement

#32 - Create the light sensor interface

Issue - State: open - Opened by mcolinj about 4 years ago
Labels: enhancement

#31 - Create the robot battery power indicator interface

Issue - State: closed - Opened by mcolinj about 4 years ago - 1 comment

#30 - Add a laptop battery indicator to the driverstation GUI

Issue - State: closed - Opened by EmilyRobotics about 4 years ago - 11 comments
Labels: Driverstation

#29 - Add robot battery voltage indicator to the driverstation

Issue - State: closed - Opened by EmilyRobotics about 4 years ago - 1 comment

#28 - Matthew fix getquit

Pull Request - State: closed - Opened by mcolinj about 4 years ago

#27 - driverstation gui crashing in getQuit

Issue - State: closed - Opened by mcolinj about 4 years ago - 1 comment

#26 - Fix issue with logging program that it will get stuck on connection

Issue - State: closed - Opened by EmilyRobotics about 4 years ago
Labels: bug

#25 - Fix threading erorr

Issue - State: closed - Opened by EmilyRobotics about 4 years ago - 1 comment
Labels: bug

#24 - Changing robot mode starts the robot thread, that should be done with a change in enable/disable state

Issue - State: closed - Opened by mcolinj over 4 years ago

#23 - Developing the driverstation further

Pull Request - State: closed - Opened by EmilyRobotics over 4 years ago - 1 comment

#22 - Figure out (and rewrite) the ADC (Analog to Digital Converter) to monitor battery voltage. Document the other ADC inputs so we can use them.

Issue - State: open - Opened by mcolinj over 4 years ago - 2 comments

#21 - Develop the driverstation further

Issue - State: closed - Opened by EmilyRobotics over 4 years ago

#20 - Setup logging such that the log info is sent from the raspberry pi to the driverstation

Issue - State: closed - Opened by EmilyRobotics over 4 years ago

#19 - Clean up speedcontroller, buzzer, logging

Pull Request - State: closed - Opened by EmilyRobotics over 4 years ago

#18 - Fix up the speedcontroller to is uses port 1, 2, 3, and 4

Issue - State: closed - Opened by mcolinj over 4 years ago

#17 - Work on shuffleboard

Issue - State: open - Opened by EmilyRobotics over 4 years ago

#16 - More updates to driverstation and general robot logic

Pull Request - State: closed - Opened by EmilyRobotics over 4 years ago

#15 - Experiment with and write up a design document for the line-following sensor.

Issue - State: open - Opened by mcolinj over 4 years ago - 2 comments

#14 - Cleanup the buzzer(IllegalBuzzer) class object

Issue - State: closed - Opened by mcolinj over 4 years ago

#13 - Figure out a license

Issue - State: open - Opened by EmilyRobotics over 4 years ago - 2 comments

#12 - Add a requirements.txt

Issue - State: closed - Opened by numerator over 4 years ago - 2 comments

#11 - Fix the main loop of the run.py according to comments in the code.

Issue - State: closed - Opened by mcolinj over 4 years ago - 1 comment

#10 - Reorganization of pikitlib into its own package, fully implemented xbox controller funcinality (In Progress)

Pull Request - State: closed - Opened by EmilyRobotics over 4 years ago - 2 comments

#9 - Create the UltraSonic component interface for use in the robot.py framework.

Issue - State: open - Opened by mcolinj over 4 years ago - 7 comments

#8 - Implement rest of Xbox controller class (in progress)

Pull Request - State: closed - Opened by EmilyRobotics over 4 years ago - 1 comment

#7 - Use two rear Neopixel lights to signal if the robot is enabled (green) or disabled (red)

Issue - State: open - Opened by mcolinj over 4 years ago - 4 comments

#6 - Implement the rest of the functions of the xbox controller

Issue - State: closed - Opened by EmilyRobotics over 4 years ago

#5 - move setMotorPWM into pikitlib

Pull Request - State: closed - Opened by EmilyRobotics over 4 years ago

#4 - Study the Motor.py and then write up a description about how to wrap it up to be used like any other motor controller.

Issue - State: closed - Opened by mcolinj over 4 years ago

#3 - Create pi-requirements.txt file (the list of all of the python libraries required to be installed on the pi)

Issue - State: closed - Opened by mcolinj over 4 years ago

#2 - Create the laptop-requirements.txt file (listing all python libraries required to be installed on laptop)

Issue - State: closed - Opened by mcolinj over 4 years ago - 1 comment

#1 - Fix misspelling of IllegalBuzzer object in the pikitlib (and fix up anywhere it is used)

Issue - State: closed - Opened by mcolinj over 4 years ago
Labels: good first issue

GitHub / frc1076/robotkitlib issues and pull requests