zingo/crazycapytime

Cheap race timer and lap counter based on ESP32 and iTag BT tags.

crazycapytime's Issues

Always start in graph pane

Add some semi-automatic testing

Invesigate different way to test the code and maybe create sub issues to implement them.

Some random ideas:

• - Maybe a test build generating signals as testdata, or a way to send signals via serial console so we can drive testing from it.
• Unit testting from platformIO
• Does an Arduino or PlatfomrIO testing framework exist? Investigate a bit...
• CI testing, like build-test, lint test, code formating test, on github?
• Simulate iTags on a 2nd ESP32, making iTags with different BTUUID appear and dissappere like in a race.
• Test maximum participants with maximum laps and save and check memory and disk left.
• Profiling? Show perf graphs a la linux boot/chrome

Put frambuffer in onchip/fast memory

To make stuff fit (and not get out of mem) the frambuffer has been moved into PSRAM, this cause some GFX glithes.

Remove RaceDB data mutex

Depends on #3

Fix graph

Graph needs a redesign to get it working after the move to use threads with message loops.
Should support some smart UI and RaceDB data separation without the need a resend every data point every second (as it's was done before)

Countdown until start can't be changed in config

Break up iTag.cpp into RaceDB and Tag handling

iTag.cpp is to big time to refactoru out the Race Database parts to it's own file?

Move execution of Load/Save to RaceDB

Load and save should execute in the running contex of the RaceDB that contain the date to Load and Save
This will make the data more isolated and the mutex can be removed as almost only the RaceDB tread will touch it.

Graph don't update correctly when autoloading on startup

There is no line added or it is clearad somehow

Support time based race

Open to implementor if "RaceDistance" is lap in this case or make lap distance configurable?
total Time could be an added maxtime?

maxtime should autoset graph?
Block new lap time should autocalculate when lap dist is changed?

Same build for both Sunton and MakerFab targets

The HW diff we use is so small so we could probe/autodetect the I2C for the touch or RTC and then have runtime cheks for the diffs.

Add big notification to show if you are slower/faster compared to plan

Add big notification to show if you are slower/faster compared to plan so it easy to spot when running passed it fast.
Maybe a "flowing" thing on the graph with some number and different bg color like green/red depending on state.

Use RSSI data to set a better time on early detected iTags

During 2:nd race test (v0.2) 2 persons that runned together got about 25s diff in time, I watch the unit one of the times when it happened and could see the "first" person was spotetd by the system really early, but the 2nd person was spoted where expected.

Invesigate:

• Look at diff for this 2 persons in all data from race 2
• Look at how RSSI values behave when approaching the unit.

Ideas

• After a detection, watch RSSI values for a short period (20-30s) and pick the time that coresponds to the owest RSSI value. Maybe use some ranges in the picking to remove fluctuating values on same distance.

Random crashes usually when using keybord

Random crashes when pressing stuff in the GUI

Make graph autosetup from values

Add a setting to autostart race at a time

Really good when using it as a race helper instead of a "race" to setup in the lap-aid-area like ona 24h race and kick it of before going to start and not needing to "start" it at the start.

• autostart
• Set clock?
• autostop/save race after max time in time based races

Autostart bug after powerloss

It seem the start of race get moved to "now" when loading a race.
This makes auto start ongoing races in case of power off/on during a race get broken as new laps show up around time "0" and not at proper start of race position.

Add autosave to make backups during race

Needed to handle race good in case of powerlost or crash. If/when RTC is added it will be crusial to be able to just continue the race like as nothing happened.

Autoload raceDB on startup

When we start load the last (or current ongoing) race

Config Race UI

Race info should not be hardcode compile time
Load and Save
Support multiple race profiles, as we rerun the same track/race in a new date

Assign 2 (or more?) iTags per perticipant

During 2nd race test one participant managed to turn off the iTag by misstake having two tags per person could fix this.
This would also make "fast" runners that don't stop more likely to be detected.

• This will need to chanage the database from tag->participants to participant->tags[]
• The gui should show the dual tag in some way
• Nice to have: You need to be able to add & assign/change tags to users in the GUI (could also be hardcoded too always use two tags per user)

Fix Load so it populate the data

Load only loads and print the info in the log, it should load the data into the systems.

Stoped race state not saved in file so it will autstart on next power on

Make participant name editable

Edit name instead of done compile time
DESCOPED, part of #1 - Select/Edit tag used like tagnumber and color on tag
DESCOPED, part of #1 - UI for multiple tags per participant, kind of duplicate to #1
Should work anythime independent on if race is started to handle late starters, or tag problems during race.
Should be saved/loade as part of race data, and tag/participant data

Crash on race start

Could be on "race" save after the repartitioning when wifi was added in the latest version just before VXO 24H.

This bug blocked it from working during the race as the unit restarted directly.

Support RTC HW

• Support clock time, e.g. race don't start at time 0 but at clock time
• If crashed/restarted and race was ongoing, just continue

When loading a race bump RTC time if time is nower in any point than "now"

This wil help in accelerated testing when you restart and time is back to "normal" time.

Also it will avoid timejumps backwards if a race is restarted and this is wrong.

Beta time based race info (for Växjö SM 24h)

Stuff can be hardcoded for one participant
That participand can have 2 tags and a graph with some god race info

There is another "add it properly" ticket. This is just to get a proof of concept to the race really soon.

Some ideas:

• Add a goal (maybe with checkpoints goals inbetween)
• Show, pace since start, current pace (last 20-30min?), pace to reach goal
• current amount before or behind goal?

---

• Open to implementor if "RaceDistance" is lap in this case or make lap distance configurable?

• total Time could be an added maxtime?

• maxtime should autoset graph?

• Block new lap time should autocalculate when lap dist is changed?

Fix Add/Sub lap

It need to be possible to correct error and modify a participand number of laps during/after the race