Products > Test Equipment
REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol
marmad:
I found what appears to be another bug in the current FW - although it's not serious. I can't say if it exists in pre-v.2 FW because I never really used this Trigger before - although I did TRY to use it once or twice - and found it very unresponsive (which would likely be because of the below-mentioned bug) - so I have a feeling it's been around for many FW versions.
I discovered it while working on the extended screen info for Triggers for the upcoming RUU 3.0: it seems as if Rigol got the parameter names backwards on the Windows Trigger. Look at the image - it's supposed to be a Trigger on exiting the Window with a rising edge. In fact, it's entering the Window with a falling edge. Both Enter/Exit and Rising/Falling appear to be operating in reverse.
EDIT: As pointed out by Wim below - not a bug, but a misunderstanding of the terms by me - although I think Rigol could name the trigger and it's settings in a better, more intuitive way.
Wim13:
Well i dont have that, my DS2000 works oke in windows trigger
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 )
If you put the position on Time, you get the uprising positions
mrubbert:
Option DSEZ working fine with: DS2072 HW101 FW213 (override old DSAZ).
Looking foreward to work with automotive CAN bus now, even if it obvius if one of the boxes dosent respond, it might help to go deeper and repair the disturbed network or the relevant box it self.
Many thanks ! :-+
Also start to like the option knob now, it is understanding my touch now :)
( the links in 1 page dosent lead you to FW213 )
mrubbert:
--- Quote from: marmad on January 09, 2014, 07:54:58 pm ---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).
--- End quote ---
Ohhh, sucking rigol if its only for HW1 people.
Have to try normal CAN bus use in garage now,
0 degre celsius outside with no heater at moment, But thats just in specifications on this scope. Humidity 85 (max 95 in spec). :bullshit:
Galaxyrise:
--- Quote from: Wim13 on January 14, 2014, 04:59:06 pm ---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 )
--- End quote ---
The key is what's happening at the trigger position, not what happened before it.
I went and had a read of the manual. Page 5-16. As you have it configured:
"trigger on the rising edge of the input signal when the voltage level is greater than the preset high trigger level"
+
"trigger when the input signal exits the specified trigger level range"
However, your screenshot shows the waveform with a FALLING edge ENTERING the specified trigger level range at the trigger position. So you have confirmed the bug Marmad found.
However, the docs are a little confusing. Consider "rising" + "enter": you can't be rising, greater than the high trigger level, AND entering the level range. So maybe the documentation should be taken with a grain of salt...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version