| Products > Test Equipment |
| Using (and living with) Siglent SDS1000X-E Series Oscilloscopes |
| << < (3/15) > >> |
| DEV001:
--- Quote from: SimonM on June 24, 2021, 12:05:54 am ---I really have to change my SSID just to configure and use the TL-WN725N WiFi dongle? If I read it correctly (Jason from SiglentNA) advises: "XE firmware being incompatible with SSIDs and PSKs that have spaces or special characters" and the solution is just to not use them. :-- Perhaps I don't read the 802.11 standards correctly, because using English-like characters (other languages too) is a "convenience" but not a "requirement" and an SSID can be up to 32 octets of just about "anything", so "do not have spaces or special characters" doesn't begin to describe the problem... The TL-WN725N was supposed to arrive today. Tomorrow's task - explain why the home WiFi might be broken and how to "fix it" for a small array of WiFi widgets we have that was working just fine until now. Simon --- End quote --- Another inexpensive option is to use an wifi router/extender/wireless bridge to authenticate to your wireless network and connect the scope ethernet port to one of the ethernet ports on the access point. You can use many inexpensive wifi routers to do this or flash OpenWRT/DD-WRT/Tomato, etc... to an older wifi router and you should be good to go until Siglent corrects the issue in firmware. It isn't ideal but if all you have is WIFI access and you don't have the ability to change the SSID this may be an alternative option. An example, this router looks like it supports wireless bridging for $19.98 https://www.amazon.com/TP-Link-TL-WA901ND-Wireless-450Mbps-Repeater/dp/B0857K4KVZ |
| tautech:
Dropping a link to this post with an excellent illustration of LAN connection and explanation of DCHP principles for reliable connections: https://www.eevblog.com/forum/testgear/siglent-ethernet-and-wifi-connection/msg3594083/#msg3594083 |
| SimonM:
--- Quote from: SimonM on June 24, 2021, 12:05:54 am ---I really have to change my SSID just to configure and use the TL-WN725N WiFi dongle? If I read it correctly (Jason from SiglentNA) advises: "XE firmware being incompatible with SSIDs and PSKs that have spaces or special characters" and the solution is just to not use them. --- End quote --- Hyphens are OK but spaces and a few other characters are not) My SSID includes by default hyphens e.g. BT-XXXXXXX. That's OK and the scope and WiFi adapter connects OK. If I change it, spaces and some of the other restricted characters won't allow WiFi to connect. The router has its own set of restrictions e.g. spaces at either end of the SSID are excluded and well documented by the BT Help. So, it turned out to be a non-event (for me) because hyphens are accepted and the scope WiFi connection works great. With five WLANs at home (and each defaulting to hyphens (-) in the SSID), that's good. Scope and WiFi adapter seem to "play well" with a home router I'm only using a "cheap" tp-link TL-WN725N adapter (about £8 from Amazon) that is restricted to the 2.4GHz band, with excellent range and speeds up to 150 Mbps that works perfectly. tp-link also has a dual-channel adapter TP-Link AC600 (Archer T2U Nano), but no real advantage using the 5GHz band that can be more "range restrictive" and some users report needing a separate Windows driver that's not required with a TL-WN725N adapter, so is most likely incompatible with the scope. Confirmed: TP-Link AC600 (Archer T2U Nano) is 2.4GHz/5GHz is definitely NOT compatible with the scope. The shielding on the scope doesn't seem to be a problem e.g. it works well enough, with the adapter in the rear USB slot and any shielding by the metalwork of the scope doesn't obviously impact the performance, unduly. Mostly I will try to use a LAN cable, but it's good to know that, if required, it also has a good WiFi range and I can now say "goodbye" to a 25' trailing LAN cable that goes between two rooms at home - that seems to be unpopular, for some unknown reason! Can you keep a secret? I noticed that the pre-shared keyword (PSK) secret password isn't quite so secret :-// - see the screenshot: WiFi connect (and future reconnects after a power cut are good) Once the WiFi is ON (connected) the scope will be ON (connected) the next time the scope is powered up. That's a good thing e.g. if the scope is configured to start after a power cut, then the WiFi connection is restored automatically, even if there is a delay as the router restarts and it keeps retrying the connection until it succeeds. :-+ Simon |
| SimonM:
Adding SDG1032X Function Generator - phase angles Having just bought the Siglent SDS1104X-E scope, and being pleased with it, I decided that I needed a 2 channel signal generator... I have just bought and started to use a Siglent SDG1032X Function Generator. We all make mistakes Being somewhat new to having a signal generator, I connected Function Generator to the scopes using a BNC cable and a 50-ohm terminator at the scope end for channel 1. I don't have a second BNC cable, so I have the second channel of the Function Generator with another 50-ohm terminator and a probe to scope 2nd channel. With both channels on and triggering on channel 1, I can only "see" channel 2. The Function Generator defaults to locking both outputs. Recognizing my "rookie" type mistake, I realize that the output from channel 1 is being exactly overlaid by channel 2. How to fix a phase angle? I now have changed the setup to have channel 1 and channel 2 of the Function Generator locked so that only channel 1 can be varied. Both channel outputs are terminated with a 50-ohm terminator and the FG is set on both channels to 50-ohm. I have two scope probes in 10x connected from channel 1 and channel 2 of the scope to the output of both 50-ohm terminators. The Function Generator is now set at 10MHz with a sine wave. That's about the upper end of what I want to use the FG for, hence the purchase of an SDG1032X. I see that the signal from channel 1 is being exactly overlaid (almost exactly) by channel 2. Knowing that there are two groups of channels on the SDS1104X-E, I have started to use channel 1 and channel 3 as my two inputs. With both probes, are set to 10X and calibrated to the 1KHz square wave test. The scope has been reset to factory defaults and then all four probes set to 10X. The scope has been switched on for at least an hour and calibrated (takes about 5 minutes). Triggering on channel 1 and connecting the "same input" to channel 2 where it's in phase: Triggering on channel 1 and connecting the "same input" to channel 3 or channel 4 it's not in phase: I can repeat this, triggering on channel 3 and connecting the "same input" to channel 4 where it's in phase: Triggering on channel 3 and connecting the "same input" to channel 1 or channel 2 it's not in phase: When I say "same input", I had initially set up the scope like the 1KHz setup. Thinking that the FG might not produce a signal that really was in phase, I connected both probes to the same 50-ohm output. That makes no difference. I have also switched the probes around to see if there is a phase difference between any of the four probes - they are the same. So I have come to the conclusion that for the "same input": Scope shows, (triggering on channel 1): 1. Channel 1 and channel 2 in phase; 2. Channel 1 and channel 3 not in phase; 3. Channel 1 and channel 4 not in phase (with the same phase difference at 10MHz). Similarly, scope show, (triggering on channel 3): 1. Channel 3 and channel 4 in phase; 2. Channel 3 and channel 1 not in phase; 3. Channel 3 and channel 2 not in phase (with the same phase difference at 10MHz). I'm not reliant on probes or the FG outputs to introduce the phase problem. Would I be wrong to think that the scope needs some extra adjustment to bring everything back "in phase", or am I expecting too much? NB I can show that the probes and the FG provide the same or an identical in-phase signal back to the scope. Simon |
| tautech:
--- Quote from: SimonM on June 29, 2021, 10:14:40 pm ---Would I be wrong to think that the scope needs some extra adjustment to bring everything back "in phase", or am I expecting too much? --- End quote --- Yes Channel Phase locking is done in the SDG.....investigate the settings. ;) Another tip if/when you need to trigger on a channel but don't need to see that waveform is to hide that channel and that functionality is in every channel's menu on P2. |
| Navigation |
| Message Index |
| Next page |
| Previous page |