Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Date

Individual

Progress

Feb 27 2021

Jess

BMS CARRIER

  • testing with two AFEs, not one in the middle

  • initially wasn't working, got just 0xff for data and PEC error

  • plugged just far left IsoSPI to carrier, then put config back to normal, then it worked fine

  • looking at thermistor readings only lists 12/AFE, changed to 32 (from schematics)

    • there's some significant reworking to be done around thermistor readings

    • seems like we already just cycle through all aux readings before proceeding, maybe can just bump to 32 different reads

  • I spent most of my time looking at code / data sheets, no real new testing

Things for other firmware members to do

  • validate the controller boards sitting on elec bench (check leds, check CAN)

  • set up what boards we currently have, make sure power sequencing works

Feb 28 2021

Jess

BMS CARRIER

  • worked on thermistor readings more

  • figured out some fiddly code bits in smoketest, we seem to be getting realistic data

    • code will definitely need some cleanup, but it's a good start

  • plugging in a resistor directly to thermistor ports didn't seem to change the data we got

  • created a real crimped 10k NTC (the expected thermistor) to test with

  • PROBING TIME (we love hardware)

    • we seem to be getting no signals via GPIO to the mux

    • turns out a bunch of debugging went into this, but we never merged the changes

    • from gerald, branch soft_222_smoke_ltc6811_validation has the changes

  • Temperature readings seem to be accurate now! this is so exciting

  • Far left AFE temperatures are actually broken, readings are wack

  • It turns out only the primary AFE reads temps correctly, which is probably a firmware issue

    • It seems like we’re only writing to the COMM register with the first AFE. The code change necessary is probably to duplicate the packet multiple times to write the same packet to all AFEs in the chain.

  • No labels