Skip to content

Conversation

@392625227
Copy link

a new protocol decoder of china fast power charger spec. UFCS. full files under https://github.com/392625227/UFCS-protocol-compare-with-USB-PD.

@kamocat
Copy link

kamocat commented May 1, 2023

Hi Edison Ren,
Thank you for your contribution. To help me review this, please:

  • provide an English translation of the UFCS specification
  • create a pull request to sigrok-dumps for the signal capture ufcs_pv.sr.

Also, I want to ask about the stacked decoder. You chose to stack on top of the UART decoder, but it's not really UART-based. From your README:

The physical layer of UFCS is the UART serial port. Almost all MCUs have their own UART serial port hardware, which makes product development very simple. However, USB-PD adopts BMC encoding, which simply means that 1 and 0 are represented by the width of the pulse, and the high level of the signal is only about 1V, which requires a hardware comparator, which increases the cost.

This sounds like each UART bytes each represents a single bit, as in HDQ. Would it make more sense to measure the bit-width directly, as the SDQ decoder does?

@guilin007
Copy link

Hello,
I want to add an analyzer to the SIF protocol.
768f65dfdc7078e6c59c31b1ae111850

The line status is low when idle.
Each frame of data consists of three parts: synchronization signal + 12-bit (12*8bit) data+end signal.
The data signal uses the high and low level duty cycle to send data packets.
Data 0: (32 Tosc for low level, 64 Tosc for high level);
Data 1: (64 Tosc for low level, 32 Tosc for high level);

Stop signal :(5-10ms low)

The ratio of high and low levels is generally 0.5ms and 1ms

I need a master to help me complete the writing, because I only know a little bit of C programming and other programming languages

Thank you very much for your help

@392625227
Copy link
Author

392625227 commented Nov 6, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants