Worked on making the ui for the replay system allowing you to pop out the diagnostic log and actuator displacement. it too multiple tries to get the actuator part correct as it stopped responding . at the moment the lap timing also doesnt seem to be updating as the race progresses.
an issue that i faced was that the leaderboard column was glitching too much so i had to work on optimising the refresh mechanism to allow it to smoothly update the live leaderboard for the race being streamed
Worked on the basic functionality for streaming historic data using livef1, and making a CLI interface for choosing year, track, and driver aswell as the type of race (qualifying, race, FP1,FP2,FP3 or sprints)
Worked on the basic functionality for streaming historic data using livef1, and making a CLI interface for choosing year, track, and driver aswell as the type of race (qualifying, race, FP1,FP2,FP3 or sprints)
Finished with drone frame and component placement.Next is setting up of the O2O communication system and control system for the drone as well as other safety/ smart features
Finished with drone frame and component placement.Next is setting up of the O2O communication system and control system for the drone as well as other safety/ smart features
In this session i worked on making the full driver board and fixing all the shorts on the schematic. due to certain crashes of KiCad there was a lot of component unsyncing happening so i had to force sync the schematic a few times to fix the errors , i also made the board to size based on the previously designed CAD model of the drone frame.
a few issues were faced while wiring the board, causing the routes to no snap on to the place , although after some trouble shooting it was fixed by changing the settings in the interactice routing tab and selecting allow DRC violations. Though this caused more trouble shooting steps in the end it allowed me to be able to quickly build the initial board. i also had to redo the board J1 socket as seen in image attached as i had forgotten to add voltage in from the ESP32 cam to this additional board to run the motors
In this session, i worked on the driver board for the drone, which the ESP32 will connect to and be able to controll the motors, its a unidirectional 4 channel controller, it uses a Q_NMOS, 10K resistors and a 1N4148 Diode. Faced a few issues because most of the schematics needed to be found using different names Q_NMOS was known as SI2300 N-channel but that name doesnt work in the kicad library. furthermore when switching to the schematics to the PCB editor most of the components didnt have a footprint assigned so i had to work on assigning footprints to each component again.
Working on a Drone swarming system that uses ESP32 with camera module for o2o( Object to object ) communication
In this first session I made the drone frame and decided the placement of various components on the frame. As well as a bit of research about the components that may be necessary for the motor driver pcb that has to fabricated / designed at a later session
In this session i worked on making the full driver board and fixing all the shorts on the schematic. due to certain crashes of KiCad there was a lot of component unsyncing happening so i had to force sync the schematic a few times to fix the errors , i also made the board to size based on the previously designed CAD model of the drone frame.
a few issues were faced while wiring the board, causing the routes to no snap on to the place , although after some trouble shooting it was fixed by changing the settings in the interactice routing tab and selecting allow DRC violations. Though this caused more trouble shooting steps in the end it allowed me to be able to quickly build the initial board. i also had to redo the board J1 socket as seen in image attached as i had forgotten to add voltage in from the ESP32 cam to this additional board to run the motors
In this session, i worked on the driver board for the drone, which the ESP32 will connect to and be able to controll the motors, its a unidirectional 4 channel controller, it uses a Q_NMOS, 10K resistors and a 1N4148 Diode. Faced a few issues because most of the schematics needed to be found using different names Q_NMOS was known as SI2300 N-channel but that name doesnt work in the kicad library. furthermore when switching to the schematics to the PCB editor most of the components didnt have a footprint assigned so i had to work on assigning footprints to each component again.
Working on a Drone swarming system that uses ESP32 with camera module for o2o( Object to object ) communication
In this first session I made the drone frame and decided the placement of various components on the frame. As well as a bit of research about the components that may be necessary for the motor driver pcb that has to fabricated / designed at a later session