Hi Hitesh,

Did you get a chance yet to see if you could get LibreOffice
to output correct values?

Thanks,

Rogue95

Hi Hitesh, I printed the value of the overflow flag to a console window via the printf statement, but got the same result. Value is still -859045888. I also changed the datatype from int16_t to short, but that only made the compiler error. It stated that parameter 7 in the ps2000_get_times_and_value...

Hi Hitesh, It would be difficult to remove the Picoscope and connect it to my PC. It's currently attached to a rack by the engineers. The code I'm using to display the value is in the below snippet. Please take a look and let me know. - Rogue95 int32_t i; int32_t time_interval; int16_t time_units; i...

Hi Hitesh, I am taking the overflow flag variable, converting it into a string, and then printing it out onto a message box. Actually, the way I'm setup, I'm compiling the code at my PC, and then running the executable on another PC that is attached to the Picoscope and test fixture for the inverter...

Hi Hitesh, This is the answer my Boss and head engineer have given: The DC voltage we are measuring is 48v (range of about 35v to 70v), but a 10 to 1 resistive divider is used which attenuates the signal so that is why the channel A is set to +/- 10v (35 to 70v divided by 10 is 3.5 to 7 volts). The ...

Hi Hitesh, Thanks for your help. Remember, the Excel file is a sample I retrieved from the PicoSDK. I haven't changed anything in the file which I'm trying to run in LibreOffice. Just for grins, I went ahead and made the arrays really large to see if that would help any, but as expected, the macro s...

Hi Andrew, Do know if there is a workaround if we run the Excel file in LibreOffice? Again the Excel file I'm talking about is "PS2000.xls" and it errors/crashes at the "ps2000_get_times_and_values(...)" call whenever we run it in LibreOffice. The reason I am asking this because we would have buy to...

Hi Hitesh,

Is there any more information that you need?
Please let me know.

Thanks,

Rogue95

Hi Hitesh, I got more accurate answers to your questions. Please see below. Hope to hear back from you soon. 1) Voltage range settings for channels A and B - It is actually +/- 10V for Channel A and +/- 1V for Channel B. 2) PicoScope device being used - Picoscope 2000 Series, model 2204A 3) Version ...

Hi Hitesh, Thanks for replying and helping me. Sorry for my my delay in replying. I've been researching the answers to give you. Please note that I have not changed any settings in the C++ sample code. I'm just running it with the defaults. I have taken the sample C++ code from the PicoSDK, copied i...

Hello all, I have now also posted the sample C code from the SDK. Please look and let me know what I might be doing wrong or what is causing the numbers to overflow in the output. void collect_block_immediate (void) { int32_t i; int32_t time_interval; int16_t time_units; int16_t oversample; int32_t ...

Hello All, I have compiled and ran the Sample C program that comes with the SDK for our Picoscope 2000 series. The numbers that output to a file are shown below. These numbers don't make sense to me except for the time values (First value in each row). It seems as if these values are overflowed valu...

Andrew, Nevermind. I found the problem. I was opening up the spreadsheet in LibreOffice and running the macros. I had assumed that they would work the same as Excel, but I found that this is not the case. When I ran macro in a borrowed a copy of Excel, it worked flawlessly. So there is some problem ...

Hi Andrew, I think the SDK on my CD is a newer version than what's on the website. Anyhow, I went ahead and downloaded the latest stable version and installed it. I had removed the .dll files from C:\Windows\System32 prior to installation as you requested. I ran the Excel macro and still got the sam...

Hi Andrew, I think my CD version is newer than the one on the website. Anyhow, I gave it a try with the one from the website and the same error happens in Excel still. I did as you said. I had removed the .dll files from C:\Windows\System32 since the software already places them in a directory that ...