Soeren,
Ok, lets try replying to the correct message
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 v
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 forw
Soeren,
Thanks for the clarfication. Since the code was from PulseView, I
gathered from your examples that the same command format following the
-d could be used with PulseView. However, on tring it I found that my
PulseView (0.4.0) did not support the '-d' option:
$ pulseview -d rigol-ds:co
Hello John,
> 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 the
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 t
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
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
downl
On Freitag, 15. Juni 2018 17:43:12 CEST rattenkopf wrote:
> Hi John
> So I am very disapointed from sigrok.
and I am very disappointed by your tone and behaviour.
Sigrok is a community effort. All developers are doing this in their spare
time. None of the developers is earning any money with th
Hello guys,
I also tried in sigrok-cli using the following command:
sigrok-cli -d rigol-ds:conn=tcp-raw/10.210.210.78/ --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
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
>
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
libsigrok
Hi Aleksander,
many thanks for your fast answer.
> I had a similar experience with Rigol DS1054Z and other devices. Sadly not
> all Sigrok's wiki pages are up to date, you have to check the bugtracker as
> well.
There is nothing said about this on the wiki!
At least I bought the rigol because it w
Hello Rolf,
I had a similar experience with Rigol DS1054Z and other devices. Sadly not
all Sigrok's wiki pages are up to date, you have to check the bugtracker as
well. Here is the list of devices that I know for sure are well supported:
* https://sigrok.org/wiki/Noname_Saleae_Logic_clone
* https
13 matches
Mail list logo
