Soeren,

Once again, thanks for clarifying that. It explains then why only one frame is captured at a time. I notice that the display is a little better behaved in 0.6.0. Sometimes the autoranging did some slightly weird things whereas in this version appears to be more consistent. I look forward to the multi-frame support in a future release.

I have looked at some of the driver code for scopes some time ago while I was looking at driver examples to help me with ideas for writing a DMM driver, but scope drivers seemed on another level of complexity entirely!

Anyway, thank you for your hard work on PulseView and your kind replies.

Regards.

Soeren Apel <mailto:soe...@apelpie.net>
15 June 2018 20:55
Hello John,

I would be interested in a solution to this as well but 'm not sure I
understood your reply to this. You replied with a reference to a
large chunk of code.

The link I gave links to a particular line: 153 in this case.
I suppose it wasn't clear, so my apologies.

You can use -d to specify the device options as well as the driver.
Example:

sigrok-cli -l 5 -d lecroy:conn=tcp-raw/192.168.0.10/111
sigrok-cli -l 5 -d lecroy:conn=vxi/192.168.0.10

For USB devices, specifying only the driver is sufficient (rigol-ds
in your case). Does this make things clearer?

All the best,
  -Soeren


Having a scan through, I presume this segment is what you were
referring to, but I am struggling to see your point. There is an
option to specify a driver, but nothing about specifying a connection
IP address or a config file - unless this is what is meant by  'input
file'? If so, then what is the format of this file and what are the
parameters that can be specified? I did find some information on File
Formats, but nothing really that relates to this issue?

BTW, I have noted -c --clean which might be useful for future
reference so thanks for that.

void usage()
  142 {
  143         fprintf(stdout,
  144                 "Usage:\n"
  145                 "  %s [OPTIONS] [FILE]\n"
  146                 "\n"
  147                 "Help Options:\n"
  148                 "  -h, -?, --help                  Show help
option\n"
  149                 "\n"
  150                 "Application Options:\n"
  151                 "  -V, --version                   Show release
version\n"
  152                 "  -l, --loglevel                  Set
libsigrok/libsigrokdecode loglevel\n"
  153                 "  -d, --driver                    Specify the
device driver to use\n"
  154                 "  -D, --no-scan                   Don't auto-
scan for devices, use -d spec only\n"
  155                 "  -i, --input-file                Load input
from file\n"
  156                 "  -I, --input-format              Input
format\n"
  157                 "  -c, --clean                     Don't restore
previous sessions on startup\n"
  158                 "  -s, --log-to-stdout             Don't use
logging, output to stdout instead\n"
  159                 "\n", PV_BIN_NAME);
  160 }


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.

There is a command line parameter for this:
https://sigrok.org/gitweb/?p=pulseview.git;a=blob;f=main.cpp;h=cdc7
50aa80aade18b21916708463189c78a41f9a;hb=HEAD#l153

PV also reconnects to USB devices if you so desire. Reconnecting to
ethernet
devices is not implemented at the moment.


--
John
John <mailto:s...@qcontinuum.plus.com>
15 June 2018 20:35
soeren,

I would be interested in a solution to this as well but 'm not sure I understood your reply to this. You replied with a reference to a large chunk of code.

Having a scan through, I presume this segment is what you were referring to, but I am struggling to see your point. There is an option to specify a driver, but nothing about specifying a connection IP address or a config file - unless this is what is meant by 'input file'? If so, then what is the format of this file and what are the parameters that can be specified? I did find some information on File Formats, but nothing really that relates to this issue?

BTW, I have noted -c --clean which might be useful for future reference so thanks for that.

void usage()
 142 {
 143         fprintf(stdout,
 144                 "Usage:\n"
 145                 "  %s [OPTIONS] [FILE]\n"
 146                 "\n"
 147                 "Help Options:\n"
148 " -h, -?, --help Show help option\n"
 149                 "\n"
 150                 "Application Options:\n"
151 " -V, --version Show release version\n" 152 " -l, --loglevel Set libsigrok/libsigrokdecode loglevel\n" 153 " -d, --driver Specify the device driver to use\n" 154 " -D, --no-scan Don't auto-scan for devices, use -d spec only\n" 155 " -i, --input-file Load input from file\n"
 156                 "  -I, --input-format              Input format\n"
157 " -c, --clean Don't restore previous sessions on startup\n" 158 " -s, --log-to-stdout Don't use logging, output to stdout instead\n"
 159                 "\n", PV_BIN_NAME);
 160 }



------------------------------------------------------------------------------
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
soe...@apelpie.net <mailto:soe...@apelpie.net>
15 June 2018 17:25
Hello guys,

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

It is. The "returned data for only CH1" bug has been fixed in git:
https://sigrok.org/bugzilla/show_bug.cgi?id=1018


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.

There is a command line parameter for this:
https://sigrok.org/gitweb/?p=pulseview.git;a=blob;f=main.cpp;h=cdc750aa80aade18b21916708463189c78a41f9a;hb=HEAD#l153

PV also reconnects to USB devices if you so desire. Reconnecting to ethernet
devices is not implemented at the moment.


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.

That is very surprising. Please submit a log of your command line and
the resulting sigrok-cli output (with -l 5) to a pastebin and show it
to us. If it's a bug, it'll be fixed.


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???

It is: https://sigrok.org/wiki/Korad_KA3005P says "korad-kaxxxp",
which is the driver name you can use with "scan" or "show" to see if it
has been found at the serial port you specified.


So I am very disapointed from sigrok.

That is very unfortunate and not the experience we wish users to have.


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

------------------------------------------------------------------------------
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>
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

--
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

Reply via email to