Bug 1026

Summary: CSV output adds 'analog' output to top of file.
Product: libsigrok Reporter: JF <sigrok.org>
Component: Output: csvAssignee: Nobody <nobody>
Status: RESOLVED FIXED    
Severity: normal CC: Gerhard.Sittig, rosendeh, sigrok, soeren
Priority: Normal    
Version: 0.5.2   
Target Milestone: ---   
Hardware: All   
OS: All   
Attachments: Sample csv output.

Description JF 2017-09-07 00:45:20 CEST
Created attachment 326 [details]
Sample csv output.

CSV output adds 'analog' output to top of file.

Tested on latest git versions on both my Pi and Windows machines (compiled myself and nightly builds, respectively).

Test device: Hantek 6022be.

Snipped output:

; CSV generated by libsigrok 0.6.0-git-393375e
; from Hantek 6xxx on Wed Sep 06 18:17:39 2017
; Channels (2/2): CH1, CH2
; Samplerate: 100 kHz
CH1: 2.19 V
CH1: 2.15 V
CH1: 2.15 V
...
CH1: 0.72 V
microseconds,V,V
10,2.18627,2.5
20,2.14706,2.40196
...


Sample csv attached.
Comment 1 Gerhard Sittig 2017-09-17 12:18:59 CEST
The issue is worse.  The analog channel will not reliably be added to the 
top of the output, it's rather that multiple analog channels as well as 
mixed signals (digital and analog at the same time) will occur in arbitrary 
interleaved ways, and won't be ordered appropriately at all.  According to 
inline comments, the current version implements some assumptions that don't 
hold.
Comment 2 Uwe Hermann 2018-04-21 15:57:27 CEST
*** Bug 1161 has been marked as a duplicate of this bug. ***
Comment 3 Uwe Hermann 2018-04-23 23:22:31 CEST
*** Bug 1131 has been marked as a duplicate of this bug. ***
Comment 4 HoracioDos 2018-10-17 00:31:49 CEST
Hello!
Any news on this issue?
Thanks!
Comment 5 sigrok 2020-08-19 18:12:40 CEST
this issue is still present (0.8.0-git-0e2f95c) and affects also released versions (0.5.2)
Comment 6 sigrok 2020-08-19 18:14:00 CEST
(In reply to sigrok from comment #5)
> this issue is still present (0.8.0-git-0e2f95c)

I meant 0.6.0-git-d7df9dc7
Comment 7 Gerhard Sittig 2020-08-19 19:29:08 CEST
Sure, and this status won't change as long as nobody is working on that 
subject. It's apparent that none of those who use the CSV output feature 
got enough interest to do something about the known issue. Want to help? 
Lend a hand! Or wait until somebody else starts acting. See comment 1, 
the current implementation is incomplete, and needs some love.
Comment 8 Gerhard Sittig 2020-08-22 19:30:41 CEST
Have committed something in 98b7b0895659 to eliminate the unexpected 
screen output with fallback data in the CSV output text. Which addresses 
this report here in its strictest sense, but does not address the issues 
mentioned in comment 1.

Have decided to create a separate report in bug 1592 for the remaining lack 
of support for some combinations of input data. Am closing this bug 1026.