Products > Test Equipment
New Siglent 2104X Plus -A Mistake?
bdunham7:
--- Quote from: Ray CI on June 07, 2023, 07:44:09 pm ---1) Only Static IP addresses and LAN configs work. DCHP is a no-go with intermittent 50 to 100% packet loss.
2) The timezone keeps resetting to UTC if the unit is powered-off via menu or warm-switch.
3) The LXI LAN Reset option does not do a HW reset on the phy port (never drops carrier) as I would expect; instead, it set the flags in the LAN configuration for "Auto DHCP" back to enabled status.
4) After saving a configuration (timebase, some channel configs etc) then, doing a power-down followed by restoring the configuration, some of the screen characteristics are not restored. e.g. Beep-sounds, menu auto-hide and some channels that were enabled are no longer enabled.
5) Also (this is probably not a bug/issue) the Ethernet port only negotiates to 100Mbps. I know of no product since the early 2000's that came with 100bT.
--- End quote ---
No need to withhold fact-based criticism. I have an older version, Hardware 02-04, Uboot-OS 5.0 and Software 1.3.9R6. Here's what mine does:
1) DHCP gets me an appropriate address and I can use all the instrument controls normally. I can ping that address all day long and never lose a packet.
2) My version does not have time zones. The RTC saves the time just fine through power cycles, although it isn't very accurate. It would be nice if it used NTP like the SDS1104X-E, which despite not having an RTC actually seems to work better once you set it up and install a wi-fi dongle.
3) My version does not have LXI. I couldn't find any equivalent command in SCPI to reset the LAN.
4) Apparently not all settings are saved this way--I turned off sound and then saved and recalled a setup and sounds were enabled. However, a soft-off plus power disconnect then restarting preserves sound, auto-hide and channel settings--all without any need for a saved config file. If your's doesn't do this, it is failing at a basic function IMO.
5) I'm not sure I agree that everything has had 1GbT for two decades....perhaps I'm behind the times but I still have two pretty nice routers that don't do a gig.
Yours sounds broken-ish, and perhaps someone with the latest version and hardware can do the same set of tests to see if yours is broken or they all are broken. Siglent is not beyond criticism here. I like my SDS2354X+ well enough and it was a relative bargain, but there are some annoying shortcomings (ERES/AVG vs math channels and the lack of wifi) made all the more annoying because the $500 SDS1104X-E gets them right. If they've added in all the bugs you are experiencing, then they have some work to do.
Martin72:
We have several 2104X+ from 2022 and 2023, maybe I could do some (but not all) tests for confirming.
--- Quote ---5) Also (this is probably not a bug/issue) the Ethernet port only negotiates to 100Mbps. I know of no product since the early 2000's that came with 100bT.
--- End quote ---
What do you want to transfer from a scope with 1Gbps ?
2N3055:
--- Quote from: Ray CI on June 07, 2023, 07:44:09 pm ---
1) Only Static IP addresses and LAN configs work. DCHP is a no-go with intermittent 50 to 100% packet loss.
2) The timezone keeps resetting to UTC if the unit is powered-off via menu or warm-switch.
3) The LXI LAN Reset option does not do a HW reset on the phy port (never drops carrier) as I would expect; instead, it set the flags in the LAN configuration for "Auto DHCP" back to enabled status.
4) After saving a configuration (timebase, some channel configs etc) then, doing a power-down followed by restoring the configuration, some of the screen characteristics are not restored. e.g. Beep-sounds, menu auto-hide and some channels that were enabled are no longer enabled.
5) Also (this is probably not a bug/issue) the Ethernet port only negotiates to 100Mbps. I know of no product since the early 2000's that came with 100bT.
--- End quote ---
My few comments:
1. DHCP has NOTHING to do with packet loss. Only way you can get packet loss because of DHCP is if DHCP server is handing out duplicate leases (same IP address to more than one device). I would look into this aspect... Also you might have problems with switch not properly negotiating duplex/speed.
2. There were some reports on early FW that if you shutdown scope aggressively fast after configuration changes, that scope might have not saved all the data to storage.. Give it 30 something seconds before commencing shutdown to verify you don't have something like that..
3. LXI LAN reset does TCP/IP stack reload. Nowhere it is stated it will hardware reset PHY controller. But hey, maybe not a bad idea...
4. See number 2.
5. There are many (much more expensive) scopes out there that have only 100Mbit Ethernet. You know why? Because on majority of embedded scopes (not PC based) there is no computing power to push much data to Ethernet. Fact that you don't something, doesn't make you expectations realistic, sorry.. Would I like to get same performance as high end performance scope that cost 20000USD from a 1000USD scope? Of course, that would be swell, thank you. But, not gonna happen, sorry...
And yes, what FW are you running? We need that info to have a chance to help you..
One thing is sure, you need to verify if your scope is really not working as expected. Problems that you see are not normal, so it is either something wrong with how you use it (I'm not saying it is, just enumerating possibility) or that particular one you got is broken.
If it is broken just ask for replacement one. In which case, these are not some "problems with model or brand", but an a damaged single specimen then. That happens. If it is a systemic problem manufacturer would be the first one that would like to know..
Best,
Ray CI:
--- Quote from: bdunham7 on June 07, 2023, 08:55:13 pm ---
No need to withhold fact-based criticism. I have an older version, Hardware 02-04, Uboot-OS 5.0 and Software 1.3.9R6. Here's what mine does:
1) DHCP gets me an appropriate address and I can use all the instrument controls normally. I can ping that address all day long and never lose a packet.
2) My version does not have time zones. The RTC saves the time just fine through power cycles, although it isn't very accurate. It would be nice if it used NTP like the SDS1104X-E, which despite not having an RTC actually seems to work better once you set it up and install a wi-fi dongle.
3) My version does not have LXI. I couldn't find any equivalent command in SCPI to reset the LAN.
4) Apparently not all settings are saved this way--I turned off sound and then saved and recalled a setup and sounds were enabled. However, a soft-off plus power disconnect then restarting preserves sound, auto-hide and channel settings--all without any need for a saved config file. If your's doesn't do this, it is failing at a basic function IMO.
5) I'm not sure I agree that everything has had 1GbT for two decades....perhaps I'm behind the times but I still have two pretty nice routers that don't do a gig.
Yours sounds broken-ish, and perhaps someone with the latest version and hardware can do the same set of tests to see if yours is broken or they all are broken. Siglent is not beyond criticism here. I like my SDS2354X+ well enough and it was a relative bargain, but there are some annoying shortcomings (ERES/AVG vs math channels and the lack of wifi) made all the more annoying because the $500 SDS1104X-E gets them right. If they've added in all the bugs you are experiencing, then they have some work to do.
--- End quote ---
Is your Icon photo a cat, dog or a space alien? LOL...
Much thanks for background sanity check. Much appreciated!
RE: 100Mbps / 100bT... Having written a few dozen Ethernet device drivers over the past 38 years of employment, I can say with great certainty, it's best to have all phy's connect at the highest rate possible even though there's no need to transfer at that rate. I would have no expectation of doing bulk transfer to an oscilloscope. The general consensus is to let the wire run as fast as it can and let the window protocol set the pace. W/O getting into details, having a slow/pokey phy on a switch is akin to plugging a USB1.0 device into a USB3.0 hub... It creates a bottleneck. In the case of an Ethernet Phy, the differences are not noticeable to the user in terms of transfer speeds but, it makes a difference to the protocols running inside the switch (aka, spanning tree, arp -and many other internal housekeeping protocols pertaining to counters and netmgt statistics).
Like I said, it might not be a bug in this case and I don't give a darn if it really is a 100bT phy. It just struck me as odd that in 2023, products are still shipping w/ 100bT.
Ray
BillyO:
--- Quote from: 2N3055 on June 07, 2023, 09:28:52 pm --- Would I like to get same performance as high end performance scope that cost 20000USD from a 1000USD scope? https://www.amazon.ca/Pyramid-Bench-Power-Supply-Converter/dp/B07KMLNLWQ
--- End quote ---
Wait a few years. What's available on today's $20,000 scope will be on tomorrows $1,000 scope. :-+
To the OP: Can you post your hardware version and your firmware version?
Also, I would respectfully suggest that there is nothing you could possibly need to do, or could do with that scope that would need more than 100Mb Ethernet. Putting it in would have added totally un-nesseccary expense. Jus' say'n. :-//
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version