You won't be making a mistake with the 1054Z. If it comes from current inventory, it will have the latest firmware 00.04.04.SP1. To the best of my knowledge, all bugs have been eliminated EXCEPT for a spelling error "Pluses" where it should be "Pulses". I can live with it...
I would suggest you read this thread only as far back as Nov 2016. That was when the lastest firmware was released. Issues with firmware older than that seem to have been fixed. Who really cares about issues at the margins way back when the scope was first introduced? They have been fixed.
There are alternatives, of course. The thing is, they cost a lot more money.
As boring as it seems, do try to read the User Manual. These is a lot of capability in the scope that you just won't find unless you read about it first. It has a lot more capability than just displaying wiggly lines.
In fact, you can download and read the manual while you wait for your scope to arrive. At least skim over it and see what it can do. You can get down to button-pushing when the scope arrives.
Possible PEBCAK error. Probably no defective scope. Recommendation: RTFM.
BTW: The scope reacts in this case when the trigger condition on channel 1 is matched (even when the channel 1 is deactivated). Then it shows the signal of channel 4.
Please look in your manual about:
Trigger- source (to a channel)
Trigger- modes: Auto, normal and single.
Manual DS1054Z Download as Pdf.
Note that the scope is in "AUTO" trigger mode. It should be showing a trace on any active channel, regardless of whether it is triggered or not, regardless of whether a trigger condition is met on the Trigger channel or not.
I think we need a little more information, but at first glance there does seem to be something wrong (possibly in addition to PEBCAK.)
See here: (no inputs to any channels, but since scope is in AUTO trigger mode, the active CH4 shows a trace -- as expected. When scope is in Normal trigger mode, no trace appears since it is WAITing for a trigger event on the trigger channel.)
Note that the scope is in "AUTO" trigger mode. It should be showing a trace on any active channel, regardless of whether it is triggered or not, regardless of whether a trigger condition is met on the Trigger channel or not.
I think we need a little more information, but at first glance there does seem to be something wrong (possibly in addition to PEBCAK.)
See here: (no inputs to any channels, but since scope is in AUTO trigger mode, the active CH4 shows a trace -- as expected. When scope is in Normal trigger mode, no trace appears since it is WAITing for a trigger event on the trigger channel.)
With this settings the oscilloscope should draw the trace.
I am not be able to reproduce the failure.
Oddly, the Tektronix DSO training material may provide the answer: Use the Auto button! Yup! Right from the factories mouth (ok, text editor), use the Autoset button Step 3 of first project. I assume Tek Autoset == Rigol Auto
http://www.tek.com/sites/tek.com/files/courseware/ST_Arduino_Labs_Combined.pdf
Then consider AC coupling and see if that doesn't work a little better.
To the best of my knowledge, all bugs have been eliminated EXCEPT for a spelling error "Pluses" where it should be "Pulses".
1054Z is also faster and has more memory, but I am worried about the software bugs with 1054Z.
With this settings the oscilloscope should draw the trace.
I am not be able to reproduce the failure.Unless the waveform DC offset placed the waveform off the display.
I recently bought a ds1054z and most of the time the trace disappears from the screen. Is this a known bug or have I got a defective unit? btw does Tequipment pay for shipping a defective unit back to them or do I have to pay for it?
Oddly, the Tektronix DSO training material may provide the answer: Use the Auto button! Yup! Right from the factories mouth (ok, text editor), use the Autoset button Step 3 of first project. I assume Tek Autoset == Rigol Auto
http://www.tek.com/sites/tek.com/files/courseware/ST_Arduino_Labs_Combined.pdf
Then consider AC coupling and see if that doesn't work a little better.
1054Z is also faster and has more memory, but I am worried about the software bugs with 1054Z.
And ... let's have a big round of applause for all the people who post endlessly about (mostly minor/unimportant) bugs in the DS1054Z. You've got people buying DS1102Es instead of DS1054Zs.
1054Z is also faster and has more memory, but I am worried about the software bugs with 1054Z.
And ... let's have a big round of applause for all the people who post endlessly about (mostly minor/unimportant) bugs in the DS1054Z. You've got people buying DS1102Es instead of DS1054Zs.
Please post links to where "people" have bought 1102E instead of 1054z due to "minor/unimportant" bugs that have been reported here.
The big "AUTO" button... If the indicator says "Auto" there should be a trace regardless of whether a trigger event is detected on the trigger channel.
The big "AUTO" button... If the indicator says "Auto" there should be a trace regardless of whether a trigger event is detected on the trigger channel.
I noticed the Auto indicator is not lit up. Is there some way to get the scope trigger to be in AUTO mode, but not active? I sort of recall something like that after pushing the single auto buttons, but I do not recall if it said stop or wait... Anyway, AUTO was not lit...
1054Z is also faster and has more memory, but I am worried about the software bugs with 1054Z.
And ... let's have a big round of applause for all the people who post endlessly about (mostly minor/unimportant) bugs in the DS1054Z. You've got people buying DS1102Es instead of DS1054Zs.
Please post links to where "people" have bought 1102E instead of 1054z due to "minor/unimportant" bugs that have been reported here.
One of the posters was considering the E just because of reading all the Z bugs, just a few posts up...
That post refers to the DS1052E, not the DS1102E. But the point still stands: Please post links to where "people" have actually purchased either of those two channel scopes _instead_ of a DS1054Z due to the "minor/unimportant" bugs that have been reported here.
The big "AUTO" button... If the indicator says "Auto" there should be a trace regardless of whether a trigger event is detected on the trigger channel.
I noticed the Auto indicator is not lit up. Is there some way to get the scope trigger to be in AUTO mode, but not active? I sort of recall something like that after pushing the single auto buttons, but I do not recall if it said stop or wait... Anyway, AUTO was not lit...
That post refers to the DS1052E, not the DS1102E. But the point still stands: Please post links to where "people" have actually purchased either of those two channel scopes _instead_ of a DS1054Z due to the "minor/unimportant" bugs that have been reported here.
And if we can't, you 'win'?
We've got one guy debating whether to get a DS1052E instead of a DS1054Z because of what he's been reading. I've bene called all sorts of names for defending Rigol here but this is 100% proof of the real reason why I do it.
a) The bugs are minor, most of them took about six months before anybody even noticed them.
b) The difference between a hobbyist owning a DS1054Z and not owning one is about ten parsecs wide.
c) The difference between owning a DS1054Z and owning an equivalent-feature 'scope with no spelling mistakes in the menus is about this ->.<- much... but you have to pay two or three times the price for that.
1054Z is also faster and has more memory, but I am worried about the software bugs with 1054Z.
And ... let's have a big round of applause for all the people who post endlessly about (mostly minor/unimportant) bugs in the DS1054Z. You've got people buying DS1102Es instead of DS1054Zs.
Please post links to where "people" have bought 1102E instead of 1054z due to "minor/unimportant" bugs that have been reported here.
One of the posters was considering the E just because of reading all the Z bugs, just a few posts up...
That post refers to the DS1052E, not the DS1102E. But the point still stands: Please post links to where "people" have actually purchased either of those two channel scopes _instead_ of a DS1054Z due to the "minor/unimportant" bugs that have been reported here.
Should I buy DS1052E or DS1054Z ?
Price is almost the same.
1054Z is also faster and has more memory, but I am worried about the software bugs with 1054Z.
Thank you very much. So am not gonna make a mistake buying a 1054Z instead of 1052E ?
My budget is max 500$, so high end devices are for now out of question.
Any consumer item at whatever price point should do what it says it will do in the specifications. Perhaps you yourself never encountered the bugs because all you need a scope to do is to show some wiggly colored lines. Other users may expect more -- like they might expect the scope to do what it is supposed to do, without freezing, giving incorrect RMS measurements, having all measurements stop working, miscounting "pluses" or any of the other "minor bugs" that have been noted over time.
"It's only 400 dollars, what do you expect" gets kind of old after a while.
b) The difference between a hobbyist owning a DS1054Z and not owning one is about ten parsecs wide.
c) The difference between owning a DS1054Z and owning an equivalent-feature 'scope with no spelling mistakes in the menus is about this ->.<- much... but you have to pay two or three times the price for that.
Any consumer item at whatever price point should do what it says it will do in the specifications.
Perhaps you yourself never encountered the bugs because all you need a scope to do is to show some wiggly colored lines. Other users may expect more -- like they might expect the scope to do what it is supposed to do, without freezing,
giving incorrect RMS measurements, having all measurements stop working, miscounting "pluses" or any of the other "minor bugs" that have been noted over time.
"It's only 400 dollars, what do you expect" gets kind of old after a while.
Any consumer item at whatever price point should do what it says it will do in the specifications.