tized
What is your firmware?
My tests has been made with 1Vp-p sine wave and 200mV/div setting. Frequency was measured with DG4162 counter.
Rigol recommendation: 4 div input amplitude.
1. Very slowly work with USB-disks. Writing to 2GB disk *.png 45KB ~18...30sec!
[FW v.00.02.00.00.04] / [FW v.00.02.01.00.03]
Have you seen these MSO4000 reviews?
Oh, there should not be so many bugs. The DS4000 platform is not new and the scope is not cheap.
It depends on what you need. The DSOX3000 is probably more mature and responsive, but it has only 4Mpoints memory (Per channel? Per four channels? It is not clear from the datasheet.) But Rigol DS4000 has 140Mpoints memory per four channels...
It depends on what you need. The DSOX3000 is probably more mature and responsive, but it has only 4Mpoints memory (Per channel? Per four channels? It is not clear from the datasheet.) But Rigol DS4000 has 140Mpoints memory per four channels...
I'm curious about the digital channels plus frame recording on the MSO4000. Can you record with digital channels on? Does the DSO capture the digital information in the frames?Thank you fo your interest! Whether I understood you correctly?
Use my RUU utility software. Screen captures to PC take ~2.5s over USB or ~6s over LAN.Thank you for your software. I will use it at near time, but I do not always have the opportunity to connect PC with DSO in laboratory. DS1000D can save image to USB-flash for 1-2sec with less powerfull hardware!
DS1000D can save image to USB-flash for 1-2sec with less powerfull hardware!
I'm curious about the digital channels plus frame recording on the MSO4000. Can you record with digital channels on? Does the DSO capture the digital information in the frames?I measured waveform update rate for analog channels with and without LA-channels. No significant differences from first post's table. Yes, MSO can record analog+digital channels simultaneously to segmented memory.
I measured waveform update rate for analog channels with an without LA-channels. No significant differences from first post's table. Yes, MSO can record analog+digital channels simultaneously to segmented memory.Great - that's a powerful feature! Thanks for checking that.
How do you add a full-scale pictures to body of first post "REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol"?Just copy the link to the image inside an image tag in the post. For example:
Hi I have a DS4054 and wanted it with the necessary firmware update here. I press on the HELP button and power button. I have it very often Try, but i don't come to update mode.. :)Without flash-disk: You press Power, 0.2..0.5sec wait, press Help (3-5 times very often), but scope loading with "Rigol" screen? This is bad. I went to bootloader after the second attempt.
Please can someone help me?
1. Very slowly work with USB-disks. Writing to 2GB disk *.png 45KB ~18...30sec!
9. Channels measurements is by FIFO-principle: when you adding new measurement, old left are deleting
18. On little overload channel signal form like slightly mirror image from up and down (as OPAMP reverse phase effect)
21. Multi-function Knob change value, when you are press on it (this is bug on all Rigol oscilloscopes)
39. Offsets for channels on 1mV/div ~0.3...0.5mV (see pictures). Ext probes is absent, channels with internal 50 Ohm
Saving large uncompressed BMPs on your 4000 will be faster than PNGs, even though they're bigger. That's because the processor in the 4000 (or the code) isn't very fast at compressing BMPs down to PNGs. Probably not surprising.
[ADDED: So the best approach is probably to save BMPs to the USB stick (fastest), then convert them to PNGs on your PC (smallest).]
I tested this bug today once again and what I has find: if USB-disk was formatted to FAT16 and it was without any files/dirs, MSO issue this results:1. Very slowly work with USB-disks. Writing to 2GB disk *.png 45KB ~18...30sec!
Yes, incredibly slow. I did find though that BMP was much faster, and also the first image saved after putting the USB drive in the scope took longer than the rest.
Yes, it is so. More datailed reasons I expressed at my RU bug-report. This is just awful for my laboratory's measurements and unlike the other my Tek and Lecroy scopes.Quote9. Channels measurements is by FIFO-principle: when you adding new measurement, old left are deletingIs this a bug?
Yes, it is so. More datailed reasons I expressed at my RU bug-report. This is just awful for my laboratory's measurements and unlike the other my Tek and Lecroy scopes.Quote9. Channels measurements is by FIFO-principle: when you adding new measurement, old left are deletingIs this a bug?
No it isn't: it's an interface-design issue. You might not like it - but it's working as designed - and so it's *not* a bug.Everything is relative :) I will correct it in bug-list.
Quote21. Multi-function Knob change value, when you are press on it (this is bug on all Rigol oscilloscopes)And that's the most annoying problem...
I think most of this problem is the slow/laggy response of the encoder/display. The system is still registering that you moved the multifunction knob while you press it in, the system finally updates the screen to one more position (past the option you were attempting to chose, but because it is no laggy you thought it was finished moving/updating) and it is chosen instead.
Rigol needs to change the amount of processing time devoted to the Menu (when there is a sub-menu extended) to the same thing it is when there is a screen overlay.
If you haven't seen it, there is an excellent screen capture utility here:
http://peter.dreisiebner.at/rigol-bildschirmkopie-lan/ (http://peter.dreisiebner.at/rigol-bildschirmkopie-lan/)
Works on Linux/Mac/Windblows, no other drivers or software required. Also works for the DSA815, probably other Rigol as well.
@ dr.diesel
Do you use this program rigol-screen copy-lan in the German version or do you have it in English?
I think are adc convertersOr maybe it's the 4 PGAs (programmable gain amplifiers)? Or are these mounted below the analog front-end shield?
I think, that it is adc. Pga and equaliser is under shield.
Can anyone make a pulse test with patched DS/MSO401x? Screenshots will be nice, as I has done upper.
Hello,
I just bought the MSO4014. (10/01/2014)
I disassemble, and I'm guessing that he is not new! :wtf:
There are traces of dust on the fan and the circuit.
Can be found on the PCB manufacturing date?
thank you
Hello,
I just bought the MSO4014. (10/01/2014)
I disassemble, and I'm guessing that he is not new! :wtf:
There are traces of dust on the fan and the circuit.
Can be found on the PCB manufacturing date?
thank you
did you complain about this at Rigol/your dealer?
What did they respond?
Anyone done calibration (over advanced menu) and self-calibration of the DS4k?28 nov 2013
28 nov 2013You personally did calibration, or factory? No, I don't know about differencies. You want to return the oscilloscope to the dealer? Why?
Do you know the differences in the Harware Version 1.3 and 1.31?
Anyone done calibration (over advanced menu) and self-calibration of the DS4k?I do a self-calibration every six month or so which is enough for me as it takes about 40m.
I do a self-calibration every six month or so which is enough for me as it takes about 40m.This calibration procedure is from DS6000 calibration (http://www.tequipment.net/assets/1/26/Documents/Rigol/DS6102/ds6102_doc_7.pdf) or not? Are You know what, specifically, calibration data will be erased when pressing the button ResumeCal? Can I do only "Equivalent Calibration" after this? Do you use when calibrating the DS6000-Cal-Kit? Are You bought the cable "BNC One-to-Five Cable" or did it yourself?
Do you know the differences in the Harware Version 1.3 and 1.31?The difference is 0.01 ;)
The extended calibration procedure of the DS4000 seems similar to what's listed in this DS6000 document, but because I don't have the equivalent instruction for the 4K, I never dared to do it.I do a self-calibration every six month or so which is enough for me as it takes about 40m.This calibration procedure is from DS6000 calibration (http://www.tequipment.net/assets/1/26/Documents/Rigol/DS6102/ds6102_doc_7.pdf) or not? Are You know what, specifically, calibration data will be erased when pressing the button ResumeCal? Can I do only "Equivalent Calibration" after this? Do you use when calibrating the DS6000-Cal-Kit? Are You bought the cable "BNC One-to-Five Cable" or did it yourself?
...The fact is, only the self-call is supposed to be accessible to the final user. We only access the extended menu because someone leaked the code sequence.Thanks for your description. Inputs to advanced menu are described in the DS6000 calibration procedure, but not in leaked code :) Did you Delay-calibration of the DS4000?
It is just 6 BNC-BNC cables and a BNC splitter on a PCB, totally equivalent and interchangeable with the one for the DS6K.Can you put pictures of the Cal-Kit on the forum? Please.
It is propbaly this one...This picture I've seen. I would like a more detailed picture of the entire set from real users, because the document is given a different picture of the cable.
It is propbaly this one:Yes, this is the one, and I bought it from Batronix like all of my Rigol T/M gear.
http://images.batronix.com/products/oscilloscopes/Rigol/Accessories/RigolScopeCalibrationSet-1200-789.jpg (http://images.batronix.com/products/oscilloscopes/Rigol/Accessories/RigolScopeCalibrationSet-1200-789.jpg)
looks like a pretty simple 1to5 BNC adaptor with controlled propagation, maybe controlled impedance, it seems to have a ground plane
on the other side.
It is advertised in the batronix shop as 'Calibration kit for the self calibration of the Rigol DS4000 and DS6000 oscilloscope series.'
Well, I would consider myself as a real user, I guess... :-DDIt is propbaly this one...This picture I've seen. I would like a more detailed picture of the entire set from real users, because the document is given a different picture of the cable.
I bought the official Rigol's DS4K calibration kit from Batronix because it is so cheap that you cannot build it yourself for less, unless you recycle old connectors.Yes I just checked the price: http://www.batronix.com/shop/accessory/test-equipment.html (http://www.batronix.com/shop/accessory/test-equipment.html)
It is just 6 BNC-BNC cables and a BNC splitter on a PCB, totally equivalent and interchangeable with the one for the DS6K.
anyone had trouble with the trigger on the DS4000? I have a DS4014 and I've noticed that with simple serial data the rising and falling edge trigger doesn't seem to work correctly. I've also noticed that the rising edge trigger doesn't always work properly depending on subtle trigger level changes.
I was playing around with the serial line decoder. It didn't happen always but I got the scope to hang up twice. It was a funny thing since I've set it up to restore last settings after power on - so it hang up every time I powered it on again automatically. After all I've found how to reset it during the boot process.
The bus protocols seem not to be one of Rigol's strength. However it doesn't matter to me, I've got the Hameg HMO in parallel, which has got much better bus decoding options than Rigol.Although that Hameg has only 2500 waveforms per second and it looks like a small poor scope... But in fact it is a compact powerful machine from Germany.
Rgds
Gunb
The bus protocols seem not to be one of Rigol's strength. However it doesn't matter to me, I've got the Hameg HMO in parallel, which has got much better bus decoding options than Rigol.Although that Hameg has only 2500 waveforms per second and it looks like a small poor scope... But in fact it is a compact powerful machine from Germany.
Rgds
Gunb
Are you running the new firmware, 00.02.01? I was having lockup problems as well until I upgraded.
Are you running the new firmware, 00.02.01? I was having lockup problems as well until I upgraded.
Well, meanwhile I've flashed the scope with version 00.02.01 and the serial decoder problems seems to be solved, i.e., it does not freeze anymore.
But I've lost the 500MHz bandwidth "option" and I've fallen back to the origin 100 MHz (oops, I assumed that would happen) :-/O
Hmm, I would like have both in common (without using a JTAG and open the scope anytime when a new update is released) :-DD
Any idea / experience if this can be done somehow?
Kind regards
Gunb
From the main Rigol "modifications" thread:
https://www.eevblog.com/forum/testgear/sniffing-the-rigol%27s-internal-i2c-bus/msg369754/#msg369754 (https://www.eevblog.com/forum/testgear/sniffing-the-rigol%27s-internal-i2c-bus/msg369754/#msg369754)
I have not found a program that works to read files. WFM
In another thread someone mentioned the decoders not operating on recorded frames, something that sounded a bit strange to me - say it isn't so I said to myself. Unfortunately that does seem to be the case (I only tested the RS232 decoder). I thought perhaps the frames had to be recorded with the decoder active but that doesn't work either - as soon as you press the record button the decoder stops updating. "Browsing" thru the recorded frames doesn't do anything with the decoded data on the screen, it just stays the way it was at the moment you pressed Record. Using the wavefor analysis function in order to "preview" the frames at the bottom of the screen the preview to the left of the current of frame somtimes distors badly and this appears to only happen when the decoder is on the screen.
Since the decoders appears to be software driven I really don't see the reason for them not being able to operate on recorded frames.
Don't know if it can be called a bug as I don't think I've seen it stated anywhere that it should work, still kind of a shame though.
Either they should block the decoding completely when switching to recorded frames or they should improve functionality. The current state can be marked as a bug.I agree, it's misleading having the decoder on screen showing "old" data.
Who's going to ask Rigol about it? 8)
I'd really would've liked them to work on recorded frames, and I'm surprised they don't but can't say if they actually should work. But again, if they aren't meant to work then they should be disabled.
Who's going to ask Rigol about it? 8)
As somebody mentioned before, MSO4000's waveform update rate goes down when serial decode is enabled. It is clearly visible with naked eyes. Not good on a $4,400 scope! http://www.rigolna.com/products/digital-oscilloscopes/mso4000/mso4024/ (http://www.rigolna.com/products/digital-oscilloscopes/mso4000/mso4024/)
Rigol MSO4000 serial decoding slows the scope down (https://www.youtube.com/watch?v=zQgcjKU80rw#)
I think that Agilent does not suffer this, but some Tektronix scopes do.
http://youtu.be/7hM6xXoWtEc?t=1m59s (http://youtu.be/7hM6xXoWtEc?t=1m59s)
http://youtu.be/OgO6s_AtX1I?t=1m56s (http://youtu.be/OgO6s_AtX1I?t=1m56s)
Oh, what happened to your Rigol DS4000? It has some disadvantages, but I still think that it is rather a powerful scope...
As somebody mentioned before, MSO4000's waveform update rate goes down when serial decode is enabled. It is clearly visible with naked eyes. Not good on a $4,400 scope!
EDIT: The memory was at the lowest setting, 14kpoints per channel.
Well, this may happen to any scope, even Agilent can be faulty sometimes... And you have said that you have other Rigol equipment, that is working properly.
Rigol has had it for over a week and I've not received any update. Kinda sucks to be down a scope!!! I've got a lot of other Rigol equip and not had issues for the most part.
I'm not surprised. I like the Agilent scopes much much better these days than the TEK. I have an MSO7104B and it is spectacular. I still like my Rigol ds4014 a lot... except it is 2 months old and already broke!
As somebody mentioned before, MSO4000's waveform update rate goes down when serial decode is enabled. It is clearly visible with naked eyes. Not good on a $4,400 scope! http://www.rigolna.com/products/digital-oscilloscopes/mso4000/mso4024/ (http://www.rigolna.com/products/digital-oscilloscopes/mso4000/mso4024/)Another comparison...
Rigol MSO4000 serial decoding slows the scope down (https://www.youtube.com/watch?v=zQgcjKU80rw#)
EDIT: The memory was at the lowest setting, 14kpoints per channel.
The Rigol has only a segmented memory (called record) and no other tools for long memory management. No Search or automatic scroll. No marks possible. Nothing like Waveform Inspector on Tektronix scopes AFAIK.
I'm not surprised. I like the Agilent scopes much much better these days than the TEK. I have an MSO7104B and it is spectacular. I still like my Rigol ds4014 a lot... except it is 2 months old and already broke!
Have you had the MSO7104B for a long time? If so, was there any one (or more) things that prompted you to buy the DS4014, or was it simply to try out something new? I am still tossing up between an Agilent MSO7054B and the Rigol MSO7034, and I keep wondering if all that extra sample memory will make up for the other shortcomings of the Rigol. I'd really appreciate your opinion.
Thanks,
As somebody mentioned before, MSO4000's waveform update rate goes down when serial decode is enabled. It is clearly visible with naked eyes. Not good on a $4,400 scope! http://www.rigolna.com/products/digital-oscilloscopes/mso4000/mso4024/ (http://www.rigolna.com/products/digital-oscilloscopes/mso4000/mso4024/)Another comparison...
Rigol MSO4000 serial decoding slows the scope down (https://www.youtube.com/watch?v=zQgcjKU80rw#)
EDIT: The memory was at the lowest setting, 14kpoints per channel.
Scope comparison during I2C decoding Part 1 (https://www.youtube.com/watch?v=RxRIX0eFNyw#ws)
Scope comparison during I2C decoding Part 2 (https://www.youtube.com/watch?v=Q5bFakNxJns#ws)
Serial decode is definitely not "robust", perhaps useable but quirky?
Does everyone else have problems with RS232 decoding on a DS4000/MSO4000 at the higher baud rates (e.g. 57600, 115200, ...)?@Sailor I think the DS2000 Firmware was based on the DS4000 ,and in the DS2000 firmware there was a bug that for RS232 decoding of 56K(fixed) was in correcting programmed for 56000!! this was indicated by varying the speed and the center frequency of NO errors was 56000.(55200-56800)
Now if the USER specified rate was used and set to 57600 the decoding would work OK.
You may wish to give USER a try.
...E-mails I received from Rigol CN
=====================================
we will fix this bug in next version about 3 months later.
Another gripe: Trying to set a USER baud rate is a lost cause on this scope. The numbers change nice and smoothly for a while, then suddenly jump wildly, by hundreds-to-thousands of counts. Turning the knob backwards a little (if the numbers had jumped forward) will often produce a jump back to near the value that you were at when the first jump occurred. Or not!
I think the DS2000 Firmware was based on the DS4000 (...)Everything is based on that old DS6000 scope, I think.
Another gripe: Trying to set a USER baud rate is a lost cause on this scope. The numbers change nice and smoothly for a while, then suddenly jump wildly, by hundreds-to-thousands of counts. Turning the knob backwards a little (if the numbers had jumped forward) will often produce a jump back to near the value that you were at when the first jump occurred. Or not!My DS2000 has the Navigation Knob to adjust the USER define Bitrate, Yes the outer Knob jumps , but the inner Know moves 1 bit at a click , it does take many rotation to change 300 counts.
The 2000s just got a major firmware revision bump (it's now listed on the Rigol site)...
The 2000s just got a major firmware revision bump (it's now listed on the Rigol site)...
"Major" in terms of functionality or fixes? Or "Major" in terms of Version number? ;)
lol, knowing them they just bumped the big number hoping shit would fix itself!
Interesting thread and thanks to the folk that have posted to it.
I'm considering a new scope and the toss up (in the $3k - $4k) range is Rigol, Agilent & Tek.
Tek seems a 'little' behind the times in the current state of the art, so bang is less for the buck than the other two. My concern with Rigol is that I think it's a tail trying to wag the dog problem in terms of getting Rigol (US/EU etc) to push for firmware bug fix requests back to the actual developers in China.
Given the cost delta between Rigol and the equivalent bandwidth Agilent is maybe 20 - 30%, this thread has convinced me to focus on the Agilent DSOX2000/3000 series where at least there's a more direct line from sales to tech. For a piece of test equipment that IS used daily and has an expected life cycle of 5+ years, penny wise and pound foolish needs to be addressed in the purchasing process.
cheers,
george.
Sadly I'd have to agree after a unsatisfying warranty repair experience. Scope was less than 2 months old, they had it for repair for 1 month! They sent it back yesterday with one of the stickers on the back missing and the warranty void sticker "voided". Adhesive is still showing on the removed stickers. It looks like second hand junk now which really sucks. I'm surprised they didn't replace the labels. Thank god I had other scopes and I wasn't relying on this one. An entire month without the primary scope probably would put us out of business!
Sadly I'd have to agree after a unsatisfying warranty repair experience. Scope was less than 2 months old, they had it for repair for 1 month! They sent it back yesterday with one of the stickers on the back missing and the warranty void sticker "voided". Adhesive is still showing on the removed stickers. It looks like second hand junk now which really sucks. I'm surprised they didn't replace the labels. Thank god I had other scopes and I wasn't relying on this one. An entire month without the primary scope probably would put us out of business!
Well, that's a pretty damning experience! Did they at least fix the rail-to-rail noise issue, and other problems you were having?
> It looks like second hand junk now which really sucks.
That's totally unacceptable for a newly purchased, 2-month old DS4104. :wtf: I'd be furious. :box:
Have you contacted Chris Armstrong at all? He's the head honco (General Manager) at Rigol US, and I'd think he'd want to know about the QoS his techs are providing (or lack thereof). His email is: carmstrong@rigol.com, just in case you don't already have it.
I've decided that there are too many things about the Rigol MSO4000 that I don't like, so it will be going back to the distributor next week. Instead, I bit the bullet last night and bought this Agilent MSO7054B...
I probably can't remember all the little things that annoyed me about the Rigol, but some of the main points were:
2. The way ... decoding ... doesn't work in segmentation
4. The lack of Mark/Search functions, which should be a no-brainer when you have such incredibly deep memory capability.
I suspect you'll really enjoy using it.
That's such a ridiculous limitation, I'd almost stop right there! And when I asked Rigol (China) about this, they claimed it worked OK decoding segmented Frames. I'm assuming they didn't understand the question I was asking... but I was pretty explicit. Maybe I should ask again, because this is something they shouldn't be short-changing.I am not sure this is applicatable as this test was done on a DS2000 , where decoding at 115.2Kb/s using scope at 20ms/div and 56Mpts, and recorded 2 frames.
Mark,
Are you saying that you've asked Rigol directly about using the decoders on recorded frames and they said it was, or should be, working?
I certainly can't make it work.
As soon as the record feature is enabled the decoder locks up completely displaying the same data on the screen even though the actual trach changes.
Recording frames without the decoder turned on and THEN turning on the decoder while "browsing" the frames is also a no-go.
I am not sure this is applicatable as this test was done on a DS2000 , where decoding at 115.2Kb/s using scope at 20ms/div and 56Mpts, and recorded 2 frames.
I show 1st & 2nd frame,
I am not sure how one would set up triggering to capture frames in segments?
maybe trigger on an Hex Byte that only occurs at the point of interest :-//
Yes the DSO is slow, It took about 1.5s to display just the trace when move to the second Frame and about 6 seconds to display the decoded Hex of that 2nd Frame
I show more on the DS2000 forum
I am not sure this is applicatable as this test was done on a DS2000 , where decoding at 115.2Kb/s using scope at 20ms/div and 56Mpts, and recorded 2 frames.
I show 1st & 2nd frame...
Yes the DSO is slow, It took about 1.5s to display just the trace when move to the second Frame and about 6 seconds to display the decoded Hex of that 2nd Frame
Perhaps there's something else going on, but it sure shouldn't take 6 seconds for it to process 700 bytes of data from the screen (the only place it gets the data to decode a protocol), and display the string.I figure 3200 Bytes;
Perhaps there's something else going on, but it sure shouldn't take 6 seconds for it to process 700 bytes of data from the screen (the only place it gets the data to decode a protocol), and display the string.I figure 3200 Bytes;
analyzes from 32000 Bits:
which are determined from 56,000,000 Pts
interpolated from 560,000,000 samples,
over the 280ms of the display,
and processed in ZOOM mode.
( in SOftware)
Note: if Not in Zoom mode the decoding from Frame to Frame is lees than a Second
Here are the details on the test I did, and just re-did just to verify I wasn't goofing it up:
Packets of 6 bytes were sent at a baudrate of 38400, only the last byte in the packet changed. "Test n" where n incremented from A to Z and then started over
* Trigger set to RS232, invert, start, 38400 baud, normal sweep (of course)
* I locked the memory depth to 14kpts which is the lowest possible setting.
* I set the timebase to 200us/div in order to be able to fit my "long" 6byte packet on the screen.
* This resulted in a sample rate of 5Msps.
With 14 divisions each 200us "long" we've got 2.8ms worth of data on the screen which matches 14kpts/56Msps.
Now, turning on the decoder. The waveform update rate is still quite OK but it's not very stable. The frequency counter is jumping between ~130 and 165Hz but the decoder on the screen is nowhere NEAR that speed - obviously.
So where is the lower limit then, with these settings. With the 250ms between packets it's almost able to decode and present each packet on the sceren. I've only seen it "skip" once in a while so I'd say I'm just on the edge there. Yes, the frequency counter reports 4 waveform updates per second - as expected. Obviously there's no need for the decoder to update the displayed data faster then you can read but really, 4 times per second IS slow IMO.
So then I hit the Record button, what happends is that the scope starts recording frames at a rate of 4 per second obviously - as expected. The decoder on the other hand completely freezes and displays the decoded data of the last packet captured before the Record button was pressed. That's not cool if you ask me.
Stopping the recording and then "browsing" thru the recorded frames with the jog wheel does NOT update the decoded data displayed on the screen. It's completely frozen with whatever data was there when the record button was pressed.
Then lets try and record frames without having the decoder enabled during recording, stopping the recording function and THEN enable the decoder. Guess what, it STILL displays that very same data from when the Record button was pressed with the decoder on the screen. And no, it does not update when browsing thru the recorded frames.
Now, if anyone can tell me what I'm doing wrong here then I'll be forever thankful because I think I've given the scope the best possible circumstances to do it's job and I don't think it does it very good at all. This is with Software version 00.02.01 as reported by the instrument.
Now, if anyone can tell me what I'm doing wrong here then I'll be forever thankful ...
... but there should be an option in the decode menu that allows the user (with a priori knowlege of the expected data) to specify (e.g. with a cursor) exactly where the decode operation should start. Implicit in setting that cursor value would be a 're-run' of the decode operation.
I think that would be a very useful capability.
?? I think you may have meant, "14kpts/5Msps"?Yes of course, it's been corrected.
I agree that it's slow. That's 250 ms, where only the first 3 ms is needed to acquire 14k samples. Then it has to process those 14k, to decimate down to 700 screen points. Updating the screen buffer takes a bit longer, since it has to merge into a variable intensity buffer first.Correct but the lack of performance has nothing to do with the display buffer, intensity grading and what not because it's perfectly capable of doing that at 165 frames per second when the decoders are turned OFF. Obviously the screen isn't updated 165 times per second but it sure is updated faster then 4Hz.
I don't think you did anything wrong.Thanks, I feel that it has kind of been the problem with all the discussions on the issues with the protocol decoders. Almost everyone who has said they are having issues with them have been told they must be doing it wrong.
Thanks for taking the time to fully test this out, rather than just complaining "it doesn't work...Not a problem, and this is the same test I've done before when I was complaining "it doesn't work" and I have reported it to Rigol. I've included their response earlier in the thread. One thing that I did differently this time thru was to use the RS232 trigger while I used normal falling edge trigger last time. It doesn't seem to make any difference what so ever in this particular setup.
Packets of 6 bytes were sent at a baudrate of 38400, only the last byte in the packet changed. "Test n" where n incremented from A to Z and then started over@H.O.
* Trigger set to RS232, invert, start, 38400 baud, normal sweep (of course)
* I locked the memory depth to 14kpts which is the lowest possible setting.
* I set the timebase to 200us/div in order to be able to fit my "long" 6byte packet on the screen.
* This resulted in a sample rate of 5Msps.
Now, if anyone can tell me what I'm doing wrong here then I'll be forever thankful because I think I've given the scope the best possible circumstances to do it's job and I don't think it does it very good at all./size]
"I decided to try with 5ms "silence" between each 6byte packet to see what happend. "
@H.O. is it possible to try with a longer Silence period between bursts
Did the jitter you encountered at specific burst delays result in your being unable to decode frames as well? You jumped into a discussion of another issue, without saying whether or not your DS2000 worked with the same config H.O had used.I was testing with the original 5ms quite between 6 bytes of data ,and all was OK at 500us ,with decoding , but at 1ms/div , all jitter happened.
Here are the details on the test I did, and just re-did just to verify I wasn't goofing it up:
...
So then I hit the Record button, what happends is that the scope starts recording frames at a rate of 4 per second obviously - as expected. The decoder on the other hand completely freezes and displays the decoded data of the last packet captured before the Record button was pressed.
Stopping the recording and then "browsing" thru the recorded frames with the jog wheel does NOT update the decoded data displayed on the screen. It's completely frozen with whatever data was there when the record button was pressed.
Then lets try and record frames without having the decoder enabled during recording, stopping the recording function and THEN enable the decoder. Guess what, it STILL displays that very same data from when the Record button was pressed with the decoder on the screen. And no, it does not update when browsing thru the recorded frames.
Mark,
I just tried it. Cold booted the scope, recorded a couple of frames and then enabled the decoder. It pops up with decoded data from I don't know where/when but it still does not update when browsing thru the frames.
If you do contact Rigol again please do keep us updated!
Teneyes,Good Pointt H.O.
I don't think it's a quirk. I think what's happening in your case is that at 1ms/div you're going to capture more than a single packet for each trigger event so "the next" trigger event will happen "in the middle" of the next a packet. You should be able to use trigger hold off to stabilise it.
Since I've got a 4k I obviously can't say for sure regarding the 2k (I suspect the manual will tell you though). On the 4k it's in te exact same place as it always is for any trigger..... Trigger menu -> Settings.Yes Edge trigger has Trigger Holdoff, (under settings)
Hi Len,Hi Mark
It does not decode recorded frames. I thought this was reported and confirmed here awhile ago when first reported on one of the UltraVision models.
But , Does the DS4000 have trigger Holdoff when one is using RS232 Trigger???Yes it has, as you can see from the screenshot in my previous reply. I haven't tested if it actually WORKS but it's there.
...at first I was thinking it was important. but Now as I was testing the best way to monitor a serial data stream is with a long buffer (using best Mem depth), then analyze by using the zoom feature , where the decoding does work. and to record long frames, then zoom and scan the Data.
...using a single capture into a deep memory buffer is not at all the same thing, or as usable IMO, as being able to use the segmented memory.
What if there's 30 seconds between packets?
I don't know why keep mixing responses from other threads...
SOn the 4k it's in te exact same place as it always is for any trigger..... Trigger menu -> Settings.
Using my DS2000 (56Mpts) here is a test of capturing & decoding 508 frames X 465 byte blocks = 236,220 Bytes,...at first I was thinking it was important. but Now as I was testing the best way to monitor a serial data stream is with a long buffer (using best Mem depth), then analyze by using the zoom feature , where the decoding does work. and to record long frames, then zoom and scan the Data.In almost all communications protocols, there are not only gaps between requests & responses, but much longer gaps of 'dead time' between those pairs. By recording just one Frame worth of data at each trigger, you can easily extend the time you can monitor by 10x, 100x, or even 1000x. Using the shortest frames, that means up to 200k (!) msgs could be captured. And Rigol brags about that 200k frame capability!
Using my DS2000 (56Mpts) here is a test of capturing & decoding 508 frames X 465 byte blocks = 236,220 Bytes,
That's good for me.
I wasn't aware that many had even bothered trying it yet (or that you were one of them), since there were some questions initially about its legitimacy. And those that had weren't noticing any significant improvements. Naturally, Rigol isn't about to make a list of things they fixed. That would require admitting that a capability that should have worked from day one (and they've been claiming did work), just showed up 2(?) years later. (Though the DS4000 folks are still waiting, even longer. :( )I am not sure I have the latest 'Offcial' version.
I am not sure I have the latest 'Offcial' version.:-DD
I know this FW has bugs that will freeze the DSO...:(
...and I am disappointed that it does fix the bugs we have reported to Rigol.
The FW is a much larger file, going from 8MB to 10MB, so it should add something.
To DS4000 owners:
I'm working on a new version of my Rigol Ultravision Utilities to handle all 4 channels of the DS4000 (as well as DS1000Zs). Since I don't own either DSO, I'd appreciate any owners willing to be alpha/beta testers. The link for the current alpha (as well as some explanatory info) is here (https://www.eevblog.com/forum/projects/software-tips-and-tricks-for-rigol-ds200040006000-ultravision-dsos/msg442444/#msg442444).
Hi,
question concerning the HORIZONTAL knob of the DS4000 series:
when I turn it fast the timebase sometimes jumps back or foward.
When turning the knob slower there's absolute no problem.
Would be interested in your experience. Either the routine for the rotary knob is not implemented well or it seems to be
broken. Usually a gray code is used for decoding such kind of knobs.
Is there a bug in the DS4000 series?
Rgds
Gunb
I'll check mine and see if it acts that way. I bet they are not sampling the knob fast enough and it is skipping states making it look like it is going backwards.
question concerning the HORIZONTAL knob of the DS4000 series:
when I turn it fast the timebase sometimes jumps back or foward.
When turning the knob slower there's absolute no problem.
I started having the same problem with the Horizontal scale knob on my DS2000 after about 14 or 15 months of owning it. I sent it back (to the dealer) for knob replacement while I was abroad a month ago. It's fine again.
Hi,Hi
question concerning the HORIZONTAL knob of the DS4000 series:
when I turn it fast the timebase sometimes jumps back or foward.
When turning the knob slower there's absolute no problem.
OK, good to know. But annoying to send it to the service. Does anybody know the part no. of these digital potentiometer? I mean, I expect it will happen in the future again and it's not difficult to change these parts. Last year our company sent an old Agilent scope to the service with the same issue and it cost about 500,-€.
Rgds
Gunb
Hi
Have You used the Key Test , see Pix below.
I had a RMA repair done on my DS2000 and received this note
Well, it was under warranty, so I only paid for shipping one-way. He offered to send me the part (or I could also just send him the encoder board already removed), but since I was leaving the country (and couldn't use the DSO), it wasn't worth my time to do the work myself to save € 30. I might be able to get the part number.
I started having the same problem with the Horizontal scale knob on my DS2000 after about 14 or 15 months of owning it. I sent it back (to the dealer) for knob replacement while I was abroad a month ago. It's fine again.How often did you use your scope? Two hours a day? Well, many Rigols might have problems with encoders. RIGOL DS1052E troubles with encoder (https://www.youtube.com/watch?v=lV3WKqZhuRQ#)
How often did you use your scope? Two hours a day? Well, many Rigols might have problems with encoders. RIGOL DS1052E troubles with encoder (https://www.youtube.com/watch?v=lV3WKqZhuRQ#)
Just be aware that Hydrawerk is an Agilent Owner and strives to put down Rigol equipment,
I'm not sure why he nitpicks so much. Just like a chicken pecking the the red spot.
Just be aware that Hydrawerk is an Agilent Owner and strives to put down Rigol equipment,Well, sorry, I am not gonna say that Agilent is perfect.
I'm not sure why he nitpicks so much. Just like a chicken pecking the the red spot.
How often did you use your scope? Two hours a day? Well, many Rigols might have problems with encoders.
Some of the Rigols encoders are made of metal, I like it. At Agilent all of them are made of plastic. But I could not find any closer info on the manufacturer, or if they are mechanical or optical.
Hi,
Seeing that the "other" Rigol thread is mostly on the DS2000 and now the 1000 series I thought I'd post here instead.
Yesterday I applied MrKrabs edition of the 02.01.00.03 DS4000 firmware and it worked like a charm, all options stayed intact, thanks MrKrabs!
In another thread someone mentioned the decoders not operating on recorded frames, something that sounded a bit strange to me - say it isn't so I said to myself. Unfortunately that does seem to be the case (I only tested the RS232 decoder). I thought perhaps the frames had to be recorded with the decoder active but that doesn't work either - as soon as you press the record button the decoder stops updating. "Browsing" thru the recorded frames doesn't do anything with the decoded data on the screen, it just stays the way it was at the moment you pressed Record. Using the wavefor analysis function in order to "preview" the frames at the bottom of the screen the preview to the left of the current of frame somtimes distors badly and this appears to only happen when the decoder is on the screen.
Since the decoders appears to be software driven I really don't see the reason for them not being able to operate on recorded frames.
Don't know if it can be called a bug as I don't think I've seen it stated anywhere that it should work, still kind of a shame though.
Hello everyone.
Thank to Cybernet and MrKrabs.
My DS4024 model to full!
also i noticed a bug in this fw , i lost the abilty to set volts/div to 500uv not a huge deal but still it says parameters overrange and minimum is 1mv/div on my 4014 now
also i noticed a bug in this fw , i lost the abilty to set volts/div to 500uv not a huge deal but still it says parameters overrange and minimum is 1mv/div on my 4014 now
Why should there be a bug? Max. sensitivity of the DS4000 series is 1mV/DIV. It's not a DS2000 with 500µV/DIV.
im kinda surprised its 3 times the price i thought it did have 500uv , but I guess the Fw is working perfectly then , wonder why rigol took away that feature on a more expensive scope , interesting
Question: what you think which one is visible (not blind) time. 112 sampled points time or 700 sampled (but mainly not visible) points time.His sample sizes in his charts are incorrect at the lower time bases. When the Rigol displays '700*', it means it's sampling <= 700, which means at 2ns/div, it's sampling 112 points.
I vote displayed sample size.I would tend to agree with you - except in the case of segments, when you can zoom out to replay the full sample size.
Ref: http://cdn.rohde-schwarz.com/dl_downloads/dl_application/application_notes/1er02/1ER02_1e.pdf (http://cdn.rohde-schwarz.com/dl_downloads/dl_application/application_notes/1er02/1ER02_1e.pdf)Although Rohde-Schwarz calculates blind-time based on the full sample size - Agilent is the company that calculates based on displayed sample size.
His sample sizes in his charts are incorrect at the lower time bases. When the Rigol displays '700*', it means it's sampling <= 700, which means at 2ns/div, it's sampling 112 points.
I would tend to agree with you - except in the case of segments, when you can zoom out to replay the full sample size.
Although Rohde-Schwarz calculates blind-time based on the full sample size - Agilent is the company that calculates based on displayed sample size.
Hey eveyone,
I'm trying to upgrade my DS4014.
I upgraded the firmware and got 00.02.01.00.03
Ultra sigma doesn't give me a large HEX. I' really lost, I'm jut a noob learning electronics.
Please help
Sam
Hey eveyone,
I'm trying to upgrade my DS4014.
I upgraded the firmware and got 00.02.01.00.03
Ultra sigma doesn't give me a large HEX. I' really lost, I'm jut a noob learning electronics.
Please help
Sam
Just install my patched firmware. It's at http://gotroot.ca/rigol/: (http://gotroot.ca/rigol/:)
http://gotroot.ca/rigol/DS4000Update.00.02.01.00.03.MrKrabs.GEL.zip (http://gotroot.ca/rigol/DS4000Update.00.02.01.00.03.MrKrabs.GEL.zip)
Here's my original message (buried in that huge thread ;) )
https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg369754/#msg369754 (https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg369754/#msg369754)
When the memory is filled up or the acquisition is stopped it is possible to change to the Playback or the Analysis Mode. Within this you can scroll to all messages frame by frame and see the decoded data.
FYI: I've finally (!) been able to get a response from Rigol regarding the decoding of recorded frames on the DS4k. They have confirmed that it is a bug (no surprise) and they are saying that it will be fixed in the next revision of the firmware. I wasn't told when in time that firmware is about to be released and/or what else they might have done to it.
Possibly, but lets hope not :)
One can't help thinking about how many actual decoder licenses for the DS4k have been sold? I mean, list price for a DS4014 is ~$2700 (Batronix (http://www.batronix.com/shop/oscilloscopes/Rigol-DS4014.html)), $600 on top of that (+22%) for the RS232 decoding alone ($1700 for the combo, and that doesn't include FlexRay which is another $1400) and then performing the way they are is ridiculous IMO.
I mean, *I* don't really have the right to complain since I didn't actually buy any decoder licenses but since my scope came WITHOUT the time limited trial licenses installed (yep, that's true) I had to enable them just to see what it was 8). And let me tell you that had I actually payed that kind of money I'd be calling and emailing my supplier each and every day untill they got me a fix or gave me my money back.
I would suspect any customer actualy paying that kind of money would too but the fact that the scope is ~3 years old (heck, I've had mine for over two) and these bugs are STILL there tells me no-one is actually paying for it.
I'm going to give a ds4014 a try. Is there a calibration board for less in the US from anywhere? The price at batronix plus dhl shipping adds that up a bit. I may even lay out a small pcb to order through itead. If I give that a try, I'd probably start with the source signal in the center and have it come out in 5 even directions...
Ok, how about this, I put this together so far. Fits inside of 5cm x 5cm for itead <9.90.
did ya balance yer impedances to 50 ohms? I'm not sure this is any better than a bunch of BNC cables and tees.
did ya balance yer impedances to 50 ohms? I'm not sure this is any better than a bunch of BNC cables and tees.
I wondered about this last night after throwing it together. I made the track lengths the same for all 5. Track widths are 20mil. Is there something I need to do to balance them? If so, what?
Edit, after looking at a couple of impedance trace calculators, if I use a 1.2mm pcb, 35um copper, substrate dielectric of 4.35, one calculator gives 87.2 mils wide track and the other gives 92 mils, so I guess I should use a 90 mil track. The one at batronix looks like it uses some pretty wide track and perhaps this is why.
EDIT 2 - I only have 4 places (between the ground spokes) I can put the 90 mil wide trace from the center connector. Can I put a ring around it, connect 4 traces from the source connector, and then 5 even traces from the ring to the router ones? Any downside to doing that?
...have it come out in 5 even directions...
I don't know how the cal board is used, but I assume that all channels are set to 50 ohms to use it.
Firstly, depending on use case, it may be necessary to terminate any unused channels with fifty ohm terminators or you'll get erroneous results.
I'm an RF guy, and the Rigol Calibration kit board looks like it has fifty ohm microstrip.
I don't know how the cal board is used, but I assume that all channels are set to 50 ohms to use it.
However, the combined impedance will be 10 ohms (five 50 ohms in parallel: see, RF ain't all black magic!) which won't match the central feed which I assume will go off to a signal generator presumeably with a 50 ohm characteristic impedance. Whether this is a problem or not I don't know, but it seems strange to go to the effort of making 50 ohm microstrip and then mismatching the feed point so grossly. But depending on the use case, if all channels are equally badly treated perhaps it doesn't matter.
It is possible there's some impedance matching such as a wideband transformer on the board to deal with the mismatch, but I couldn't see any evidence of this. You could use a minimum loss pad to provide a broadband match too (basically a pi or T made out of resistors, they're inherently broadband, but more lossy than a transformer).
A couple of other comments. Firstly, depending on use case, it may be necessary to terminate any unused channels with fifty ohm terminators or you'll get erroneous results. Secondly, the closeness of those BNCs on your board might make for a bit of fun when trying to fit the cables, you might want to do a fit check first, I did a similar thing with SMA connectors on a board a few years ago, you don't make that mistake twice!
The email said 02.01, but if you look at the first few bytes of the file, you'll see it's actually 00.02.02.01.01.
00.02.02.01.01 has 9570200 bytes
00.02.01.00.03 has 9091982 bytes
sha1sum:
ab2b226cf3b5fbd42cd72054e6ba773d35973512 DS4000Update.00.02.01.00.03.GEL
5a76dc73098e1a2ddb4492d17f8a26397b09e1dd DS4000Update.00.02.02.01.01.GEL
I've added them to the above post.
Cheers.
Could you please add here the firmware changes / bug fixies / improvements?
Hi,
Nothing was included apart from the binary itself, but I have asked for them.
Here is the link from Rigol - which is still working for me:
http://beyondmeasure.rigoltech.com/acton/ct/1579/s-0592-1501/Bct/l-3f49/l-3f49:bfa/ct2_0/1?sid=QeaAQw9Wk (http://beyondmeasure.rigoltech.com/acton/ct/1579/s-0592-1501/Bct/l-3f49/l-3f49:bfa/ct2_0/1?sid=QeaAQw9Wk)
Hi,
Have you tried it yet? Let me know if it works better than my pcb. $40 isn't a bad deal for it. When I called Rigol they wanted $120 or something!
BTW, all of you 4K users, if anyone wants a spare set of probes, I usually use my own probes, so I have 4 brand new RP3500A's. They normally retail for $220 each, but I'll sell them for $130 each.
Thanks,
Alan
Hi,
Have you tried it yet? Let me know if it works better than my pcb. $40 isn't a bad deal for it. When I called Rigol they wanted $120 or something!
BTW, all of you 4K users, if anyone wants a spare set of probes, I usually use my own probes, so I have 4 brand new RP3500A's. They normally retail for $220 each, but I'll sell them for $130 each.
Thanks,
Alan
Hey Alan! Waiting for the scope to warm up to try it now. :-)
do you know the changes in the newest 00.02.02.03.05 version? Are there release notes included?
Could you please add here the firmware changes / bug fixies / improvements?
But there have always been recurring comparisons, discussions and doubts in several threads here in the forum (and elsewhere) whether or not the hardware of the different bandwidth models really was indeed identical, all individual devices capable and tested for full-bandwidth operation, etc., because Rigol never offered bandwidth-upgrades via option-keys themselves.Well, untill we get to compare an upgraded 100MHz DS4k scope to a "real" 500MHz DS4k scope there's no way to say for sure. All I can personally say is that while feeding a 100MHz, 100mV peak to peak signal into my DS4014 it showed as 85mV pre update and 98mV post update. I'm willing to bet that there's NO difference between a "real" 500MHz model and an updated 100MHz unit.
Although I haven't seen any official Rigol bandwidth upgrade-options for sale anywhere, so far, why should they document this possibility in the release notes, now, if they didn't plan to sell such option keys?TE Equipment is selling the bandwidth options. Though, just as the manual says, only for 200MHz and 350MHz models.
Probably no 401x-owners out there who dare uninstalling their bandwidth-options, updating the firmware and trying to re-install the bandwidth options, are there? ;-) Are there already any reports from new 401x-owners, whose scopes already shipped with the new firmware? Do the bandwidth-keys still work?We'll have to see if someone dares to update. I'm currently on 02.02.01.01 and see no need to update at the moment so I'll just wait.
He mentions he has a DS4014/500, which, I suppose, means a 100 MHz DS4014 unlocked to 500 MHz.Correct.
While we may certainly doubt that his DS4014 suddenly has turned into a 1 GHz scope after the firmware update, it has most probably not fallen back to 100 MHz bandwidth during the update.Correct, it was just an observation I thought was interesting. The signal was much attenuated and some tweaking of levels was required, but the freq counter displayed correctly and the trace was visible which was a surprise.
This makes me wonder if the bandwidth keys can still be installed in the new firmware running on a "virgin" 100 MHz DS/MSO 401x?!I expect it still works, but that is based on my theory that Rigol implemented the license key feature a while ago and just added it to the release notes now.
Maybe the release notes and manuals just match the real firmware features accidentally every once in a while... :-D
DS/MSO4000: 00.02.02.04.03 appears to be available.
You STILL haven't decided on what scope to buy or are you shopping for another? Which one did you get last time? Do you know what you're looking for in a scope these days? Did you get the big government funding or are you buying with your own money?
With that said you do realise that if you do a 140Mpts capture you can pan/zoom thru it and the scope will decode what's on the screen at any given time?
Just updated. For those with hacked scopes, it does change the model number back to original, but note it adds the "Bandwidth 500M" option. All other options kept and appear normal.
FWIW The model number not changing was in the release notes.
Does your Decode2 work? I saw there was a change a release or two ago which split the options into two banks, so I got a license code for the second set of options and that worked for me.
dr. diesel does it allow you to downgrade (you may or may not want to test it, I understand if you don't).
Updated my DS4014. What is with the size of the counter now? It is huge...
Hi all!
I find a new bug in the help system of my a device!
3. I press a key "Help", then a key "F1" (left menu) and see this (please, look image)...
Hello,
I do not have this bug ...
Hi all!Part of flash not programmed properly? Is it just for that one image or others in the help too? Have you tried doing the firmware update again?
I find a new bug in the help system of my a device!
3. I press a key "Help", then a key "F1" (left menu) and see this (please, look image)...
Part of flash not programmed properly?I too have this idea. But this is strange situation. Update my MSO4014 completed correctly, without errors.
Is it just for that one image or others in the help too?What pictures should i see more?
Have you tried doing the firmware update again?Yes, I did the update again!
Hi,
But, as I said in the SA thread, Rigol isn't monitoring these forums, we need to report the issues to them.
I was just wondering in general if the other graphics in the help items had similar corruption or only that one place.
2.QuoteIs it just for that one image or others in the help too?What pictures should i see more?
I was just wondering in general if the other graphics in the help items had similar corruption or only that one place.
2.QuoteIs it just for that one image or others in the help too?What pictures should i see more?
But with others experiencing similar corruption this sounds like something for Rigol to fix.
What comes to mind are possibly corrupted graphics embedded in the firmware update file or some code bug. Or then corrupted firmware update image on the server but I would have expected there to be checksums to detect corrupt update file.
Can anyone perform some saving speed tests on DS4000? Is it so slow as DS1000Z? Is there any solution for saving fast large files?
Hi all!
I find a new bug in the help system of my a device!
In order:
1. I downloaded firmware from the site beyondmeasure.rigoltech.com. Firmware sent me to the site rigoltech.com on my e-mail. The official software the official site! Ok!
2. I upgraded firmware in my a device MSO4014 to version 00.02.02.04.03. Ok!
3. I press a key "Help", then a key "F1" (left menu) and see this (please, look image)...
I'm depressed and I can not eat and sleep! :-\ |O Help me! ;D
My friends, please, look in your devices the help system.
Very thanks!
I _greatly_ dislike the new preschooler sized way too large counter - it takes up way too much screen space.
What is the latest hardware version of the MSO4014, the one I received today from tequipment.net is hardware version 1.3 and firmware version 00.02.02.SP1. That seems old.
The screen on mine flickers, has anyone else encountered this?
What option code do you use to get ALL the options, like the Power Analysis and 1553B Decoder? I don't think you get the PA feature with the FAB9 code.
Have we figured out what the MA option is yet? Is that short for Modulation Analysis?
I found this PDF that talks about the Ultra Power Analysis software... any idea where to get the software?
Where can I get a current copy of the NI VISA and IVI driver software so that I can interface this with my computer?
What option code do you use to get ALL the options, like the Power Analysis and 1553B Decoder? I don't think you get the PA feature with the FAB9 code.
Try BAH9
From memory you also need CAH9 to enable the same options on the 2nd decoder. In theory according to the text file DAH9 should do both banks at the same time.
What option code do you use to get ALL the options, like the Power Analysis and 1553B Decoder? I don't think you get the PA feature with the FAB9 code.
Try BAH9
From memory you also need CAH9 to enable the same options on the 2nd decoder. In theory according to the text file DAH9 should do both banks at the same time.
Wouldn't it be RA39? That enables both unknown features, bandwidth, and decoders. and 500MHz, MA, and Power Analysis. and all known decoders.
Has anyone noticed that i, 0, and 1 are missing from that option code chart? Also xAx9 doesn't appear to unlock the 1553B decoder.
What option code do you use to get ALL the options, like the Power Analysis and 1553B Decoder? I don't think you get the PA feature with the FAB9 code.
Try BAH9
From memory you also need CAH9 to enable the same options on the 2nd decoder. In theory according to the text file DAH9 should do both banks at the same time.
Wouldn't it be RA39? That enables both unknown features, bandwidth, and decoders. and 500MHz, MA, and Power Analysis. and all known decoders.
Has anyone noticed that i, 0, and 1 are missing from that option code chart? Also xAx9 doesn't appear to unlock the 1553B decoder.
Ah yes I was having trouble opening the PDF so was just reading the text file which isn't so straightforward.
I found a copy of the pdf here and now it makes more sense.
Yes I agree RA39 looks like it turns everything on.
Regarding the 1553B decoder, I'm not sure if anyone else has managed to enable that or if its just me. If just me then it was probably blind luck more than anything, and all I can say is its possible somehow :)
However I remember turning on the 'license reapplication bit' at some stage - which would make the second letter 'S' instead of 'A'. So maybe give that a try if you have tried everything else.
$ strings DS4000Update.GEL |grep "Trial Version" -A24
Trial Version
Expired
Never Expires
Minute
Option Name:
Time Left:
Offcial Version
RS232
FlexRay
500M
350M
200M
1553B
RS232 Decoder
SPI Decoder
I2C Decoder
CAN Decoder
FlexRay Decoder
Bandwidth 500M
Bandwidth 350M
Bandwidth 200M
Power Analysis
1553B Decoder
Installed Options
Option Edition:
I used RS39, on my first attempt, and that gave me the 1553B decoder and Power Analysis options, and I already had everything else from the previous time I used the FAB9 option code.
What exactly is the difference between xAxx and xSxx? Do other characters work in the second position?
I used RS39, on my first attempt, and that gave me the 1553B decoder and Power Analysis options, and I already had everything else from the previous time I used the FAB9 option code.
What exactly is the difference between xAxx and xSxx? Do other characters work in the second position?
Nice one :)
Using S turns on the top bit, whereas A turns off all of the bits.
The top bit is described as the 'License re-application bit' in this text file:
http://gotroot.ca/rigol/DS4000%20Series%20Options.txt (http://gotroot.ca/rigol/DS4000%20Series%20Options.txt)
My guess on the A vs S is that its not a licence re-application bit at all. Instead it just changes the option bits to select the PA and 1553B options instead of the standard set of options.
Code: Bits: Action:
RA39 00000 Option Installed!
RB39 00001 The option has been installed!
RC39 00010 Option Installed!
RD39 00011 The option has been installed!
RE39 00100 The option has been installed!
RF39 00101 The option has been installed!
RG39 00110 The option has been installed!
RH39 00111 Option Installed!
RJ39 01000 License is unavailable!
RK39 01001 License is unavailable!
RL39 01010 License is unavailable!
RM39 01011 License is unavailable!
RN39 01100 License is unavailable!
RP39 01101 License is unavailable!
RQ39 01110 License is unavailable!
RR39 01111 License is unavailable!
RS39 10000 Option Installed!
RT39 10001 Option Installed!
RU39 10010 The option has been installed!
RV39 10011 The option has been installed!
RW39 10100 The option has been installed!
RX39 10101 The option has been installed!
RY39 10110 The option has been installed!
RZ39 10111 Option Installed!
R239 11000 License is unavailable!
R339 11001 License is unavailable!
R439 11010 License is unavailable!
R539 11011 License is unavailable!
R639 11100 License is unavailable!
R739 11101 License is unavailable!
R839 11110 License is unavailable!
R939 11111 License is unavailable!
I can't get my measurements size to even change, my counter is huge as well.
It has a bug - you can't save and then load setups. It gives a version error. Even if you delete it, save a new one, it won't load it. :palm:Yes, I can confirm that... :(
Also, their font size increase for measurements runs into the waveform area.This happens only on the Ultra large setting, and it mostly covers the grid delimiter... I personally don't care and would be much more annoyed if either the grid area or the channel voltage settings were reduced in size to accommodate that.
Also, also, the counter is still freaking huge...Yes, that is very strange.
I've just become a proud owner of a used DS4014 and have been busy testing the scope which seems to work well.
While doing that, I have encountered some problems with RS232 protocol decoding and on one occasion a specific key sequence caused the instrument to freeze and I had to powercycle.
My Firmware is Version "00.02.00" and my Hardware is Version "1.2" as seen when pressing Utility > System > System Info
I'm wondering if it is wise to upgrade to a later/latest firmware, but I don't know if my hardware version is compatible with the latest firmware.
I don't want to brick the scope as I have to use it for project, but it would be nice to upgrade and get rid of the accumulated bugs.
Has anyone got the latest firmware running on a DS4014 with hardware version1.2 ?
Is it required to upgrade in steps or straight to the latest version?
Has anyone bricked a DS4014 or similar by performing a firmware upgrade?
Any infos would be much appreciated. Many thanks!
See Reply #328, there's a link...
Don't update to the 00.02.02.05.02 version, there is a bug that doesn't allow you to load/save a setup. Waiting for a new version to fix this.
Sorry Gunb, maximum attachment size is 1MB, not enough for firmware file.
Contact Rigol and request it here:
http://beyondmeasure.rigoltech.com/acton/form/1579/001e:d-0001/0/-/-/-/-/index.htm (http://beyondmeasure.rigoltech.com/acton/form/1579/001e:d-0001/0/-/-/-/-/index.htm)
In my experience you no longer have to ask for it always.
After a certain point in time it seems like they set up a mailing list / subscription thing. From time to time I get emails from them with links to the latest firmware for the instruments I've previously requested the firmware for. I don't even have to go looking for it, when there's a new version they tell me about it. Of course, if you're using disposable email adresses and that kind of stuff it won't work.
If you're not going to update untill the firmware is free of bugs you're not ever going to update. I haven't updated to the latest because I haven't had any issues with what I have and I never save/load setups so that particular bug wouldn't bother me much. YMMV of course.
Who said I'd never have updated the scope?No one said that. All I'm saying is that if you're waiting for a bug free version before updating you're going to be stuck where you are because every version will be "buggy". If the bugs in that particular version hurts you or not is of course up to each and every one to decide. The revision history included in the firmware download isn't all that great (but better than nothing) and does of course not include any newly introduced bugs...
So, the question is what are the pros and cons to update or not?Well, the pros are listed in the release notes. The cons, apparently, is that save/load setups are broken. I don't know of anything else but I'm sure there is.
I'm one of the first owners of the DS4000. And I fixed a few bugs in the ealier releases by reporting bugs to the German Rigol support in the past.I've had my DS4k for a while too, May 2012 to be precise, so I've gone thru a couple of versions and reported some bugs as well. I won't take credit for actually fixing them though.
No one said that. All I'm sayi....
FFT for channel number x is forced to zero when channel number x-1 is switched to GND couplingYes, that happens here as well. Latest FW.
Could someone on the latest DS4k firmware please try to replicate this bug:BTW, this still happens with the latest firmware.
FFT for channel number x is forced to zero when channel number x-1 is switched to GND coupling
1: Connect a probe to channel 2 and observe some trace
2: Turn on FFT for channel 2 and observe some spectrum
3: Switch Coupling for channel 1 to GND
4: Observe FFT trace for channel 2 is now zero.
This does not happen with the new firmware.FFT for channel number x is forced to zero when channel number x-1 is switched to GND couplingYes, that happens here as well. Latest FW.
Also, did you notice that the trigger line on the display disappears? IIRC this happened with me when I closed the FFT mode. To bring it back I had to go to Trigger menu and fiddle with something there.
Fun with 00.02.03.00.03: In the trigger menu falling and rising edge trigger options are exchanged: choosing 'rising edge' triggers on falling edge and vice versa.
Don't want to downgrade just to check - is that a new one or didn't I catch this before?
Maybe the corresponding input channel is set inverted? On mine, the polarity of the trigger slope is correct after the update (as it has been before as well...).
Cheers,
Thomas
Another interesting finding during disassembly: Since my scope is an MSO version and is of fairly recent manufacturing date (february 2016), it shows that Rigol continuously improves their products, see the attached photo. They took care of the rather hot-running ADCs (as reported by several contributors) by replacing the individual heat sinks with a single, big, machined heat sink that covers the whole "high temp area" of the digital signal processing path.What some may want to know is your DSO's HW revision #.
Sure. H/W of my MSO4014 is 0.1.3.1
Cheers,
Thomas
So I cracked that thing open and swapped in two decent ALPS encoders (the original ones don't appear to be bad quality, it's only Rigol used the wrong type in that place).I agree: the original encoders have good quality but the difference in usability is massive!
Another interesting finding during disassembly: Since my scope is an MSO version and is of fairly recent manufacturing date (february 2016), it shows that Rigol continuously improves their products, see the attached photo. They took care of the rather hot-running ADCs (as reported by several contributors) by replacing the individual heat sinks with a single, big, machined heat sink that covers the whole "high temp area" of the digital signal processing path. Well done!After the heatsink hackjob on mine, just be sure the large heatsink is actually touching the ADCs, as I recall they were slightly thinner than the Virtex 5s.
Moreover, the photo finally shows the purpose of the high speed connector on the main board that Connor Wolf was referring to in his teardown video. This connector isn't visible in the photo but it shows that it actually intefaces to the logic analyer subassembly on the MSO models.My non-MSO oscilloscope has the high-speed connector populated. Interesting to see its function.
And with no common heatsink?Sure. H/W of my MSO4014 is 0.1.3.1
Cheers,
Thomas
Nice work on the encoder, and thanks for thinking to ask that question tautech.
Another data point - My scope is from mid 2014 and the HW version is also 0.1.3.1
And with no common heatsink?Sure. H/W of my MSO4014 is 0.1.3.1
Cheers,
Thomas
Nice work on the encoder, and thanks for thinking to ask that question tautech.
Another data point - My scope is from mid 2014 and the HW version is also 0.1.3.1
Same model?
And with no common heatsink?Sure. H/W of my MSO4014 is 0.1.3.1
Cheers,
Thomas
Nice work on the encoder, and thanks for thinking to ask that question tautech.
Another data point - My scope is from mid 2014 and the HW version is also 0.1.3.1
Same model?
Did you guys see the DS4014E and DS4024E they have on the Chinese site. The DS4014E looks to be about half the price of the DS4014 if you look at the CNY numbers they have. Oddly, it only has 2GSa/s listed instead of 4GSa/s -On Russian site
Is each channel @2GSa/s?I don't think it is - similarly to the DS4000, it says "up to 2GSPS for each channel". I would find it hard they would save some money by simply removing the ADC channel interleaving. Perhaps it is a cheaper dual channel 1GSPS ADC and the 2GSPS is only on every two channels. It could also use a different frontend that goes only to 200MHz.
Added flex Ray decoding.The DS4000 has FlexRay, and at a certain point Rigol offered this for free.
Three additional details: four channel only, smaller memory (14Mpts/channel) and slower update rate (60kwfm/s).Could it be possible that they have done a lower cost re-design for the hardware with newer and cheaper as well as lower performance parts.
. I would find it hard they would save some money by simply removing the ADC channel interleaving of the MXT201's.In the display ,pg3 ,shows 4chs and at 2GSa/s. Perhaps dual DS4000 ADCs
I can't see in the photo what the exact part number is (would there exist an original better quality version of the photo that shows the part number on the Virtex?) but the cheapest Virtex 5 from Digikey is $250 for one piece:That is the exact Virtex P/N on my DS4014.
http://www.digikey.com/product-detail/en/xilinx-inc/XC5VLX30-1FFG324C/122-1558-ND/1768318 (http://www.digikey.com/product-detail/en/xilinx-inc/XC5VLX30-1FFG324C/122-1558-ND/1768318)
I wonder if they missed the sales forecast for their DS4000 oscilloscopes and may be trying to recover some of the cost with a minimal redesign. I know many folks that wanted a DS2k with four channels, and that may be Rigol's response to that demand.. I would find it hard they would save some money by simply removing the ADC channel interleaving of the MXT201's.In the display ,pg3 ,shows 4chs and at 2GSa/s. Perhaps dual DS4000 ADCs
Who is the target market?
Or dumping DS4000 end of life supplies?
I can't see in the photo what the exact part number is (would there exist an original better quality version of the photo that shows the part number on the Virtex?) but the cheapest Virtex 5 from Digikey is $250 for one piece:That is the exact Virtex P/N on my DS4014.
http://www.digikey.com/product-detail/en/xilinx-inc/XC5VLX30-1FFG324C/122-1558-ND/1768318 (http://www.digikey.com/product-detail/en/xilinx-inc/XC5VLX30-1FFG324C/122-1558-ND/1768318)
I imagine they redesigned the product with a smaller framebuffer (about 1/2 of the original wfm/s) which may also require a smaller FPGA.
Thank you for the closeup picture of the FPGA. Looks like they are using the larger FFG676 package with more IO.The distributors do not have budgetary price for 1ku for this FPGA, therefore it is very difficult to figure out exactly how much Rigol is paying for them. I would imagine they have quoted at least multiples of 10ku (2ku of 4ch oscilloscopes), where price would be significantly reduced.
So it would be this one for $287.50 each
http://www.digikey.com/product-detail/en/xilinx-inc/XC5VLX30-1FFG676C/122-1559-ND/1768319 (http://www.digikey.com/product-detail/en/xilinx-inc/XC5VLX30-1FFG676C/122-1559-ND/1768319)
If the DS4000 uses 5 pieces of these FPGAs that would be $1437.50 just for the FPGAs at the Digikey price. I imagine it should be possible to design a more cost optimized version these days.
Also if they are creating a cost optimized version that is intended to sell at lower price then unless they are planning to completely discontinue the current DS4000 they will probably need some way to differentiate from the regular DS4000. For that they may limit some of the capabilities even if there would be no real technical reason for that.
Hi All - Just to let you all know Rigol have indeed released two new DS-4000E models.John, thanks for confirming my initial suspicion: the DS4000E seems to address the demand for a "four channel" DS2000. A very smart move IMHO, given they only need to do a very minimal redesign.
These are released to fill a cost gap in the range between the DS-1000Z and existing DS-4000 for a 4 channel 100/200Mhz DSO. There are 2 models , DS-2014E 100Mhz 4 ch and DS-4024E 200Mhz 4 ch
Primary differences as has been pointed out are ;
Lower price - the above link has our local $ Aud pricing
Max sample rate 2GS/s vs 4GS/s
Memory depth 14Mpts vs 140Mpts
wfms/s 60,000 vs 110,000 wfms/s
If you follow the link as above to the Emona web site you can click on more info and download a 10 page brochure.
If you have any questions on these at all let me know.
And it's not correct with regards to the DS4000 either.I can confirm what H.O. said.
For single channel it's 4Gs/s and 140Mpts, for dual channel it's half (2Gs/s and 70Mpts). If you have a four channel scope then you have two dual channel scopes connected to one screen.
So, on a four channel version you can have 2 channels (1/3 or 2/4 at 4Gs/s and 140Mpts each) or 3 or 4 channels at 2Gs/s and 70Mpts each.
I don't read Chinese but I'm pretty sure that 1Gs/s you see splashed in there with all the Chinese tokens is reffering to the sample rate for the digital channels - which on theDSMSO4000 is 1GHz.
Hi - I'll check with Rigol and wether or not there are independent ADC's per ch. or shared and let you know.
I don't yet have a unit in country to try on , our demo stock are on order but still a few weeks off.
It's actually weird that Rigol has introduced these new models as part of the DS4000 series, and not as part of the DS2000 series.
Before, the sample rate always defined the number in the DS series:
1 GS/s => DS1000 series
2 GS/s => DS2000 series
4 GS/s => DS4000 series
They could have used the following alternatives: DS2104A, DS2204A. Would be more logical to me!
, it's reasonably priced and it's hackable...LOL
The cost reduction has to come from somewhere, and there is plenty to reduce in a DS4000 as I stated before (FPGAs, ADCs, memory). I suspect memory and GSPS are not upgradeable, but perhaps decoders and other functions. Obviously we would only be sure after opening one up and comparing IC markings., it's reasonably priced and it's hackable...LOL
Upgradable ? NOT easy, I think,
Could just be the DS2000 56M memory, different front end filter Amp.
It's actually weird that Rigol has introduced these new models as part of the DS4000 series, and not as part of the DS2000 series.Apart from the fact that:
Before, the sample rate always defined the number in the DS series:
1 GS/s => DS1000 series
2 GS/s => DS2000 series
4 GS/s => DS4000 series
The cost reduction has to come from somewhere, and there is plenty to reduce in a DS4000 as I stated before (FPGAs, ADCs, memory). I suspect memory and GSPS are not upgradeable, but perhaps decoders and other functions. Obviously we would only be sure after opening one up and comparing IC markings.Yes we have no idea if any re-design and cost reduction has actually been done.
Hacking is a go (500MHz, serial), but be warned: serial decode still has major bugs after all these years, and it's still done in software. Right now the big problem is that serial decode vanishes if you scale or shift the waveform (trigger still works though). A year ago the problem was that decode didn't work in segmented memory. Make sure the scope still makes sense to you with that caveat. When you include the price of a Saleae to compensate, the sticker price of a DS4k starts getting awfully close to that of an Agilent DSOX2014A + serial decode upgrade.If you are looking for a brand new oscilloscope, if two channels are sufficient for you (especially if you plan to purchase a logic analyzer) and you are located in North America, Rigol's clearance bin (http://www.rigolna.com/clearance/) has a good deal on a DS4012 - I bought my DS4014 there.
IMO the Rigol+Saleae still makes good sense -- more memory, more waveform/s, more bandwidth if you hack it, more decodes and more memory in the Saleae. But it's not the no-brainer of a $400 DS1054 vs a $1.5k Tek.
Hacking is a go (500MHz, serial), but be warned: serial decode still has major bugs after all these years, and it's still done in software. Right now the big problem is that serial decode vanishes if you scale or shift the waveform (trigger still works though). A year ago the problem was that decode didn't work in segmented memory. Make sure the scope still makes sense to you with that caveat. When you include the price of a Saleae to compensate, the sticker price of a DS4k starts getting awfully close to that of an Agilent DSOX2014A + serial decode upgrade.Except other than at the extreme top end (10ns/div and faster when the synthetic 50,000 wfm/s limit is applied) and while only running a single channel the Agilent/Keysight 2000 still has a faster update rate, with dual channels or vectors the gap widens more as the Rigol slows down, 99% of use cases the Rigol update rate will be much slower by factors of x3, x10 or more. There are marketing specs which use corner cases to sell products, and then things like "the feel" of a responsive hardware driven capture system, compared to the Rigol display stuttering or failing to respond to knobs.
IMO the Rigol+Saleae still makes good sense -- more memory, more waveform/s, more bandwidth if you hack it, more decodes and more memory in the Saleae. But it's not the no-brainer of a $400 DS1054 vs a $1.5k Tek.
Hmm, how about a DSOX3014A for 1700 from Keysight? Easy to enable everything for the most part. If you wait for Keysight to list one on ebay you can get a deal.
Hmm, how about a DSOX3014A for 1700 from Keysight? Easy to enable everything for the most part. If you wait for Keysight to list one on ebay you can get a deal.
100Mhz is'nt enough bw for me.. I need to do ethernet eye diagrams.. so minium 200Mhz. ideally more.
Because Real Men only need one and a half harmonic ::)
Seriously, though, it sounds like the DS4k is the appropriate choice here. 500MHz gets you 4+ harmonics rather than 1+ and deep memory isn't going to hurt for looking at packets and/or sticking them in segmented memory.
Here's my silly "upgrade" to my MSO4014, inspired by another thread...
;D
Thank you for the closeup picture of the FPGA. Looks like they are using the larger FFG676 package with more IO.
So it would be this one for $287.50 each
http://www.digikey.com/product-detail/en/xilinx-inc/XC5VLX30-1FFG676C/122-1559-ND/1768319 (http://www.digikey.com/product-detail/en/xilinx-inc/XC5VLX30-1FFG676C/122-1559-ND/1768319)
Andrew - a reset using the front panel keys only resets the current configuration stored in FRAM. To remove keys you have to use the SCPI command to uninstall them. Do some searching for scpi uninstall here and you should be able to find it.
I got curious so I tried all the codes for the second position (Rx39), below are the results. Also noticed in the key entry options setup page that the 0, 1, I, and O keys are missing, so I wasn't able to test those combinations. Another interesting thing I found was that after I entered in 32 keys the system wouldn't let me enter in anymore, when I pressed the apply button noting happened. I tried uninstalling the keys but that still wouldn't let me enter more keys, I ended up having to do a factory reset before it would start accepting more keys.
The Emona site shows a 18.5% (2779/3410) difference in price between DS4014 and DS4014E ...
I don't know why anyone would choose the E model for 18% ...
I wouldn't bet on it. The DS4000 uses expensive chips, and halving sample rate + waveform rate could save them significant BOM cost. My money would be on finding the same board and layout in the DS4000E but with two ADCs and two Virtex 5s missing.
DS4000:
4x ADC08D1000 (2GS*4 or 4GS*2): $1360 on mouser, $800 on taobao
5x XC5VLX30-1FFG324C: $1300 on digikey
I ended up selling the four RP3500A probes that came with my DS4014 for around $100 each, reducing the cost of my DS4014 by $400. I didn't like the readout pin that scratches the crap out of the scope anyway.Wow $100 each! I always thought the price was set to make it look as though you were getting a valuable freebie with a scope. They are a very basic probe and in the case of mine poorly made.
What type of activities are done in hardware in the DS/MSO4000 series?
I assume the same counts for the triggering in the logic analyzer.
I think triggering is analog and is done in hardware. They have huge ASICs on the front end and they manage to produce "trigger out" almost immediately after the trigger occurs.
I meant triggering in the logic analyzer on a pattern. Pattern triggering in the LA must be done in software, as it creates more flexibility. Or would they really cover all these combinations in hardware?
Irritations
...
2) Fan noise. As usual on a Rigol.
The PC software. I am staggered that Rigol can get away with something this mind blowingly awful. My first Rigol, an entry level DS1022CD, had Ultravision s/w while this was pretty limited I assumed my MSO4014 would come with something better. How wrong could I have been. It was so much worse!I agree; the software is not great. The user marmad was creating a software to interact with the DS4000 series. I can't find the thread (nor used it)
1) The power switch on the front panel does not switch the power off it just shuts down the software. This leaves the MSO taking enough power to make it warm to the touch. The true power switch is on the back inconvieniently situated under the mains input socket. In practical terms this is unusable so you are left with the wall socket.I don't quite like this as well, but unfortunately these days many different brands and models of test gear are doing the same.
The noise itself does not bother me, but the DS4014 has a Delta fan that has survived well the test of time. I replaced it with a slightly more silent fan (also from Delta) and added rubber bumpers to reduce vibration.Irritations
...
2) Fan noise. As usual on a Rigol.
While the fan noise can be an irritation, at least Rigol uses very good fans (assuming they're consistent on this). The DS1054Z apparently comes with the Sunon ME50151V3-000C-A99, which uses magnetic levitation bearings. These will have a longer life than anything else, all else being equal.
In contrast, my Siglent SDG1025 comes with a crap Chinese fan that started to make groaning noises less than 2 years into its life. I can't be bothered to send the unit in for fan replacement since they're likely to simply replace it with another crap fan that will exhibit similar behavior after the warranty has expired, and the shipping costs would exceed the price of a good replacement fan.
I agree; the software is not great. The user marmad was creating a software to interact with the DS4000 series. I can't find the thread (nor used it)
The noise itself does not bother me, but the DS4014 has a Delta fan that has survived well the test of time. I replaced it with a slightly more silent fan (also from Delta) and added rubber bumpers to reduce vibration.The fans in my Rigols have proved completely reliable. I will wait until the warranty is up before going inside. In the past I have found that a small movement of a fan inside an instrument can have a dramatic effect on noise level. Its all about reducing turbulence. I don't know if the same trick can be pulled on the Rigol but I may give it a go.
Regardless, the largest part of the noise comes from the air flowing inside the case and not from the fan itself - it is hard to change this.
After I wrote my post earlier this morning I thought the exact same thing you mentioned above; when I replaced the fan I also added quite a number of heatsinks to the oscilloscope (absolutely necessary in my case), which surely increased the turbulence by quite a factor. Despite this, the noise level decreased in a small part due to the fan and (I believe) in greater part because of the rubber bumpers.The noise itself does not bother me, but the DS4014 has a Delta fan that has survived well the test of time. I replaced it with a slightly more silent fan (also from Delta) and added rubber bumpers to reduce vibration.The fans in my Rigols have proved completely reliable. I will wait until the warranty is up before going inside. In the past I have found that a small movement of a fan inside an instrument can have a dramatic effect on noise level. Its all about reducing turbulence. I don't know if the same trick can be pulled on the Rigol but I may give it a go.
Regardless, the largest part of the noise comes from the air flowing inside the case and not from the fan itself - it is hard to change this.
What is the status on unlocking bandwidth/features with the MSO4000 series. I recall that the riglol worked for the DS4K series, but I can't recall if something different had to be done with the MSO4K.
So I put in the latest firmware I could get (00.02.03.02.00) and it went fine.I came here looking for comments regarding the latest DS4000 series firmware. Sounds like it's working well for you. I've downloaded the file, just don't want to rediscover that it has problems. Anyone else have comments regarding what appears to be the latest DS4000 firmware, "DS4_FW_Update_v00_02_03_00_03.zip"?