Releases: Lunar-Eclipse255/maelstrom
Releases · Lunar-Eclipse255/maelstrom
0.5.1
Bugfixes:
- Added a 0.5s delay to the end of init to prevent issues with multiple functions writing to the same file
Full Changelog: v0.5.0...v0.5.1
0.5.0
Features:
- Integrated checking if a file existed on the inside of maelstrom functions, so now users don't have to do
if (file_created[0]) {}
- Simulated faults 0x00-0x0F with
motor_fault_log()
to verify that they work
Bugfixes:
- Fixed
motor_fault_log()
so it actually works
Full Changelog: v0.4.7...v0.5.0
0.4.7
Bug fixes:
- In a previous release the motor error code was accidentally commented out
- This was resolved in this version, so now the motor warning code works again
- Updated README to be more up to date
Full Changelog: v0.4.6...v0.4.7
0.4.6
Bug fixes:
- In a previous release the battery threshold code was accidentally commented out
- This was resolved in this version, so now the battery warning code works again
0.4.5
Changes:
- Modified how
maelstrom::logging::set_robot_coords()
works so that it only needs to be written once inopcontrol()
instead of twice
Full Changelog: v0.4.4...v0.4.5
0.4.4
Bugfixes:
- Fixed issue #7 in which motors that were disconnected before the program started weren't displayed as disconnected in the logger
Full Changelog: v0.4.3...v0.4.4
0.4.3
Bugfixes:
- Made set_robot_coords() actually update the coords in the vector, where before it was just adding the new coords to the end of the vector
Full Changelog: v0.4.2...v0.4.3
0.4.2
Bugfixes:
- Fixed issue #1 where using the functions
maelstrom::logging::set_robot_coords()
andmaelstrom::logging::robot_coords_log()
would freeze the program, this was due to the mutexes being improperly utilized. - Fixed an issue with maelstrom::logging::robot_coords_log() not writing to the data log file because the filename was improperly initialized
Note: Image attached of how the coords logging looks.
Full Changelog: v0.4.1...v0.4.2
0.4.1
Bugfixes:
- Fixed issue #8, now log messages timestamps will be the time since the program began in the format min:s:ms, instead of the timestamps being stuck at the minute that the program was compiled
Full Changelog: v0.4.0...v0.4.1
0.4.0
Features:
- Redid file naming scheme to be numerically index-based instead of date based because the date was taken from compile time, not run-time
- Modified
motor_fault_log()
so no data abort exceptions will occur - Added print statements to the PROS integrated terminal if something went wrong
Full Changelog: v0.3.0...v0.4.0