Hi Joerg, I opened https://sigrok.org/bugzilla/show_bug.cgi?id=1149 for this issue so we can track it properly. Can you please add a complete log to the bug tracker, including a short acquisition? I'd like to know what happens with the driver at what point in time. Thanks!
-Soeren On Sat, 2018-03-31 at 18:31 +0200, Jörg wrote: > Hi Uwe, > > the bug for the default threshold is fixed in the Dslogic driver with > commit 86a1571 (api.c). > > The problem is not the driver, but Pulsview can not take over this > condition. > > Pulseview also queries values regarding -binding- in libsigrok: > > > sr: [253:34.373654] hwdriver: sr_config_get(): key 30041 (clock_edge) > sdi 0x10c02b0 cg NULL -> 'rising' > sr: [255:07.505557] hwdriver: sr_config_get(): key 30024 > (external_clock) sdi 0x10c02b0 cg NULL -> false > sr: [263:33.507641] hwdriver: sr_config_get(): key 30023 > (voltage_threshold) sdi 0x10c02b0 cg NULL -> > (1.3999999999999999, 1.39 99999999999999) > sr: [281:01.317140] hwdriver: sr_config_get(): key 30001 > (captureratio) > sdi 0x10c02b0 cg NULL -> uint64 0 > > The value 1.4 is important here. So not just the OPT list of the > driver, whose values are converted into widget element, where my > problem lies. It is not possible for me to find a name for this > element > in the source code, as it will automatically be embarrassed depending > on the ability of the driver. > > Thus, I can not find a way as with the SAMPLERATE widget (which is > definitely defined) with the set command > > > auto gvar = device->device()->config_get(ConfigKey::SAMPLERATE); > uint64_t samplerate = > Glib::VariantBase::cast_dynamic<Glib::Variant<guint64>>(gvar). > get(); > assert(!updating_sample_rate_); > updating_sample_rate_ = true; > sample_rate_.set_value(samplerate); > > > the Threshold widget via software to the default or hardware driver > value (DSlogic has already downloaded this value). > > The misconduct arises now, since the value of the threshold widget is > zero, this is again downloaded after RUN command on the HW. > > > Unfortunately, I can not get any further here because I have not > found > a way to get at the Threshold widget. > > Does anyone have a suggestion? > > Who is currently working on Pulseview on the Device Config module > (deviceoptions.cpp / binding.cpp)? > > > Thank you. > > Jörg > > > > > > > > Am Sat, 10 Feb 2018 18:28:06 +0100 > schrieb Uwe Hermann <u...@hermann-uwe.de>: > > > > > Hi, > > > > On Sun, Feb 04, 2018 at 07:08:59PM +0100, Jörg wrote: > > > > > > the latest version of "pulseview" from the Git has the threshold > > > mark L <0V H> 0V for the device driver Dreamsourcelab-DSlogic. > > > > > > I have read that in the driver is 1.5V default. > > > > > > Is this default value not read out from the driver and set by PV? > > > > This is a known bug in the libsigrok driver, see > > https://sigrok.org/bugzilla/show_bug.cgi?id=1081 > > > > Shouldn't be too hard to fix, patches welcome! > > > > > > Uwe. > > > ------------------------------------------------------------------- > ----------- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > sigrok-devel mailing list > sigrok-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sigrok-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
