Feedback is always appreciated. I understand what you're talking about on the continuity of the phase plot. I had realized at one time that would happen, but haven't been analyzing circuits with phase responses near the +/- 180 degree boundary. I like the idea of having a plot-center phase offset - ...

Great! Thanks for all your help! These fixes will go into a v0.4b, which I'm planning to release in the next week. When that's done, I'll post back here. In the meantime, let me know if your pre-amp measurements look correct.

It turns out that the frequency output was not the problem and that I do have a bug in the timebase calculation - and it literally was a single incorrect constant! I used 50MS/s as the max frequency instead of 100MS/s because I was thinking about the max frequency possible with two channels - d'oh! ...

Here's what I've figured out so far and where I'm stuck: The fact that the last ~3/4 of the time domain plots look blank is due to an unintentional vector re-size going on in PicoScope::GetData - lines 862-865 in v0.3b. This is also compounded by an incorrect buffer size calculation. It seems to thi...

I think we got closer to the solution :wink: I agree! These are not at all what I imagined, so I'm glad we got them. There seems to be some kind of mismatch between timing calculations and buffer size since the data just suddenly stops at about 1/4 of the whole sweep. That's where I'll focus my deb...

I think the issue with outputting the diagnostic plots is a due to a couple of things which I've learned with some experimentation. PLplot's advertised Unicode support is really about the display of plot text. For output graphics file creation, it still uses functions like plsfnam and fopen which ta...

I could create a file there without any problems, but how could I eliminate that accent from my folder name? By creating a new user, and reinstalling the program for him? Yes, that might work - at least for a short term diagnosis/workaround. There really should be no reason the whole program can't ...

great! I did it: the stdout file remained 0 size, the error output got 11 lines of this message: "Can't open C:\Users\Zoltán\Documents\FRA4PicoScope\diag\step0try0.svg." a couple of times I tried running the app in admin mode, but didn't help. usually I try this if something should work, but does n...

One other thing we can try here is to capture PLplots diagnostic messages, which go to stdout and stderr. If you've got the patience to try one more thing it should not take long. This may be easiest with a copy of the app and its three PLplot support files in a directory you're sure you have write ...

I really have that diag directory in every FRA folder now :) But I still have no output file. Just one more thought here. From some of the screen shots you provided, it looks like you're using Windows 8, is that right? I could try running some tests there to see what the diagnostic plotting issue m...

Yes, I pressed continue for the autorange limit dialog. What are the PLplot support files? I have the following in the .exe directory: plxtnd5.fnt cmap0_default.pal cmap1_default.pal btw. yesterday I got your PM, but I still cannot send any.. Yes, those are the right files. If those were missing th...

I really have that diag directory in every FRA folder now :) But I still have no output file. I just noticed that I can export the plot data though, so I tried it and it worked, the log shows the correct path, there's a diag folder at that path too. (I mean it matches your suggested path) I have to...

it's probably a different issue, but I found it interesting, that even if I set the max tries to 1, the autorange kept increasing the input ranges (50-100-200-500 mV). is this on purpose? nevermind, I think it's logical if the first attempt wasn't successful, then next time it tries the next level ...

it's probably a different issue, but I found it interesting, that even if I set the max tries to 1, the autorange kept increasing the input ranges (50-100-200-500 mV). is this on purpose? nevermind, I think it's logical if the first attempt wasn't successful, then next time it tries the next level ...

Posting this quickly since it's getting pretty late where you are ... That error is that one related to the diag directory not existing. What I said before was probably confusing. By app data directory, I meant the one in your documents folder, not the one in the roaming profile. E.g. c:\Users\Zoltá...