Siglent: SigScopeLab & Binary File - Page 1
Forum section: electronics / testgear

author: hpw
author_rank: Frequent Contributor
timestamp: February 11, 2024, 08:25:00 pm
content: So like to process some sample data form SDS2000X plus: Save binary data at the SDSRecord Length Analog: 20'000'000Sample Rate 2'000'000'000Vertical Scale CH2:+1.000000E-003Vertical Offset CH2:+0.000000E+000Horizontal Scale 1.00E-03Second Voltcsv file using the converter tool given on SDS in ZIP file for MS PC.Record Length Analog:20000000Sample Rate 2000000000Vertical Scale CH2:+1.000000E-003Vertical Offset CH2:+0.000000E+000Horizontal Scale 1.00E-03Second Volt-5.00E-03 1.08E-04-5.00E-03 1.08E-04-5.00E-03 8.33E-05-5.00E-03 9.17E-05-5.00E-03 1.08E-04-5.00E-03 1.08E-04.......form Excel getting only maximal 1'048'571 samples to saved to txt as selected columns !!!So did Memory load the Bin into SigScopeLab: Complains maximal of 2M samples Deal now as expecting better SigScopelab over network:Issue 1: Samples gets burst signals as never seen on SDSIssue 2: FFT Math channel without any scaling, so hard to know what range do we have selectedsee picture..Hp

author: slugrustle
author_rank: Frequent Contributor
timestamp: February 11, 2024, 08:36:59 pm
content: I'm having a bit of trouble parsing what you wrote, and I can't help you with the items under heading . But maybe I can help with this one:Quote from: hpw on February 11, 2024, 08:25:00 pmExcel has a maximum limit of 1'048'576 rows = 2^20 rows. Seehttps://support.microsoft.com/en-us/office/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3.To quote an intern at work after dealing with some other issues in Excel, "for as important and widely used as Excel is, it's not a very good tool."

author: hpw
author_rank: Frequent Contributor
timestamp: February 12, 2024, 08:10:49 pm
content: Quote from: slugrustle on February 11, 2024, 08:36:59 pmI was a bit confused about the none working SW, as channel 2 burst and dynamically missing lines. Also heavy reduced 2M sample limitation to load into memory.The FFT without any X/Y scaling.In addition on the SDS2000X, the math as FFT binary export failed with an error message, so I started to use this Free SW...Interesting would be an API for 3thrd party to retrieve any data in any SW.Hp

author: slugrustle
author_rank: Frequent Contributor
timestamp: February 13, 2024, 12:53:38 am
content: If you're handy with SCPI, you might be able to get the data you want that way. If you're already going to the trouble of writing such a program, manipulating the data with a scale factor, etc. could be done as part of the extraction.Unfortunately, in the latest programming manual for the SDS2000X plus, extracting FFT data is only "documented" through an example under the headingRead Waveform Data of FFT Example.

author: hpw
author_rank: Frequent Contributor
timestamp: February 13, 2024, 08:25:22 am
content: Quote from: slugrustle on February 13, 2024, 12:53:38 amWell, thank you, reading the BIN file (as more accurate) is the better/simpler direction but as onhttps://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-bugs-missing-features-feature-requests/msg5330459/#msg5330459a pitta again. Form me no surprise from this company.Hp

author: 2N3055
author_rank: Super Contributor
timestamp: February 13, 2024, 09:23:57 am
content: Quote from: hpw on February 13, 2024, 08:25:22 amAs it is not a surprise that you come up with offensive statements without proper research...We would be better able to help you if could explain better what you want.Did you notice this post was mostly your monologue so far. People are hesitant to help you because it is really hard to understand what are you really saying, and then you tend to be, well, not nice, to those that try to.As it was said to you, you need to get data from the scope as raw captures and do all the processing (FFT and all) on your PC.No scope will do half of processing just the way you want it.Only way to have complete control is to do it all in code.In that post you are referring to Programing manual "As anE02Adocumentation update request for the "How to Extract Data from Binary File...""I went to Siglent's site and newest Programing manual that you can download from there is versionEN11ELinked:https://siglentna.com/download/41216/?tmstv=1707815266Please take a look and see if that can help you...

author: hpw
author_rank: Frequent Contributor
timestamp: February 13, 2024, 10:44:04 am
content: Quote from: 2N3055 on February 13, 2024, 09:23:57 amWell, well... today is the 13.You completely missed, how the binary format locks like and this is NOT given on your referenced pdf at all, only my reference as the documentation to use, as it is with false calculation algo and not complete as already V4 used for SDS200x Plus!!!! .... just use any hex editor and thanAs I like to read the DATA from the saved bin file as stored on the SDS2000X plus... no more and nothing less.CheersHpHp

author: 2N3055
author_rank: Super Contributor
timestamp: February 13, 2024, 12:44:31 pm
content: Quote from: hpw on February 13, 2024, 10:44:04 amAs I said, it is hard to really understand what are you saying. Also, as I said, instead of all the facepalms, please try to explain better.One thing that helps in that is that you should explain things one by one, without changing the topic all the time.It wasn't clear what data you are referring to: BIN or CSV saved to file from scope, or data pulled from the network via SCPI.If I get you right now, you are saving data to BIN file and trying to open that.As documentation you use document "How-to-Extract-Data-from-the-Binary-File.pdf" with version stamp E02AThat document describes data format up to v3 of data.Your scope seems to save data with higher version, v4, which seems different.Is that correct?Make note, I'm trying to help you. I don't have that scope myself so cannot try it myself.When complaining to manufacturer, faceplams don't help.But if we can report actual problem, they will respond and fix it.That way the have clear problem to solve and have no excuse they didn't know.

author: nctnico
author_rank: Super Contributor
timestamp: February 13, 2024, 04:52:26 pm
content: If you want to use data from an instrument either save as text (CSV) or read 'live' data using SCPI. Anything else is a crapshoot. And never ever use manufacturer provided software as this is typically written by an intern.

author: hpw
author_rank: Frequent Contributor
timestamp: February 13, 2024, 05:36:46 pm
content: Quote from: nctnico on February 13, 2024, 04:52:26 pmAs it goes on.Using the CSV data, the given sample value are truncated / shorted. The values are IMHO not precise enough as missing mantissa.So the best is reading the sample values from the BIN file. Also, less effort required to read it into the App.IMHO, even with SCPI, the data is written into the BIN file & requires exact knowledge about the internal data structureAND how to calculate the Sample Values as binary offset on the BIN file.So the data is the following as real sample values and corresponding BIN as words values:- ch_volt_div_val is = 0.001 (1mV/div)- ch_vert_offset is = 0 (Volts) 1.08E-04 has BIN value as 33600 1.08E-04 has BIN value as 33600 8.33E-05 has BIN value as 33408 9.17E-05.....Now as mentioned Formula on page 46 in the Siglent Binary manual:voltage = (data-128) * ch_volt_div_val /1000/code_per_div + ch_vert_offsetIs false while:a) is for 8 bit offset binary, V4 has 16 bit offset binary!!b) code_per_div is as 25 for the old SDS2000X plus data structureWhat is needed, an updated Formula for SDS2000X Plus, as calculations using BIN Version 4:voltage = (data-32767) * ch_volt_div_val /1000/code_per_div+ ch_vert_offsetit looks as the value of code_per_div should be changed and this needs Siglent.Hp

author: nctnico
author_rank: Super Contributor
timestamp: February 13, 2024, 05:41:10 pm
content: Quote from: hpw on February 13, 2024, 05:36:46 pmNo, with SCPI you receive the data in the format you want with precision you want (typically you can select how the result is formatted unless Siglent messed this up). Yoursoftwarescript can then decide how to write the data into a file.

author: Performa01
author_rank: Super Contributor
timestamp: February 13, 2024, 06:23:59 pm
content: Here is some data about current Siglent DSOs (codes/LSB in visible screen area, codes/LSB per division):SDS800X HD: 3840 LSB, 480/div;SDS1000X-E: 200 LSB, 25/div;SDS2000X Plus: 240 LSB, 30/div; (960 LSB, 120/div in 10 bit mode);SDS2000X HD: 3840 LSB, 480/div;SDS6000 H12 Pro: 3400 LSB, 425/div;EDIT: added the obvious: in 10 bit mode, you have to multiply the numbers by 4!

author: hpw
author_rank: Frequent Contributor
timestamp: February 13, 2024, 08:34:04 pm
content: Quote from: Performa01 on February 13, 2024, 06:23:59 pmSo voltage = (data-32767) * ch_volt_div_val /1000/code_per_div + ch_vert_offsetusing 1.08E-04 Volts has BIN value as 33600voltage = (33600-32767) * ch_volt_div_val /1000 / 30 + 0 is2.77766 E-5but should result in 1.08E-4 VoltsSo as for Binary V4, any difference for the Binary Word offset has to be considered as no any longer 8Bit.Or I am wrong,As for ....  if the code_per_div value is 100/13 the Sample Values gets as the original

author: hpw
author_rank: Frequent Contributor
timestamp: February 14, 2024, 09:28:33 am
content: Quote from: Performa01 on February 13, 2024, 06:23:59 pmDid now checked the same thing with an applied Signal as:3.92E-03mV from CSV and Bin as 62848 Peak >> getting with may 100/13 (7.6923) more or less the same 3.9105mV signal back.This means the value of 30 is NOK! 30 is may valid for the older V3 binary version.So Siglent engineers please ..Hp

author: tautech
author_rank: Super Contributor
timestamp: February 14, 2024, 06:34:35 pm
content: Quote from: hpw on February 14, 2024, 09:28:33 amAre on CNY holidays for another week.

author: points2
author_rank: Regular Contributor
timestamp: February 18, 2024, 04:59:04 pm
content: Hi,Just a quick mail to support you hpwI had the same feeling about this SW when I tried it(although it was a more basic try than yours)Thanks to you for creating this topic.It's a nice & promising topic !"Nice" : because the display of this SW is "nice" on a 1440p screen (far nicier than the web interface or thru VNC viewer that enable only a copy/paste of the scope with the resolution of the scope... + big lag...)"Promising" : because in the last months I realized I tend to use more & more the remote display than the scope itself (by playing with nobs & buttons). I find that viewing the measurement from my desk (front of PC screen) is more friendly (to me)."Promising" because this SW doesn't work... but if one day it works, it's gonna be a great add-on to the device itself !Please find here the link to my post vs my 1st experience with this SW a few days ago =>https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/msg5336969/#msg5336969(I didn't see this dedicated topic when I posted)According to Siglent web site =>https://www.siglenteu.com/service-and-support/firmware-software/pc-software/#sigscopelabit is the 1st released version... so we can expect some fixes in the (near?) "future"but I don't understand why they released such a buggy stuff... and why version "V0.4.9.2" ? I can't figure out how the version v0.1.0.1 was more buggy than this one

author: hpw
author_rank: Frequent Contributor
timestamp: February 20, 2024, 09:14:12 am
content: As it goes on...IMHO the SW is more like on Alpha stage or as Banana wareImportant to know:- If you use any LAN or WIFI, you will see any RF on your spectrum, may not on 12Bit, but if you use large FFT and high bit's as from an Audio ADC.This means, to switch off any LAN / WIFI is a mustdo...- The sampled data as given in the BIN file and may also over the remote SW is time scale dependent. So about 5ms you get the full 100M samples. Iffaster time scales used as 5us you may get 20k samples only. You will see below the time icon about the used sample size.- The Save/Export of sample data using multiple channels, gets multiple files!!!!! not as promised in the BIN specifications as each channel data added after the other- the BIN file comes with the exact scale factors as for each SDS any different and bits dependent as for SDS2000X plus (8/10 bits)

author: antian
author_rank: Contributor
timestamp: February 27, 2024, 09:05:21 pm
content: Hi sorry to revive this but I am having trouble trying to extract data from the BIN file of my SDS2000X plus. I found a few codes that work with my SDS1000X-E exported and I am hoping to use this Matlab code (https://www.mathworks.com/matlabcentral/fileexchange/99529-import-siglent-oscilloscope-binary-file) but it looks like it isn't reading the bin files from the SDS2000X plus (latest firmware). Unfortunately I am not very familiar with decoding binary but when I fread I see the file is read as an array of 5004096 values. The first value in the 0x00 address is 4 which I believe should correspond to the version but the file on how to extract data from binary says there is supposed to be a 0, 1, or 2. Does this suggest that the binary format has changed? I believe the document I am looking at from Siglent says it was last updated in 2019. Since it looks like the data starts after the 4096th row, I think the data starts on 0x1000 which is different that what the manual says of 0x800.

author: hpw
author_rank: Frequent Contributor
timestamp: February 28, 2024, 10:32:05 am
content: Quote from: antian on February 27, 2024, 09:05:21 pmWith the new FW you have already the V4 format.The specification about V4 format is given in earlier post. In other words, your reading BIN SW should take care of any versions and act according.Hp

author: antian
author_rank: Contributor
timestamp: February 29, 2024, 09:19:13 am
content: Quote from: hpw on February 28, 2024, 10:32:05 amHi, thanks for the information in the other posts, I really appreciate it. I found a decent Matlab code (https://www.mathworks.com/matlabcentral/fileexchange/99529-import-siglent-oscilloscope-binary-file) that reads data from my 1000X BIN well but unfortunately it doesn't do the 2000X either and I'm planning to just modify this. I'm not sure if it's because I am a total binary noob or I am missing something or if it's matlab but I changed the waveform data location offset to x1000, the code_per_div = 30, and the data subtraction by 32767, but it looks like something is still off and it might be missing some sections.For example, there is a value (the number 16) in 0x05 so is there supposed to be something in 0x04 - 0x7? I'm looking at a file with only Ch1 on and it looks like my ch1_on indication starts on 0x08 instead of 0x04 per the outdated manual. When I tried to add a space / skip for 0x04 - 0x7, the script still does not work so I have a feeling value might be important.Another example is that ch1_volt_div_val is supposed to start on 0x14 but that position is empty. The next value I see is at 0x30.I appreciate the help!

author: hpw
author_rank: Frequent Contributor
timestamp: February 29, 2024, 10:04:51 am
content: Quote from: antian on February 29, 2024, 09:19:13 amAs long you not understand the V4 specification fully, any pitta to seeMay simple provide a SHORT sampled BIN using your SDS2K + and also from the SDS1000X-E .Also tell if any BIN provided from the SDS2k + whether used 8 bit or 10 bit acq.Hp

author: antian
author_rank: Contributor
timestamp: February 29, 2024, 08:18:49 pm
content: Quote from: hpw on February 29, 2024, 10:04:51 amCool so I found the document on V4 for the 2000X HD (updated 2023-1-17) but I don't think it matches up exactly. I've attached the PDF I am looking at. I see it has a data_offset_byte_ at 0x04-0x07 which makes sense perfectly, the ch1_on matches whats expected [1 0 0 0] for only Ch1_on, but reading the ch1_volt_div_val is not coming out. The document says it's supposed to start on 0x18-0x3f (so basically up until 0x40 when ch2_volt_div_starts?) and the first 64-fit float points should be the value, the next 32-bit is the magnitude and the next 32-bit is the unit. This is the same format as V3 when it comes to reading the ch1_volt_div_val I believe. This is outlined in Table 2 in the document but my matlab fread shows this first 40 lines because ch2_volt_div_val is supposed to start on 0x40:Code:INDEXVAL041020304051660708190100110120130140150160170180190200210220230240250260270280290302403163328330340350360370380390There is no value in the 64-bit float point starting at 0x18. The matlab script should be reading that first 64-bit properly so it looks like there's no data? Do you have an idea what might be going on?Any help is greatly appreciated

author: hpw
author_rank: Frequent Contributor
timestamp: February 29, 2024, 08:50:16 pm
content: Quote from: antian on February 29, 2024, 08:18:49 pmagain and again beef neededProvide a SHORT sampled BIN using your SDS2K + and also from the SDS1000X-E .Also tell if any BIN provided from the SDS2k + whether used 8 bit or 10 bit acq.As attached as ZIP format.CheersHp

author: antian
author_rank: Contributor
timestamp: March 01, 2024, 01:27:21 am
content: Quote from: hpw on February 29, 2024, 08:50:16 pmHi,I have attached two files: one of ~15V p2p sine wave from the sds1000x and one ~20V p2p square wave from the sds2K+. The SDS2K+ is taken with 8 bits. I did more digging and realized I was reading hex wrong and I think the error is reading the ch1_volt_div_val. The matlab code reads the sds1000x totally fine but it doesn't does the sds2K+ with V4. At 0x18-0x3f when it is supposed to be reading a volt_div_val scaling of ~4V for channel 1, it reads 1V for channel 1 and completely wrong numbers for the other channels. I believe at 0x18-0x3f the first 8 bits are for the 64-bit float point and this reads [0 0 0 0 0 0 240 63]. I don't actually know how to convert this to a decimal but that doesn't look correct?Thanks a lot for the help

author: Calvin
author_rank: Regular Contributor
timestamp: March 01, 2024, 05:53:06 am
content: Hi,had installed the SigScopeLab a couple of days ago on a WIN10 computer.Unfortunately the software crashes always and already when trying to connect to the scope.What a piece of s*****.Also the GUI doesn´t look intuitive at all.Fortunately the Webserver functions well .... so there seems hardly any need for a another piece of crappy software ... or?regardsCalvin

author: 2N3055
author_rank: Super Contributor
timestamp: March 01, 2024, 09:11:11 am
content: Quote from: Calvin on March 01, 2024, 05:53:06 amI don't know about stability on your PC. You should contact Siglent support for that.As for GUI, that is not a MS Office application..It is not a PC based mathematical package that happens to be able to load file from scope.That is scope OFFLINE application. This is literally software that runs on scope but compiled for Windows.Many manufacturers have the same.It is very powerful thing. You can save a signal in the office, put it on laptop and analyse (math decode, whatever) later...I didn't try it in depth yet, but I also had some intermittent connection problems.Or shall I say, more like timeouts on longer timebases..No crashes though.Will test more one of these days when I have some time... Not very soon unfortunately.

author: hpw
author_rank: Frequent Contributor
timestamp: March 01, 2024, 10:25:24 am
content: Hi,I see in your ZIP 20kV_1kHz_C2_sample.bin as format V4!!! sds2000xplus_square.bin as format V4!!!>> As I have attached two files: one of ~15V p2p sine wave from the sds1000x and one ~20V p2p square wave from the sds2K+.>> The SDS2K+ is taken with 8 bits. I did more digging and realized I was reading hex wrong and I think the error is reading the>> ch1_volt_div_val.>> The matlab code reads the sds1000x totally fine but it doesn't does the sds2K+ with V4. At 0x18-0x3f when it is supposed to>> be reading a volt_div_val scaling of ~4V for channel 1, it reads 1V for channel 1 and completely wrong numbers for the other>> channels. I believe at 0x18-0x3f the first 8 bits are for the 64-bit float point and this reads [0 0 0 0 0 0 240 63].So where is the sds1000x file as expecting V3 or any else??Also 20kV_1kHz_C2 as 20E3 Volts !!??In addition to provide as to control each read values as:- Y Scaling in Volts- Y Offset readings as in Volts- Probe scales as xxxx- samples given from X time scalesHp

author: hpw
author_rank: Frequent Contributor
timestamp: March 01, 2024, 10:52:49 am
content: Quote from: 2N3055 on March 01, 2024, 09:11:11 amOffline or even years later to repeat the measurements with any better toolsReading BIN files islimitedto 2M samples, so FFT and scale down is impossible.

author: 2N3055
author_rank: Super Contributor
timestamp: March 01, 2024, 11:49:58 am
content: Quote from: hpw on March 01, 2024, 10:52:49 amHmm,as I said, will look into it when I have time.Thanks for details...Best,

author: hpw
author_rank: Frequent Contributor
timestamp: March 01, 2024, 06:53:27 pm
content: Quote from: antian on March 01, 2024, 01:27:21 amAs your file with large probe settingsSource File: sds2000xplus_square.binFormat is 8bit--------------------------------------------Ch-1 is ONScale: 1Magnitude: 8Probe: 4000Offset: 0Div Value: 30And opened question:As your 4000 gain probe, please provide a BIN with any Offset (<> 0). While nothing mentioned whether the offset has tomultiplied by the probe attenuation's.As real Offset * probe attenuation??

author: antian
author_rank: Contributor
timestamp: March 03, 2024, 07:42:05 pm
content: Quote from: hpw on March 01, 2024, 10:25:24 amSorry it looks like I attached the wrong sds1000x file so I have correctly attached it here. It should be a 40 p2p / 2 kHz sine wave. The actual voltage of this is 40 kV but sometimes I don't define the probe as 1000x so it reads 40 p2p but sometimes I do set the proper probe like in the case of the other sds2000x file.Quote from: hpw on March 01, 2024, 06:53:27 pmIn the sds2000x file, I was using a power supply with a 4000:1 voltage readout so the probe was set at 4000:1. There should have not been any offset, but it is possibly it was small. I'll make a file tomorrow with an offset. To make sure I am reading BIN correct, the ch1_probe should be at 0x244 - 0x24b and that address reads [0 0 0 0 0 64 175 64]. Does that translate to 4000 as a 64 bit float or am I looking at something/somewhere wrong? My code is reading the probe and vert_offset values incorrectly but does the offset get saved prior to the probe attenuation or after?Thanks

author: nctnico
author_rank: Super Contributor
timestamp: March 03, 2024, 09:01:10 pm
content: Quote from: 2N3055 on March 01, 2024, 09:11:11 amProbably a good option. However, there are a myriad of reasons why software crashes on a Windows PC. Language & localisation settings, filesystem access rights, registry settings, graphics driver capabilities, I/O ports that behave oddly, missing or extra updates which change certain API behaviour, etc, etc. In 99% of the cases the programmer is to blame for not testing on all Windows versions with all localisations and various update levels. Typically the root cause is not checking whether an API call returns a valid pointer which in turn can produce an error message which can point to where the program went wrong. Writing robust & serviceable software is much harder than it looks.

author: hpw
author_rank: Frequent Contributor
timestamp: March 03, 2024, 09:48:29 pm
content: Quote from: antian on March 03, 2024, 07:42:05 pmYour SDS1000x, as converting it to csv:Version 1 as reading as Hex Editor NeoRecord Length Analog:1400000Sample Rate 1000000000Vertical Scale CH1:+3.380000E+000 CH3:+3.620000E-002Vertical Offset CH1:+0.000000E+000 CH3:-4.488800E-002Horizontal Scale 1.00E-04Second Volt Volt-0.000728 4.87E+00 1.16E-02-0.000727999 4.87E+00 1.01E-02-0.000727998 5.00E+00 1.16E-02-0.000727997 5.00E+00 1.16E-02-0.000727996 5.00E+00 1.16E-02Is IMHO a complete different header with spec's. As SD2K+ writes for each channel a different file (not what the spec's V4 tells).Best to use the BIN file and convert it to csv and read the first settings & sample values.Repeat until you get what is given within the csv file, so your V4 specification readings matches.Attached an example with probe settings and offset... as cvs and my text data should matchHp

author: antian
author_rank: Contributor
timestamp: March 04, 2024, 02:45:51 am
content: Yeah with your data it looks like my processing script has the same errors. So I wouldn't mind to have everything converted to a CSV and then read the CSV but I have to first get this script to read it properly. For my work I have literally hundreds of BIN files that I then loop through with some signal analysis and I don't want to manually click each one so if there's a way I can run the exe for all the files in a folder, that would be great. I tried briefly to do a button-pressing based automation of this but if you simply copy and paste the path of the BIN into FileConverter.exe file, it didn't work for me and I had to manually click the BIN file for that exe to work.For my script I am now manually reading every byte and it properly reads the version (4), data offset btye, and which channels are on, but the ch_volt_div_vals are not correct and I am slowly getting more confused the more I dig in. I am looking at your file and ch2_volt_div_val should be at 0x40-0x67. It looks that corresponds to the bytesBased on the CSV file, I should possibly expect this to translate to 0.005. However, When I used the binary reading Matlab function and defining a float64,it reads that set of 8 8-bits as 2.12e314 which cant be correct. When I manually convert that array into its binary, concatenate those binary numbers into , that translates into something also wrong but am i just using a wrong calculator? This is the same issue with my own SDS2K+ files. I plan to look at a file with the same signal across the sds1000x and sds2K+ to see if that helps me figure our what in the world matlab is reading.

author: hpw
author_rank: Frequent Contributor
timestamp: March 04, 2024, 08:09:21 am
content: As for BIN files, I suggest you to use the "Hex Editor Neo" as you are able to convert HEX to Word / DWord / Doubleand really see whats the beef within HEX Editor data. Sometimes the float are different aligned as not starting at 8x.So simple select and copy the double data to a new file and get 8x aligned starting.- Or simple dump your header data as text before doing any else steps. As your SDS1000 Matlab code is doing it right.- Or ask someone who is fit with Matlab. I am NOT not fit with Matlab is for me still $$kor use Octave.- The draw back is may, as you do not get any Matlab debuggerHp

author: martin1959
author_rank: Contributor
timestamp: March 05, 2024, 10:16:00 am
content: When running SigScopeLab on a Windows 10 machine with German language settings, the software starts but has trouble with number formats, i.e. decimal separator.Using the software, I set the horizontal time to "2,0 ms/div" (2 milliseconds). The software does not understand the "," decimal separator (as used in Germany) and wrongly sets the horizontal time to 2s/div (2 seconds).I then changed the MS Windows setting to use "." as decimal separator and then the SigScopeLab software was happy with it.

author: antian
author_rank: Contributor
timestamp: March 06, 2024, 09:42:10 am
content: Quote from: hpw on March 04, 2024, 08:09:21 amAs an update, I finally got it working for the SDS2000X. I was not reading the 3 sets of the 64-bit float points after each value for ch_volt_div_val, ch_vert_offset, etc. This was a painful way to learn binary but I really appreciate the help. I'll upload an updated version of it on the matlab forums.

author: tautech
author_rank: Super Contributor
timestamp: January 06, 2025, 08:19:25 am
content: Customer required 10s captures to be available for offline analysis.Despite SigScopeLab limitations we can inspect them at 1ms and faster.Remove .txt from attachment