Siglent Technical Support join in EEVblog

[tautech]

Very interesting how to do this?

Now your scope is fixed please take any discussion of hacking to another thread, this one:
https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/

[McBryce]

Hi tautech,
      any idea when Siglent are going to release the latest Firmware for the SHS806? New units come with 5.09.01.07 (which also doesn't fix all known bugs), but the Siglent site only offers 5.09.01.05.


McBryce.

[tautech]

Hi tautech,
      any idea when Siglent are going to release the latest Firmware for the SHS806? New units come with 5.09.01.07 (which also doesn't fix all known bugs), but the Siglent site only offers 5.09.01.05.


McBryce.

Watch the websites as it's to be released soon due to your request. 

[McBryce]

Top!

Now if they could manage to fix up the graphic settings that mess up after restarting the device, I'd be even more impressed 


McBryce.

[pantelei4]

Watch the websites as it's to be released soon due to your request. 

I wonder what will be fixed this time?
They fixed most of the oscilloscope bugs last time. Trendplot bugs have not been fixed.
I'm afraid to flash the device again, so as not to get a brick.

[tautech]

Watch the websites as it's to be released soon due to your request. 

I wonder what will be fixed this time?

Dunno, not a lot I believe but since it's been a while since the last one Siglent thought it was appropriate to fulfill the request.

I'm afraid to flash the device again, so as not to get a brick.

Fear not, there have been developments for recovery of SHS800 models, well 60, 100 and 150 MHz ones.
Another member had bricked his AKIP (rebrand) and some member kindly supplied him with a memdump of which he flashed into his bricked unit and recovered it. 
See here:
https://www.eevblog.com/forum/repair/try-to-find-siglent-shs806-oscilloscope-firmware-(dump)/

I too have this memdump file should someone need it and I need to do a little write up on the chip to flash as I have a busted SHS board here to inspect.

[tinhead]

tested right now the VNA page:

- text size in top of the pages is perfect for me
- text under overview section is now too big (bottom part of http://int.siglent.com/products-overview/sva1000x/#navs )
- text under other sections small, but still ok (bottom part of http://int.siglent.com/products-application/sva1000x/ )

id do always use 100% scaling everywhere, no issues with 1900x1080 Resolution. However few things are not working properly (tested with brave, firefox, chrome, opera, edge and safari - yeah i know), like filter in download section (it jumps back to "select .."). App notes and resources links are broken, faq link typo -> http://int.siglent.com/common/fqa/, troubleshoting/maintenance/op. tips links in chinese language -> http://int.siglent.com/common/guzhang/ (think ggling for tips ...), some pictures are toooooo large (e.g. http://int.siglent.com/about/ , the picture on the top of the page have 7000x4000 resolution, this is 15MB jpeg - one can see the photoshop editing http://int.siglent.com//u_file/images/19_08_23/cb1489b73f.jpg, other Images on that page are gif/png … if photoshop, then the ong one, really, who cares about building size and then with fake logos? One can easiy find that this HQ Building is middle of tech Center, and wow, i found two other companies in exact same build with photoshoped logo on it - e.g. https://www.ecerimg.com/nimg/e4/f7/ea4d7231a1801c4c9d22166a4b5d/liantronics_co_ltd.jpg so no, please edit this, this is cheap marketing, a picture of garage is better), warranty check is not working -> http://int.siglent.com/account.php?module=warranty (but it works on ...trial.ly200...)  , few images have focus but no content (yet, i assume it will be added), filer from product section are broken as well (e.g. sds1000x-e page-> resources -> Firmware does query http://int.siglent.com/download/firmwares/?ProId=12 but results are from every product, not proId=12).

Overall i like the design, but it must be finalized

few other things:

- i can create new account, when i save it, it does forward me to ///. No problem, refresh the website shows me logged in
- i can't add my products, error "Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://219.133.........................home/intsiglent/public_html/member/module/product-registration.php on line 32"

Sure, when i create account on siglent.trial.ly200 and try to register my products, then everything works.

One additional side note: i have SAG1021, siglent.trial.ly200 does recognize it wrongly "Product number： SDG2122X Serial number： SAGxxxx". I do have two SDS1204X-E, one with older S/N can be added as SDS1204X-E (Product number： SDS1204X-E Serial number： SDSMMDxxxxx), the newer one however will get recognized as "Product number： SDS1202X-E Serial number： SDSMMExxxxx", so wondering is this is general warranty check problem, or only due to my test on siglent.trial.ly200

[koba30]

Please use the Default button and return the DSO to factory settings.

Monitor usage settings and see if the problem reappears.
If it does please report the settings used at the time so we can report them to the factory for their engineers to investigate.
You can save the settings used in the Save/Recall menu.

Oh, and be sure to power OFF using the power button so the system can shut down properly.
It is NOT advisable to use the wall switch to power OFF.

Please use the Default button and return the DSO to factory settings.

Its Done.

Monitor usage settings and see if the problem reappears.
If it does please report the settings used at the time so we can report them to the factory for their engineers to investigate.
You can save the settings used in the Save/Recall menu.

Ok, I will monitor and inform to you any issue.

Oh, and be sure to power OFF using the power button so the system can shut down properly.
It is NOT advisable to use the wall switch to power OFF.

I always use the power button, the DSO is powered by a PSU to avoid a unexpected turn off.

Hi,
The problem persists, I even had to turn it off and on twice to get to use the DSO.
Attached the setup files and Excel file with the data of different setups.



Regards

[tautech]

The problem persists, I even had to turn it off and on twice to get to use the DSO.

OK thanks for the further info.

Have you tried reinstalling the latest firmware ?
Do the problem persist when the scope is NOT powered through the UPS ?

Factory support is on holiday until next week.

[koba30]

The problem persists, I even had to turn it off and on twice to get to use the DSO.

Have you tried reinstalling the latest firmware ?

Yes, attached pictures of firmware upgrade.

Do the problem persist when the scope is NOT powered through the UPS ?

Yes with or without UPS, the problem persist (stuck on logo at power on) when the Ac line power supply is removed for a least 12 hours.

Thanks in advance.

[kvd]

Hi all,

I recently updated the firmware on my SDS1202X-E and I noticed this blue badge with a B in it. I never saw it in previous firmware versions. Can anybody tell me what it signifies?

Greetings, Koen.

edit: gated measurement perhaps?

[tautech]

Is it still there with BW limiting OFF ?

[BillB]

I have a number of these supplies (all running the latest FW) LAN connected using static IP addressing.  One the same LAN (same switch) they behave differently than other Siglent connected equipment (SDM3045X, SDG1032X, SDS1104X-E) that are also set-up with static IP addressing. 

Some of the issues include just setting the IP address.  Sometimes it seems as if I need to set DHCP and receive an assigned address before setting a static IP will take.

Another more pressing issue is that I've had an SPD3303X-E become unresponsive on a static IP after a few days.  It would not respond to pings, power cycles did not bring back connectivity, nor did resetting the IP to the same or different static value.  I had to change to DHCP, receive an address, then switch back to static mode and enter the static IP again for it to become responsive again.

On the same switch, an SDS1104X-E serving up it's instrument control page is rock-solid (and very nice, BTW)

Finally, it would be great if the EasyPower application would allow for running multiple instances so that more than one device can be controlled at a time.

[tv84]

power cycles did not bring back connectivity

Very strange!!!

What about a power cycle of the switch, at that moment, instead of power cycling the equipment?

[BillB]

power cycles did not bring back connectivity

Very strange!!!

What about a power cycle of the switch, at that moment, instead of power cycling the equipment?

I did physically unplug the cable from the port and back with no change.  I can't power down the switch (other stuff connected and working) but really don't it's the switch as I've seen this behavior with multiple SPDs on switches of different manufacturer.  Besides, every other device on the switch is working properly.

[tv84]

Assuming SPD's fault, looks like an example of a bad re-initialization of software structures. 

[tautech]

power cycles did not bring back connectivity

Very strange!!!

What about a power cycle of the switch, at that moment, instead of power cycling the equipment?

I did physically unplug the cable from the port and back with no change.  I can't power down the switch (other stuff connected and working) but really don't it's the switch as I've seen this behavior with multiple SPDs on switches of different manufacturer.  Besides, every other device on the switch is working properly.

Bill, can you state which FW and SW versions of the SPD's and EasyPower you're using ?
For the SPD1kX there was new FW back in April and at the same time a new EasyPower version was released too.
https://siglentna.com/service-and-support/firmware-software/dc-power-supplies/#spd1000x-series

[BillB]

Bill, can you state which FW and SW versions of the SPD's and EasyPower you're using ?
For the SPD1kX there was new FW back in April and at the same time a new EasyPower version was released too.
https://siglentna.com/service-and-support/firmware-software/dc-power-supplies/#spd1000x-series

I don't have the SPD1168 in front of me, but I am sure it is running 2.1.1.8 from April.

Easypower V100R001B01D01P18

SPD3033X-E  1.01.01.02.05,V3.0

I can't say for sure, but I don't think I've seen the issue while EasyPower is connected to the supply.  I am running a test now with a 3303 connected with EasyPower to see if it ever loses communication.

[tautech]

Thanks Bill. Siglent have set up some connectivity tests to see if the can find any similar issues.
The better info we can give them the better chance of them replicating the problem.

I can't say for sure, but I don't think I've seen the issue while EasyPower is connected to the supply. 

This is interesting, are you using another program to communicate with SPD's ?
Or is it the LAN connection is unresponsive/broken when you want/need to use it ?

[BillB]

Thanks Bill. Siglent have set up some connectivity tests to see if the can find any similar issues.
The better info we can give them the better chance of them replicating the problem.

I can't say for sure, but I don't think I've seen the issue while EasyPower is connected to the supply. 

This is interesting, are you using another program to communicate with SPD's ?
Or is it the LAN connection is unresponsive/broken when you want/need to use it ?

I've seen the static-IP-not-working-until-DHCP-used issue more often than I have seen the device-stops-responding-on-ethernet issue.

Occasionally I am using SCPI automation with PyVISA based scripting, but most often I am trying to connect with EasyPower.  The times I have seen it unresponsive have been with the device on for a long period of time without anything communicating, then I try to fire up EasyPower.  EasyPower doesn't see it, then I try to ping the supply and it does not respond to pings.
 

[n3mmr]

Can one calibrate an SDS1204X-E against external accurate sources in any real sense?

I now have a gpsdo as a ref clock for my sdg2122x and a very accurate voltage source available, and the measurements performed by the DSO are off by "significant" amounts, though still well within spec.

[Performa01]

Can one calibrate an SDS1204X-E against external accurate sources in any real sense?

I now have a gpsdo as a ref clock for my sdg2122x and a very accurate voltage source available, and the measurements performed by the DSO are off by "significant" amounts, though still well within spec.

All Siglent X-series DSOs provide a Self Calibration feature for the amplitude related parameters. The internal reference for this has the accuracy and stability to sufficiently serve the purpose for the entire lifetime of the instrument.

I do not know if there is any internal clock frequency adjustment (which would require a VCTCXO as internal clock source). Midrange instruments like the SDS5000X provide the option for using an external clock if better timing accuracy is critical.

Here are some general considerations:

•   Calibration accuracy in a DSO is limited by the resolution of the ADC. For the SDS1000X-E, SDS1000X, SDS2000X-E and current SDS2000X, there are 25 LSB/division, consequently accuracy can never be any better than 1/25 division.
•   For very low levels, calibration accuracy is limited by noise as well as the output range and resolution of the internal calibration source (which might not be optimized for the high sensitivities below 10mV/div).
•   In general, it makes little sense to adjust an instrument to any accuracy far better than its specification. Even if a certain (better) accuracy could be achieved, calibration would be void after a short while, because of thermal drift and limited long-term stability. DSO acquisition is rather complex and the attenuators, amplifiers and references are optimized for wide bandwidth and decent pulse response rather than high accuracy and stability, which would be difficult to achieve at the same time (and very expensive).
•   It’s the same for all instruments. For instance, a decent DMM is more accurate than a DSO (but with an extremely limited bandwidth), and it can be adjusted during the calibration process. But even if you adjust it to a much higher accuracy than specified, this is just a momentary situation and the specification still applies, i.e. the error margins have not changed for the specified calibration interval. You’d need a better reference, better dividers, more precise amplifiers and a better ADC (and then some), where “better” stands for more resolution, less noise, less offset and linearity error, less temperature drift, better long-term stability and a better design that takes care of interferences, voltage drops and thermal EMF more effectively. In a DSO, there are other (partially contradicting) priorities.

[n3mmr]

Even my lowly TTi  handheld frequency counter has a calibration adjustment on its back...

And since my gpsdo delivers accuracy around 10E-10 setting the 8th digit correct seems to be reasonable.

The counter maintains the adjusted accuracy over at least several days and readjustingis not a problem.

So, while your argument is well understood, there are still short term advantages to calibrating.

[Performa01]

I would be surprised if the cheap 25ppm clock oscillator in the entry level SDS1000X-E series can be calibrated at all. There is absolutely nothing in the service manual that would support such a speculation.

Frequency counters on the other hand always need to have some adjustment, since their one and only purpose is to measure frequencies with reasonable accuracy. Cheap specimen might just have a descrete X-tal with a series trimmer capacitor to pull the frequency, so it's very common that such devices can (and need to be) adjustable, even from the outside.

An entry level DSO should not be compared to a dedicated frequency counter, not even a "lowly" one. This is also why I still have fond memories of my old analog scope, which had a dedicated buffered output for the currently triggered channel, where I could have a real frequency counter permanently connected.

The SDS5000X has a much more accurate 1ppm timebase and I have negotiated long before that future DSOs above the entry level will have that as well.

As already stated, the SDS5000X accepts an external clock on top of that, so any desired accuracy can be achieved.

I'm sorry to say that features like more accurate (and maybe even tuneable) clock oscillators and even more so external clock in/out are features that cost money. The better oscillator alone would be a few dollars more and that really matters for an instrument that is sold for a few hundred dollars to consumers, where the factory only gets a fraction after duties and import fees, taxes, distributor/dealer profit margins and transportation costs have been paid.

[n3mmr]

I looked thru the calibration chapter of the sdg2000x service manual and found something a little confusing.
There are references to Python scripts "prepared previously", as in
 "Double click and run the script FeedbackAdjust.py prepared previously."

Are these scripts described somewhere, or downloadable or are you supposed to design them on your own?