Siglent SHS810 save/recall problem

[Andbyk]

I have Russian version device SHS810 – AKIP4125/2 (sw 3.01.02.01/hw 1-31-3.3). In SAVE/RECALL mode I found strange trouble. This trouble appears as interaction between memory cells of device. If I save in device memory waveforms with different vertical sensitivity when I recall it again amplitude of waveforms are false.
For ex:
-   waveform in the cell ?1 has profile with 1,0V/div;
-   waveform in the cell ?2 has profile with 10V/div;
-   if I recall waveform from cell ?1 after waveform from cell ?2 amplitude ?1 will be in 10 times more than true waveform ?1;
-   if I recall waveform from cell ?2 after waveform from cell ?1 amplitude ?2 will be in 10 times less than true waveform ?2;
-   for recall true waveform I press RUN/STOP button and then F5 button again;
-   in the time area any distortions are absent.

Could anybody please explain me such behavior of my device? Is this SW or HW trouble? May be owner of SHS800 devices met similar problem?

[tautech]

Welcome to the forum.

I'll have to get my SHS810 out and test to see if I can duplicate your problem.
Watch this thread. 

Siglent have a tech support thread for assistance if needed:
https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/

[Andbyk]

Thank you very much Tautech for link

[tautech]

I could not replicate your problem with my SHS810. FW 3.01.02.01 and same HW as yours.
The latest Siglent FW is 3.01.02.02R2
http://www.siglentamerica.com/support_software_15

[Andbyk]

Thank you for link! But I have tested this american version last week. Problem not disappear 

[tautech]

Can you post some screen shots?

[Andbyk]

A,B -are true WF. C -recall A after viewing B. D -recall B after viewing A

[tautech]

A couple more questions

Is this a new unit?
How long have you owned it?

I see you have the BW limit on, why?
Does your problem show when using the probe cal 3V 1KHz waveform?

At Recall waveform the scope is in Run/Stop mode, then to clear the recalled waveform press Run/Stop to return to live waveform input.

I'm tring to assertain if the way you are using the scope is the problem, sorry but I have little idea of your skill level and I'm only trying to help if I can. 

[Andbyk]

Unit's age is 1,5 year.
I'm single owner.
BW limit on because I don't need wide BW for test signals.
Problem is out when I use  calibrator  with different vertical sensitivity (0,5 1,0 10V/div).
Run/Stop I use for clear false WF and recall true WF by pressing F5.
The same problem I see when recall WF from USB flash drive.

[Andbyk]

I found important dependence!
Save/recall problem appear when I save WF thus:
trigger's mode - AUTO;
press Run/Stop for stop WF;
save WF in device memory.
If I save WF with NORMAL mode trigger without pressing Run/Stop problem is out!
If save WF with SINGLE mode trigger problem appear again
Can you explain me this dependence?

[tautech]

Can you explain me this dependence?

I've pointed Siglent technical support to your last post.
Let them take the time to explore the problem and report back. 

[Andbyk]

Thank you very much!
I hope Siglent will help me

[tautech]

Thank you very much!
I hope Siglent will help me

As your HH is branded as AKIP, you should contact them too about your problem.
Your local brand distributor should always be your first contact.
Do understand AKIP have this unit with their name on it, so it is their responsibility to support it in the first instance, not Siglent's.

I can't say if it's a bug, it might be. 
Last Siglent FW was in March, so I'd guess the next FW 6 months from then.

So looking forward, you should keep an eye out for new FW updates for the next few months.

But you have found a solution in the method you store and recall, hopefully that's a good work around untill new FW is released.

[Andbyk]

Yes of course!
Contact with distributor was my first  step.
But they said me "we don't see such problems on our devices". They didn't contact with Siglent about my problem, I think.
I'll be continue contact with my distributor for change FW or device.
I guessed to get response from owner SHS8** devices on this forum.
Thank you very much tautech for help!

[tautech]

I can tell you that the problem has been refered to Siglent R&D and if they can duplicate it there should be a fix sometime in the future.
Siglent themselves have been reluctant to post in this thread as you understand because they where not the immediate supplier.

Good that these problems are bought and aired here, hopefully we all benefit from the improvements.

It's disappointing that you did not get a better hearing from AKIP. 

[DazA1]

@Andbyk

Does changing the memory depth make any difference? I have had problems saving files to USB in LongMem mode (SHS806 software 3.01.02.02R2 Hardware 1-31-3.3).

The files are always exactly 2.00Mb and when i try to view them they either fail to load (error message) or the waveform is there but is really small.

I have contacted Siglent and sent pictures, files and even a video i took but that was 2 months ago and they went quiet.

I have just watched the video again and noticed that i had to reduce the time base to get the waveform on screen, it also had a lot of flicker on the screen?

[tautech]

@Andbyk

Does changing the memory depth make any difference? I have had problems saving files to USB in LongMem mode (SHS806 software 3.01.02.02R2 Hardware 1-31-3.3).

The files are always exactly 2.00Mb and when i try to view them they either fail to load (error message) or the waveform is there but is really small.

I have contacted Siglent and sent pictures, files and even a video i took but that was 2 months ago and they went quiet.

I have just watched the video again and noticed that i had to reduce the time base to get the waveform on screen, it also had a lot of flicker on the screen?

Did you get confirmation of the stuff you sent them?
Latest FW you've mentioned was released in March and if your problem is identified as a bug it should be fixed with the next FW, normally every 6 months.
I'd ask in this thread how they are getting on with your problem:
https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/

[Andbyk]

@Andbyk

Does changing the memory depth make any difference?

I don't found any dependence from memory depth. 
Save/recall problem is out only if I save waveform to device or USB with NORMAL mode of trigger.

[Andbyk]

Another bug from SHS810.
If I save Reference waveform when trigger has SINGLE mode I get very interesting pictures 
When trigger has AUTO or NORMAL mode Ref A and Ref B are saving correctly.
Besides, colour of messages for Ref A and Ref B on display must be vice-versa. I think 

[Andbyk]

The good news for Siglent!
Today I couldn't   to get yesterday's results for all modes of trigger
Reference waveforms were saving finely!
What will say my device tomorrow?

[Wall-E]

The SHS800 DMM's 'Continuity' test doesn't work properly.

https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/msg761207/#msg761207

[Andbyk]

My SHS810 has the same problem with DMM's 'Continuity' test.

[Wall-E]

The SHS800 DMM's 'Continuity' test doesn't work properly.

https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/msg761207/#msg761207

My SHS810 has the same problem with DMM's 'Continuity' test.

Siglent now has a fix for the flawed SHS800/1000 Oscilloscope's DMM 'Continuity Test' !
Contact Siglent Customer Support and tell them that you would like your unit corrected.
NOTE: The SHS800/1000's DMM 'Continuity Test' is a useless function as it is currently in these units.  Good news: You can now get it fixed. . .
More info here: https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/msg831827/#msg831827