Bug 1133 - Time scale incorrect when using non-zero pretrigger capture ratio
Summary: Time scale incorrect when using non-zero pretrigger capture ratio
Status: CONFIRMED
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Driver: fx2lafw (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
: 1233 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-03-07 16:34 CET by minenofmeer
Modified: 2018-06-15 11:50 CEST (History)
3 users (show)



Attachments
1% pre-capture (149.16 KB, image/png)
2018-03-07 17:25 CET, minenofmeer
Details
0% pre-capture (159.42 KB, image/png)
2018-03-07 17:26 CET, minenofmeer
Details
1% pre-capture (2.15 KB, application/zip)
2018-03-07 17:35 CET, minenofmeer
Details
0% pre-capture (2.73 KB, application/zip)
2018-03-07 17:36 CET, minenofmeer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description minenofmeer 2018-03-07 16:34:45 CET
Hi,

First of all: thank you very much for developing and sharing this really great tool.

I just compiled from source on a raspberry pi 3. 
I am using a Chinese USBEE clone (fx2lafw driver) to debug i2c communication.
When pre-trigger-capture-ratio is unequal to zero the time scale in the output of pulseview is not correct (factor 2 to small, time readings are to small, frequencies to high) for digital inputs. When pre-trigger-capture-ratio is set to zero the data are correctly displayed.
The analog input is always displayed correctly.

I did the same tests on a x86 linux machine, with also a recently compiled version of sigrok/pulseview. The outcome was the same: faulty display of digital signals when pre-trigger-capture-ratio is set unequal to zero.



PulseView 0.5.0-git-7b7ab1f

Qt
5.9.2
glibmm
2.54.1
Boost
1_62
libsigrok
0.6.0-git-187c300b/4:0:0 (rt: 0.6.0-git-187c300b/4:0:0)
- glib
2.54.3 (rt: 2.54.3/5403:3)
- libzip
1.1.2
- libserialport
0.1.1/1:0:1 (rt: 0.1.1/1:0:1)
- libusb-1.0
1.0.21.11156
- libftdi
1.4
- Host
armv7l-unknown-linux-gnueabihf, little-endian
- SCPI backends
TCP, RPC, serial, USBTMC
libsigrokdecode
0.6.0-git-fb1870b/4:0:0 (rt: 0.6.0-git-fb1870b/4:0:0)
- glib
2.54.3 (rt: 2.54.3/5403:3)
- Python
3.6.4+ / 0x30604f0 (API 1013, ABI 3)
- Host
armv7l-unknown-linux-gnueabihf, little-endian
Comment 1 Soeren Apel 2018-03-07 16:43:24 CET
Hello, can you please show us some screenshots?
Comment 2 minenofmeer 2018-03-07 17:25:15 CET
Created attachment 393 [details]
1% pre-capture
Comment 3 minenofmeer 2018-03-07 17:26:03 CET
Created attachment 394 [details]
0% pre-capture
Comment 4 minenofmeer 2018-03-07 17:35:32 CET
Created attachment 395 [details]
1% pre-capture
Comment 5 minenofmeer 2018-03-07 17:36:52 CET
Created attachment 396 [details]
0% pre-capture
Comment 6 Soeren Apel 2018-03-07 17:46:05 CET
Thanks for the files. The fact that the analog output is correct in both cases tells me that this is a driver issue, not a PV issue. I'm reassigning the bug.
Comment 7 Uwe Hermann 2018-06-15 11:50:42 CEST
*** Bug 1233 has been marked as a duplicate of this bug. ***