Products > Test Equipment
New Siglent 2104X Plus -A Mistake?
<< < (6/7) > >>
Ray CI:

--- Quote from: KungFuJosh on June 09, 2023, 08:54:06 pm ---If the issue isn't what Rob (Tautech) suggested above about pressing the power button too long at shut off, I would return it and get a new one. The SDS2000XP series is a great scope, but if you've got a bad unit, don't waste more return window time on it.

--- End quote ---

Yes, thank you...  It's going back.  The vendor (Saelig, https://www.saelig.com/ -Not affiliated with them) has been great.  I sent follow-up email to Siglent North America early this morning and cc'd the vendor.   Siglent NA has gone silent but, the vendor sent an email with an RMA and is also covering return shipping.   They are making the best of an unfortunate situation.  Last week, they mentioned I'm not the first person to have problems like this.   It will go back via UPS in the next 24 hours.

BTW: I have only tried shutting it down via menu and momentary press of the power switch until it says "shutting down" (or words to that effect).  -Was not aware a long press did a hard reset.

Thanks folks...

Ray

bdunham7:

--- Quote from: Ray CI on June 09, 2023, 09:25:38 pm ---Yes, thank you...  It's going back.

--- End quote ---

Bummer--it sounds like you didn't even get to do many scope-y things with it!  I'm just curious, what made you go for the LAN/communications issues first?  I've had mine for awhile and as far as I can remember, this is the first time I've connected it--and I'm relieved to see mine works.  If you got a dud, that happens.  If these problems are widespread or model-wide with the last revision, then Siglent has screwed up a perfectly good scope model and woe unto them. 
Ray CI:

--- Quote from: bdunham7 on June 10, 2023, 01:07:21 am ---
--- Quote from: Ray CI on June 09, 2023, 09:25:38 pm ---Yes, thank you...  It's going back.

--- End quote ---

Bummer--it sounds like you didn't even get to do many scope-y things with it!  I'm just curious, what made you go for the LAN/communications issues first?  I've had mine for awhile and as far as I can remember, this is the first time I've connected it--and I'm relieved to see mine works.  If you got a dud, that happens.  If these problems are widespread or model-wide with the last revision, then Siglent has screwed up a perfectly good scope model and woe unto them.

--- End quote ---

No, I haven't done any "scope-y" things with the exception of checking probe calibration on C1 and C2 and, verifying the AWG has output.  Well, I did one thing just to make sure the scope was really working...  I have about 150' remaining from a 1000' spool of CAT 6A cable and did a reflection test to measure the length.   Indeed, the reflection time was about 480nS. 

I setup the LAN first because A) I reviewed the quick start guide and user manual before powering on.  B) The LAN indicator displayed a big red X and the Date/Time was not set properly.  It's been a long journey ever since.

Questions for you or anybody else: 

1) Do you have the same model of scope (2104x plus)?
2) What version of software is it running (mine is 1.5.2R3)?
3) What is the hardware version (mine is 05-05)?
4) What is the CPLD version (mine is 05)?
5) Does your Date/Time maintain the Timezone setting properly?


Thanks
Ray
KungFuJosh:

--- Quote from: Ray CI on June 10, 2023, 12:07:21 pm ---1) Do you have the same model of scope (2104x plus)?
2) What version of software is it running (mine is 1.5.2R3)?
3) What is the hardware version (mine is 05-05)?
4) What is the CPLD version (mine is 05)?
5) Does your Date/Time maintain the Timezone setting properly?

--- End quote ---

I have the 2104X Plus, "improved" to the 2504X Plus.
Software is 1.5.2R3
Hardware version 02-04
CPLD version 03
Date/Time work fine, no issues, but I can't set the timezone though. No idea why, never tried before today. I don't know if that's a bug, or if a different setting is disabling that. I'll just assume it's a bug. 😉

In general, it's a great scope. The only bug that actually bugs me (and they're fixing it, hopefully next version) is the screen capture file name stays on until you close the info box. The next version is supposed to have options to change how that behaves. They're generally good about fixing bugs.
Ray CI:

--- Quote from: KungFuJosh on June 10, 2023, 01:41:11 pm ---
--- Quote from: Ray CI on June 10, 2023, 12:07:21 pm ---1) Do you have the same model of scope (2104x plus)?
2) What version of software is it running (mine is 1.5.2R3)?
3) What is the hardware version (mine is 05-05)?
4) What is the CPLD version (mine is 05)?
5) Does your Date/Time maintain the Timezone setting properly?

--- End quote ---

I have the 2104X Plus, "improved" to the 2504X Plus.
Software is 1.5.2R3
Hardware version 02-04
CPLD version 03
Date/Time work fine, no issues, but I can't set the timezone though. No idea why, never tried before today. I don't know if that's a bug, or if a different setting is disabling that. I'll just assume it's a bug. 😉

In general, it's a great scope. The only bug that actually bugs me (and they're fixing it, hopefully next version) is the screen capture file name stays on until you close the info box. The next version is supposed to have options to change how that behaves. They're generally good about fixing bugs.

--- End quote ---

Thank you so much KungFuJosh!

Some more questions (sorry for not asking in the original post)...

Do you use DHCP or statically configured LAN settings?
Is the IP address high-up or low in the subnet range?  (high example w/Class C  x.y.z.200, low example x.y.z.75).

Based on the latest analysis and reading comments in other websites, it's possible:  A) The IP address problems are also happening to other people and B) The configuration recovery glitches are attributed by turning off the device using either long-press or short-press on the power button and C) The Timezone issue is a common problem.

FWIW:  I'm looking at the DHCP exchange on the wire.  Both DHCPDISCOVER and DHCPOFFER look proper; however, DHCPREQUEST looks sketchy and I'm not seeing a DHCPACK in some cases.  Also, the Siglent is not passing the hostname in the request sequence.  After clearing the router's tables, I can freely get other IP devices in the house to use the same IP address that the Siglent is choking on.  I can replicate the Siglent issue with two different brands of router.  If I set a pre-configured DHCP object in the router mated to the Siglent MAC addr AND if the pre-configured IP address is in the x.x.x.200 range, the Siglent will work. 


I have not had to resolve a bug in DHCP since 1999 or 2000...  That said, there's little doubt in my mind, this is a Siglent bug.  Since I don't know the Siglent's HW/SW partitioning and overall software/firmware architecture, I have no idea if these bugs are fixable or not.   If they want to send me the code and architecture diagrams, I'll fix it for them -for a small fee.

Ray
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod