Bug 883

Summary: "probes" dialog does not reflect device state after initial connect
Product: libsigrok Reporter: Gerhard Sittig <Gerhard.Sittig>
Component: Driver: hameg-hmoAssignee: Nobody <nobody>
Status: RESOLVED FIXED    
Severity: normal CC: soeren, stefan.bruens, uwe
Priority: Normal    
Version: unreleased development snapshot   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Gerhard Sittig 2017-01-08 13:55:49 CET 
This was observed in a Hameg HMO2524 setup:

Pulseview does not remember settings for TCP connected devices (see #882). 
Pulseview does remember settings for USB connected devices.  Upon close 
and re-start, the previous state of enabled channels and probes is retained.

For the first connect to a USB attached HMO2524, the channels' state is 
determined via SCPI queries, but does not reflect in PulseView's probes 
dialog.  Instead, all channels are enabled.  After manual adjustment, 
the state is retained across invocations (see above, for USB, not TCP).
Comment 1 Soeren Apel 2017-06-03 16:01:52 CEST 
Turns out this is a hameg-hmo issue as the channel state isn't updated when querying the device state.

Compare
http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/hameg-hmo/protocol.c#l449

with the drivers that don't show this bug:
http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/yokogawa-dlm/protocol.c#l447
http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/rigol-ds/protocol.c#l795
Comment 2 Soeren Apel 2017-12-02 18:25:44 CET 
*** Bug 1068 has been marked as a duplicate of this bug. ***
Comment 3 Uwe Hermann 2017-12-10 14:30:49 CET 
Fixed in bd70ec4b7325707a8b2f2fdf5ebf097051781c7b, thanks!