Hi John,
Will do it tomorrow - Although I´ve covered the "area" around the button with my hands, to make sure I´m not too blind...
But I´ll check it again.
Martin
Today I´ve seen something in the channel dialogbox, I haven´t seen before at my siglent.
Probe symbols were displaying...Does anybody when they will come up ?
And what does they mean?
At home I didn´t got these symbols (pic shows at work (left), home)
Anybody have any success enabling "telnet" access to an SDS2000X Plus lately? Running latest firmware (Version: V1.3.9R6), and the 'siglent_device_startup.sh' on a USB key method is not working for me. I'm Linux savvy, and have tried multiple times with various tweaks to the content of the file as found on other posts, but no joy. If someone can verify it still works for them, I'll keep at it...
Thanks
iMac:KINGSTON $ ls -l
-rwxrwxrwx@ 1 aaaaaaa staff 29 20 Feb 11:35 siglent_device_startup.sh
iMac:KINGSTON $ cat siglent_device_startup.sh
/usr/sbin/telnetd -l /bin/sh
It could be we already got this in the past, I couldn´t remember it actually:
Measuring...
Today at work, I had to adjust a triangle-signal for offset - Using the siglent for the first time for it.
Took as always the "mean" parameter, set the timebase in such manner, to have at least one full period on the screen.
Using the gate-lines for exactly zero-crossing at the beginning and end of the period.
Works fine, no problem at all - But I also got the frequency parameter acitve, nothing was displayed except *** .
The "hardware-counter" (?) instead is working...
Sounds so familar to me, I´m sure we got this case..
Martin
OK sinisa, got it...
But...
For calculating the frequency a full period is all you need, when you calculate it manually (f=1/T).
A DSO can´t do it ?
But it can measure/calculate amplitude, mean and all other "vertical stuff" ?
Interesting..
When you don´t specify the measure gate, it will measure on the whole screen.
Frequency then will be measure correctly, but mean for example not*.
When you specify the measure gate, about one period, mean will be correctly measured, but frequency not.
interesting, again..
And why can the "hardware counter" get it ?
Because it gather the "information" over the whole memory and not what´s on the screen ?
Interesting, the third..
Martin
*) The lower the timebase will be set, the more you came closer to the value it measures on only one period
# A script to tweak a few things on a Siglent SDS2000X Plus scope
# (developed on firmware = V1.3.9R6)
#
# Expects you to have files named "profile" and "localtime" in the top level
# directory of the USB media alongside this script. Use "localtime" file from any Linux
# OS configured for the desired timezone, or grab one from "/usr/share/zoneinfo/".
# Path to this script and other support files
USB_TLD=$(dirname $0)
# Clone /etc so we can make some run-time mods (very small)
/bin/cp -a /etc /tmp
# Now cover original /etc with a bind mount to copied dir
/bin/mount --bind /tmp/etc /etc
# Change the root password for telnet
# Generated with "mkpasswd --method=sha256crypt"
echo 'root:$5$pr81dcqw1/OpvOPT$L8tE.M8YZHEGY7DW2SqBJl9Abn/tjYbRiGoF9gFQAS/' | chpasswd -e
# Add localtime file from USB media for setting timezone
/bin/cp ${USB_TLD}/localtime /etc/localtime
# Augment environment for the shell with personal preferences from USB media
/bin/cat ${USB_TLD}/profile >> /etc/profile
# Remount as read-only (or not)
#/bin/mount -o remount,ro /etc
# Start telnet server (requires login via password above)
/usr/sbin/telnetd
# Set NTP server address as needed for your environment
# Note: resolver does not currently work, so must be numeric IP address
NTP_SERVER_IP="192.168.1.222"
# Create a script to run when "ntpd" generates an event
# Remove "#DEBUG " to get logging of the events
NTPD_SCRIPT="/tmp/set_rtc.sh"
NTPD_LOG="/tmp/ntpd_log.txt"
/bin/cat >${NTPD_SCRIPT} <<-"HEREDOC"
#!/bin/sh
NTPD_LOG="/tmp/ntpd_log.txt"
#DEBUG echo $1 >> ${NTPD_LOG}
#DEBUG echo "stratum=$stratum, freq_drift_ppm=$freq_drift_ppm, poll_interval=$poll_interval, offset=$offset" >> ${NTPD_LOG}
if [ $1 == "step" ]; then
/sbin/hwclock --systohc
#DEBUG echo "Set RTC" >> ${NTPD_LOG}
fi
#DEBUG /bin/date -u >> ${NTPD_LOG}
#DEBUG /bin/date >> ${NTPD_LOG}
HEREDOC
# Make above ntpd script executable
/bin/chmod a+rx ${NTPD_SCRIPT}
# Start the NTP daemon with the option to run a script on events
/usr/sbin/ntpd -S ${NTPD_SCRIPT} -p ${NTP_SERVER_IP}
For calculating the frequency a full period is all you need, when you calculate it manually (f=1/T).
A DSO can´t do it ?
But it can measure/calculate amplitude, mean and all other "vertical stuff" ?
Interesting..
When you don´t specify the measure gate, it will measure on the whole screen(lecroy, siglent).
Frequency then will be measure correctly, but mean for example not*.
When you specify the measure gate, about one period, mean will be correctly measured, but frequency not.
interesting, again..
And why can the "hardware counter" get it ?
Because it gather the "information" over the whole memory and not what´s on the screen ?
Interesting, the third..
Hi,
The colleagues are impressed about the sds2k+, so the next two scopes are now on their way...
When the current probe will arrive next week (hopefully), all the stuff will be send to the ext. cal-lab.
I´ll scan the protocols then and present them here, FYI.
Great question, wouldn't VESA mount threads help?