jittercompany / f1-led-circuit Goto Github PK

1. Limit brightness
2. Change function to pub async fn make_red(&mut self, led_num: usize) -> Result<(), SPI::Error> and loop over all LEDs (so only 1 at a time is on)

I have had a successful experience using an SHT31 temperature and humidity sensor using I2C.

SHT31:

https://www.digikey.pt/pt/products/detail/sensirion-ag/SHT31-DIS-F2.5KS/6212137?utm_adgroup=&utm_source=google&utm_medium=cpc&utm_campaign=PMax_Product_Zombie%20SKUs&utm_term=&productid=6212137&utm_content=&utm_id=go_cmp-18734772434_adg-_ad-__dev-c_ext-_prd-6212137_sig-Cj0KCQjwlN6wBhCcARIsAKZvD5gSOAvqh30QL-ChqUxGYAhbBT3Ox3EsK55l6X6DxkMbmEh59wAJCwUaAnPtEALw_wcB&gad_source=1&gclid=Cj0KCQjwlN6wBhCcARIsAKZvD5gSOAvqh30QL-ChqUxGYAhbBT3Ox3EsK55l6X6DxkMbmEh59wAJCwUaAnPtEALw_wcB

This is the crate I used:

https://crates.io/crates/sht31

For the data pulled from https://openf1.org/

Attached is are the data points for the x, y, and z coordinates as well as the corresponding timestamp for Max Verstappen's results from the 2023 Dutch Grand Prix.

zandvoort_data.csv

Here is how I generated this data:
https://github.com/CodingInGreen/f1-led-circuit-track-data

I attempted to plot the data here:
https://github.com/CodingInGreen/f1-led-circuit-track-plot/blob/main/zandvoort_track.png

But as you can see the plot doesn't represent anything close to the actual track's form.

There are positive and negative integers as the x and y coordinates, so we need to find the origin (0,0) for this data.

There is a separate project that is successfully mapping the data to the form of the track, it's open source, but they haven't yet built out the track for Zandvoort so you can see in this example if you select the 2023 race for the Zandvoort track the 3D car drives around without a track:
https://www.f1nsight.com/
https://github.com/adityakotha03/F1nsight

We discussed the possibility of live data streaming over Wifi. The owner of the openf1 repository says that there IS access to real-time data during the race.

br-g/openf1#46

1. Run the same demo from a separate task
2. Start stop the task or the animation by pressing the start stop button

• f1-led-circuit-rust to firmware
• f1-led-circuit-kicad to kicad or pcb

• Checks formatting
• Run cargo tests
• Builds firmware

We want to use addressable LEDs.

As far as we know there are two versions:

• Neopixel (WS2812, WS2813...)
• APA102
• ... Maybe there others?

They work with different protocols.

To make a selection we should make an overview of the available parts and figure out the differences between them.

• dimensions
• power requirements
• maximum daisy chained length?
• protocol
• Are they recommended for new designs (by the manufacturer)?
• ...

Board labeled #2. LEDs light up through U67. Routing between U67 and U68 may be defective, as U68 through U96 do not light up.

We need to calculate the maximum current consumption for the board and select the appropriate power adapter and voltage regulator/buck converter.

The folder name is incorrect

Currently, we know the high level requirements vaguely. But we should write them down in a detailed and testable/measurable way.

Requirement - Turn one HD108-2020 LED of the f1-led-circuit board a specific RGB color.

4301x2xxx8x6.pdf

Wurth Elektronik
Series: Tact Switches
Part Number: 430 182 070 816

I first output to a .csv file the coordinates for the x,y positions of the LED footprints from KiCad. I set the origin to be offset by the KiCad x, y coordinate of the bottom left PCB edge corner, so that we'd be dealing with only positive x and y coordinates.

This is the script to get that data:
https://github.com/JitterCompany/f1-led-circuit/blob/master/kicad/x_y_led_coords_zandvoort/get_x_y_from_origin.py

I then output to a .csv file the dataset from the race data from Max Verstappen's 2023 Dutch Grand Prix at Zandvoort using program:
https://github.com/CodingInGreen/f1-led-circuit-track-data/blob/main/src/main.rs

I then plotted that data using this program:
https://github.com/CodingInGreen/f1-led-circuit-track-plot/blob/main/src/main.rs

Which gave me this plot:
https://github.com/CodingInGreen/f1-led-circuit-track-plot/blob/main/zandvoort_track_adjusted.png

I then normalized the x,y coordinates of the output from the KiCad led footprint positions to the track data using this program:
https://github.com/CodingInGreen/f1-led-circuit-normalize-data/blob/master/src/main.rs

And plotted the led positions using this program:
https://github.com/CodingInGreen/f1-led-circuit-plot-leds/blob/master/src/main.rs

Which gave me this plot:
https://github.com/CodingInGreen/f1-led-circuit-plot-leds/blob/master/led_plot_adjusted.png

The next step correlate the led positions with the track data.

Here is the datasheet with the proper dimensions of the component:

NUF2030XV6_D-2319419.pdf

In the current pcb layout the footprint dimensions are slightly off from the component dimensions.

We will hand solder the component as it is very close to fitting or leave it off the board.