Any good (and working) site to generate the keys to unlock all features?
Give it a good workout first... all features are working anyway (except 100MHz).
Calibration date sheet (certificate of calibration): 25-dec-2015 ....(working at xmas???)
Att
Christmas isn't a holiday in China.
McBryce.
I know kkkk. ..but it is strage ins´t? i was with my family eating the xmas dinner...and someone in the other side of the world was at his job calibrating a oscilloscope... a world with many cultures...nice!
Yeah, but looking from their side... You were probably working while they were off celebrating their new year, which was the 8th of February for us (and next year it's on the 28th of January, figure that one out!) and it was the start of year 4713!). Their leap year is also next year, not this year?
McBryce.
a "world" with many cultures...nice!
there are "countries" with many cultures. and each culture's holiday is the nation's holiday. isnt it nice? or nicer? or not?
Why?
Samsung remote control (38KHZ)
1 - Tektronix TBS 1072B-EDU - triggering the signal with no problems.
2- My Brand new, out of the box Rigol can´t trigger? Why?
What am i doing wrong?
Any help, or this is a DS1054Z triggering Flaw?
UPDATE: After changing the memory depth to 24Mpoints it triggered! But, in about 35 hrs of use, trial will be gone letting me with just 12Mpoints max...
It is not visible clearly with the time resolution you chose on the scope screen, but I would assume that there always is a rising edge of the signal at the trigger timepoint (towards the left of the screen). I.e. the scope triggers as you asked it to do. But the IR signal is a complex pattern, and you have done nothing in your trigger settings to ensure that you always trigger on the same edge within the signal packet.
You will need to set a hold-off time, or e.g. set a trigger that becomes active at the end of a long high pulse (with a duration close to duration of the gap between two packets). Your Rigol scope can do that nicely.
The Tek scope probably has a slower waveform update rate, which causes the scope to be ready for the next sweep just in time for the next IR packet repeat. Increasing the memory size on the Rigol has a similar effect, I assume. But the match in times is just a coincidence; it is not the "proper" way to get a stable signal displayed. A suitable trigger setting as mentioned above is the way to go.
It would probably make more sense to trigger on a pulse width of that longer high value at the beginning of the trace.
Also, there is an easy solution for 24M points going away
It would probably make more sense to trigger on a pulse width of that longer high value at the beginning of the trace.
Yes, that's what I said (or meant to say) in my second paragraph.
Also, there is an easy solution for 24M points going away
The same easy solution might also be required to retain the advanced triggering capabilities
It would probably make more sense to trigger on a pulse width of that longer high value at the beginning of the trace.
Yes, that's what I said (or meant to say) in my second paragraph.
Also, there is an easy solution for 24M points going away
The same easy solution might also be required to retain the advanced triggering capabilities
After setting 24MPTS it triggered. But just at 10ms horiz.
https://youtu.be/YlqafSK8jds
After setting 24MPTS it triggered. But just at 10ms horiz.
That's just a coincidence. You slowed down your scope to the point where period of sampling and period of signal line up for good triggering. It has nothing to do with 24 Mpts specifically and it is not a universal solution, it will fail on some other signal.
Use triggering on pulse with or some other feature for complex signals. That's why all those advanced triggering things are there.
After setting 24MPTS it triggered. But just at 10ms horiz.
That's just a coincidence. You slowed down your scope to the point where period of sampling and period of signal line up for good triggering. It has nothing to do with 24 Mpts specifically and it is not a universal solution, it will fail on some other signal.
Use triggering on pulse with or some other feature for complex signals. That's why all those advanced triggering things are there.
Didn´t worked none of them so far...i´ll investigate more...and explore more triggering options..thks...
Hi!
It looks like the rigol is triggering just fine, but it's doing it a lot faster than the Tek and so it catches all the edges, not just the first. The Tek is set at 10m/div and the Rigol is at 5 - that may make a difference.
If you set your holdoff time to > ~100ms it should only trigger at the beginning of the packet. TriggerMenu->Setting->Holdoff
--
Mihai
Hi!
It looks like the rigol is triggering just fine, but it's doing it a lot faster than the Tek and so it catches all the edges, not just the first. The Tek is set at 10m/div and the Rigol is at 5 - that may make a difference.
If you set your holdoff time to > ~100ms it should only trigger at the beginning of the packet. TriggerMenu->Setting->Holdoff
--
Mihai
It worked set the holdoff to 100ms...but i´ve tried three times before get working...Thks..used to tektronix...now learning some new trick on this new one...thks again
Looks like it's triggering perfectly to me.
ie. There's always a rising edge under the orange marker labelled with a 'T'
You should be able to get it to trigger properly (that is, as you expect on the first pulse in the repeating pulse train) using either Pulse or Nth (edge) triggering, with the proper other sub-settings for either type.
Looks like it's triggering perfectly to me.
ie. There's always a rising edge under the orange marker labelled with a 'T'
Yes u´re right. Maybe i used the wrong term. It is
T´D, but the waveform is not stable to read...it keeps running on the screen... The trigger is at that position so i can see the hole waveform packet.
Look the latest video...that´s what i want..tks..
Looks like it's triggering perfectly to me.
ie. There's always a rising edge under the orange marker labelled with a 'T'
Yes u´re right. Maybe i used the wrong term. It is T´D, but the waveform is not stable to read...it keeps running on the screen... Look the latest video...that´s what i want..tks..
The Tek got
lucky in that its memory holds a nice multiple of that particular signal. That means it always triggers in the roughly the same place in the burst of pulses. It probably wouldn't lock with a slightly longer/shorter signal.
If you want the Rigol to lock then you can use the "timeout trigger" to look for the gap between bursts of signal.
Try "Nth" trigger, set "Edge" to 1 and "Idle" to a value just greater than the duration of the entire pulse train. (Looks like 85-90 ms would be good. Press the multifunction knob to get the setting keyboard, rather than just turning the knob to get the 85-90 ms Idle time. Leave Trigger Holdoff set to minimum value.)
How many more times do we want to ask and answer that same question today?
How many more times do we want to ask and answer that same question today?
What do you expect... it's only 400 dollars!
How many more times do we want to ask and answer that same question today?
As many times as it takes for the person who asked the question to fully understand the problem and the solution. Isn't that what Forums like this are for?
McBryce.
Isn't that what Forums like this are for?
It is. Don't get stressed. It was just a remark.
Isn't that what Forums like this are for?
It is. Don't get stressed. It was just a remark.
Sorry, forgot the smiley, not stressed at all here
Bryce.