Page Comparison

Sept 20

Aashmika + Jess

POWER SELECT

• couldn't repro issue with shdn pin line 287 power_select.c turning the board off briefly (0.5 seconds)

• started checking valid pin readings and they were broken

• checked continuity for all the valid pins + resistors and everything looked fine (no shorts)

• was a bit discontinuous with the controller board plug, resoldered

• valid pins worked after resoldering! note: valid pins are active-low, should change code to reflect that

• voltage reading is consistently wrong but some are more correct than others, hardware to debug vsense pins

• isense are all wrong, scaling factors seem off

babydriver snippet for checking valid pins:
def read_pins():
print('a8', gpio_get('a', 8))
print('a9', gpio_get('a', 9))
print('a10', gpio_get('a', 10))

Sept 26

Aashmika + Jess

BMS CARRIER

• branch: soft_151_bms_validation

• KS doesn't work using smoke_bms. Button works, but not GPIO change observed on KS monitor.

• turning the relays on does nothing
  CURRENT SENSE

• running smoke_ads1259

• scope doesn't show good output at carrier board

• clock seems fine, MOSI seems slightly off

• output was super wavy and hard to read

• spi port 2 seems completely borked, no output

• spi port 1 seems ok

• Tried two different controller boards
  AFES

• vsense works for all three flawlessly!
  POWER SELECT

• resoldered the entire thing

• vsense works now! no scaling factor change

• TODO: tune scaling factors for isense

• TODO: remove jumpstart schematic stuff, 3v3 cell

• TODO: tune temp sense

Oct 1 (Happy spooky season)

Mitchell + Nita

CHARGER:

• Verified that EVSE is outputting power. The LED on the EVSE indicates charge state, and as such was used to debug.

  • When connected and CP pin is low, EVSE is WHITE

  • When the Control Pilot select pin goes high, the impedance changes and the EVSE interprets this and goes into charge mode (BLUE)

• Setup E-Load:

  • Use CV Mode, Set to 100V (and turn on)

• Received CAN messages from ELCON:

  • 12V LED lights up at CAN Socket, indicating that the Elcon has power (SHOULD BE SEEN IF CONFIGURATION IS CORRECT)

  • Sending message with corresponding ID from charger board via prv_periodic_send (every 1s)

  • Receive message of different ID (18FF50E5) from charger, and parse data

• NEXT STEPS:

  • Hardware:

    • Solve control pilot analog read (pin A5) not able to be read by MCU

  • Firmware:

    • Validate control pilot circuit

      • Rewrite module to read analog values from AN5 and AN6, to get both duty cycle (AN5) and amplitude (AN6) of PWM

    • Validate Elcon communication

      • Ensure logic to transmit values is correct, and corresponds to output received by E-Load