-
#3000 Reply
Posted by
RBBVNL9
on 12 Feb, 2022 07:00
-
in RTA4004 there a 1.1 more error. [...] and in the CAN text is "RTB2000".
Seems your RTA has a bit of an identity crises....
(My Keysight alse sends out an "Agilent!" string as part of its serial training siglent, but thats a slightly different thing...)
Best regards, RBBVNL9
-
#3001 Reply
Posted by
egonotto
on 12 Feb, 2022 12:06
-
Hello,
the RTA4004 has the same error as RBBVNL9 describes " the scope only triggers in CAN (ID&data) if you set the exact right message length, while in LIN that is not the case...".
Moreover in german often they write adresse where identifier is meant.
Best regards
egonotto
-
#3002 Reply
Posted by
RBBVNL9
on 12 Feb, 2022 14:51
-
the RTA4004 has the same error as RBBVNL9 describes " the scope only triggers in CAN (ID&data) if you set the exact right message length, while in LIN that is not the case...".
egonotto, thanks for confirming! The more I look at this, the more I think its a bug, present in 3 places but not in 4 other four places where this same function is offered. And apparently present in both RTB2xxx and RTA4xxx series (and likely also in RTM3xxx series but this is not yet confirmed).
Work for the R&D firmware upgrade people....
-
#3003 Reply
Posted by
nctnico
on 12 Feb, 2022 18:40
-
My best is that this is due to using decimated data for measurements and math.
-
#3004 Reply
Posted by
goaty
on 21 Feb, 2022 22:38
-
Man, you need to work at R&S as a test engineer.
-
#3005 Reply
Posted by
nctnico
on 21 Feb, 2022 22:45
-
When is the last time you have seen a PAL signal? I can imagine they added it for completeness and didn't pay much attention to testing it.
-
#3006 Reply
Posted by
SL4P
on 21 Feb, 2022 23:07
-
Well, he did say SD…I’m hoping he meant Serial Digital (~270Mbps)
So I’m hoping that’s where his comment came from.
-
#3007 Reply
Posted by
nctnico
on 22 Feb, 2022 01:54
-
AFAIK SD is standard definition. Like 700 x 500 pixels (4:3) or so which is good old analog television.
-
#3008 Reply
Posted by
bayjelly
on 22 Feb, 2022 02:01
-
When is the last time you have seen a PAL signal? I can imagine they added it for completeness and didn't pay much attention to testing it.
Super niche, but I'm using PAL triggering
all the time for some self-made video circuits. Works overall pretty well for me, except that triggering on a certain line is sometimes glitching to another line, which could however be an artifact of my terribly jittering color burst frequency that drives the whole signal (synthesized from a clock that doesn't fit at all).
Not to negate your point, PAL signals probably are rather rare nowadays.
-
#3009 Reply
Posted by
nctnico
on 22 Feb, 2022 11:32
-
I don't use Python either but I have copy & pasted Python scripts together to get screendumps from various devices. Having an extra module that deals with reading & formatting the data makes life easier for Python copy & pasters like me.
-
#3010 Reply
Posted by
MaxZ
on 01 Mar, 2022 09:41
-
Anyone got a download link for the now old firmware v2.300? Couldn't find it on R&S website and I don't want to do an upgrade on my oscilloscope without a way back.
Edit: Someone sent it to me, thank you!
Thanks!
Max
-
#3011 Reply
Posted by
MaxZ
on 01 Mar, 2022 13:00
-
Update to v2.4 went flawlessly but the bug I hoped to be fixed is unfortunately still there... Reported half a year ago, maybe a post here gives it some more attention:
To reproduce
* hook up any channel to the 1kHz probe calibration signal (signal source really doesn't matter but this is the easiest)
* Put it into auto mode, with the trigger somewhere above/below the signal (=> free running)
* Hit the stop button
What you get are multiple overlapping waveforms on the screen. You have to scroll horizontally or rescale to get rid of the excessive waveforms. Note that I don't have any persistence option enabled.
This issue can also occur when using normal mode plus single shot. This is especially annoying because it's not always obvious that you have multiple overlapping waveforms...
Hope this gets fixed!
Max
-
#3012 Reply
Posted by
nctnico
on 02 Mar, 2022 18:09
-
Update to v2.4 went flawlessly but the bug I hoped to be fixed is unfortunately still there... Reported half a year ago, maybe a post here gives it some more attention:
To reproduce
* hook up any channel to the 1kHz probe calibration signal (signal source really doesn't matter but this is the easiest)
* Put it into auto mode, with the trigger somewhere above/below the signal (=> free running)
* Hit the stop button
What you get are multiple overlapping waveforms on the screen. You have to scroll horizontally or rescale to get rid of the excessive waveforms. Note that I don't have any persistence option enabled.
This issue can also occur when using normal mode plus single shot. This is especially annoying because it's not always obvious that you have multiple overlapping waveforms...
IMHO it is not a bug but a feature. Some Tektronix oscilloscopes also do this. Sometimes it is handy to have the previous capture still on the screen to see how a signal has changed compared to the current acquisition. Sometimes it is a nuisance because you have to do something (probably pressing the channel button also clears the old trace) to get rid of the previous trace.
-
#3013 Reply
Posted by
2N3055
on 02 Mar, 2022 19:35
-
..................
I think Siglent has such a function, with Fast and Slow Acquisition, but I know that only from reading here in the forum.
...............
I cannot say about other scopes, but SDS6000A series shows only last acquisition on stop. You need to enable short persistence to get multiple acquisitions on screen when you stop.
Fast and Slow Acquisition mode is a switch between digital persistence (Fast) and old school single acquisition per display cycle (Slow) mode.
With LeCroy, Siglent and R&S you get previous acquisitions history buffers too. That is much more powerful way to look at burst of previous triggers...
-
-
I've been seeing a really odd issue on my RTM3004 since the last FW update.
Every so often, the screen very briefly fills with a fuzzy blue (ch4 colour) mush. frequency of occurrence is of the order of 10s of minutes.
Now it gets weirder....
I turned Ch4 off to see if this stopped it, but every so often it still did the same, andat the same time, it also turned Ch4 back on!
Will try to get a video at some point.
-
#3015 Reply
Posted by
goaty
on 11 Mar, 2022 08:51
-
Mike, the R&S is just afraid of all those Tornado lasers around, so thats why the malfunction....
-
#3016 Reply
Posted by
vokars
on 15 Mar, 2022 18:12
-
Math Source and Signal-to-Noise-Ratio
Hi RTB2000 Community,
I still would like to buy the RTB 2000. Could someone, who already has this device, tell me,
1. if the math trace source can be a reference waveform? The user manual seems to say: No, only measurement channels or other math channels?
2. what is your preferred method for measuring the signal-to-noise ratio / signal noise independent from the device noise?
I am asking, because I would solve item 2 with this method:
a) measure StDev of the noise floor without any signal: Device Noise
b) measure the signal in average acquisition mode to eliminate the noise (down to a sufficient level) and save as a reference waveform.
c) Switch average acquisition mode off again and create a math channel to substract the reference from the signal (needs 1. : Reference as math source).
d) Calculate StDev from this math channel
e) Calculate the signal noise StDev with sqrt( StDev(noise from d)^2 - StDev(noise floor from a)^2 )
I expect, that this could be done with SCPI/Python script, but within the device would be much better.
-
#3017 Reply
Posted by
simone_b
on 29 Mar, 2022 14:31
-
Hello,
I have an RTB2004 that after calibration (not made by R&S) has the issue that you can see attached: waveform should be the reference square wave of the oscilloscope.
The R&S support suggested to run a self alignment procedure and check, but unfortunately it didn't fix it.
Now I have 2 options: paid replacement (about half the price of a new one, delivery time 20weeks) or buy an ex-demo unit with a 2weeks of delivery time.
Do you know what this issue is and if it is something fixable by user (oscilloscope is already out of warranty, so opening it doesn't void warranty)?
-
#3018 Reply
Posted by
KaneTW
on 29 Mar, 2022 14:42
-
That's an interesting failure. Can you go to the finest timebase and see what happens? Mess with different acquisition settings as well.
-
#3019 Reply
Posted by
simone_b
on 29 Mar, 2022 14:52
-
Hello KaneTW,
thanks for your reply. Please see attached capture.
I didn't say in my previous post that the oscilloscope has been updated to the latest FW version available (02.400) and that it was resetted to the factory settings with a secure erase
-
#3020 Reply
Posted by
simone_b
on 29 Mar, 2022 14:56
-
Also, channel 3 and 4 are not affected by this issue, but only 1 and 2
-
#3021 Reply
Posted by
nctnico
on 29 Mar, 2022 14:59
-
That could be a hardware defect. How about going back to the company that did the calibration and let them deal with the issue? They seem to have broken your scope.
-
#3022 Reply
Posted by
KaneTW
on 29 Mar, 2022 15:04
-
Thank you. A few theories would be a high speed signal coupling onto the ADC input, or data corruption coming out of the ADC.
Can you try (separately):
* Turning off interleaved mode (in case there's an issue with interleaving)
* Changing the sample rates
* Turning on hi-res mode
Wouldn't be surprised if something fried the ADC. I don't remember the ADC structure -- is Ch1+Ch3 interleaved or Ch1+Ch2?
That could be a hardware defect. How about going back to the company that did the calibration and let them deal with the issue? They seem to have broken your scope.
Yep. Looks like they messed something up for sure.
-
#3023 Reply
Posted by
simone_b
on 29 Mar, 2022 15:05
-
The company that did the calibration can't repair or probably it's better to say that don't want to repair and give support. I'm angry about that, as I sent a working oscilloscope and I received a broken one
-
#3024 Reply
Posted by
KaneTW
on 29 Mar, 2022 15:05
-
The company that did the calibration can't repair or probably it's better to say that don't want to repair and give support. I'm angry about that, as I sent a working oscilloscope and I received a broken one
Sounds like it's time to lawyer up.