search

analogdevicesinc / scopy

A software oscilloscope and signal analysis toolset
http://wiki.analog.com/scopy
GNU General Public License v3.0
384 stars 158 forks source link

Scopy: Logic Analyzer no longer shows decoded data at changed baud rate #1377

Open SgoSkz opened 1 year ago

SgoSkz commented 1 year ago

Environment:

Describe the bug Logic Analyzer no longer shows the decoded data for UART when changing baud rate

To Reproduce Steps to reproduce the behavior:

  1. Go to "Logic Analyzer" in Scopy
  2. Set UART to respective pins
  3. Set single capture
  4. See decoded data
  5. Change baud rate
  6. See error

Expected behavior Decoded data shows up

Screenshots image 115200 (default) baud rate image 38400 (changed) baud rate

Additional context Scopy.ini https://pastehub.net/fdc83de4341

SgoSkz commented 1 year ago

Updating firmware did not fix the issue. New FW Version: v0.29

adisuciu commented 1 year ago

I don't think it should decode though. To me It looks like your signal is at 115200 baudrate, not at 38400 ..

SgoSkz commented 1 year ago

You are absolutely correct, 115200 is the correct baudrate, but when I change it back to 115200 from 38400, the decoded messages still dont show up. I'll add a screenshot soon

SgoSkz commented 1 year ago

image image image

jjmoreno1163 commented 1 year ago

Hi, I have the same issue, when changing to any baudrate value, decoding doesn't work.

adisuciu commented 1 year ago

The solution here would be to trigger another decoding when one of the decoding parameters changes if I understand correctly. It should do this even when the acquisition stopped.

SgoSkz commented 1 year ago

Could you elaborate a little more on that? From what I'm getting, you mean to scan for another message and it should decode properly? That is not the case for my situation, I will provide screenshots when I get the time.

adisuciu commented 1 year ago

Well it seems to me that there are no new acquisitions in betwseen changing baud rates. Decoding only seems to work upon new acquisition, not upon changing decoding parameters. My suggestion is to either decode upon changing decoding parameters, or manually trigerring a new decode (via a button).

SgoSkz commented 1 year ago

This is an active 9600 baud rate scan with no decode messages at 9600 decode value for the logic analyzer. image Changing any respective trigger settings for both DIO and extern trigger does not cause decoded messages to appear

adisuciu commented 1 year ago

I just tested and it works just fine for me .. image Can you try removing your ini files ? https://wiki.analog.com/university/tools/m2k/scopy-troubleshooting?s[]=scopy&s[]=troubleshooting#reinstall_ini_files

SgoSkz commented 1 year ago

unfortunately, deleting the ini files in %AppData%/ADI does not solve the issue for me. Is the version you are testing also v1.4.1?

image image

adisuciu commented 1 year ago

I reproduced this. I used v1.4.0 where things seem to work just fine. I will take a look.

pitsche commented 9 months ago

I found a workaround. Change the default in C:\Program Files\Analog Devices\Scopy\decoders\uart\pd.py to the value you need. Restart Scopy and that's it.

molitoris commented 3 weeks ago

The logic analyzer does no longer shows the decoded data for UART after changing the baud rate

OS: Windows 11 SW Version: v1.4.1-f4beeb1

andrei47w commented 3 weeks ago

This bug was fixed for all platforms on the main branch. Will be available in the next release.