Siglent SDS800X HD 12 bit DSO's

[2N3055]

Hey all you new Siglent users, I've just scanned through hours of posts and have somehow not seen the answer to the following Q.
Can the activation codes for the logic analyzer (SLA1016) on the 1104 and 1204 be used on the 800 series, or do you need to buy a new activation code when you buy the new 800 series scope?
I look forward to your answers, opinions and links to where this question might already have been answered, but that I've missed.

Yes that question was answered.

License is not for the SLA1016, it is for the scope to be able to use SLA1016.
License is for single oscilloscope, you cannot transfer it to to other scope, even the same type.

[bateau020]

New code, as they are linked to the serial number of the scope. You can buy it if you want, but know that there is an alternative. Search "keygen".

[ebastler]

License is not for the SLA1016, it is for the scope to be able to use SLA1016.
License is for single oscilloscope, you cannot transfer it to to other scope, even the same type.

On a related note, the firmware for the SLA1016 will need to be upgraded for use with the SDS800X HD. So the logic analyzer unit can no longer be used with the SDS1104X or SDS1204X scopes. Maybe a future firmware for the SLA will provide backwards compatibility?

[eTobey]

Can anyone explain why the signal needs 20ms, to settle in this thread?: https://www.eevblog.com/forum/beginners/probe-compensated-but-level-of-square-signal-gt-20ms-not-looking-good/msg5519191/#msg5519191

[egonotto]

Hello,

a day ago Batronix had the SDS804X HD in stock. I was already hoping that the delivery problems would ease. But now it says “in stock in 41-60 days”

Best regards
egonotto

[Martin72]

For understandable reasons, the 800 is very popular and sells out quickly.
When I advertised my SDS804, it took less than 20 hours and it was gone...
However, if I can believe my sources, and I do, the supply bottleneck will soon be history.

[tautech]

For understandable reasons, the 800 is very popular and sells out quickly.

However, if I can believe my sources, and I do, the supply bottleneck will soon be history.

Yes, in a few more weeks.....

[nanopico]

I know it's too early, but is there an intention to change the hardware revision?

[eTobey]

I know it's too early, but is there an intention to change the hardware revision?

Why should they change the hardware?

[nanopico]

Not totally, hardware revision can also mean the replacement of some components in the BOM.

[2N3055]

Not totally, hardware revision can also mean the replacement of some components in the BOM.

Yes we understand but why would they change HW revision 2 months after release?

[ebastler]

Not totally, hardware revision can also mean the replacement of some components in the BOM.

I guess the question was: Why are you asking? Are you looking for specific improvements? Are you concerned about anything getting worse due to "value engineering"?

As you said, it's a relatively new product, and I am not aware of any issues which would drive a hardware change. Also, under-the-hood hardware changes are typically not publicly announced, certainly not in advance. You don't want customers getting concerned about having "old" hardware, or waiting with their purchase until a new revision comes out.

[eTobey]

Not totally, hardware revision can also mean the replacement of some components in the BOM.

That does not really answer my question. Why does it matter to you, if they would change anything on the hardware?

[awakephd]

I got so much info from this thread that I purchased the Siglent 804x.  I have a question about probes though.  So I want to make noise measurements, so I want a probe that has better than 20 Mhz bandwidth at 1x.  It would be nice to have 200 Mhz bandwidth at 10x so I only have one probe.  Looking at the threads, is the RIgol PP215 or the PVP2350 the one to get.  Siglents probes dont see to have the specs.  Thanks.

I found the scope to be great except that it doesnt have wifi (yet).  And it is a pain to be having to connect a LAN cable all the time.  So I searched for a solution and found one.  My requirement is for a LAN to wifi bridge that uses USB power that is low and once configured, can be ignored.  I found (in the US) a Vonets VAP11N-300.  Its not the fastest out there, but it is plenty fast and it uses low power. Their spec is .5A but I measured .25A.  It costs $26 in the US from Amazon.  It needs to be configured on a laptop that has both a free ethernet port and USB port.  Plug it in, wait a minute for it to boot, connect to 192.168.254.254 in your browser the first time. Turn off repeater mode, change password, search hotspot and connect to your wifi.  Reboot the unit and it should now work.  After it connects to your wifi, you must now connect to vonets.cfg.  If you want, you can configure the NTP server.   One warning is check the firmware version before attempting to update firmware.  It took overnight for hte firmware to download, so I would skip that if possible.  Then shut down and attach to your Siglent.  When the Siglent boots, it will show 1969 as the date until about a minute.  Then the Vonets finishes booting and the time (if you have configured the NTP server in Siglent) is now correct!  You can now attach the Vonets with double sticky tape to the back of the Siglent.

I realize it has been a while since this post, but I hope it is okay to follow up on it. Based on this post, I bought the same model, Vonets VAP11N-300, to work with my new Siglent SDS804X HD. But thus far I have not had success in getting it to work. I can set it up in bridge mode, and hook it up to the Siglent, and see from the signal lights that it has connected to my wifi. But I can't seem to figure out how to enter an NTP server address that works, and I can't seem to find the Siglent on the network so that I can try to connect to it via the wireless. Maybe it doesn't allow the latter, but since I can't even get the former to work, I must be doing something wrong. And actually, once I configure the vonets device for bridge mode, I can't seem to access it via vonets.cfg. I reset the unit and started over, but wound up with the same result.

If anyone has any ideas, or could point me to more information, I would be most grateful! Or if perhaps I should send this back and get something different, I'm open to suggestions. My hope / goal is to have a USB-powered wifi-to-ethernet bridge that allows 1) NTP and 2) wifi access to the scope.

[KungFuJosh]

I realize it has been a while since this post, but I hope it is okay to follow up on it. Based on this post, I bought the same model, Vonets VAP11N-300, to work with my new Siglent SDS804X HD. But thus far I have not had success in getting it to work. I can set it up in bridge mode, and hook it up to the Siglent, and see from the signal lights that it has connected to my wifi. But I can't seem to figure out how to enter an NTP server address that works, and I can't seem to find the Siglent on the network so that I can try to connect to it via the wireless. Maybe it doesn't allow the latter, but since I can't even get the former to work, I must be doing something wrong. And actually, once I configure the vonets device for bridge mode, I can't seem to access it via vonets.cfg. I reset the unit and started over, but wound up with the same result.

If anyone has any ideas, or could point me to more information, I would be most grateful! Or if perhaps I should send this back and get something different, I'm open to suggestions. My hope / goal is to have a USB-powered wifi-to-ethernet bridge that allows 1) NTP and 2) wifi access to the scope.

It sounds to me that you (most likely) correctly configured the bridge device, but you still need to manually configure the network settings in the SDS800.

[BillyO]

But I can't seem to figure out how to enter an NTP server address that works

There is a bug with entering the NTP server IP.  Certain IP addresses just cannot be entered.  I tried to report this in the bug thread, but no one took any notice, nor did anyone make an attempt to re-create or verify.  I guess you and I are the only ones that care.  It took me a while but I found a non-ideal NTP server I could enter.  128.233.154.245 worked for me, just in case you are hitting the same problem.

[tautech]

Based on this post, I bought the same model, Vonets VAP11N-300, to work with my new Siglent SDS804X HD. But thus far I have not had success in getting it to work. I can set it up in bridge mode, and hook it up to the Siglent, and see from the signal lights that it has connected to my wifi. But I can't seem to figure out how to enter an NTP server address that works, and I can't seem to find the Siglent on the network so that I can try to connect to it via the wireless. Maybe it doesn't allow the latter, but since I can't even get the former to work, I must be doing something wrong.

I/O>LAN
Select DHCP and select OK.

If you know your LAN IP it might be something like this: 192.168.0.xxx and when reopening LAN settings your LAN DHCP should have assigned an IP for the scope.
You can how deselect DHCP and close the window and your scope should retain the IP negotiated for the scope.

And actually, once I configure the vonets device for bridge mode, I can't seem to access it via vonets.cfg. I reset the unit and started over, but wound up with the same result.

Normal I would say.
My TP Link TL-WR802N when configured in Bridge mode is totally invisible to the network.

[EvgenyG]

It took me a few attempts to enter an IP starting with 200 range, had to delete and enter it again a few times, the scope did not like it. Eventually it went through. Clearly some bug. Ideally they should make it a DNS name.

[BillyO]

It took me a few attempts to enter an IP starting with 200 range, had to delete and enter it again a few times, the scope did not like it. Eventually it went through. Clearly some bug. Ideally they should make it a DNS name.

Thanks for the verification.  I tried some 20 times using all sorts of different strategies and could not get one that started with 204 or higher to enter at all,

[awakephd]

Many thanks, all. Tautech (is it Rob? I think?), thanks for the specific menu path to follow - I kept looking for something that would let me see or set the IP address, but apparently in all the wrong places. And also for the information that the vonets will be invisible in bridge mode. I have so much to learn ... !

[mawyatt]

Many thanks, all. Tautech (is it Rob? I think?), thanks for the specific menu path to follow - I kept looking for something that would let me see or set the IP address, but apparently in all the wrong places. And also for the information that the vonets will be invisible in bridge mode. I have so much to learn ... !

Rob is the "Valued Added" benefit for all Siglent instruments here, few folks appreciate this until they own Siglent gear, then find his value. A few like to bash him for his Siglent alliance, those usually don't own Siglent gear, less knowledgable, and/or jealous

BTW Rob pointed us on how to acquire the IP address for the NTP time server (nice feature), and has helped with numerous questions and recommendations.

New folks should follow tautech, rf-loop, 2N3055 and Performa01, realizing they represent Siglent, however provide an enormous TE technical resource for those "willing to listen and understand"  

Best,   

[2N3055]

It took me a few attempts to enter an IP starting with 200 range, had to delete and enter it again a few times, the scope did not like it. Eventually it went through. Clearly some bug. Ideally they should make it a DNS name.

Thanks for the verification.  I tried some 20 times using all sorts of different strategies and could not get one that started with 204 or higher to enter at all,

Reported. Thanks.
I would have never stumbled upon this, because I run NTP on my router....

[tautech]

Many thanks, all. Tautech (is it Rob? I think?), thanks for the specific menu path to follow - I kept looking for something that would let me see or set the IP address, but apparently in all the wrong places. And also for the information that the vonets will be invisible in bridge mode. I have so much to learn ... !

Rob is the "Valued Added" benefit for all Siglent instruments here, few folks appreciate this until they own Siglent gear, then find his value. A few like to bash him for his Siglent alliance, those usually don't own Siglent gear, less knowledgable, and/or jealous

BTW Rob pointed us on how to acquire the IP address for the NTP time server (nice feature), and has helped with numerous questions and recommendations.

New folks should follow tautech, rf-loop and Performa01, realizing they represent Siglent, however provide an enormous TE technical resource for those "willing to listen and understand"  

Best,

Thank you Mike and I would recommend 2N3055 be added to this list.

We just do what we can......

[awakephd]

A follow up report: Success! Well, 90% success. I am now able to sync with the NTP server that Billy-O provided, and I can access the scope via wifi. Tried it on my phone first, and wow - could not believe how immediate it is when I touch the phone screen and the scope responds.

But ... so far ... the date is correct, but the time is off by 4 hours. Yes, before you ask, I changed the time zone ... but maybe not to the correct choice? I set it to "America/New York" since I'm in the same time zone as New York. Is there something else I'm doing wrong? Or <ignorance alert> do I need to use an NTP server that is specific to the US east coast? </ignorance alert>

[BillyO]

But ... so far ... the date is correct, but the time is off by 4 hours. Yes, before you ask, I changed the time zone ... but maybe not to the correct choice? I set it to "America/New York" since I'm in the same time zone as New York.

Hmm, same time zone as me.  Not sure what might be happening.  I did have a bit of a brain fart in setting the time zone though.  Just check that it is New York.  First time I did try it didn't work and can't for the life of me remember what I did wrong the first time, or right the 2nd time.