Hi Soeren,
I agree partially with it, that users don't want to wait, however I
probably wouldn't have a problem with waiting a bit longer than with having
no data at all. But I get your point. I have tried doing it with smaller
blockes, but the device is sending it in one chunk and including the header
of the complete block. The block of data is 14 megabytes big, and already
transferring it costs about 10 seconds. Is it possible that the buffer in
the scpi implementation is to small? I ask this because the error pops up
yust after about 60% of the transfer is completed from the device (seen
from the network Analizer).
Greetings,
Marchel.
Op zo 4 feb. 2018 15:09 schreef Soeren Apel :
> 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
> almost a minute and instead assume that the software has crashed.
>
> Is there something you can do to change this? Fetch the data in
> smaller blocks, for example?
>
> Also, what format is the data in? Human-readable (ASCII) or binary?
>
> -Soeren
>
>
> On Sun, 2018-02-04 at 14:50 +0100, Marchel H wrote:
> > Hello Team,
> >
> > I have a problem with the scpi read data call. I have done some scans
> > with wireshark, and I see that the READ data is going to the device,
> > however, the device starts sending data after about 40 seconds. I
> > know this is slow( its on the 14M memory depth).
> >
> > Is there any way to set the scpi time out time via the API?
> >
> > Greetings,
> > Marchel.
> > ---
> > ---
> > 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
