You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
(9) |
May
(20) |
Jun
(1) |
Jul
|
Aug
(8) |
Sep
(8) |
Oct
|
Nov
|
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(25) |
Feb
(1) |
Mar
(14) |
Apr
(12) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
(8) |
Nov
(14) |
Dec
(3) |
2012 |
Jan
|
Feb
(13) |
Mar
(17) |
Apr
(32) |
May
(22) |
Jun
(35) |
Jul
(56) |
Aug
(16) |
Sep
(8) |
Oct
(26) |
Nov
(30) |
Dec
(29) |
2013 |
Jan
(23) |
Feb
(19) |
Mar
(9) |
Apr
(39) |
May
(30) |
Jun
(23) |
Jul
(33) |
Aug
(7) |
Sep
(13) |
Oct
(40) |
Nov
(91) |
Dec
(43) |
2014 |
Jan
(59) |
Feb
(37) |
Mar
(28) |
Apr
(43) |
May
(37) |
Jun
(21) |
Jul
(56) |
Aug
(43) |
Sep
(44) |
Oct
(102) |
Nov
(31) |
Dec
(48) |
2015 |
Jan
(111) |
Feb
(114) |
Mar
(36) |
Apr
(59) |
May
(19) |
Jun
(17) |
Jul
(13) |
Aug
(36) |
Sep
(24) |
Oct
(43) |
Nov
(66) |
Dec
(39) |
2016 |
Jan
(41) |
Feb
(33) |
Mar
(21) |
Apr
(54) |
May
(48) |
Jun
(34) |
Jul
(42) |
Aug
(73) |
Sep
(31) |
Oct
(115) |
Nov
(41) |
Dec
(48) |
2017 |
Jan
(31) |
Feb
(32) |
Mar
(23) |
Apr
(20) |
May
(70) |
Jun
(26) |
Jul
(17) |
Aug
(22) |
Sep
(15) |
Oct
(14) |
Nov
(20) |
Dec
(4) |
2018 |
Jan
(45) |
Feb
(27) |
Mar
(16) |
Apr
(54) |
May
(30) |
Jun
(50) |
Jul
(25) |
Aug
(5) |
Sep
(7) |
Oct
(60) |
Nov
(75) |
Dec
(21) |
2019 |
Jan
(18) |
Feb
(14) |
Mar
(17) |
Apr
(15) |
May
(17) |
Jun
(9) |
Jul
(12) |
Aug
(11) |
Sep
(22) |
Oct
(30) |
Nov
(19) |
Dec
(18) |
2020 |
Jan
(29) |
Feb
(12) |
Mar
(54) |
Apr
(51) |
May
(50) |
Jun
(50) |
Jul
(34) |
Aug
(29) |
Sep
(54) |
Oct
(77) |
Nov
(26) |
Dec
(16) |
2021 |
Jan
(71) |
Feb
(22) |
Mar
(63) |
Apr
(15) |
May
(23) |
Jun
(30) |
Jul
(23) |
Aug
(15) |
Sep
(5) |
Oct
(12) |
Nov
(7) |
Dec
(5) |
2022 |
Jan
(44) |
Feb
(33) |
Mar
(16) |
Apr
(5) |
May
(9) |
Jun
(13) |
Jul
(7) |
Aug
(34) |
Sep
(22) |
Oct
(5) |
Nov
(31) |
Dec
(33) |
2023 |
Jan
(15) |
Feb
(3) |
Mar
(9) |
Apr
(20) |
May
(50) |
Jun
(6) |
Jul
(6) |
Aug
(6) |
Sep
(4) |
Oct
(7) |
Nov
(7) |
Dec
(6) |
2024 |
Jan
(8) |
Feb
(10) |
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Gerhard S. <ger...@gm...> - 2020-06-23 21:27:20
|
On Sun, 2020-06-21 at 00:02 +0200, Walter Goossens wrote: > > my korad ka3005p reports itself as being v5.5 and with this patch I > can use it with smuview. > > It is also available at my github: https://github.com/wgoossens/libsigrok/tree/feature/korad-ka3005p-v5.5 Merged in 8b58a519e4d9, thanks! virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. |
From: Walter G. <cre...@gm...> - 2020-06-20 22:02:21
|
Hi all, my korad ka3005p reports itself as being v5.5 and with this patch I can use it with smuview. It is also available at my github: https://github.com/wgoossens/libsigrok/tree/feature/korad-ka3005p-v5.5 Walter Goossens |
From: Christian M. <os...@c-...> - 2020-06-20 21:09:42
|
Hello Marcel, thanks for your answer. It's great that I reached you with the mail. On 19/06/2020 08:16, marchelh wrote: > Hi Christian, > > I'm the author of the current implementation of the Siglent device > driver. So maybe I can help finding the issue, also I have a almost > direct path to Siglent engineering, and I'm able to ask direct questions > when I have problems. I didn't read the complete message back but what I > understand is that the device does not responde with the correct > identification? Or does some functionality not work? The device identifies itself with "SDS2000X Plus". I attached the patch from my first mail again. With that patch I get some data but after some samples (between half and two thirds of the data on the scope screen) I only get a bit of noise and Sigrok hangs. > If the device > identification string is not recognized, than probably adding the device > specific string in the list should work, however, it is possible that > some of the properties that get set in this area need to be set for the > 2000 Plus. I will have a look this weekend if I can find, based on the > spec sheet, if there are any properties that need attention. I assume that one of the first problems is to get the values for the fields in the structures right. The big problems are - max_timebase in struct siglent_sds - min_vdiv in struct siglent_sds - min_timebase in siglent_sds_model I'm not sure why these fields are arrays with two values each and I haven't started reading the code yet to find that out. > > Kind regards, > Marcel. > > P.S. The Siglent devices have some quirks that some responces are slow, > specially the older series. Als due to program memory limitations, not > all advertised functions are available at API level. I have made some > notes on that on the compatibility sheet of SigRok. Noted. From what I've seen the SDS2000X seemed quite fast. I haven't had a really slow operation or response yet. But I haven't checked too much on the network interface yet. Best regards Christian > > > > -------- Oorspronkelijk bericht -------- > Van: Gerhard Sittig <ger...@gm...> > Datum: 07-06-2020 22:15 (GMT+01:00) > Aan: sig...@li... > Onderwerp: Re: [sigrok-devel] Siglent SDS2000X Plus series > > On Sun, 2020-06-07 at 16:40 +0200, Christian Mauderer wrote: >> >> I had already a short look at the structure definitions when adding this >> but some haven't been clear without some further analysis. Therefore I >> hoped that I would reach someone via the mailing list who has experience >> with Siglent devices and maybe still has some notes from an earlier >> port. That would be a better starting point. Analyzing the code without >> that was my second best option after that. > > Take my words with a grain of salt. And there are more than five > people on the mailing list AFAIK. :) Let's see what others can > say. Perhaps the author of the current Siglent SDS support is > around as well. May just take a few days to respond perhaps. > > > virtually yours > Gerhard Sittig > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > |
From: Uwe H. <uw...@he...> - 2020-06-20 16:33:31
|
Hi, On Mon, Jun 08, 2020 at 08:58:57PM -0700, Anatol Pomozov wrote: > Fixes bug #1526 Merged and closed bug, thanks a lot! Uwe. -- http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org |
From: marchelh <mar...@gm...> - 2020-06-19 06:16:19
|
Hi Christian,I'm the author of the current implementation of the Siglent device driver. So maybe I can help finding the issue, also I have a almost direct path to Siglent engineering, and I'm able to ask direct questions when I have problems. I didn't read the complete message back but what I understand is that the device does not responde with the correct identification? Or does some functionality not work? If the device identification string is not recognized, than probably adding the device specific string in the list should work, however, it is possible that some of the properties that get set in this area need to be set for the 2000 Plus. I will have a look this weekend if I can find, based on the spec sheet, if there are any properties that need attention. Kind regards,Marcel. P.S. The Siglent devices have some quirks that some responces are slow, specially the older series. Als due to program memory limitations, not all advertised functions are available at API level. I have made some notes on that on the compatibility sheet of SigRok. -------- Oorspronkelijk bericht --------Van: Gerhard Sittig <ger...@gm...> Datum: 07-06-2020 22:15 (GMT+01:00) Aan: sig...@li... Onderwerp: Re: [sigrok-devel] Siglent SDS2000X Plus series On Sun, 2020-06-07 at 16:40 +0200, Christian Mauderer wrote:>> I had already a short look at the structure definitions when adding this> but some haven't been clear without some further analysis. Therefore I> hoped that I would reach someone via the mailing list who has experience> with Siglent devices and maybe still has some notes from an earlier> port. That would be a better starting point. Analyzing the code without> that was my second best option after that.Take my words with a grain of salt. And there are more than fivepeople on the mailing list AFAIK. :) Let's see what others cansay. Perhaps the author of the current Siglent SDS support isaround as well. May just take a few days to respond perhaps.virtually yoursGerhard Sittig-- If you don't understand or are scared by any of the above ask your parents or an adult to help you._______________________________________________sigrok-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Timo K. <tj...@ik...> - 2020-06-18 20:42:15
|
SCPI framework is really nice, but currently it cannot be used with a rather large group of instruments that support "SCPI like" protocols (that are not fully SCPI compliant). I'd like to propose generic "quirks" support to SCPI framework to allow using this excellent framework in drivers for devices that aren't fully SCPI compliant. I'm proposing adding "quirks" variable in sr_scpi_dev_inst struct that contains bitmap of various flags for quirks. This way a hardware driver can enable quirks if needed, and SCPI code can be kept clean and readable while still supporting devices not conforming to standards. This should reduce the need for basically "re-implementing" what SCPI framework already can do in countless drivers for devices that implement only subset of SCPI protocol, etc... This initial implementation is based on adding Siglent (SPD3303C/X/X-E) PSU support to scpi-pps driver. (I also have GW-Instek 8200A series support added to scpi-dmm driver that would also need additional quirk to integrate cleanly...) (https://github.com/sigrokproject/libsigrok/commit/ca3de968497e6b0e890af74cdd26ca4d43c1178a) diff --git a/src/scpi.h b/src/scpi.h index 312f5e8a..7e55c9f3 100644 --- a/src/scpi.h +++ b/src/scpi.h @@ -75,6 +75,12 @@ enum scpi_transport_layer { SCPI_TRANSPORT_VXI, }; +enum scpi_quirks { + SCPI_QUIRK_CMD_OMIT_LF = (1 << 0), + SCPI_QUIRK_OPC_UNSUPPORTED = (1 << 1), + SCPI_QUIRK_SLOW_CHANNEL_SELECT = (1 << 2), +}; + struct scpi_command { int command; const char *string; @@ -113,6 +119,7 @@ struct sr_scpi_dev_inst { uint64_t firmware_version; GMutex scpi_mutex; char *actual_channel_name; + uint32_t quirks; }; SR_PRIV GSList *sr_scpi_scan(struct drv_context *drvc, GSList *options, diff --git a/src/scpi/scpi.c b/src/scpi/scpi.c index 2477cf23..b0fa4ed5 100644 --- a/src/scpi/scpi.c +++ b/src/scpi/scpi.c @@ -157,8 +157,10 @@ static int scpi_send_variadic(struct sr_scpi_dev_inst *scpi, /* Allocate buffer and write out command. */ buf = g_malloc0(len + 2); sr_vsprintf_ascii(buf, format, args); - if (buf[len - 1] != '\n') - buf[len] = '\n'; + if (!(scpi->quirks & SCPI_QUIRK_CMD_OMIT_LF)) { + if (buf[len - 1] != '\n') + buf[len] = '\n'; + } /* Send command. */ ret = scpi->send(scpi->priv, buf); @@ -819,6 +821,11 @@ SR_PRIV int sr_scpi_get_opc(struct sr_scpi_dev_inst *scpi) unsigned int i; gboolean opc; + if (scpi->quirks & SCPI_QUIRK_OPC_UNSUPPORTED) { + g_usleep(SCPI_READ_RETRY_TIMEOUT_US); + return SR_OK; + } + for (i = 0; i < SCPI_READ_RETRIES; i++) { opc = FALSE; sr_scpi_get_bool(scpi, SCPI_CMD_OPC, &opc); @@ -1266,6 +1273,8 @@ SR_PRIV int sr_scpi_cmd(const struct sr_dev_inst *sdi, ret = scpi_send(scpi, channel_cmd, channel_name); if (ret != SR_OK) return ret; + if (scpi->quirks & SCPI_QUIRK_SLOW_CHANNEL_SELECT) + g_usleep(100 * 1000); } va_start(args, command); @@ -1311,6 +1320,8 @@ SR_PRIV int sr_scpi_cmd_resp(const struct sr_dev_inst *sdi, ret = scpi_send(scpi, channel_cmd, channel_name); if (ret != SR_OK) return ret; + if (scpi->quirks & SCPI_QUIRK_SLOW_CHANNEL_SELECT) + g_usleep(100*1000); } va_start(args, command); Does this approach sound ok? (it would seem like existing code has support for some specific "quirks" already but it likely would be easier to maintain having quirks only enabled if needed) Initia Siglent SPD3303 support for scpi-pps driver: https://github.com/tjko/libsigrok/tree/siglent-scpi -- Timo <tj...@ik...> |
From: Merlijn W. <me...@wi...> - 2020-06-15 21:49:36
|
Hi Wolfram, Thanks for the reply -- see inline. On 14/06/2020 13:27, Wolfram Sang wrote: > Hi Merlijn, > >> My question is -- what would the best way to integrate support in the >> korad-kaxxxxp driver? Some flag to enable quircks for this device? > > I'd go this way. If the rest of the protocol is largely the same, it > makes sense to me to have a quirk to fix up the in/out communication and > then proceed as normal. Ok - will attempt to write up a "proper" patch somewhere next week. >> I know all of this seems ridiculous and makes me seem like a fool, but I've > > Why should you be seen as a fool? :) I can easily imagine the > manufacturer broke it. I have seen much worse [1]. Admittedly, that one is pretty bad. Perhaps a accurate way to say that is: it took me some time to realise I was not going crazy. :-) >> Sniffing with portmon.exe on Windows shows the same behaviour, so this is not a >> Linux driver bug or a WINE bug, as far as I can tell. > > Sounds reasonable to me. Ok, thanks! Cheers, Merlijn |
From: Timo K. <tj...@ik...> - 2020-06-15 04:30:48
|
On Thu, Jun 4, 2020 at 10:19 AM Gerhard Sittig <ger...@gm...> wrote: > > > If you want to help, review and extend the test sequence for the > > > endianess conversion. Getting more coverage is highly desirable. Current tests look very comprehensive. Only one thing came to mind, maybe the "test_endian_write_inc" test should also test the write_u16le_inc/write_u32le_inc functions? > And I like how you keep improving that device's driver from the > feedback that you get. Will be a nice one when integrated into > mainline, which no doubt is going to happen AFAICS. :) I cleaned up the driver bit more (no more sending struct to device) and added support for the device "address" (that likely is almost always unused, but someone might have multiple loads and have use for it...). I can't think of anything to add to it at this point. I opened pull request via github: https://github.com/sigrokproject/libsigrok/pull/69 -- Timo <tj...@ik...> |
From: JULIO A. <jca...@gm...> - 2020-06-14 16:00:23
|
i want to share the dumps for the Padded Jittering Data Link PJDL V4.1 used in Pjon Comm protocol. https://github.com/jcallano/sigrok-dumps/tree/master/pjonSWBB I will try to develop a decoder for this protocol. |
From: Wolfram S. <ws...@th...> - 2020-06-14 11:45:50
|
Hi Merlijn, > My question is -- what would the best way to integrate support in the > korad-kaxxxxp driver? Some flag to enable quircks for this device? I'd go this way. If the rest of the protocol is largely the same, it makes sense to me to have a quirk to fix up the in/out communication and then proceed as normal. > I know all of this seems ridiculous and makes me seem like a fool, but I've Why should you be seen as a fool? :) I can easily imagine the manufacturer broke it. I have seen much worse [1]. > Sniffing with portmon.exe on Windows shows the same behaviour, so this is not a > Linux driver bug or a WINE bug, as far as I can tell. Sounds reasonable to me. Kind regards, Wolfram [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f076ef44a44d02ed91543f820c14c2c7dff53716 |
From: Merlijn W. <me...@wi...> - 2020-06-14 10:52:51
|
Hi Geert, others, On 21/05/2020 14:22, Geert Stappers wrote: > On Tue, May 19, 2020 at 02:21:58PM +0200, Merlijn Wajer wrote: >> The follow patch adds support for the Velleman LABPS3005DN device that I >> acquired about a month ago. The protocol is slightly different from all the >> other korad-kaxxxxp devices. Most notably, the device requires '\n' to be sent >> literally (0x5c, 0x6e) - not sure how they let that happen. > > http://thedailywtf.com/submit-wtf > > For those who are not familiar with the The Daily WTF > > The Daily WTF is your how-not-to guide for developing software. We > recount tales of disastrous development, from project management gone > spectacularly bad to inexplicable coding choices. > > Example article https://thedailywtf.com/articles/destination-undefined I'll consider doing it, could be fun indeed. Now to the less fun but more rewarding -- any other thoughts from you or anyone else, regarding my patch? I'd like to get support in sigrok somehow. Maybe a command line switch to switch it into this mode, or a new driver (even though most of the code will remain the same...?) Cheers, Merlijn |
From: Soeren A. <so...@ap...> - 2020-06-13 07:15:52
|
Hello Mickael, Please join us on #sigrok on freenode to get a wiki account, that's where the bot resides. As for the CLI switch... it would require a driver API change so that all drivers can make use of it. I'm not 100% sure what would be the best way to approach this, so doing this as a proof-of-concept for one driver might be a good base for further discussion. -Soeren On Sat, 2020-06-06 at 23:53 +0200, Mickael Bosch wrote: > >> if users > >> want the information to be available, and up-to-date. Waiting for > >> somebody else to do it all (and do stuff they don't even know > >> about) won't result in much progress. > > I agree. May I have a wiki account to add the TENMA_72_2705_V65 in the > wiki? My point was to say that the devices listed in the Korad KAxxxxP > series page [1] should be in the main supported hardware page [2] > because (presumably a lot of people and) I see no relation between a > Korad product and a Tenma product at a first glance. > > Soeren, I like the CLI switch improvement. If I understand it correctly, > all libsigrok/hardware/*/api.c should be modified to comply with it? > > [1] https://sigrok.org/wiki/Korad_KAxxxxP_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: > > > 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 I would have to write a > > > > complete driver. I had a good surprise when I saw that the > > > > korad-kaxxxxp driver already does all the hard stuff. That said, do > > > > you think that listing *all* known compatible devices in [2] would > > > > help sigrok newbies like me and show that sigrok rules? > > > > > > Here is the trick question: Can you enumerate all known > > > compatible devices, and tell whether they are operational, > > > without having access to them? Can you tell how to determine the > > > devices' capabilities or limits in advance, and how they may or > > > may not identify themselves? That may answer the question whether > > > the project is able to provide the support out of the box for > > > devices they don't know about in the first place ... :) > > > > My take on it is this: how can users verify whether a device works or > > not if they *must* alter the source code first and compile everything > > from scratch? That's not helping, honestly. > > > > What I would wish for is a command-line switch that allows users to > > forego the whitelisting in the drivers and force a particular driver to > > use a particular (USB) device to be a particular model. That way, users > > wouldn't need to alter the source code. > > > > Alas, none of us have the time to work on that, I reckon. > > > > -Soeren > > > > > > > > > Which means that it does take the users' reports of their > > > existance and whether they work, before support can be claimed. > > > Also users participating in wiki updates is required, if users > > > want the information to be available, and up-to-date. Waiting for > > > somebody else to do it all (and do stuff they don't even know > > > about) won't result in much progress. > > > > > > > > > virtually yours > > > Gerhard Sittig > > > -- > > > If you don't understand or are scared by any of the above > > > ask your parents or an adult to help you. > > > > > > > > > _______________________________________________ > > > sigrok-devel mailing list > > > sig...@li... > > > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > > > > > > _______________________________________________ > > sigrok-devel mailing list > > sig...@li... > > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Soeren A. <so...@ap...> - 2020-06-11 10:20:02
|
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 working on analog output already. Uwe and I worked on logic output, here's the last working state: https://github.com/abraxa/libsigrokdecode/commits/master https://github.com/abraxa/pulseview/commits/srd_output_logic Those two already work together but it's more of a proof-of-concept than something I'd want to see merged because the sample data is handled in a very inefficient manner. That's independent of the supporting architecture, however. >From my point of view, the more important part is the handling in libsigrokdecode because I can assist you with the PV side if you have issues there. I do however not know how Uwe envisions the analog output to look like API-wise on libsrd because there are certain considerations to be made. Maybe he'll chime in but for me, even being able to send *anything* over to PV would already be a big step forward. Adding the remaining features like measurement units would be straightforward at that point. There is however one constraint you should know about: the sample rates of libsrd input and output data *must* be the same. I would highly suggest you join us on #sigrok on freenode if you want to work on this so we can align better and answer any questions you may have. -Soeren On Thu, 2020-06-11 at 09:09 +0000, C.R...@lu... wrote: > Hi all, > > I am building a motor controller. It works by measuring the speed > from an encoder signal, running a PID loop, and generating a PWM > signal to drive the motor. > > I would like to fine-tune the PID loop. Therefore I'm looking for a > way to generate graphs on my screen that show me the speed and the > WPM duty cycle. > > I'm looking at Pulseview. I can use the Stepper motor protocol > decoder to convert the encoder pulses to speed numbers. I can also > use the PWM protocol decoder to convert PWM pulses to Duty Cycle > numbers. > > Now I'm looking to plot these two numbers as lines. > > I've made a mock-up (see the attachment). The top signals are the > digital signals from the PWM output (D0) and the encoder input (D1). > In the middle there are 2 protocol decoders, Stepper motor and PWM. > At the bottom are 2 lines that plot the numbers collected by the > protocol decoders in the middle. > > Is something like this possible? > Where do I begin if I want to make this happen? > > Cheers, > Cedric > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: <C.R...@lu...> - 2020-06-11 09:33:31
|
Hi all, I am building a motor controller. It works by measuring the speed from an encoder signal, running a PID loop, and generating a PWM signal to drive the motor. I would like to fine-tune the PID loop. Therefore I'm looking for a way to generate graphs on my screen that show me the speed and the WPM duty cycle. I'm looking at Pulseview. I can use the Stepper motor protocol decoder to convert the encoder pulses to speed numbers. I can also use the PWM protocol decoder to convert PWM pulses to Duty Cycle numbers. Now I'm looking to plot these two numbers as lines. I've made a mock-up (see the attachment). The top signals are the digital signals from the PWM output (D0) and the encoder input (D1). In the middle there are 2 protocol decoders, Stepper motor and PWM. At the bottom are 2 lines that plot the numbers collected by the protocol decoders in the middle. Is something like this possible? Where do I begin if I want to make this happen? Cheers, Cedric |
From: Arno M. <au...@fa...> - 2020-06-09 20:17:08
|
HI, I made a pull request for the SPDIF decoder in January (Pull request #26). Until now nothing happened. There is no response and I don't know if I made a mistake and the pull request is not really visible on your side. Or will the pull requests sometime be evaluated in a certain time slot? I'm curious. Regards Arno |
From: Anatol P. <ana...@gm...> - 2020-06-09 03:59:25
|
bindings/swig/doc.py generates a swig interface file for ruby bindings that includes docstrings with comments braces ( /* and */ ) like this: %feature("docstring") sigrok::Channel::type "/* Type of this channel. */\n"; %feature("docstring") sigrok::Channel::enabled "/* Enabled status of this channel. */\n"; SWIG generates *.cxx and adds its own braces to the docstring: /*/* Document-class: Sigrok::Error Exception thrown when an error code is returned by any libsigrok call. */ */ this causes compilation error for Ruby bindings. To fix the error we should not add extra braces to the docstring. With this patch libsigrok compiles fine with with ruby 2.7 and swig 4.0.2. Fixes bug #1526 Signed-off-by: Anatol Pomozov <ana...@gm...> --- bindings/swig/doc.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/bindings/swig/doc.py b/bindings/swig/doc.py index e8767af8..182f5477 100644 --- a/bindings/swig/doc.py +++ b/bindings/swig/doc.py @@ -46,7 +46,7 @@ for compound in index.findall('compound'): if language == 'python': print('%%feature("docstring") %s "%s";' % (class_name, brief)) elif language == 'ruby': - print('%%feature("docstring") %s "/* Document-class: %s\\n%s */\\n";' % (class_name, class_name.replace("sigrok", "Sigrok", 1), brief)) + print('%%feature("docstring") %s "Document-class: %s\\n%s\\n";' % (class_name, class_name.replace("sigrok", "Sigrok", 1), brief)) elif language == 'java': print('%%typemap(javaclassmodifiers) %s "/** %s */\npublic class"' % ( class_name, brief)) @@ -77,10 +77,10 @@ for compound in index.findall('compound'): for name, desc in parameters.items()]) + '";') if language == 'ruby' and kind == 'public-func': print(str.join('\n', [ - '%%feature("docstring") %s::%s "/* %s' % ( + '%%feature("docstring") %s::%s "%s' % ( class_name, member_name, brief)] + [ '@param %s %s' % (name, desc) - for name, desc in parameters.items()]) + ' */\\n";') + for name, desc in parameters.items()]) + '\\n";') elif language == 'java' and kind == 'public-func': print(str.join('\n', [ '%%javamethodmodifiers %s::%s "/** %s' % ( @@ -111,4 +111,4 @@ for compound in index.findall('compound'): print('%}') elif language == 'ruby' and constants: for member_name, brief in constants: - print('%%feature("docstring") %s::%s "/* %s */\\n";' % (class_name, member_name, brief)) + print('%%feature("docstring") %s::%s "%s\\n";' % (class_name, member_name, brief)) -- 2.27.0 |
From: <zen...@gm...> - 2020-06-09 03:54:07
|
Hi Soeren, Forget my previously email. My bad, this is due to 32 bit build I am using. When building with 64 bits, it work fine for me. I could use it capture much much longer. Best Regards Zeng Wei From: zen...@gm... <zen...@gm...> Sent: 2020年6月8日 14:49 To: 'Soeren Apel' <so...@ap...>; sig...@li... Subject: RE: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples Hi Soeren, I am fresh developer for Pulseviewer. Right now I have an issue with the PulseViewer. After I build the application for windows, and run the application for windows. The application(analog channel sample rate 781.25Khz, digital channel sample rate 6.25Mhz) could only run for a few(less than 40s). It seems memory will be limited to ~1.2GByte for windows. I have tried to use 2 x Windows 10 machine, I could see the similar problem. As for comparison, I run the application under Ubuntu, it seems to work fine for 8mins(81% of 16GB memory). Do you know if there is any settings to allowed change the application memory limitation? Is it something force relate to glib or PulseView? Do you have any idea on this kind of issue? Thanks for the help. Best Regards Zeng Wei From: zen...@gm... <mailto:zen...@gm...> <zen...@gm... <mailto:zen...@gm...> > Sent: 2020年6月6日 13:09 To: 'Soeren Apel' <so...@ap... <mailto:so...@ap...> >; sig...@li... <mailto:sig...@li...> Subject: RE: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples Hi Soeren, When I add key SR_CONF_SAMPLERATE and only enable get function, it works for me now. I could use my Saleae Logic 8 Pro to capture the analog channel data along with the digital channel data now. And the timestamp could be shown on the menu title as well. SR_CONF_SAMPLERATE_COMBINED | SR_CONF_GET | SR_CONF_SET | SR_CONF_LIST, SR_CONF_SAMPLERATE | SR_CONF_GET, Take the below snapshot as for the moment I could use the Saleae Logic 8 Pro to do the USB-PD analyisis now. VBUS, CC1, CC2 and USB-PD packet parsed data in the single view. Best Regards Zeng Wei From: zen...@gm... <mailto:zen...@gm...> <zen...@gm... <mailto:zen...@gm...> > Sent: 2020年6月6日 9:35 To: 'Soeren Apel' <so...@ap... <mailto:so...@ap...> >; sig...@li... <mailto:sig...@li...> Subject: RE: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples HI Soeren, Thanks for the reply. The reason I am adding the new key SR_CONF_SAMPLERATE_COMBINED, because as for the Saleae Logic software, they are supporting the different combination of the digital channel's and analog channel's sample rate. For example below is the combination I have, the digital channel sample rate could be 6.25Mhz or 500Mhz, while analog sample rate could be from 1 samples to 50Mhz samples, and for the user, it would better they will know what is the digital channel sample rate and what’s the analog channel sample rate they are selecting. static const ad_combined_sprt_t ad_comb_samplerates[] = { [0] = {"DIG_500M_ANA_50M", SR_MHZ(500), SR_MHZ(50)}, [1] = {"DIG_500M_ANA_12.5M", SR_MHZ(500), SR_KHZ(12500)}, [2] = {"DIG_500M_ANA_6.25M", SR_MHZ(500), SR_KHZ(6250)}, [3] = {"DIG_500M_ANA_3.125M", SR_MHZ(500), SR_KHZ(3125)}, [4] = {"DIG_6.25M_ANA_1.562M", SR_MHZ(6250), SR_HZ(1562500)}, [5] = {"DIG_6.25M_ANA_781.25K", SR_KHZ(6250), SR_HZ(781250)}, [6] = {"DIG_500M_ANA_125K", SR_MHZ(500), SR_KHZ(125)}, [7] = {"DIG_500M_ANA_5K", SR_MHZ(500), SR_KHZ(5)}, [8] = {"DIG_500M_ANA_1K", SR_MHZ(500), SR_KHZ(1)}, [9] = {"DIG_500M_ANA_100S", SR_MHZ(500), SR_HZ(100)}, [10] = {"DIG_500M_ANA_10S", SR_MHZ(500), SR_HZ(10)}, }; The original question is how the pulseview decide to use “+2s" or "+5 Msa" as the menu title? As shown from the below picture. May need your help guide me to the point where the pulseview code decide to change to “+ Msa” as unit. Thanks Best Regards Zeng Wei -----Original Message----- From: Soeren Apel <so...@ap... <mailto:so...@ap...> > Sent: 2020年6月6日 1:15 To: zengweitotty <zen...@gm... <mailto:zen...@gm...> >; sig...@li... <mailto:sig...@li...> Subject: Re: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples 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 oversampling/interpolation in the driver in such a case. Also, is it possible to use the same sample rates for analog and logic signals? If so, I see no necessity to have different samplerates in the first place. Regards -Soeren On Fri, 2020-06-05 at 23:30 -0700, zengweitotty wrote: > Hi All, > > Recently I am working on supporting Saleae Logic 8 Pro with > Pulseview. Most features are working fine now, I could get both analog > channel data and digital channel data. I have added the analog channel > and digital channel. > > Currently I face a problem, if anyone anyone in the email list > could help me out, I am appreciate. > > As for the Saleae Logic 8 Pro, it support different digital > sample rate and analog sample rates, when I do the change to support > different sample rate I add a special key called as > SR_CONF_SAMPLERATE_COMBINED, The menu which was displayed as timestamp > based things . Like "+2s" > .. > "+10s", but now it shows "+5 Msa". My question is where is the code to > display timestamp instead of samples ? > Thanks. > > Best Regards > > Zeng Wei > > _______________________________________________ > sigrok-devel mailing list > <mailto:sig...@li...> sig...@li... > <https://lists.sourceforge.net/lists/listinfo/sigrok-devel> https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: <zen...@gm...> - 2020-06-08 21:49:14
|
Hi Soeren, I am fresh developer for Pulseviewer. Right now I have an issue with the PulseViewer. After I build the application for windows, and run the application for windows. The application(analog channel sample rate 781.25Khz, digital channel sample rate 6.25Mhz) could only run for a few(less than 40s). It seems memory will be limited to ~1.2GByte for windows. I have tried to use 2 x Windows 10 machine, I could see the similar problem. As for comparison, I run the application under Ubuntu, it seems to work fine for 8mins(81% of 16GB memory). Do you know if there is any settings to allowed change the application memory limitation? Is it something force relate to glib or PulseView? Do you have any idea on this kind of issue? Thanks for the help. Best Regards Zeng Wei From: zen...@gm... <zen...@gm...> Sent: 2020年6月6日 13:09 To: 'Soeren Apel' <so...@ap...>; sig...@li... Subject: RE: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples Hi Soeren, When I add key SR_CONF_SAMPLERATE and only enable get function, it works for me now. I could use my Saleae Logic 8 Pro to capture the analog channel data along with the digital channel data now. And the timestamp could be shown on the menu title as well. SR_CONF_SAMPLERATE_COMBINED | SR_CONF_GET | SR_CONF_SET | SR_CONF_LIST, SR_CONF_SAMPLERATE | SR_CONF_GET, Take the below snapshot as for the moment I could use the Saleae Logic 8 Pro to do the USB-PD analyisis now. VBUS, CC1, CC2 and USB-PD packet parsed data in the single view. Best Regards Zeng Wei From: zen...@gm... <mailto:zen...@gm...> <zen...@gm... <mailto:zen...@gm...> > Sent: 2020年6月6日 9:35 To: 'Soeren Apel' <so...@ap... <mailto:so...@ap...> >; sig...@li... <mailto:sig...@li...> Subject: RE: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples HI Soeren, Thanks for the reply. The reason I am adding the new key SR_CONF_SAMPLERATE_COMBINED, because as for the Saleae Logic software, they are supporting the different combination of the digital channel's and analog channel's sample rate. For example below is the combination I have, the digital channel sample rate could be 6.25Mhz or 500Mhz, while analog sample rate could be from 1 samples to 50Mhz samples, and for the user, it would better they will know what is the digital channel sample rate and what’s the analog channel sample rate they are selecting. static const ad_combined_sprt_t ad_comb_samplerates[] = { [0] = {"DIG_500M_ANA_50M", SR_MHZ(500), SR_MHZ(50)}, [1] = {"DIG_500M_ANA_12.5M", SR_MHZ(500), SR_KHZ(12500)}, [2] = {"DIG_500M_ANA_6.25M", SR_MHZ(500), SR_KHZ(6250)}, [3] = {"DIG_500M_ANA_3.125M", SR_MHZ(500), SR_KHZ(3125)}, [4] = {"DIG_6.25M_ANA_1.562M", SR_MHZ(6250), SR_HZ(1562500)}, [5] = {"DIG_6.25M_ANA_781.25K", SR_KHZ(6250), SR_HZ(781250)}, [6] = {"DIG_500M_ANA_125K", SR_MHZ(500), SR_KHZ(125)}, [7] = {"DIG_500M_ANA_5K", SR_MHZ(500), SR_KHZ(5)}, [8] = {"DIG_500M_ANA_1K", SR_MHZ(500), SR_KHZ(1)}, [9] = {"DIG_500M_ANA_100S", SR_MHZ(500), SR_HZ(100)}, [10] = {"DIG_500M_ANA_10S", SR_MHZ(500), SR_HZ(10)}, }; The original question is how the pulseview decide to use “+2s" or "+5 Msa" as the menu title? As shown from the below picture. May need your help guide me to the point where the pulseview code decide to change to “+ Msa” as unit. Thanks Best Regards Zeng Wei -----Original Message----- From: Soeren Apel <so...@ap... <mailto:so...@ap...> > Sent: 2020年6月6日 1:15 To: zengweitotty <zen...@gm... <mailto:zen...@gm...> >; sig...@li... <mailto:sig...@li...> Subject: Re: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples 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 oversampling/interpolation in the driver in such a case. Also, is it possible to use the same sample rates for analog and logic signals? If so, I see no necessity to have different samplerates in the first place. Regards -Soeren On Fri, 2020-06-05 at 23:30 -0700, zengweitotty wrote: > Hi All, > > Recently I am working on supporting Saleae Logic 8 Pro with > Pulseview. Most features are working fine now, I could get both analog > channel data and digital channel data. I have added the analog channel > and digital channel. > > Currently I face a problem, if anyone anyone in the email list > could help me out, I am appreciate. > > As for the Saleae Logic 8 Pro, it support different digital > sample rate and analog sample rates, when I do the change to support > different sample rate I add a special key called as > SR_CONF_SAMPLERATE_COMBINED, The menu which was displayed as timestamp > based things . Like "+2s" > .. > "+10s", but now it shows "+5 Msa". My question is where is the code to > display timestamp instead of samples ? > Thanks. > > Best Regards > > Zeng Wei > > _______________________________________________ > sigrok-devel mailing list > <mailto:sig...@li...> sig...@li... > <https://lists.sourceforge.net/lists/listinfo/sigrok-devel> https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Nazmus S. <sak...@gm...> - 2020-06-08 01:56:03
|
Hi All. I have a question ... maybe it's not possible. I wanted to ignore a specific Pulase in SPI Decode. [image: image.png] Here in above picture the red circle Pulse is a invalid CLK signal and which makes wrong decode all the data after this wrong CLK. If it's possible to mark an area in PulseVire and make it ignore in decoding will be great. Is it possible anyhow? Thanks in advance. Regards. Nazmus Sakib. |
From: Gerhard S. <ger...@gm...> - 2020-06-07 20:14:03
|
On Sun, 2020-06-07 at 16:40 +0200, Christian Mauderer wrote: > > I had already a short look at the structure definitions when adding this > but some haven't been clear without some further analysis. Therefore I > hoped that I would reach someone via the mailing list who has experience > with Siglent devices and maybe still has some notes from an earlier > port. That would be a better starting point. Analyzing the code without > that was my second best option after that. Take my words with a grain of salt. And there are more than five people on the mailing list AFAIK. :) Let's see what others can say. Perhaps the author of the current Siglent SDS support is around as well. May just take a few days to respond perhaps. virtually yours Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. |
From: Christian M. <os...@c-...> - 2020-06-07 14:41:11
|
Hello Gerhard, thanks for the replies. On 06/06/2020 12:36, Gerhard Sittig wrote: > On Fri, 2020-06-05 at 18:18 +0200, Christian Mauderer wrote: >> >> I recently got my hands on a Siglent SDS2104X Plus. [ ... ] >> >> Is there some guide or some hints (like notes for porting an older >> Siglent model) that I could use as a starting point to find out what the >> values mean and determine the right values for my scope? > > Usually you'd get the vendor's programming guide for those SCPI > speaking devices. Then compare more recent models' capabilities > to the existing implementation, whether the same set of > instructions can be kept, or new instructions were introduced and > are required to use the newer device's features. Check the > vendor's download area for programming guides, or programming > related chapters in the user manual. > Currently the guide is a bit short on SCPI. They currently have only published a guide for IVI (which basically is just an abstraction). I hoped that the SCPI is similar enough to other Siglent systems that the commands would work and that I can guess the ones that don't. >> @@ -196,6 +197,8 @@ static const struct siglent_sds_series supported_series[] = { >> { 50, 1 }, { 500, 100000 }, 14, 8, 14000363}, >> [SDS2000X] = {VENDOR(SIGLENT), "SDS2000X", SPO_MODEL, >> { 50, 1 }, { 500, 100000 }, 14, 8, 14000363}, >> + [SDS2000XP] = {VENDOR(SIGLENT), "SDS2000X Plus", SPO_MODEL, >> + { 50, 1 }, { 500, 100000 }, 14, 8, 14000363}, >> }; >> >> #define SERIES(x) &supported_series[x] > > The specific question of what the supported_series[] table items' > fields mean -- just lookup the the item's data type declaration > (here: struct siglent_sds_series). Your diff's context (the > hunk's caption) shows it already. Get an editor that's capable of > navigating source code, if you don't have one yet. Otherwise > you'd be stuck with mere text search, which is possible but more > tedious. I had already a short look at the structure definitions when adding this but some haven't been clear without some further analysis. Therefore I hoped that I would reach someone via the mailing list who has experience with Siglent devices and maybe still has some notes from an earlier port. That would be a better starting point. Analyzing the code without that was my second best option after that. Best regards Christian > > > virtually yours > Gerhard Sittig > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > |
From: Mickael B. <mic...@li...> - 2020-06-06 21:53:49
|
>> if users >> want the information to be available, and up-to-date. Waiting for >> somebody else to do it all (and do stuff they don't even know >> about) won't result in much progress. I agree. May I have a wiki account to add the TENMA_72_2705_V65 in the wiki? My point was to say that the devices listed in the Korad KAxxxxP series page [1] should be in the main supported hardware page [2] because (presumably a lot of people and) I see no relation between a Korad product and a Tenma product at a first glance. Soeren, I like the CLI switch improvement. If I understand it correctly, all libsigrok/hardware/*/api.c should be modified to comply with it? [1] https://sigrok.org/wiki/Korad_KAxxxxP_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: >> 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 I would have to write a >>> complete driver. I had a good surprise when I saw that the >>> korad-kaxxxxp driver already does all the hard stuff. That said, do >>> you think that listing *all* known compatible devices in [2] would >>> help sigrok newbies like me and show that sigrok rules? >> >> Here is the trick question: Can you enumerate all known >> compatible devices, and tell whether they are operational, >> without having access to them? Can you tell how to determine the >> devices' capabilities or limits in advance, and how they may or >> may not identify themselves? That may answer the question whether >> the project is able to provide the support out of the box for >> devices they don't know about in the first place ... :) > > My take on it is this: how can users verify whether a device works or > not if they *must* alter the source code first and compile everything > from scratch? That's not helping, honestly. > > What I would wish for is a command-line switch that allows users to > forego the whitelisting in the drivers and force a particular driver to > use a particular (USB) device to be a particular model. That way, users > wouldn't need to alter the source code. > > Alas, none of us have the time to work on that, I reckon. > > -Soeren > > > >> Which means that it does take the users' reports of their >> existance and whether they work, before support can be claimed. >> Also users participating in wiki updates is required, if users >> want the information to be available, and up-to-date. Waiting for >> somebody else to do it all (and do stuff they don't even know >> about) won't result in much progress. >> >> >> virtually yours >> Gerhard Sittig >> -- >> If you don't understand or are scared by any of the above >> ask your parents or an adult to help you. >> >> >> _______________________________________________ >> sigrok-devel mailing list >> sig...@li... >> https://lists.sourceforge.net/lists/listinfo/sigrok-devel > > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > |
From: <zen...@gm...> - 2020-06-06 20:09:19
|
Hi Soeren, When I add key SR_CONF_SAMPLERATE and only enable get function, it works for me now. I could use my Saleae Logic 8 Pro to capture the analog channel data along with the digital channel data now. And the timestamp could be shown on the menu title as well. SR_CONF_SAMPLERATE_COMBINED | SR_CONF_GET | SR_CONF_SET | SR_CONF_LIST, SR_CONF_SAMPLERATE | SR_CONF_GET, Take the below snapshot as for the moment I could use the Saleae Logic 8 Pro to do the USB-PD analyisis now. VBUS, CC1, CC2 and USB-PD packet parsed data in the single view. Best Regards Zeng Wei From: zen...@gm... <zen...@gm...> Sent: 2020年6月6日 9:35 To: 'Soeren Apel' <so...@ap...>; sig...@li... Subject: RE: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples HI Soeren, Thanks for the reply. The reason I am adding the new key SR_CONF_SAMPLERATE_COMBINED, because as for the Saleae Logic software, they are supporting the different combination of the digital channel's and analog channel's sample rate. For example below is the combination I have, the digital channel sample rate could be 6.25Mhz or 500Mhz, while analog sample rate could be from 1 samples to 50Mhz samples, and for the user, it would better they will know what is the digital channel sample rate and what’s the analog channel sample rate they are selecting. static const ad_combined_sprt_t ad_comb_samplerates[] = { [0] = {"DIG_500M_ANA_50M", SR_MHZ(500), SR_MHZ(50)}, [1] = {"DIG_500M_ANA_12.5M", SR_MHZ(500), SR_KHZ(12500)}, [2] = {"DIG_500M_ANA_6.25M", SR_MHZ(500), SR_KHZ(6250)}, [3] = {"DIG_500M_ANA_3.125M", SR_MHZ(500), SR_KHZ(3125)}, [4] = {"DIG_6.25M_ANA_1.562M", SR_MHZ(6250), SR_HZ(1562500)}, [5] = {"DIG_6.25M_ANA_781.25K", SR_KHZ(6250), SR_HZ(781250)}, [6] = {"DIG_500M_ANA_125K", SR_MHZ(500), SR_KHZ(125)}, [7] = {"DIG_500M_ANA_5K", SR_MHZ(500), SR_KHZ(5)}, [8] = {"DIG_500M_ANA_1K", SR_MHZ(500), SR_KHZ(1)}, [9] = {"DIG_500M_ANA_100S", SR_MHZ(500), SR_HZ(100)}, [10] = {"DIG_500M_ANA_10S", SR_MHZ(500), SR_HZ(10)}, }; The original question is how the pulseview decide to use “+2s" or "+5 Msa" as the menu title? As shown from the below picture. May need your help guide me to the point where the pulseview code decide to change to “+ Msa” as unit. Thanks Best Regards Zeng Wei -----Original Message----- From: Soeren Apel <so...@ap... <mailto:so...@ap...> > Sent: 2020年6月6日 1:15 To: zengweitotty <zen...@gm... <mailto:zen...@gm...> >; sig...@li... <mailto:sig...@li...> Subject: Re: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples 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 oversampling/interpolation in the driver in such a case. Also, is it possible to use the same sample rates for analog and logic signals? If so, I see no necessity to have different samplerates in the first place. Regards -Soeren On Fri, 2020-06-05 at 23:30 -0700, zengweitotty wrote: > Hi All, > > Recently I am working on supporting Saleae Logic 8 Pro with > Pulseview. Most features are working fine now, I could get both analog > channel data and digital channel data. I have added the analog channel > and digital channel. > > Currently I face a problem, if anyone anyone in the email list > could help me out, I am appreciate. > > As for the Saleae Logic 8 Pro, it support different digital > sample rate and analog sample rates, when I do the change to support > different sample rate I add a special key called as > SR_CONF_SAMPLERATE_COMBINED, The menu which was displayed as timestamp > based things . Like "+2s" > .. > "+10s", but now it shows "+5 Msa". My question is where is the code to > display timestamp instead of samples ? > Thanks. > > Best Regards > > Zeng Wei > > _______________________________________________ > sigrok-devel mailing list > <mailto:sig...@li...> sig...@li... > <https://lists.sourceforge.net/lists/listinfo/sigrok-devel> https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: <zen...@gm...> - 2020-06-06 16:35:42
|
HI Soeren, Thanks for the reply. The reason I am adding the new key SR_CONF_SAMPLERATE_COMBINED, because as for the Saleae Logic software, they are supporting the different combination of the digital channel's and analog channel's sample rate. For example below is the combination I have, the digital channel sample rate could be 6.25Mhz or 500Mhz, while analog sample rate could be from 1 samples to 50Mhz samples, and for the user, it would better they will know what is the digital channel sample rate and what’s the analog channel sample rate they are selecting. static const ad_combined_sprt_t ad_comb_samplerates[] = { [0] = {"DIG_500M_ANA_50M", SR_MHZ(500), SR_MHZ(50)}, [1] = {"DIG_500M_ANA_12.5M", SR_MHZ(500), SR_KHZ(12500)}, [2] = {"DIG_500M_ANA_6.25M", SR_MHZ(500), SR_KHZ(6250)}, [3] = {"DIG_500M_ANA_3.125M", SR_MHZ(500), SR_KHZ(3125)}, [4] = {"DIG_6.25M_ANA_1.562M", SR_MHZ(6250), SR_HZ(1562500)}, [5] = {"DIG_6.25M_ANA_781.25K", SR_KHZ(6250), SR_HZ(781250)}, [6] = {"DIG_500M_ANA_125K", SR_MHZ(500), SR_KHZ(125)}, [7] = {"DIG_500M_ANA_5K", SR_MHZ(500), SR_KHZ(5)}, [8] = {"DIG_500M_ANA_1K", SR_MHZ(500), SR_KHZ(1)}, [9] = {"DIG_500M_ANA_100S", SR_MHZ(500), SR_HZ(100)}, [10] = {"DIG_500M_ANA_10S", SR_MHZ(500), SR_HZ(10)}, }; The original question is how the pulseview decide to use “+2s" or "+5 Msa" as the menu title? As shown from the below picture. May need your help guide me to the point where the pulseview code decide to change to “+ Msa” as unit. Thanks Best Regards Zeng Wei -----Original Message----- From: Soeren Apel <so...@ap...> Sent: 2020年6月6日 1:15 To: zengweitotty <zen...@gm...>; sig...@li... Subject: Re: [sigrok-devel] Question about how to change the menu to show the timestamp instead samples 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 oversampling/interpolation in the driver in such a case. Also, is it possible to use the same sample rates for analog and logic signals? If so, I see no necessity to have different samplerates in the first place. Regards -Soeren On Fri, 2020-06-05 at 23:30 -0700, zengweitotty wrote: > Hi All, > > Recently I am working on supporting Saleae Logic 8 Pro with > Pulseview. Most features are working fine now, I could get both analog > channel data and digital channel data. I have added the analog channel > and digital channel. > > Currently I face a problem, if anyone anyone in the email list > could help me out, I am appreciate. > > As for the Saleae Logic 8 Pro, it support different digital > sample rate and analog sample rates, when I do the change to support > different sample rate I add a special key called as > SR_CONF_SAMPLERATE_COMBINED, The menu which was displayed as timestamp > based things . Like "+2s" > .. > "+10s", but now it shows "+5 Msa". My question is where is the code to > display timestamp instead of samples ? > Thanks. > > Best Regards > > Zeng Wei > > _______________________________________________ > sigrok-devel mailing list > <mailto:sig...@li...> sig...@li... > <https://lists.sourceforge.net/lists/listinfo/sigrok-devel> https://lists.sourceforge.net/lists/listinfo/sigrok-devel |
From: Soeren A. <so...@ap...> - 2020-06-06 10:43:11
|
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 I would have to write a > > complete driver. I had a good surprise when I saw that the > > korad-kaxxxxp driver already does all the hard stuff. That said, do > > you think that listing *all* known compatible devices in [2] would > > help sigrok newbies like me and show that sigrok rules? > > Here is the trick question: Can you enumerate all known > compatible devices, and tell whether they are operational, > without having access to them? Can you tell how to determine the > devices' capabilities or limits in advance, and how they may or > may not identify themselves? That may answer the question whether > the project is able to provide the support out of the box for > devices they don't know about in the first place ... :) My take on it is this: how can users verify whether a device works or not if they *must* alter the source code first and compile everything from scratch? That's not helping, honestly. What I would wish for is a command-line switch that allows users to forego the whitelisting in the drivers and force a particular driver to use a particular (USB) device to be a particular model. That way, users wouldn't need to alter the source code. Alas, none of us have the time to work on that, I reckon. -Soeren > Which means that it does take the users' reports of their > existance and whether they work, before support can be claimed. > Also users participating in wiki updates is required, if users > want the information to be available, and up-to-date. Waiting for > somebody else to do it all (and do stuff they don't even know > about) won't result in much progress. > > > virtually yours > Gerhard Sittig > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > > _______________________________________________ > sigrok-devel mailing list > sig...@li... > https://lists.sourceforge.net/lists/listinfo/sigrok-devel |