Here's another question... is it possible to make the scope stop confirming that I really want to auto setup when I press the key? Just do it!
I never use it as want to be master of instrument and NOT let it make choices for me.
Does anyone know what the external 10MHz clock levels should be? Is a ±12V pk sinusoid fine?
Does anyone know what the external 10MHz clock levels should be? Is a ±12V pk sinusoid fine? I can't seem to find this anywhere in any of the datasheets or manuals... And I hesitate to plug in a ±12V source if the instrument expects 0-5V or something.
BTW, if Siglent NA is watching: when downloading the SDS5000X User Manual from the documents page (https://siglentna.com/resources/documents/digital-oscilloscopes/#sds5000x-series) I actually get the Service Manual... I found the manual somewhere else through google though, but it would be nice to know that it's up to date.
Does anyone know what the external 10MHz clock levels should be? Is a ±12V pk sinusoid fine? I can't seem to find this anywhere in any of the datasheets or manuals... And I hesitate to plug in a ±12V source if the instrument expects 0-5V or something.
BTW, if Siglent NA is watching: when downloading the SDS5000X User Manual from the documents page (https://siglentna.com/resources/documents/digital-oscilloscopes/#sds5000x-series) I actually get the Service Manual... I found the manual somewhere else through google though, but it would be nice to know that it's up to date.
Guys,
I am trying to save some captured data. But due to it's size, I am forced to save it as binary.
But I can not convert/decode the capture.
Has anybody gotten the Bin2csv tools or the Python script working ?
Any pointers, appreciated !
Cheers,
rudi
Guys,
I am trying to save some captured data. But due to it's size, I am forced to save it as binary.
But I can not convert/decode the capture.
Has anybody gotten the Bin2csv tools or the Python script working ?
Any pointers, appreciated !
Cheers,
rudi
Bug !
Save of the BIN2CSV utility to USB stick is not working....reported.
However, grabbed from another model.
Unzip and install on PC.
A while since I last used it so can't exactly remember the details but it was quite simple and all you need to know is in the Readme.txt file.
The BIN2CSV utility can only be saved to USB via use of the File Manager accessed from within Save/Recall.
To save BIN2CSV the File Manager Save or Save As virtual buttons must be used.
This is not obvious until you take the time to study File Manager.
The Save and Save As virtual buttons could be improved with a bolder font and/or Save could be highlit to bring the eye to the Save virtual button.
Suggested feature request/improvement to Siglent for SDS5kX and SDS2kX+: make Save more visible in File Manager.
Oh wait, it's early. It's should be 0x03, right? Did you set the decoder CPOL+CPHA correctly?
Oh wait, it's early. It's should be 0x03, right? Did you set the decoder CPOL+CPHA correctly?
Hi !
yes, it should have been 0x03. The clock edge is set to rising edge, data is MSB first.
As I said, it works about 70% of the time and I get expected data. But the 30% of the time when I really need it work, it doesn, lol.
You seem to be running SPI at 20MHz. What is the maximum SPI clock rate the oscilloscope supports? It may be your SPI bus is simply too fast for the decoding to work. This can depend on the record length; unfortunately this isn't specified in the manual or datasheet.
You seem to be running SPI at 20MHz. What is the maximum SPI clock rate the oscilloscope supports? It may be your SPI bus is simply too fast for the decoding to work. This can depend on the record length; unfortunately this isn't specified in the manual or datasheet.
Hi,
SPI bus is rated up to 50 MHz. If the scope says it supports SPI bus decoding. I would expect it to be able to operate withing valid parameters of the SPI specification.
Unfortunately neither statement is correct. First: There is no limit to what speed is supported by SPI. You can run it at several GHz if you manage to get the timing right. Second: every DSO has a limit to the speed it can decode. For example: on my GW Instek it depends on the memory length. With a short memory length it has no problem decoding SPI at 125MHz but at longer memory lengths, the maximum speed drops. In the end a DSO has a limited amount of resources to do the decoding which in turn limits the number of samples it can process within a reasonable amount of time.
Unfortunately neither statement is correct. First: There is no limit to what speed is supported by SPI. You can run it at several GHz if you manage to get the timing right. Second: every DSO has a limit to the speed it can decode. For example: on my GW Instek it depends on the memory length. With a short memory length it has no problem decoding SPI at 125MHz but at longer memory lengths, the maximum speed drops. In the end a DSO has a limited amount of resources to do the decoding which in turn limits the number of samples it can process within a reasonable amount of time.
You are right, there are no hard limits for the SPI bus clock speed. But 20 MHz, is by today's standards low speed.
Also, I have switched to the Logic Analyzer mode, so it should record only one bit per sample, and not 8 bits
per signal. If there are any limitations due to memory or such, that the Data Sheet of the DSO should have
listed them. I have run my test using different time bases, and sampling rates. Short and large captures.
Yes, when I try to record 200mS worth of SPI traffic, it just chokes and doesn't do anything useful. On the
other hand, I can record 200mS worth of analog traces and save them to flash drive and then decode it
myself.
The fact remains, that the decoder IS BROKEN. It works 70% of the time, and when you really need it does not.
Another thing I forgot to mention, the very first transaction in a capture is ALWAYS decoded wrong.
I would be happy to work with Siglent and provide sample traces if they are interested.
And don't forget, saving digital traces is also broken (saved as all zeros). And yes I have the threshold
set correctly ...