UI of triggering is strange, for example I want to see RS232 data as ASCI chars, I see interesting place to me, and want to trigger on specific letter 'D' for example. For that purpose I need to find somewhere ASCI codes table and find the number of that letter.
Yes, that's definitely a PITA.
Just because triggering UI works with numbers only, no letters, no HEX.
I've found picture with another example, I2C decoding shows hex values, triggering works with dec values only.
Thanks for the screenshot on that. At first I was confused, but then I realized that while Rigol provides several different
output formats, only one
input format is available (decimal numerics). Thanks!
My DS2202A has locked up again..
This time I was messing with the measurement buttons and I believe it was the 'STATS' button that I pressed. The scope then goes unresponsive.
Basically I had ALL those yellow measurement readings on the screen and I was looking for a button to kill them. I could turn them all off , but haven't yet seen how to change them individually.
Whatever - the scope should not lock up, and worst - a power cycle does not fix it...
It sits there .. dead showing the Rigol logo. Scope is virtually new - unadulterated.
In all it seems a nice scope - but I'm going to get bored if I keep having to reflash the firmware every so often!
**UPDATE** Power cycle with 6th Grey button being repeated pressed has unlocked it... back in business.
Twice?? That sounds like a broken scope. I'd file a support request.
Yes - done that, but since it happened both times since after I did a firmware upgrade, and only this timerecovered the scope using the '6th grey button' ( set defaults), I'm going to assume it was something to do with that ( for now)... ...
oh oh.... Just been trying it.. pressing the Statistic button has locked it up again.
Mode: Just channel 1 display ON. No Input signal. Display All ON. From a power up having only been messing with the measure functions.
I don't expect a power cycle to clear it alone....
Nope, just 3 beeps and then stuck.
Booting while pressing grey button no 6 fixes it.
I can't seem to replicate it... but so far each lockup has been related to the Display All , All Measure and Statistic buttons.
Edit:
Now I can repeat it ..
Power up:
Press 6th left hand grey button once ( to activate menu ) press again to select 'width'.
Press 7th left hand grey button to activate 'duty'
Press Measure
Check vertical channel 1 operates by adjusting knob
Press 'Statistic'
Check vertical channel 1 now doesn't operate. Scope is locked up and needs a reset to default to operate again.
I've bought the Rigol 2072A-S. I was looking for the original firmware but the one in the first page is not available anymore.
Is it possible to update the page with a new link?
Thanks you...
Some guy
posted that there is a version 00.03 firmware from Rigol. He did not share with us though
Anyone else hear about a new 00.03 firmware for DS2000/DS2000A series?
Someone sent it to me (might be the same guy) by e-mail. I put it up on my website, but I was just assuming it was actually the existing version from February, so the filename is wrong if it is in fact a new version. I won't be able to try it for a few days, but the file is:
http://www.gotroot.ca/rigol/DS2000-02_01_00_03.7zIf anyone else wants to give it a stab. Let me know if I should rename it...
Someone sent it to me (might be the same guy) by e-mail. I put it up on my website, but I was just assuming it was actually the existing version from February, so the filename is wrong if it is in fact a new version. I won't be able to try it for a few days, but the file is:
http://www.gotroot.ca/rigol/DS2000-02_01_00_03.7z
If anyone else wants to give it a stab. Let me know if I should rename it...
Thanks! The compressed filename is indeed wrong, but the .GEL binary file has ASCII numbers 00.03.00.00.00 at the beginning.
The file is much larger than previous .GEL files.
Well, the glass of whiskey in my hand kept telling me to load the new firmware, so I did.
BTW is there any difference upgrading by booting and hitting help a couple of times with the image on the USB drive, or just booting normally, sticking the drive in and following the upgrade prompts? I just followed the on screen prompts when it was fully booted this time around.
My DS2072A reads:
Model: DS2302A
Software Version: 00.03.00
Hardware Version: 2.0
All options still showing installed as "Official Version"
Don't know what's changed or been fixed, but that's what I can see for now.
I may try downgrading just to see what happens.
I renamed the file. New link:
http://www.gotroot.ca/rigol/DS2000-03_00_00_00.7z
If anyone has the actual 00.02.01.00.03 files I'd appreciate a copy to put up. The rapidshare links upthread are all broken for me.
I've fixed the FW links in
the second post (moved all the files from rapidshare to my own server) and added the latest v.03 to the list. I haven't heard anything about this latest version, but I'm currently travelling and away from the DSO, so no chance to experiment with it for awhile.
Somebody else might experiment and see if Rigol has dealt with any of the bugs listed in the above-linked post.
FW 00.03.00 ??Tested Math Log() function, working but the
DSO locks up! See log of a sawtooth with a bit of Negative values; Note log(-negative) = 0
DSO display and controls Lock up when you try to edit expression 'Off'
but USB still reports the display with a SCPI command
It is looking like this is a Beta Version
NO fix of Bugs 17,18..
Back to FW#00.02.01.00.03
Sometimes the intensity stays tha same even if you try to adjust it. Probably someone has noticed it here. This issue appears at certain memory length settings, I think.
Sometimes the intensity stays tha same even if you try to adjust it. Probably someone has noticed it here. This issue appears at certain memory length settings, I think.
Hi Hydrawerk
I did some testing and noted that in the Video there was recording frames with the Persistence not set to Min.
when in Min persistence , and Frames are recorded and the Rigol will Play back the frames at a Fix normal visible intensity (about same as Infinite persistence brightness)
But when the persistence is not set to Min. the Frames are recorded at that intensity setting and you cannot adjust the playback intensity.
when the intensity is set low during record, you can Barely see the waveform
and
when the intensity is set High during record, you can Clearly see the waveform
What does persistence mean if recording frames? ( could be segmented frames)
Shown below are 4 Displays: 7% intensity, 50% intensity, 100% intensity, 0% intensity but Min. Persistence
I hope that helps show what happens
Sometimes the intensity stays tha same even if you try to adjust it. Probably someone has noticed it here. This issue appears at certain memory length settings, I think.
Close the menu and you can adjust intensity. Should read the manual carefully!
OK, I should have read the manual...
My Wave Intensity always goes to 50% no matter what I attempt to set it to. Is this the same issue as in the previous few posts? Brightness adjusts the grid intensity and works ok.
My Wave Intensity always goes to 50% no matter what I attempt to set it to. Is this the same issue as in the previous few posts? Brightness adjusts the grid intensity and works ok.
Pushing down on the intensity adjustment knob sets the intensity to 50% (it's a shortcut).
Don't push it down after adjusting the intensity. Just stop turning the knob and the intensity will lock to your setting after a second or so.
Pushing down on the intensity adjustment knob sets the intensity to 50% (it's a shortcut).
Don't push it down after adjusting the intensity. Just stop turning the knob and the intensity will lock to your setting after a second or so.
OK, I didn't know that. I did read the "waveform intensity" part of the book. So now, the intensity setting stays where I set it, but it doesn't change the brightness of the waveform. Am I interpreting what the "waveform" is? I think it's the yellow and blue channel 1/channel 2 traces. I upgraded to 00.02.01.00.03 this morning. I "think" the intensity used to work ok, but my memory is not to be trusted, either.
Pushing down on the intensity adjustment knob sets the intensity to 50% (it's a shortcut).
Don't push it down after adjusting the intensity. Just stop turning the knob and the intensity will lock to your setting after a second or so.
OK, I didn't know that. I did read the "waveform intensity" part of the book. So now, the intensity setting stays where I set it, but it doesn't change the brightness of the waveform. Am I interpreting what the "waveform" is? I think it's the yellow and blue channel 1/channel 2 traces. I upgraded to 00.02.01.00.03 this morning. I "think" the intensity used to work ok, but my memory is not to be trusted, either.
Yes, the waveform intensity control is the brightness of the traces.
The range of brightness is not very dramatic. Try looking at the rise/fall transitions of the calibration waveform as you adjust the intensity. You should see the brightness change in them
.
May be this already mentioned somewhere, but I just noticed it: MSO version of DS2000A series is coming!
Maybe that's what the big v00.03 firmware update and version number jump is about?!
See
http://www.rigol.com/ and select the Chinese localization.
Yes, the waveform intensity control is the brightness of the traces.
The range of brightness is not very dramatic. Try looking at the rise/fall transitions of the calibration waveform as you adjust the intensity. You should see the brightness change in them.
You are 100% correct. When looking at the square wave, brightness has a good effect on the rise/fall lines, and does close to zilch for the horizontal lines. I finally found the button-push 50% brightness setting in the manual section for the multi-function knob. So if you read and remember the whole manual, the info is there. If you use it as a single-subject reference, you'll never find how the knob push sets the brightness. Thanks, from a part-time user who doesn't remember all the details.
May be this already mentioned somewhere, but I just noticed it: MSO version of DS2000A series is coming!
That just went public recently. I don't think it's been mentioned here yet. Good catch!
Maybe that's what the big v00.03 firmware update and version number jump is about?!
Yes, there were significant changes to the FW (and substantial increases in size) to incorporate the new LA functionality, AND all the new SCPI commands supporting it.
They obviously focused on those enhancements, and de-prioritized correcting known bugs on the analog side (for now).