Work Log 1
Find two electric skateboards and pull info on them to determine a baseline.
Focused features were battery, motors, speed, and range.
Work Log 2
Detail the design for the control slice.
My portion was to determine possible communication protocols.
Choices were narrowed down to I2C and CAN for the low number of wires used and the ability to have multiple masters in the system.
I2C is more integrated and natively supported in the Arduino family. CAN is very robust yet isn’t natively supported. Use of CAN may be cost prohibitive.
Work Log 3
My particular project is the control slice of the overall board. Lots of changes has occurred this past week. Previously the control slice was going to be the “middleman” for most of the operations as it would take in speed inputs from the user and output those to the drive slice. However, the overall project saw a change in execution to achieve our goal. The project is going to use more off the shelf components than originally planned. This will help realize our goal of making this easy for others to replicate the design. In the previous week we worked on what microcontroller would be used and what communication protocol we would utilize. With our new plan for the slice the microcontroller may become obsolete, we may need to switch to something like a raspberry pi to run the software needed. For this coming week we are working on figuring out how to switch the slice over to the new plan of telemetry gathering/reporting and battery monitoring. We found an open-source software called VESC that looks like it will do exactly what we are after, so a major goal is to become familiar with this software and its implementation. We also need to get a full list of parts we need ordered. We will also need to get with the battery slice to see what things we need covered that the batteries BMS doesn’t cover. Some concerns I have for the week is how this new project redefinition will affect the previous goals for the control slice and how those will change.
Work Log 4 (Begin semester 2)
Some general project updates have been made. We are adapting the modular design to function on an existing skateboard and not just the 3D printed design. This week the main goal is to try and find a software solution to a multi battery detection system. We need the design to be able to allow the end user to add an additional battery to the system as seamlessly as possible. This is likely to be the largest hurdle of the semester. The current thought is to have an additional ESP32 present in each new battery “slice.” This would allow the main ESP32 to detect the presence of a new one and respond accordingly. My biggest concern would be getting this system to work as flawlessly as possible. It will be difficult to test because our own board will only have the one battery so we will need to simulate the second battery in some way.
Work Log 5
For week 5 the goal is to continue fleshing out the multi battery detection system. We need to get the code sorted to detect a new ESP32 on the CAN Bus. The biggest concern is the same as last week and not being able to actually test the multi-battery system with a real battery. We will also need to find a way to simulate a battery for testing.