Hi,
Thanks for letting us know but the wiki page isn't linking to
https://sigrok.org/download/binary/sigrok-cli/sigrok-cli-NIGHTLY-x86_64.appimage,
so I'm not quite sure where you got that link from.
The link to
https://sigrok.org/download/binary/sigrok-cli/sigrok-cli-NIGHTLY-i686-debug.appimage
Hello,
> I'm doing a first attempt at writing a decoder to capture reads from an
> EPROM and need to decode address and data. This will be quite a few pins.
> Is it possible to suggest default locations/names for each pin? When I run
> the hantek 4032 logic analyzer, the pins are labelled A0 -
Hello Chris,
Would you mind opening pull requests for these? It makes it easier for us
to see what has been included yet and what hasn't.
https://github.com/sigrokproject/libsigrok/pulls
Thanks,
-Soeren
On Thu, 2020-10-29 at 23:34 -0500, Chris Fester wrote:
> Hi all,
>
> I recently
erio
>
> On 10/29/20 5:12 PM, Doug Wegscheid wrote:
> > Valerio: a clarification:
> >
> > the device I sent you a link to works well with sigrok.
> >
> > I think Soeren is saying that the device you initially referenced does
> > NOT work with sigrok.
>
Hello Valerio,
This device is unfortunately not supported by sigrok.
>From my point of view, a generic $10 FX2-based 8ch/24MHz logic analyzer
would serve you well.
Regards,
-Soeren
On Thu, 2020-10-29 at 12:05 +0100, Valerio Messina via sigrok-devel wrote:
> hi,
> I want to snif an I2C bus
Hello,
That branch has been merged to libusb mainline in the meanwhile, see
https://github.com/libusb/libusb/issues/252
and
https://github.com/libusb/libusb/commit/d67eb5beaa44c17c09f089a522ff483f4978a978
Hence, using a libusb checkout of this commit or later should work.
Regards,
-Soeren
Merged with slight modifications in
d1b479f74c9d1eb61b56cc4980d7328ec50216df, thank you!
-Soeren
On Fri, 2020-10-09 at 15:59 +0200, Mickael Bosch wrote:
> Hi,
>
> I wanted a script to start/stop the pulseview capture.
>
> The modification uses the already implemented UNIX signal handlers to
Thanks, you two! This is what I love to see - helpful bug report, quick
turnaround time, quick reporter feedback, bug solved, everyone happy.
Awesome!
-Soeren
On Fri, 2020-10-23 at 14:48 +0200, sdbbs wrote:
> Hi Gerhard,
>
> Many thanks for the response!
>
>
> > The previous implementation
Hello Oleg,
Where did you find the information that this device is supported by sigrok?
Regards
-Soeren
On Mon, 2020-09-28 at 17:27 +0300, Oleg wrote:
> Hi, all.
>
> I bought dscope u2b20 and i have trouble - sigrok/pulseview don't see it :-).
>
> ~$ ls /usr/local/share/sigrok-firmware/
>
Hello Michael,
Thanks for your contribution! Did you see
https://sigrok.org/wiki/Protocol_decoder_HOWTO#Submitting_your_decoder ?
It would be great to at least have some samples files so we can catch future
regressions. Also, do you have documentation available? It would be great to
have a
;.
>
> Many thanks for helping with the build problem. I have to look for what
> I've got now nd how to run the self-build version.
>
>
> Best regards,
> Helge
>
>
> Am 13.09.2020 um 12:26 schrieb Soeren Apel:
> > Hello Helge,
> >
> > There's a bu
Hello Darek,
You can't find it because it's currently not implemented :)
I recently implemented math channels for analog signals, math channels for
logic signals will follow soon.
Regards
-Soeren
On Sun, 2020-09-13 at 17:58 +0200, darek wrote:
> Dear All,
> Apologies, my question is not
Hello Helge,
There's a bug report for this, using the exact same versions you use:
https://sigrok.org/bugzilla/show_bug.cgi?id=1461
It confirms my suspicion that cmake is the culprit and that updating it
will fix this. For this reason I don't consider this a PV bug but a cmake
bug.
Regards
Hello,
For that, you use the "save session setup" menu entry in the save menu.
Nonetheless, the session setup is saved along with the .sr file and has the
.pvs extension, so that setup is already saved.
Regards
-Soeren
On Wed, 2020-09-02 at 09:30 -0500, Dick Hollenbeck wrote:
> Hi,
>
>
>
Well... that's why I'm not messing with make files unless I really, really
have to. I know it's not my strong point ;)
-Soeren
On Sun, 2020-08-30 at 10:01 +0200, Wolfram Sang wrote:
> Hi Soeren,
>
> > Personally, my prefered solution would be to ask the user when uninstalling
> > as he/she is
I agree with Gerhard, the decoders dir is the place most likely changed by
users and wiping it may have unwanted consequences. Maybe a user simply
wanted to install a different version of libsrd to test a PD against, not
expecting the decoders dir to be wiped in the process.
Personally, my
Hello David,
You may want to check this thread:
https://www.mail-archive.com/sigrok-devel@lists.sourceforge.net/msg02674.html
Regards
-Soeren
On Sun, 2020-08-09 at 12:13 +0100, David Slipper wrote:
> The other day I found myself in need of looking at an 18 wire bus.
>
> Now I have a 16bit
Hello,
The Hantek 4032L supports it:
https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/hantek-4032l/api.c;h=26a9315e5035024c9559f679a950576a72246b95;hb=HEAD#l42
If you use an external clock, PV lets you specify the sample rate as it has
no way of knowing the frequency.
-Soeren
Hello,
You can check PV's about window to see where it searches for firmware
files.
Also, if you increase the log level to 5 before trying to connect to the
device, you then can go back to the log window to see what it did and where
it failed.
If you're still stuck after checking these, please
Hello,
Thanks for reaching out and wanting to contribute to our project.
Please keep in mind that using bytes to store the analog data values may work
for oszilloscopes but not for other data sources. This means we'd need to be
able to have both types of storage and PV needs to be able to
Added, thanks for contributing!
https://sigrok.org/gitweb/?p=libsigrokdecode.git;a=commit;h=397ec00dae6800d733f0efbbf430a6f8c0bed000
On Sun, 2020-07-12 at 13:58 -0700, Thomas Hebb wrote:
> Info taken from https://www.st.com/resource/en/datasheet/m24c32-w.pdf.
>
> Signed-off-by: Thomas Hebb
>
Hello Helge,
Thanks for contributing! Please see
https://sigrok.org/wiki/Protocol_decoder_HOWTO#Submitting_your_decoder
Regards
-Soeren
On Fri, 2020-07-10 at 17:45 +0200, Helge Kruse wrote:
> Hello,
>
> I have needed to decode the ISP protocol for AVR controllers.I found
> that the decoder
Hello David,
Have you considered running PV from a battery-powered laptop? That way you
can also isolate the scope from mains earth.
Regards
-Soeren
On Mon, 2020-07-06 at 19:30 +0100, David Slipper wrote:
> Hi, I have a couple of logic analysers and a Hantek 6022 scope that I use a
> lot
t;
> [1] https://sigrok.org/wiki/Korad_KAP_series
> [2] https://sigrok.org/wiki/Supported_hardware#Power_supplies
>
> Mickael
>
> On 06/06/2020 12:42, Soeren Apel wrote:
> > On Sat, 2020-06-06 at 12:27 +0200, Gerhard Sittig wrote:
> >
Hello Cedric,
This is on our road map but at the moment, no one is working on it.
Essentially, what you're asking for is "PD analog output".
Our intention was to work on PD logic output first and then analog
output afterwards. From my point of view, there's nothing really
preventing you from
On Sat, 2020-06-06 at 12:27 +0200, Gerhard Sittig wrote:
> On Sat, 2020-06-06 at 00:29 +0200, Mickael Bosch wrote:
> > [ ... yet another compatible ... ]
> >
> > The "*IDN?" output is:
> >
> > TENMA 72-2705 V6.5 SN:<8 digits SN>
> >
> > [ ... ]
> >
> > BTW, when I bought this device I thought
Hello,
Thanks for working on this!
You said you introduced SR_CONF_SAMPLERATE_COMBINED but what is its
purpose and how do you think it should be used?
PulseView at this point only supports one sample rate for all signals
and that's not going to change anytime soon, so you'll have to perform
Hello Sam,
Thanks for the change! I would appreciate if you could open a pull
request for https://github.com/sigrokproject/libsigrokdecode and
if you have .sr files that contain RGBW communication, also against
sigrok-dumps. That way, Uwe has less work to do and the project as a
whole can
Hello Fred,
You may want to check the output in the log.
You can access it from within the settings dialog.
Regards
-Soeren
On Fri, 2020-05-29 at 08:36 -0400, Fred Decker wrote:
> Hi needed to fix a bug in the DCC decoder included in Pulseview.
> Using Windows 10, I opened it in notepad++ and
Hi guys,
Quick feedback from my side: PV is certainly going to have RLE
compression implemented, by fall if things go as planned.
The biggest hurdle is maintaining the drawing performance, as Gerhard
pointed out.
-Soeren
On Tue, 2019-09-24 at 11:08 +0200, David Given wrote:
> I was in the
Hello Phill,
PulseView only supports logic analyzers and oscilloscopes at this time,
which is why other drivers are filtered out as you noticed.
If you want to use a DMM with a graphical interface, I suggest using
either
https://sigrok.org/wiki/Sigrok-meter
or
https://sigrok.org/wiki/SmuView
Hello Doug,
At the moment there isn't, so that's what I'd do as well.Except maybe
not across the entire sample range because you don't actually *know*
what the entire sample range is in the PD.
What's a suitable annotation length starting at sample #0? Yeah, I
don't know either. :)
-Soeren
On
Hello Jacques,
Sounds like a bug in automoc.
Which version of CMake do you use?
-Soeren
On Tue, 2020-05-19 at 11:24 -0400, Jacques Pelletier wrote:
> Hi,
>
> I'm trying to compile pulseview but I get error messages.
>
> "error: redefinition of ‘struct
>
Hello Doug,
Decoders usually don't output anything aside from annotations as that
would produce a lot of output for little gain to the user.
If you want to add debug messages for development purposes, you can add
print() calls as you see fit.
HTH
-Soeren
On Sun, 2020-05-17 at 02:44 +,
Hello,
https://sigrok.org/doc/pulseview/unstable/manual.html#_command_line_interface
Regards
-Soeren
On Mon, 2020-05-11 at 16:20 +, Patrick Dorion wrote:
> Hello,
>
> I can’t launch PulseView either 0.41 that worked before on this
> machine, or 0.42.
>
> Both gives me:
>
>
Hello David,
As of now, the colors are auto-generated because PV must work with any
protocol decoder in a generic way. I understand the issue you're having
and I would like to work out a way that works for you and people in
similar situations.
However, I'm currently unsure how to achieve this.
Thanks, you're right:
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/boost/boost-1.72.0-r1.ebuild#n175
I really wish they had pointed out why the heck they disable it.
I guess I'll have to file a bug in the gentoo bugzilla...
-Soeren
On Sat, 2020-04-25 at 00:10 +0200, Wolfram Sang
Thanks Wolfram, I tried patch #2 but CMake complains with an error
message I'm apparently too dumb to understand:
-- Qt version: 5.12.3
-- Looking for backtrace
-- Looking for backtrace - found
-- backtrace facility detected in default set of libraries
-- Found Backtrace: /usr/include
CMake
Hello Helge,
Is that the exact code you're running:
If so, wouldn't it need to be
def __init__(self):
pass
def decode(self, ss, es, data):
instead? Maybe that's what's confusing the python parser.
Regards
-Soeren
On Mon, 2020-04-13 at 11:13 +0200, Helge Kruse
Hello Wolfram,
Thanks for your input :)
> The latter is called a void message and declared illegal
> in the specs.
So it would make sense to emit a warning annotation if
this condition is encountered in FIND_ADDRESS?
-Soeren
On Sun, 2020-04-05 at 19:02 +0200, Wolfram Sang wrote:
> Hi,
>
> >
111
>
> RI#: 1111
>
>
> On Tuesday, March 24, 2020, 08:43:51 AM EDT, Soeren Apel <
> soe...@apelpie.net> wrote:
>
>
> ok, so the installed version of lib
that to the meter.
>
> On Tuesday, March 24, 2020, 07:47:09 AM EDT, Soeren Apel <
> soe...@apelpie.net> wrote:
>
>
> ok, so it's a serial device, which I forgot to check before.
> Serial devices are never discovered by --scan, so the device
> node must be specified o
vc920' found 0
> devices.
> sr: [00:00.132044] hwdriver: Scan of 'voltcraft-vc940' found 0
> devices.
> sr: [00:00.132249] hwdriver: Scan of 'voltcraft-vc960' found 0
> devices.
> sr: [00:00.132467] hwdriver: Scan of 'tenma-72-7730' found 0 devices.
> sr: [00:00.132681] hw
Hello Richard,
Which libsigrok version does "sigrok-cli -V" report? This lib contains
the drivers.
Please try connecting with the nightly AppImage:
https://sigrok.org/wiki/Downloads#Linux_AppImage_binaries
If that still doesn't work, you can run "sigrok-cli --scan -l 5"
and attach the log
e...@gmail.com>:
> > Thanks a lot! It worked!
> >
> > чт, 27 февр. 2020 г. в 23:04, Soeren Apel :
> > > Exactly, see
> > >
> > > https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/demo/api.c;h=3b77d40cdd36bf3f127c6bd90ef
Hello Helge,
does it work if you install libgtk2.0-dev?
I don't run Ubuntu so it's just a guess, but may be worth a try.
-Soeren
On Sat, 2020-03-14 at 17:51 +0100, Helge Kruse wrote:
> Hi,
>
> I switched to Ubuntu and tried to build sigrok as described here:
>
Hello Inessa,
While I'm sure there are use cases for this, I have to admit
that I haven't yet come across one. Which ones do you have
in mind?
Clarifying that may help figuring out which way it should go.
Regards
-Soeren
On Wed, 2020-03-04 at 13:13 +0300, Inessa Kavalenka wrote:
> Hi
Exactly, see
https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/demo/api.c;h=3b77d40cdd36bf3f127c6bd90ef132f56204b050;hb=HEAD#l452
for an example of what Fabian is refering to.
Regards
-Soeren
On Thu, 2020-02-27 at 19:12 +0100, Fabian Schwartau wrote:
> Hi,
> back then I wrote
Hello David,
to be honest, your request is a little confusing to me and it would be
nice if you could elaborate a bit.
> I am looking at modifying the DCC protocol ... Many protocol
> decoders display all frames but with some (all??) DCC controller
> hardware they continually resend the last
Hello Fabian,
> sigrok-cli is detecting my device just fine. However, Pulseview is
> not.
> I'd like to know why.
That's because PV only shows devices with a device capability of a
logic analyzer or an oscilloscope as is the case with e.g. demo:
Hello Marc,
It's unfortunate that you apparently feel that the help that was given
was unhelpful. While I wasn't involved in the discussion at hand, I'd
like to point out that we do welcome all contributors and generally try
to help them as much as time permits.
We don't ever want you to feel
Hello Helge,
Your suggested change has been performed by gsi on Oct 11th:
https://sigrok.org/w/index.php?title=Protocol_decoder_HOWTO=revision=14507=13616
Thanks!
-Soeren
On Fri, 2019-10-11 at 10:09 +0200, Helge Kruse wrote:
> Hi,
>
> In the Protocol_decoder_HOWTO page we can read:
>
> On
Hello Jessy,
A microcontroller is best suited to do this in realtime because
a PC doesn't have a native SPI interface. While sigrok does intend
to be able to do signal analysis in realtime, the python bindings
need a little love to be user-friendly. For this reason, C or C++
are the preferred
Hi Benedikt,
I saw that the current state of your HD44780 branch doesn't
yet send the image out using OUTPUT_BINARY. Can you add this
maybe?
-Soeren
On Sat, 2019-11-23 at 15:16 +0100, Soeren Apel wrote:
> Uwe, Gerhard and I are discussing the issue on IRC, so
> I suggest you join whenev
Uwe, Gerhard and I are discussing the issue on IRC, so
I suggest you join whenever you have time so we can discuss the details
of how we can make it happen.
It's just a little easier than email :)
-Soeren
On Sat, 2019-11-23 at 14:38 +0100, Soeren Apel wrote:
> Hello Benedikt,
>
>
Hello Benedikt,
> Yes, I would be interested. That sounds interesting and very useful.
> It will require a lot of work in nearly all parts of sigrok i guess,
> and sigrok-test for example.
Great! Honestly I don't think it would be too much work.
As I understand it, we only need to add a new
Hello Benedikt,
Thanks for the PD!
One thing I've always wanted to do was to show images in PV that
correspond with PD output - in other words, PD annotations in
image form.
This PD would be a great opportunity to work on this feature because
the output of the device that the PD simulates is
Hello David,
sigrok-meter is functional but there's currently no maintainer,
unfortunately.
I'm not sure why we don't provide Windows binaries for it. My
assumption is that there are two reasons:
1) it's written in python so theoretically, no binary is needed
2) no one stepped up and did it
Hello sdbbs,
> * If I establish a setup in PulseView, that uses analog channels,
> conversion to logic, and protocol decoding; and save this as an .sr
> file; - can I then use sigrok-cli to browse the decoded data in the
> .sr file?
Unfortunately not. While we do try to maintain a common feature
Hello sdbbs,
> > * Why did PulseView decide to map (U8) byte value 0x00 to -500 mV,
> > and (U8) byte value 0xFF to 500 mV? In other words, how did it
> > decide on this default range - is this documented anywhere, and can
> > I change the interpreted analog range (in volts)?
The range of the
Hello Guido,
While I appreciate the work you do, you're also creating a
lot of unnecessary mail traffic on the ML that is hard to
handle. There is no need to immediately announce every single
change you made - it's customary for contributors to continue
working on their local branches and then
Hello David,
We don't have a generic data logger driver, so a new driver would need
to be created if you want to access the device via USB. There are
plenty of drivers to draw ideas/concepts/code from in case you want to
go that route.
Alternatively, you can write an import module that can parse
software devs to use. The UI for PulseView would
> have to be overhauled to use Apple's APIs, though.
>
> I hope that helps set expectations.
>
> -Chris
>
> From: Soeren Apel
> Sent: Saturday, November 3, 2018 4:01 PM
> To: paulcrawfordgm; sigrok-devel@lists.sourc
Hello Paul,
Personally, I don't know what would be required to make PV work
on iOS and how much work that would entail. However, I assume that
there are significant differences in how devices are accessed
compared to OSX, so it's probably not a straightforward matter.
If you have an idea of how
Hello,
https://www.sump.org/projects/analyzer/ and
https://sigrok.org/wiki/Openbench_Logic_Sniffer and
https://sigrok.org/wiki/Saanlima_Pipistrello_OLS are
all FPGA-based devices using the SUMP protocol and
supported by sigrok.
>From what I understand, SUMP2 is a completely
incompatible
GDEPS})
>
> Does that help anything?
>
> Thanks,
>
> Paul
>
> > On Oct 2, 2018, at 07:17, Soeren Apel wrote:
> >
> > Hello Paul,
> >
> > > -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
> > > CMa
Hello Paul,
> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
> CMake Error at CMakeLists.txt:86 (message):
> libsigrok C++ bindings missing, check libsigrok's 'configure'
> output
> (missing dependencies?)
Did you see this? Did you check?
Regards,
-Soeren
On Tue,
Hello Albert,
I personally use 4-char tabs but it's not a requirement.
We don't enforce the 80 char rule strictly because there
are corner cases where the code is much more readable when
allowed to exceed the 80 char limit on a few lines.
Readability is king and we live in 2018 after all :)
little-endian.
> - SCPI backends: TCP, serial, USBTMC.
> - libsigrokdecode 0.6.0-git-288e22b/4:0:0 (rt: 0.6.0-git-
> 288e22b/4:0:0).
> - Libs:
> - glib 2.50.2 (rt: 2.50.2/5002:2)
> - Python 3.4.4 / 0x30404f0 (API 1013, ABI 3)
> - Host: i686-w64-mingw32.static.posix,
Hello Bill,
You have indeed come to the right place but unfortunately, all I can
say for now is that this feature is still on the to-do list. While I
do understand that demand for this is (understandably) high, there
are more pressing items that have higher priority.
Nonetheless, this feature
Hello Chris,
thanks for the report. Please attach test-suite.log, the build
unfortunately doesn't contain any helpful information.
Regards,
-Soeren
--
Check out the vibrant tech community on one of the world's most
Hello Brian,
I'd like to apologize for my late response, life does have that
nasty habit of getting in the way of fun activities :)
> I don't think my branch is the best possible way to do it, and I
> don't care if
> you don't do it exactly as I did it, but I think it is important that
> it be
Hello,
> Hopefully I'm missing something obvious...
> I have decoded some data that was captured with a logic analyzer and
> now I would like to save only the decoded data (as seen in Pulseview)
> to a file. Is there any simple way of doing this?
Currently, no. That's still on the to-do list.
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
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
Hello Ian,
I suggest you check out the changes the Saanlima folks made to support
their Pipistrello OLS:
http://pipistrello.saanlima.com/index.php?title=Welcome_to_Pipistrello#
Open_Bench_Logic_Sniffer_on_Pipistrello
http://pipistrello.saanlima.com/index.php?title=Pipistrello_as_Logic_An
alyzer
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,
Hello Vlad,
> So, as far as I understand, in terms of libsigrok an implementation
> of that would need:
>
> 1. New packet type which would carry a number of bits for each sample
> 2. Code for VCD import/export
> 3. PulseView waveform display
>
> Is this something libsigrok could have? Any
Hello Marchel,
From my point of view, increasing the timeout is the wrong approach.
The reason for this is that no user is going to be willing to wait
this long to see data. Even if the sigrok client (e.g. PV) would tell
the user that it's busy fetching data, users won't expect this to take
On Fri, 2018-01-26 at 11:26 +, Chris Obbard wrote:
> >
> > Heck, Cypress even has a datapump
> > demo firmware for the FX3 written already. It's all there.
> >
> > https://github.com/esden/bitmagic is what I'm betting on because he
> > has commercial interest. It's obvious that such a design
Hello folks,
> Wouldn't it be better to invest more time in support for existing
> logic analyzers? Features like memory compression support for
> pulseview would help the project a lot more in my opinion.
No, because frankly, what's currently out there is crap.
Using an FPGA as a front-end
Hi Wolram,
> > insist that DreamsSource labs is not an ethical company since they
> > treated (and still treat) the sigrok project like shit.
>
> Didn't know that, but really good to know! Uwe Bonnes pointed to the
> same direction. Any pointers for details?
It's been a while and I'm not aware
Hi Wolfram and Chris,
Chris, you asked for an ethical company and for a product that
you can recommend to colleagues. In this case, I must strongly
insist that DreamsSource labs is not an ethical company since they
treated (and still treat) the sigrok project like shit.
Hence, I strongly advice
Hello Brian,
I agree with you about the discussion, it's always nice to realize that
we essentially have the same goals :)
I haven't yet looked at the ticklegends commit in depth, only saw that
it's relatively small. Will do as you suggested.
> I think we agree on the undesirability of having
Hi Sylvain,
as mentioned on IRC, we'd prefer to adapt the driver to silently
deal with this problem instead of requiring user intervention.
What I mean is that the leading "*IDN " from the response can simply
be removed when it is encountered. Since the COMM_HEADER setting is
set by the driver
Hi Jason,
> Here is a set of four scripts I use to manipulate the two 8-channel
> srzip files into one 16-channel srzip of GPIB data.
>
> https://github.com/pepaslabs/gpib-spy/tree/master/pulseview-scripts
Thanks a lot :)
Can we add them to our sigrok-util repo?
> I've just received a
Hi Jason,
> I gave this a shot, but something went wrong (Pulseview gives a
> "generic / unspecified" error when I try to open up the resulting zip
> file).
libsigrok complains:
session-file: Not a sigrok session file: no version found.
This is because the "out" folder is used within the .sr
etermines the number of bits sigrok expects per sample, so if
you increase the number of bits from 8 to 16, it'll read two
bytes per sample instead of one.
Then, all you need to do is to mux those binary "logic-1" files.
Regards,
-Soeren
>
> Thanks again,
> Jason
>
>
Hi David,
while we certainly do appreciate the bug reports, we'd prefer
if you could file them with our bug tracking system at
http://sigrok.org/bugzilla/
This way, we can track it better.
All the best,
-Soeren
On Fri, 2017-05-26 at 12:48 -0700, David C. Wiens wrote:
> PulseView is not
Hi Mickael,
> I found this project interesting so I bought
> a sigrok compatible logic analyser "Open Bench Logic Sniffer" and
> oscilloscope "Sainsmart DDS-120".
That's a lot of faith you put into a project that you didn't know :)
Thanks for the trust!
> The oscilloscope works well with
Hi Roman,
like I said before: this is not a bug and the reason you receive
compiler errors is because your libsigrok is too old. Please
update your libsigrok installation. If you installed from git then
please make sure that no older installations performed by a
packet management system remain.
Hi Robert, hi Alex,
since logic data isn't stored per-channel but per-sample,
we in this case have 16 bit-sized samples. Repeat that
for 10^6 samples for 4 minutes and we end up with 458MiB
of raw data. I think that's manageable.
The issue with PV is that for simplicity in the implementation,
it
Hi Robert,
> gcc -Wall -o "using-libserialport" "using-libserialport.c" -pthread
I don't see the inclusion of the actual library there.
Please go to Build->Set Build Commands, add "-lserialport" to
the command line and try again.
That should work if you installed the library system-wide.
If
Hi Benjamin,
> The device seems to be added in commit 2f4b0f6 (Jul 2016)
> Not sure if it release yet (I use the ubuntu built; no custom ppa
> added)
>
> It did not work for me I am new to sigrok I might do something wrong.
> Here what I've done:
> I just plug in the device and fiddle around
Hi Pettu,
thanks for the fixes, it's always nice if others help out =)
> diff --git a/pv/mainwindow.cpp b/pv/mainwindow.cpp
> index f7c4712..9e82fc8 100644
> --- a/pv/mainwindow.cpp
> +++ b/pv/mainwindow.cpp
> @@ -269,8 +269,8 @@ void
> MainWindow::remove_session(shared_ptr session)
>
>
Hi Paul,
> I just started using Pulseview 0.4.0 with a clone USBee AX Pro 8
> channel digital input. Everything seems to work fine and thank you
> for providing this software.
Thanks for using it!
> When I looked at the channel colours I noticed that they had gone
> back to the default
t; On Thu, Oct 27, 2016, at 09:56 PM, Soeren Apel wrote:
> >
> > Hi Anthony,
> >
> > without checking versions, my assumption is that the
> > libsigrok version is too old. Support for the HC device
> > was added in early 2016, which was after the last
> > o
Hi Anthony,
without checking versions, my assumption is that the
libsigrok version is too old. Support for the HC device
was added in early 2016, which was after the last
official release. This means that in order to use it,
you'll either have to try the PPAs (see wiki) if your
distribution
Hi Daniel,
thanks for the PD!
Do you have sample measurements (.sr) that we can add
to the sigrok-dumps repository? We use them to verify
correct operation of the PD when making changes.
All the best,
-Soeren
On Sat, 2016-10-15 at 19:10 +0200, trilader wrote:
> Hi.
>
> I've written a basic
Hi Boris,
thanks for continuing the work Uffe has done! It's highly
appreciated. We wouldn't want to leave FreeBSD behind :)
@Uffe: I thank you as well!
All the best,
-Soeren
On Wed, 2016-10-12 at 01:28 +0300, Boris Samorodov wrote:
> Hi All,
>
> I'm new to the list. I've just adopted some
1 - 100 of 126 matches
Mail list logo
