Which usb sticks are people finding that works on the scope? [...]
Protocal Version: USB 2.00
Current Speed: High Speed
Max Current: 100mA
USB Device ID: VID = 1221 PID = 3234
Serial Number: 2010042716480359
Device Vendor: USB2.0
Device Name: Flash Disk
Device Revision: 0000
Manufacturer: USB2.0
Product Model: Flash Disk
Product Revision: 3.00
Chip Vendor: Micov
Chip Part-Number: 3.00
Physical Disk Capacity: 1939865600 Bytes
Windows Disk Capacity: 1939603456 Bytes
Internal Tags: AA2E-QAHS
File System: FAT
ContMeas ID: 3CC6-01-00
Some one else mentioned this "bug" before, but just to elaborate (and it's been added to the bug list on page 1):
All SCPI commands related to CAN triggering and decoding appear to be missing in the latest FW. A bigger PITA is the fact that the mode is not correctly reported for TRIGGER, although it is for DECODE. That means if BUS1 is set to CAN, and you query:
:BUS1:MODE?
...you get:
CAN
...even though you can't change any of the parameters of the BUS.
But if TRIGGER is set to CAN, and you query:
:TRIG:MODE?
...the VISA connection times out, and any software (like RUU) will believe the DSO has been disconnected (since :TRIG:MODE? should ALWAYS return a value).
See my picture, it starts at going up, dotted line and exits on trigger position steady line ,
( not on the steady line before trigger point, but on trigger point )
What was the position of your position button ?
See my picture, it starts at going up, dotted line and exits on trigger position steady line ,
( not on the steady line before trigger point, but on trigger point )
What was the position of your position button ?
All the information is in the bottom line of my image.QuoteSee my picture, it starts at going up, dotted line and exits on trigger position steady line ,
( not on the steady line before trigger point, but on trigger point )
Sorry, your image confirms the problem - it is NOT triggering on Exiting the Window - it's triggering on Entering. Rigol has definitely made a mistake, either with their English translations - or their understanding of what those terms mean.
It is easy to proof that you are wrong.., change the T1 cursor, and you will see that it changes the trigger point
and that is the exit.
I still dont agree, i still think it works correct.
But how to tell, it is in the definition of enter or exit the trigger level.
I try: the sine wave goes to the first T2, the the trigger knows it has to wait for the signal to exit
the window T1 level, the first hit of T1 is the enter mode, the second hit is the exit.
I still dont agree, i still think it works correct.
But how to tell, it is in the definition of enter or exit the trigger level.
It is called window, thats is correct but, it is not only in between, but also NOT inside is a window.
It is called window, thats is correct but, it is not only in between, but also NOT inside is a window.
I understand that - but then I think they choose the wrong name for the Trigger - at least as far as English is concerned. If I'm defining something with 4 sides (two screen edges and the two levels), I think of that as the Window. Perhaps the name Levels would be more appropriate - and a better description of what's happening.
About your post before: Using the same sine wave, gives the same outcome,
but try a complex signal, a dual tone or something with different hights in it,
then you see the advantage of windowing.
But how to tell, it is in the definition of enter or exit the trigger level.
Ah, so you're saying "high" + "enter" means "enter the region above the high threshold" not "enter the region between the thresholds." That explains why the manual calls it "Windows" (plural) trigger! Yeah, everything does make sense with that meaning (except the "rising edge of the input" part of the manual.) Thanks