Rolf,
After doing a further bit of testing a bit of a chat on IRC with Uwe and
filing a bug report (as I would like this to work with my Rigol to work
as well), we eventually discovered that a bug report had already been
filed back in August 2017 and had been fixed in April 2018. I then
downloaded the latest version of the libsigrok module from the GIT
repository, compiled it and installed it.
As recommended, I tested again, first using sigrok-cli. This now
returned data from both channels that I had selected (CH1 and CH2). I
also tried CH1 and CH4 for good measure and data was also returned for
CH4. Encouraged by this I fired up PulseView and was now getting two traces.
I think it unfair to say that the Rigol is not supported. There is a
difference between 'not supported' and 'having a bug'. This has already
been fixed and the latest version of the module is available to download
and compile and should work. It must be downloaded from the GIT though,
rather than the tarball.
You didn't mention which platform you are working on? I am using it on
Linux Mint 18.3 64-bit so can so far only confirm my findings on that
platform.
Incidentallly, when I first tried using my Brymen 869s with sigrok-cli,
I kept getting a 'segmentation fault'. This turned out to be old
libraries lying around that were installed from the Linux Mint
repository. After these were completely purged and latest versions
re-installed the problem disappeared. If you had previously installed
sigrok from a repository, you might check that there is nothing old
still lying around somewhere.
The other issue I had was trying to run sigrok-cli as an ordinary user.
It worked fine when I tried running with sudo. It turned out that a udev
rule needed to be set up for sigrok to be able to access USB devices as
an ordinary user. With a bit of research I was able to derive a rule
from the examples already in the default file and test it with my meter.
Once confirmed working, the developers added it to the rule file that is
supplied by default. To be sure, I have encountered a number of issues
and experienced a degree of frustration, but all of these issues were
sorted one by one with the help of the developer community.
https://sigrok.org/wiki/Libsigrok
BTW, the UT61 is supposed to be well supported - a quick look at the
hardware support list shows 4 variants of this meter confirmed as tested
and working with sigrok. Perhaps you could share what command line
parameters are you using to query the UT61b? There appear to exist
different cables for this meter. Can you confirm which one you have. If
you are using Linux then the lsusb command should return an ID and
description.
To the sigrok devs,
How is PulseView data capture from my Rigol DS1054Z oscilloscope
supposed to work? When I click Run, a snippet of data is captured and
the capture stops after perhaps just a second. I can expand the captured
data to fit the window and the trace does then resemble what is on my
oscilloscope, but is it supposed to capture only one frame? Is it
possible to configure the number of captured frames somewhere? Or is
capture supposed to be continuous until I click Stop?
Regards.
rattenkopf <mailto:rattenko...@gmx.net>
15 June 2018 16:43
Hi John
thanks for your answer.
I likewise have a Rigol 1054Z and your comment prompted my to get the
oscilloscope out and complete the testing I was doing some time ago to
get my devices working with Sigrok. I am using the following software
versions:
libsigrok 0.5.0
libserialport 0.1.1
libsigrokdecode 0.5.0
sigrok-cli 0.7.0
sigrok-meter pre-release ?
pulseview 0.4.0
This was downloaded an complied from the Sigrok git some months ago now,
but much newer than the version used by Aleksander Alekseev as well as
those that installed by default from the Linux distro repository.
As I wrote, I compiled the newest version from the sigrok-git and have
the reported problems.
I also tried in sigrok-cli using the following command:
sigrok-cli -d rigol-ds:conn=tcp-raw/10.210.210.78/5555 --frames 1 -O
analog --channels CH1,CH2
This also returned data for only CH1, so it seems this is not a
PulseView but a rigol-ds driver issue.
So the Rigol is not really supported
I also experienced the problem you mentioned with the network connection
config not being saved and having to be re-entered.
I mean, that the connetion and device data on every start have do
reentered - so it should be either a command line parameter to pulseview
or part of a config file.
I made some notes along the way and I am happy to provide these if they
will help, but I suspect that you will have already followed the same
processes as I have.
So because the support for the rigol is unsatisfied I try to connect the
UT61b which didn't work either. An own written program has no problems,
but after a try with sigrok-cli I get a memmory error. So also this
device is not really supported.
The ka3005p could not be tested because I found no sigrok device name
after more the a hour of search. Why is the sigrok device name not
written in the corresponding wiki page???
So I am very disapointed from sigrok.
Fine regards
Rolf
John <mailto:s...@qcontinuum.plus.com>
15 June 2018 14:45
Rolf,
I likewise have a Rigol 1054Z and your comment prompted my to get the
oscilloscope out and complete the testing I was doing some time ago to
get my devices working with Sigrok. I am using the following software
versions:
libsigrok 0.5.0
libserialport 0.1.1
libsigrokdecode 0.5.0
sigrok-cli 0.7.0
sigrok-meter pre-release ?
pulseview 0.4.0
This was downloaded an complied from the Sigrok git some months ago
now, but much newer than the version used by Aleksander Alekseev as
well as those that installed by default from the Linux distro repository.
Although I was able to connect successfully using both USB and
ethernet and capture data, I experienced some of the issue you have.
For example, when connected to USB I was able to capture both
channels. When connected to the network I could only capture one
channel as you did.
I also tried in sigrok-cli using the following command:
sigrok-cli -d rigol-ds:conn=tcp-raw/10.210.210.78/5555 --frames 1 -O
analog --channels CH1,CH2
This also returned data for only CH1, so it seems this is not a
PulseView but a rigol-ds driver issue.
I also experienced the problem you mentioned with the network
connection config not being saved and having to be re-entered. When
clicking run, this seems to do something for maybe one or two seconds
which also seems consistent with what you appear to be experiencing.
This does seem to capture one frame of data - i.e equivalent to a
screen width on the oscilloscope. I'm wondering whether this is by
design although it would be useful to be able to set the number of
frames to capture. I didn't experience any crashes though although the
connection and along with it PulseView did freeze once and I had to
re-boot the oscilloscope. PulseView eventually came back with a
timeout message and a request to wait or cancel.
I know firmware is sometimes required, as it was for my generic logic
analyzer and took a little trial and error to hunt down the correct
version, although I'm not aware of such a requirement for Rigol
oscilloscopes.
I have successfully used my Brymen or Fluke DMMs with sigrok-meter but
have never considered trying them with PulseView so I can't comment on
that at present, but I will give them a go and see what happens.
I made some notes along the way and I am happy to provide these if
they will help, but I suspect that you will have already followed the
same processes as I have.
Regards.
------------------------------------------------------------------------------
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
rattenkopf <mailto:rattenko...@gmx.net>
14 June 2018 10:22
Hi,
I'm new to the mailing list and sigrok and have a lot of problems using
the programs.
I have a rigol mso1104z, a korad ka3005p and a unit-t ut61b, all devices
should be fully supported as the wiki stated.
Yesterday I compiled all sigrok programs from git (using the corr.
script) to be shure to have the newest version (get version 0.5.. for
pulseview).
My problems are:
1. I found no manual or even tipps with a simple description how to use
the cli or a gui with a device and get the features of that device -
for example for ka3005o and ut61b.
2. Pulseview mostly crashes and only shows only one wave (from a dcf77
source) and only with 20 ms hori. resolution and than stops. How can
I see more?
3. The network address and the device type needs always put in again
after restart/crash. Why can the values (IP, port, device) not be
saved and reloade - best in a config-file?
4. How can I help to make the programs or dokumentation better. I can
compile the programs with the debug-flag and run them with gdb but I
think I can't program new features (at least now).
Fine regards
Rolf
------------------------------------------------------------------------------
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
--
John
------------------------------------------------------------------------------
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
