Hi there,
I'm having a problem with the SPI Decoder: After capturing an SPI sequence, which works well and shows the correct data (in the list view), I'd like to zoom in to see the full binary data also in the line view (where it is abbreviated). Hoewever, the full binaries only flash shortly and then vanish - I then see only two lines of MOSI and MISO, and no decoded data at all. It vanishes also from the list view. I only zoom up one additional level - and everything is gone (though signals of several bytes are on the screen). When I zoom back out, the abbreviated numbers return...
Am I just too stupid to use this correctly, or is it a bug? I'm using the latest firmware of the scope.
Cheers,
AnikSimply, Siglent DSO's with deep memory are optimized for zoom in and the best way to use the deep memory is to capture long (slow) and zoom in for detailed inspection.
Zoom mode works well here using by the dual timebase feature and pan through the record or scroll the decode table.
Thanks, tautech, I totally had missed that! Using the zoom function/dual time base I get what I wanted and wasn't able to find
Did I overlook all that in the documentation of the scope? I couldn't find a detailed description of the LA features and their use yet.
Cheers, Anik
SP2035A reduction is from $179 to $75 and is certainly very well priced now.
SP2035A reduction is from $179 to $75 and is certainly very well priced now.
I don't know if that was a typo or if they have raised the price already. I'm seeing $79 (US).
Just under $100 with shipping is what I paid a few minutes ago.
Still, there's enough of these out there now there's quite a community willing to help those that are still finding their feet. Keep asking questions and someone will help.
Some really good news for those that have purchased SDS2104X Plus, hacked it and need/want higher BW autosense probes.
It seems Siglent does want to sell probes and at really hot pricing too on the SP2000 and 3000 10x autosense range.
https://siglentna.com/products/accessories/probes/passive-probes/
Yes I may have helped them to see the obvious.
Some really good news for those that have purchased SDS2104X Plus, hacked it and need/want higher BW autosense probes.
It seems Siglent does want to sell probes and at really hot pricing too on the SP2000 and 3000 10x autosense range.
https://siglentna.com/products/accessories/probes/passive-probes/
Yes I may have helped them to see the obvious.
This is good timing! Just bought my SDS2104X Plus with an SPL2016/LA bundle, and those supplied probes aren't great. Neither are my Tek TPP0201's to be fair. Both seem to -3dB at 160 Mhz.
I only see siglent na with the cheaper price so far, and they don't seem to ship to 'straya.
Anyone know what the -3dB bandwidth is on the SP2035A? Is it just 350MHz like it says, or is it higher than specified like with the cheaper probes?
Anyone know what the -3dB bandwidth is on the SP2035A? Is it just 350MHz like it says, or is it higher than specified like with the cheaper probes?
Anik
Screenshots help immensely to point out possible settings errors so use the blue Print button to capture them to a USB stick and upload them here in the Attachments section when you post.
...
I've tried to reproduce the none-responsiveness of the UI, but didn't succeed yet - strange...
But since I'd liked to try with the print button, here is another question: the decoded data doesn't appear right under the 8 bit it comes from (see screenshot), is that normal?
The data is correct obviously, but it is harder to compare to the signal here than I'm used to.
Thanks & cheers,
Anik
1. CS is missing (at least on screen period)
2. You are decoding a 16 bit word as two 8 bit values (what about endianess?)
Anik
Screenshots help immensely to point out possible settings errors so use the blue Print button to capture them to a USB stick and upload them here in the Attachments section when you post.
I've tried to reproduce the none-responsiveness of the UI, but didn't succeed yet - strange...
But since I'd liked to try with the print button, here is another question: the decoded data doesn't appear right under the 8 bit it comes from (see screenshot), is that normal?
The data is correct obviously, but it is harder to compare to the signal here than I'm used to.
Thanks & cheers,
Anik
Very normal with the settings you have used.
Why a Pulse trigger instead of an Edge trigger ? Did you use any Trigger Holdoff ?
...
I've tried to reproduce the none-responsiveness of the UI, but didn't succeed yet - strange...
But since I'd liked to try with the print button, here is another question: the decoded data doesn't appear right under the 8 bit it comes from (see screenshot), is that normal?
The data is correct obviously, but it is harder to compare to the signal here than I'm used to.
Thanks & cheers,
Anik
1. CS is missing (at least on screen period)
2. You are decoding a 16 bit word as two 8 bit values (what about endianess?)
Very normal with the settings you have used.
Why a Pulse trigger instead of an Edge trigger ? Did you use any Trigger Holdoff ?
Hi Tautech,
no I didn't use any holdoff. And I'm using the pulse trigger in this case, because the before the signals I want to see there are many shorter pulses, which are ignored in this way.
I wouldn't mind using something else, but it works perfectly.
As I mentioned, the signals look as they should, the decoding is right, I'm only confused, why the decoded data is not aligned with the bits.
It's no drama, of course, just a little strange thing.
What setting especially made you write "Very normal with the settings you have used."?
Thanks & cheers,
Anik
Very normal with the settings you have used.
Why a Pulse trigger instead of an Edge trigger ? Did you use any Trigger Holdoff ?
Hi Tautech,
no I didn't use any holdoff. And I'm using the pulse trigger in this case, because the before the signals I want to see there are many shorter pulses, which are ignored in this way.
I wouldn't mind using something else, but it works perfectly.
As I mentioned, the signals look as they should, the decoding is right, I'm only confused, why the decoded data is not aligned with the bits.
It's no drama, of course, just a little strange thing.
What setting especially made you write "Very normal with the settings you have used."?
Thanks & cheers,
AnikBy what I see on the screenshot the scope is in Stop mode, that is not running and the reason why the decode is not aligned. When triggering is solid the decode should align with the bits while the scope runs.
By what I see on the screenshot the scope is in Stop mode, that is not running and the reason why the decode is not aligned. When triggering is solid the decode should align with the bits while the scope runs.
There is absolutely no reason for decoding to depend on a trigger! In fact, having decoding alignment depending on a trigger will mis-align the decoding in many circumstances.
QuoteThere is absolutely no reason for decoding to depend on a trigger! In fact, having decoding alignment depending on a trigger will mis-align the decoding in many circumstances.
If it´s so, for what are the special decoding trigger types good for ?