# Aviation Protocol Decoders? 1553 and ARINC-429? **URL:** \ **Category:** Uncategorized\ **Created:** [March 29, 2025, 8:46pm UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329 "2025-03-29T20:46:03Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![andy.nicholas](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@andy.nicholas](https://discuss.saleae.com/u/andy.nicholas)\ **Post date:** [March 29, 2025, 8:46pm UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329/1 "2025-03-29T20:46:03Z")
Has anyone in the community created decoders for common aviation standards like MIL-1553 and ARINC-429? These seem like they should be simple to create and wondered if these already exist as supported or community created protocols? If not, is there a suggested protocol template I could use to start writing my own protocol decoder? MIL-1553 is Manchester encoded. 429 is RTZ encoded. ---
**Author:** ![billy.hughes](https://avatars.discourse-cdn.com/v4/letter/b/b3f665/32.png) [@billy.hughes](https://discuss.saleae.com/u/billy.hughes)\ **Post date:** [April 1, 2025, 12:39am UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329/2 "2025-04-01T00:39:52Z")
The Associated WIKI page has great info on the bits and bytes. > **[ARINC 429](https://en.wikipedia.org/wiki/ARINC_429)** > > ARINC 429, the "Mark 33 Digital Information Transfer System (DITS)," is the ARINC technical standard for the predominant avionics data bus used on most higher-end commercial and transport aircraft. It defines the physical and electrical interfaces of a two-wire data bus and a data protocol to support an aircraft's avionics local area network. > ARINC 429 is a data transfer standard for aircraft avionics. It uses a self-clocking, self-synchronizing data bus protocol (Tx and Rx are on separate ports... ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [April 2, 2025, 9:28pm UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329/3 "2025-04-02T21:28:02Z")
@andy.nicholas Thanks for writing in! We post all publicly available community shared analyzers in the link below. Unfortunately, MIL-1553 and ARINC-429 are not listed. > **[Community Shared Analyzers | Saleae Support](https://support.saleae.com/community/community-shared-protocols)** We’re also tracking various requests for variations of Manchester modes in the post below (I added a comment for you there to track your need for these to be officially supported). > **[Manchester LLA - Support more modes - Logic 2 - Ideas and Feature Requests -...](https://ideas.saleae.com/b/feature-requests/manchester-lla-support-more-modes/)** > > Currently our Manchester LLA supports the following modes: > \- Manchester > \- Differential Manchester > \- Bi-Phase Mark > \- Bi-Phase Space > > It would be nice to add support for other modes and variations, such as: > \- Bi-Phase Line > \- NRZ (M, S, and L) > \- DAL For quick reference, our Protocol Analyzer SDK documentation can be found below. A good starting point template might be the Manchester analyzer that is included with the device (source code linked below as well). > **[Protocol Analyzer SDK | Saleae Support](https://support.saleae.com/saleae-api-and-sdk/protocol-analyzer-sdk)** By the way, in case you needed help with developing a custom analyzer, I wanted to shout out the folks over at Binho LLC as they provide services for getting you quickly up and running with custom low-level analyzers and extensions! They are our official partners for getting help with projects such as this. I’ve provided their contact link below in case you wanted to reach out to them for help with development. > **[Custom Protocol Analyzer Development for Saleae Logic](https://binho.io/pages/custom-protocol-analyzer-development)** > > Binho crafts custom protocol analyzers for Saleae Logic. Add an I2C layer, tweak an existing solution, or build a new decoder from scratch. ---
**Author:** ![prajwaltr93](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@prajwaltr93](https://discuss.saleae.com/u/prajwaltr93)\ **Post date:** [May 21, 2026, 5:33am UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329/4 "2026-05-21T05:33:53Z")
Hi @andy.nicholas i just started working on ARINC 429 analyzer, would like you to test and let me know if there are any issues. > **[GitHub - prajwaltr93/Saleae-ARINC-429-Analyzer: ARINC 429 Analyzer for Saleae Logic Analyzer](https://github.com/prajwaltr93/Saleae-ARINC-429-Analyzer)** > > ARINC 429 Analyzer for Saleae Logic Analyzer please note, this is very much beta and would love your inputs. thanks in advance. i have few todo’s. planning to implement the same by this weekend. ---
**Author:** ![prajwaltr93](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@prajwaltr93](https://discuss.saleae.com/u/prajwaltr93)\ **Post date:** [May 21, 2026, 5:35am UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329/5 "2026-05-21T05:35:16Z")
Hi @timreyes i am planning to publish my LLA, attaching the link here. please let me know if have to fix anything before i do that. thanks in advance, Prajwal > **[GitHub - prajwaltr93/Saleae-ARINC-429-Analyzer: ARINC 429 Analyzer for Saleae Logic Analyzer](https://github.com/prajwaltr93/Saleae-ARINC-429-Analyzer)** > > ARINC 429 Analyzer for Saleae Logic Analyzer ---
**Author:** ![andy.nicholas](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@andy.nicholas](https://discuss.saleae.com/u/andy.nicholas)\ **Post date:** [May 21, 2026, 6:30am UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329/6 "2026-05-21T06:30:50Z")
Awesome! I have to go find one of our ARINC guys at work now to see what we can connect this to. We previously would not connect Saleae to anything like this because… well, there was no decoder. ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [May 22, 2026, 11:48pm UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329/7 "2026-05-22T23:48:17Z")
@prajwaltr93 Looks great! Thanks so much for sharing your work with us! I just tested the Windows version. ![ARINC](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/f/f881e152e5aceb534c98b922812bff9c8f990323.png) We’ll get this up on our Community Analyzers list! > **[Community Shared Analyzers](https://www.saleae.com/support/community-contact/community-shared-protocols)** > > The following analyzers are not officially supported nor developed by Saleae, but instead, were kindly shared by our community of users. Please contact us if... ---
**Author:** ![prajwaltr93](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@prajwaltr93](https://discuss.saleae.com/u/prajwaltr93)\ **Post date:** [May 27, 2026, 4:57am UTC](https://discuss.saleae.com/t/aviation-protocol-decoders-1553-and-arinc-429/3329/8 "2026-05-27T04:57:16Z")
@timreyes thanks for including this in community analyzers list !, regards, Prajwal