# Mancester decoding issue

**URL:** https://discuss.saleae.com/t/mancester-decoding-issue/2846
**Category:** Uncategorized
**Created:** [April 29, 2024, 4:11pm UTC](https://discuss.saleae.com/t/mancester-decoding-issue/2846 "2024-04-29T16:11:56Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![BitBob](https://avatars.discourse-cdn.com/v4/letter/b/ecb155/32.png) [@BitBob](https://discuss.saleae.com/u/BitBob)
#### Post date: [May 1, 2024, 2:22pm UTC](https://discuss.saleae.com/t/mancester-decoding-issue/2846/7 "2024-05-01T14:22:04Z")

</div>

Okay, you might want to check out:

> [@Decode cc1101 or cc1121 data](https://discuss.saleae.com/t/decode-cc1101-or-cc1121-data/2773):
>
> Hi i’m new here and i just got my saleae analyzer, and i give it a first try i solder some bodge wire to a cc1121 module on MISO/MOSI/CS/CLK and i got some RF data but i can not understand how to interpret that data since i only get the hex value and not the function of the hex value, so my question is, is there a cc1101 or cc1121 decoder witch parse all my hex value and give me the correct function ? like in this example : Address Name HEX Value 0x00 IOCFG3 0x02 0x01 SYNC3…

… which talks about a [CC1101 decoder](https://github.com/smdjeff/saleae-cc1101) that is also available in the “Extensions” tab of the Logic 2 GUI. With that High-Level Analyzer, you can dig into the SPI messages to the CC1101 chip.

My guess is that the high-level information you are looking for, such as:

> [@levmarvel85](#):
>
> hex value ( E0 07 C0 9C 55 6B 67 9E )

… is buried deeper in the lower-level SPI data stream.

Thus, you’ll need to dig into the [CC1101](https://www.ti.com/product/CC1101) chip and specifically the [datasheet](https://www.ti.com/lit/gpn/cc1101) to learn more about what information actually is being passed in between MCU and the IC.

[Edit] I am curious how [ISO 15693](https://en.wikipedia.org/wiki/ISO/IEC_15693) which is at 13.56 MHz is being interfaced with a CC1101, which runs at higher frequencies (315/433/868/915 MHz)? This could also be part of your problem – they may have some clever use of the hardware, but then do some software-level decoding of the bitstream, such that the hexadecimal values you’re looking for are not present in the low-level SPI traffic.

---

_[View the full topic](https://discuss.saleae.com/t/mancester-decoding-issue/2846)._