Difference between revisions of "K-Scale CANdaddy"
(4 intermediate revisions by the same user not shown) | |||
Line 30: | Line 30: | ||
== Battery Charger == | == Battery Charger == | ||
− | |||
− | |||
− | |||
− | |||
== CAN Communication == | == CAN Communication == | ||
Line 41: | Line 37: | ||
* What do we do if supply-side GND is missing? | * What do we do if supply-side GND is missing? | ||
− | + | = Design = | |
− | + | == Schematic == | |
+ | == Layout == | ||
+ | == Final Form Factor == | ||
= Other = | = Other = | ||
Line 51: | Line 49: | ||
# I understand that there is a way to both use the battery as a source as well as to charge it using the USB. However, wouldn't this mean not being able to put a diode within the circuit directing current in one direction? Isn't this a hazard, destroying the circuit the moment a bit of noise comes through? | # I understand that there is a way to both use the battery as a source as well as to charge it using the USB. However, wouldn't this mean not being able to put a diode within the circuit directing current in one direction? Isn't this a hazard, destroying the circuit the moment a bit of noise comes through? | ||
# Power Ground in the context of a switching regulator for our circuit to amplify 3.7 V battery to 5 V source. Do we just connect Power Ground to Battery Ground? | # Power Ground in the context of a switching regulator for our circuit to amplify 3.7 V battery to 5 V source. Do we just connect Power Ground to Battery Ground? | ||
− | |||
== Notes == | == Notes == | ||
Line 58: | Line 55: | ||
*** Reduces amount of wiring for STM32, requires just one SPI bus with a bunch of easily programmable chip selects | *** Reduces amount of wiring for STM32, requires just one SPI bus with a bunch of easily programmable chip selects | ||
** Cons: Need to understand the interface for the MCP2515. Need to confirm how interrupts and timing works. | ** Cons: Need to understand the interface for the MCP2515. Need to confirm how interrupts and timing works. | ||
+ | |||
+ | == Github Repository == |
Latest revision as of 07:38, 28 May 2024
Contents
Features[edit]
- USB-C + Battery compatibility
- Able
Voltage[edit]
- Load sharing between USB and battery
Central Components[edit]
MCU[edit]
STM32[edit]
Used:
STM32F407VET6 Justification: 512 kB of flash memory, unit price at $3, powerful enough to run heavy programs
Buttons + Debouncer[edit]
- Button Debouncer
- TODO: Add the IC name
LCD[edit]
PCF2518[edit]
- How do we connect I2C chip to the LCD screen?
Battery Charger[edit]
CAN Communication[edit]
MCP2515[edit]
- How to get supply-side VCC without having it on the bus (from supply-side GND)?
- What do we do if supply-side GND is missing?
Design[edit]
Schematic[edit]
Layout[edit]
Final Form Factor[edit]
Other[edit]
Questions[edit]
- How does the switching regulator mechanism work?
- Do digital logic levels depend on source voltage? For example, let's say that a 3.3V powered device is sending signals to a 5V power device. From my understanding of the datasheet, a direct connection between the signals should not be allowed. However, why is this? What are the internal mechanisms of the pins that make it so that the logic levels need to be based off of the source voltage?
- I understand that there is a way to both use the battery as a source as well as to charge it using the USB. However, wouldn't this mean not being able to put a diode within the circuit directing current in one direction? Isn't this a hazard, destroying the circuit the moment a bit of noise comes through?
- Power Ground in the context of a switching regulator for our circuit to amplify 3.7 V battery to 5 V source. Do we just connect Power Ground to Battery Ground?
Notes[edit]
- Need to figure out the interface for the SPI lines using MCP2515
- Pros if successful:
- Reduces amount of wiring for STM32, requires just one SPI bus with a bunch of easily programmable chip selects
- Cons: Need to understand the interface for the MCP2515. Need to confirm how interrupts and timing works.
- Pros if successful: