# Saleae team - we would love samples of protocol captures!

**URL:** <https://discuss.saleae.com/t/saleae-team-we-would-love-samples-of-protocol-captures/520>\
**Category:** Uncategorized\
**Created:** [May 15, 2020, 10:48pm UTC](https://discuss.saleae.com/t/saleae-team-we-would-love-samples-of-protocol-captures/520 "2020-05-15T22:48:18Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Collin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/collin/32/53_2.png) [@Collin](https://discuss.saleae.com/u/Collin)\
**Post date:** [May 21, 2020, 12:28am UTC](https://discuss.saleae.com/t/saleae-team-we-would-love-samples-of-protocol-captures/520/14 "2020-05-21T00:28:04Z")

</div>

Here’s a little capture of the comm between a Tesla Model S battery module and the master board. As you might imagine, Tesla did not exactly provide a handy protocol specification document for this. 😉 So, the only references are open source projects. Luckily, I did write one of those: [https://github.com/collin80/TeslaBMS](https://github.com/collin80/TeslaBMS)

[ModelS\_BMS.sal](https://discuss.saleae.com/uploads/short-url/aB5wOMZFhOrUs0NJcIcpJ8OsF77.sal) (9.7 KB)

I haven’t taken the time to built a python HLA for this yet. If I remember correctly the various commands and responses are more or less static in length so it should be possible to write some sort of state machine that interprets the data into a higher level output.

The BMS uses an extremely odd bit rate so it’s kind of interesting from that perspective. The async serial decoder seems to be working well and results fill out the table properly.

---

_[View the full topic](https://discuss.saleae.com/t/saleae-team-we-would-love-samples-of-protocol-captures/520)._