You did well. Maybe it is my mistake... age catches up quickly in Covid times. I used to parse those things but I think it stopped at the X-E...
Thanks
Ah, your parser is pretty impressive! I have some work ahead of me
I've just upgraded a 'fully optioned and fully bandwidthed' one from 1.3.7R5 to 1.3.9R4 without any issues and it seems to work fine at a first glance.
Just wondering how to configure a network share.
Under I/O-Settings / Net Storage there is a directory to be configured.
Suppose it should be an UNC path, but there is no "\" available on the virtual keyboard.
I'd like to access a share like: \\fritz.box\FRITZ.NAS\Dokumente\Share_Siglent
Tried with just the IP-address as directory and credentials, leading into "Mount directory error. ..." Trying again gives this error again and the system then hung completely. Only a power cycle helped.
Linux uses /
Sorry. Windows-blindness.
thx a lot. Works like a charm now.
Don´t know what I´ve meausured before, now I got appx 650ps too.
Seems like my results are slightly faster, but also looks like worse overshoot. Did you check how much overshoot you got?
Hi,
Did you check how much overshoot you got?
Didn´t know it anymore, can check it tomorrow.
Checked the bodnar also on a lecroy 500Mhz waverunner, it´s overshoots are slightly less.
Hi,
Did you check how much overshoot you got?
Didn´t know it anymore, can check it tomorrow.
Checked the bodnar also on a lecroy 500Mhz waverunner, it´s overshoots are slightly less.
What does each scope show when you turn off sinc, to show the raw sample points? Also, are both in peak detect or normal mode? If normal, it would be interesting to see if they're closer when peak detect is enabled on both.
Also, are both in peak detect or normal mode?
Basic fundamentals:
With full ADC sampling rate (without decimation) Peak detect have no effect, of course.
As you can see all these, least as far as I can see, have done with full sampling speed.
Also, are both in peak detect or normal mode?
Basic fundamentals:
With full ADC sampling rate (without decimation) Peak detect have no effect, of course.
As you can see all these, least as far as I can see, have done with full sampling speed.
Oh. You're right. Good call.
It would be interesting to see the raw points for both, in case there's a difference in the sinc construction method being used.
The last FW update has about half the size oft the preceding updates.
Thats interesting ?
The last FW update has about half the size oft the preceding updates.
Thats interesting ?
No problem. All help/language files what have no changes do not need update.
But that means it's not a cumulative update, but requires a certain minimum version to build upon?
But that means it's not a cumulative update, but requires a certain minimum version to build upon?
It's not like you can buy empty scope without OS like with PC-s..
If you see problem with someone not upgrading for 10 years, yeah you might need some interim upgrades.
That is not something unusual.
Might be inconvenient in that case, but not a show stopper. It simply needs to be documented.
And most of the people upgrade on regular base anyways.
What does each scope show when you turn off sinc, to show the raw sample points? Also, are both in peak detect or normal mode? If normal, it would be interesting to see if they're closer when peak detect is enabled on both.
Here are from mine with sinc off. I could not see any difference with peak detect or not. Also checked both AC and DC coupling without any difference.
Fast mode:
And slow mode:
If you see problem with someone not upgrading for 10 years, yeah you might need some interim upgrades.
That is not something unusual.
Might be inconvenient in that case, but not a show stopper. It simply needs to be documented.
Should definitely be documented. I added it in the bug thread.
What does each scope show when you turn off sinc, to show the raw sample points? Also, are both in peak detect or normal mode? If normal, it would be interesting to see if they're closer when peak detect is enabled on both.
Here are from mine with sinc off. I could not see any difference with peak detect or not. Also checked both AC and DC coupling without any difference.
Fast mode:
And slow mode:
Best way to look at fast repetitive signals is by using dot mode. It will , in effect, act as a sort of an ETS mode and show much better signal fidelity.
Try it.
Like RF-loop said, peak detect is not working at all at max sample rate. Which, because of long mem, you will keep to quite long timebases.
But that means it's not a cumulative update, but requires a certain minimum version to build upon?
It's not like you can buy empty scope without OS like with PC-s..
If you see problem with someone not upgrading for 10 years, yeah you might need some interim upgrades.
That is not something unusual.
Might be inconvenient in that case, but not a show stopper. It simply needs to be documented.
And most of the people upgrade on regular base anyways.
In principle it's OK, but what it saves in download bandwidth is easily outweighed by the inconvenience of having to download multiple versions and applying them in the correct order. If I were Siglent, I'd distribute full firmware updates only.
Having an update mechanism that enforces dependencies on previous firmware versions is pretty much mandatory in that case. Merely documenting that you need to install all previous updates is not enough. It only leads to customer frustration and an increase in support tickets.
Can anyone confirm that it's impossible to install this latest firmware on a scope with an older firmware than the previous version?
Can anyone confirm that it's impossible to install this latest firmware on a scope with an older firmware than the previous version?
The update instructions say it's compatible from 1.3.5R5. You get the newest app in any case, but the supporting files will be "old", like documentation.
A bit offtopic but just popped up after i did some play around after successfully updated to the latest FW:
Is there a way to load the waveform data of the Bode plot also? Neither the Webinterface not the EasyScopeX SW downloads correct data. Csv can be saved locally via dialog, but then you have to operate the USB stick all the time.
Best way to look at fast repetitive signals is by using dot mode. It will , in effect, act as a sort of an ETS mode and show much better signal fidelity.
Try it.
Tried it now
This is somehow best reconstruction about your signal how ADC see it and best what this instrument can.
Naturally no one know what it is in source output without connected to oscilloscope and also when connected no one know how it change from oscilloscope input port (BNC) and when it travel to ADC input.
As can see this figure shape can also very perfectly find in image where is lines with Sinc Off. When know how to look.
Does anybody know the maximum power of the 50 Ohm input resistors?
Is there any input protection in place?
I'm thinking of following the performance checks from the HP8015A pulse generator manual and HP recommends a 20db power attenuator.
HP8015A output voltage is max +/- 8V into 50 Ohms.
Does anybody know the maximum power of the 50 Ohm input resistors?
Is there any input protection in place?
I'm thinking of following the performance checks from the HP8015A pulse generator manual and HP recommends a 20db power attenuator.
HP8015A output voltage is max +/- 8V into 50 Ohms.
There is maximum input voltage specified, as written right next to BNC: < 5VRMS at 50 Ohms
+/-8V squarewave is 8V RMS...
So attenuator is in order..
A 6dB (power, /2 in voltage) attenuator will drop it to 4V RMS an 4V P-P, well into range.
Just "upgraded" to latest version...
Some nice features (like "full span" on the FFT).
A few gripes...
Any way to reduce the absolutely ridiculous fixed 4 decimal places of "precision" that the trace axis seem to have gained for horizontal and vertical scales in the last release (or maybe the one before that) - I'm particularly looking at the FFT? And why does the FFT information now move out of the corner of the screen...
Does anybody know the maximum power of the 50 Ohm input resistors?
Is there any input protection in place?
I'm thinking of following the performance checks from the HP8015A pulse generator manual and HP recommends a 20db power attenuator.
HP8015A output voltage is max +/- 8V into 50 Ohms.
There is maximum input voltage specified, as written right next to BNC: < 5VRMS at 50 Ohms
+/-8V squarewave is 8V RMS...
So attenuator is in order..
A 6dB (power, /2 in voltage) attenuator will drop it to 4V RMS an 4V P-P, well into range.
Thx 2N3055! Advantage for those able to read.
Will order some attenuators to fill my TEA beginner's drawers. :-)