Siglent Technical Support join in EEVblog

[pantelei4]

Do not use this firmware, it has problems for older HW.
SHS800
http://www.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SHS800_V100R003B01D02P02R7.ADS

For HW version 1-31-3.3, does the new firmware not work?

For both series the Continuity buzzer response has been improved:

Is this all a change?
And what about the normal trigger mode?

[tautech]

Do not use this firmware, it has problems for older HW.
SHS800
http://www.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SHS800_V100R003B01D02P02R7.ADS

For HW version 1-31-3.3, does the new firmware not work?

For both series the Continuity buzzer response has been improved:

Is this all a change?
And what about the normal trigger mode?

Post #593 edited and updated with correct links.

[pantelei4]

tautech, Please tell us how to properly update the firmware, so as not to make a brick?
http://www.siglentamerica.com/USA_website_2014/FAQ/SHS/upgrade_the_latest_firmware.pdf

[tautech]

tautech, Please tell us how to properly update the firmware, so as not to make a brick?
http://www.siglentamerica.com/USA_website_2014/FAQ/SHS/upgrade_the_latest_firmware.pdf

Yes, it is a little confusing but if you press the > (right) button the incorrect file warning disappears.



You have correctly navigated to the firmware update file from within the UI, it's highlighted (selected) and now press "Load" (F4). Prompts after this point are self explanatory and the SHS will ask to be power cycled when the update is finished.

Firmware load failures mostly arise from power interruptions while updating but the for the SHS series you do have the inbuilt battery should there be a power failure.
Some use a UPS for power security while updating and that's a good safeguard but without one try to resist doing updates in stormy weather when power failures are more likely.

As a footnote the new 2R7 FW now works as expected in my SHS810. 

[pantelei4]

Yes, I updated the firmware. Scaling in the normal mode of the trigger does not work, as before. The buzzer is intermittent, the continuity is unusable.
Siglent kicked the programmers out of the work, who did the firmware?

They made a bad color gamut when the screen is inverted, you can not read the menu. And many more bugs. 

[tautech]

Yes, I updated the firmware. Scaling in the normal mode of the trigger does not work, as before. The buzzer is intermittent, the continuity is unusable.
Siglent kicked the programmers out of the work, who did the firmware?

They made a bad color gamut when the screen is inverted, you can not read the menu. And many more bugs. 

Please make a detailed list with each bug, describe it and how to replicate it.
Screenshots are useful too, please post any that better show the problems than text does.
All this is what the engineers find the most helpful.

Post the list here or PM it to me, either way I will bring it to their attention.

[pantelei4]

SHS806 On the old and new firmware equally.
1.Noise at inputs without signal
2.Delay between channels, the same signal at the inputs.
3-6.Interpolation sin? one picture with different time/div
7. No interference, which is not, 10kHz ?? 
Does Siglent have no engineer to see it? 
Let him pay me for testing their bad firmware.
This is not all, there are more than a dozen bugs.
 With such shortcomings SHS series of oscilloscopes should be generally forbidden.

[GeorgeOfTheJungle]

While you are at it pass them this one too with a footnote: "SDS1102X can't decode, thank you very much"

[tautech]

Emails sent.

[Tjuurko]

SDM3055 and problems with temperature measurement.

SDM3055 fw: 1.01.01.16R2

For example, the dependence of the resistance measurement on a 2-wire circuit is plotted against time. Moments of switching ranges can be seen. (see R.png)

1. Switch to TEMP (PT100). Switching moments became very visible. The switching time is about ~700 ms. (see T.png)

2. When measuring the temperature using the PT100, the entire range is divided into two automatically selected sections: (-200.00 ... + 379.50) °C and (+266.34 ... + 850.00) °C. Nowhere is this moment reflected.

3. Each resistance measurement by the SCPI command blocks the operation of the temperature meter (PT100) by ~800 ms.
For example, such a cycle of commands will only record the change in resistance, the temperature will not change.

CONF:RES AUTO
READ?
CONF:TEMP RTD,PT100
READ?

After the end of the cycle, the temperature will start to change and be measured correctly only after ~50 measurements.

4. I would like to get a 4-wire temperature measurement for the PT100.

[pantelei4]

Siglent series SHS800/1000
7. Math scale 100nV By default and changes are not remembered the next time you start. 
8. Probe 10X ?nd other coefficients, except 1X, are not taken into account in the calculation Math channel and Skope Trend Plot.
In the screenshot CH1+CH2  2V/djv Math scale 200mV/div 

[DazA1]

As another SHS806/1062 user i would like to add a few of the bugs i found.


- I agree with pantelei4 the probe settings (X10 X100) are ignored in Scope Trend Plot mode.

- The trend CSV files (both meter & scope trends) are not time/date stamped which makes it harder to plot and understand later.

- The filter turns off once the scope is triggered or if you press the Run/Stop button and then you have to go back to turn it on again.

- When saving a BMP image sometimes the waveforms would disappear from the screen for a second and the saved BMP image would have no waveforms in it.

- In inverted screen colours mode it is difficult to read the values when you select All Measurements in cursor measure mode (yellow text on a light green background).

- and the last one (maybe if someone else can test this on theirs) when measuring a 9V battery in meter trend mode moving the cursors around you can get the voltage to briefly drop to exactly 1.000mV.


I think there maybe a problem with EMC susceptibility as when using it on industrial control panels it seems to lock up or not save files properly. In these panels there can be thyristors and IGBT's switching heater banks and motors. I don't use it enough in that environment to be a 100% sure though.

Overall i like my Siglent SHS scopes but the firmware does seem to let them down. And before anyone asks i have sent emails to Siglent but i got told we are looking into it (2015 & 2016) so i gave up, maybe if everyone with a Siglent SHS scope adds there bugs to this list maybe something will be done.

[Siglent America]

Thank you for your comments.
We in the USA are familiar with a couple of these issues but I have passed your list on the the product manager and VP.

Thanks again.

[Andbyk]

maybe if everyone with a Siglent SHS scope adds there bugs to this list maybe something will be done.

I have the rebranding version of SHS810 for Russia named AKIP4125/2 since 2014. Plus to mentioned bugs I would like add my favorite pain - storage system. I wrote about https://www.eevblog.com/forum/testgear/siglent-shs810-saverecall-problem/msg706464/#msg706464
Since 2016 Russian distributor of Siglent's devices don't sold AKIP4125/2 anymore and changed name to AKIP4125/2A.
I asked they which difference beetwen devices. They said - we don't know exactly, but specification the same.
I guess, Siglent fixed some bugs in hardware of SHS800 and new devices don't has old problems.
I don't beleve that Siglent will  be do anything for repair old  version devices
I use some usefull properties of SHS810 for floating measurements and works in field and don't require more from it. Device's battery enouth for 3-4 hour of working.

[tautech]

I guess, Siglent fixed some bugs in hardware of SHS800 and new devices don't has old problems.
I don't beleve that Siglent will  be do anything for repair old  version devices
I use some usefull properties of SHS810 for floating measurements and works in field and don't require more from it. Device's battery enouth for 3-4 hour of working.

My personal SHS810 has a 2013 production date and the latest firmware makes no distinction of when the unit was made. So use the new firmware in any SHS but unfortunately the new firmware apparently only improved the Continuity test response. 

So yes, we expect more improvements but they can be only as good as the quality of feedback to the engineers.
Got what you think is a bug, then list it here.

[Andbyk]

My personal SHS810 has a 2013 production date and the latest firmware makes no distinction of when the unit was made. So use the new firmware in any SHS but unfortunately the new firmware apparently only improved the Continuity test response. 

I installed 2R7 version but don't see any difference from 2R2.

[pantelei4]

So use the new firmware in any SHS but unfortunately the new firmware apparently only improved the Continuity test response. 

Good hardware was spoiled by bad firmware.
We must make Siglent fix all the bugs.  

[tautech]

So use the new firmware in any SHS but unfortunately the new firmware apparently only improved the Continuity test response. 

Good hardware was spoiled by bad firmware.
We must make Siglent fix all the bugs.  

Are you saying the new firmware created all the issues you have reported and they were not there before ?
To get good results we must give good detailed feedback.

[pantelei4]

Are you saying the new firmware created all the issues you have reported and they were not there before ?

The same problems were with the old firmware.
2R7 version don't  any difference from 2R2.
I wanted to say that bugs corrupt a good device.
I like it, but I often want to break it against the wall.   

[Siglent America]

The "bug" was actually just a slower-than-desired continuity beeper function. We made a hardware modification that also required the FW update and the difference is obvious. Units that have shipped in the last year or so have included this new HW. Upgrading an older design to the newer FW will have no effect on the instrument.

[pantelei4]

We made a hardware modification that also required the FW update and the difference is obvious.

What should I solder?

[Siglent America]

We made a hardware modification that also required the FW update and the difference is obvious.

What should I solder?

The new board has more than one component changed or added as well as a new etch or jumper.

[StillTrying]

I'm amazed at how may bugs there are in my CML+. 

https://www.eevblog.com/forum/testgear/siglent-cml-firmware/25/

[tautech]

While you are at it pass them this one too with a footnote: "SDS1102X can't decode, thank you very much"

Initial feedback from the factory is at timebases slower than 10ms there is a problem that the engineers are looking at.

[rf-loop]

While you are at it pass them this one too with a footnote: "SDS1102X can't decode, thank you very much"

Initial feedback from the factory is at timebases slower than 10ms there is a problem that the engineers are looking at.

Yes, error need urgently and perfectly fix - and at once without training rounds .