Products > Test Equipment

Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)

<< < (24/74) > >>

Karel:

--- Quote from: pascal_sweden on May 14, 2017, 05:04:26 pm ---Who is actually communicating all these bugs to Rigol? Or is there a Rigol application engineer on this forum?

--- End quote ---

A couple of forum members have reported most of the bugs.

To my knowledge, no Rigol representative visits this forum.
If they do, they do it quietly.

Fungus:

--- Quote from: Karel on May 14, 2017, 04:34:28 pm ---I have read the manual and it's not correct behaviour. Thank you very much.

Instead of showing me a screenshot of a part of the manual that I have already read for three times, you could maybe offer
some arguments or reasoning why you think it is correct.


The maximum number of frames recorded is 5.

The maximum number of frames to be played back is set to 3.

The query to maximum number of frames that can be played back should be the number of recorded frames: 5.

The query to maximum number frames set to playback is 3.


--- Quote ---:FUNCtion:WREPlay:FMAX?
Description Query the maximum number of frames can be played, namely the maximum number of frames recorded.

--- End quote ---

When you set the end frame for playback, you don't change the number of recorded frames.

--- End quote ---

My "argument" is that on the very next line of the manual, under the one you're throwing around, it says this:


--- Code: ---Use the :FUNCtion:WRECord:FEND command to set the maximum number of frames
recorded.
--- End code ---

So yes, it does change the number of recorded frames.

You may not like the function, but it's not a bug.  :popcorn:

PS: You can play back a subset of frames using the ":FUNCtion:WREPlay:FCURrent" function, or just start playing and monitor the current position.

Karel:
I'm not talking about :FUNCtion:WRECord:FEND.

I'm talking about :FUNCtion:WREPlay:FMAX

Changing the setting for :FUNCtion:WREPlay:FMAX has nothing todo with :FUNCtion:WRECord:FEND.

Recording and playback are two completely different things. Once you have recorded some frames (5 in the xample),
you can playback them, either all five or just one or only frame 2 to 4. This does not affect the number of frames stored in memory.

After playback has finished, you can playback again the same frames or set other values for the number of frames to playback.
Again, as long as you don't record again, the number of recorded frames stays the same.

What's so difficult  to understand about this?

kcbrown:

--- Quote from: Karel on May 14, 2017, 06:16:17 pm ---I'm not talking about :FUNCtion:WRECord:FEND.

I'm talking about :FUNCtion:WREPlay:FMAX

Changing the setting for :FUNCtion:WREPlay:FMAX has nothing todo with :FUNCtion:WRECord:FEND.

--- End quote ---

The documentation clearly claims otherwise.



--- Quote ---Recording and playback are two completely different things. Once you have recorded some frames (5 in the xample),
you can playback them, either all five or just one or only frame 2 to 4. This does not affect the number of frames stored in memory.

After playback has finished, you can playback again the same frames or set other values for the number of frames to playback.
Again, as long as you don't record again, the number of recorded frames stays the same.

What's so difficult  to understand about this?

--- End quote ---

If the documentation says that "function A reads value X, and function B sets value X", then how is it a bug when your use of B results in A reporting the value that you handed to B?

Karel:

--- Quote from: kcbrown on May 14, 2017, 08:42:27 pm ---
--- Quote from: Karel on May 14, 2017, 06:16:17 pm ---I'm not talking about :FUNCtion:WRECord:FEND.

I'm talking about :FUNCtion:WREPlay:FMAX

Changing the setting for :FUNCtion:WREPlay:FMAX has nothing todo with :FUNCtion:WRECord:FEND.

--- End quote ---

The documentation clearly claims otherwise.

--- End quote ---

No, it doesn't. Please show me where it does.


--- Quote from: kcbrown on May 14, 2017, 08:42:27 pm ---
--- Quote ---Recording and playback are two completely different things. Once you have recorded some frames (5 in the xample),
you can playback them, either all five or just one or only frame 2 to 4. This does not affect the number of frames stored in memory.

After playback has finished, you can playback again the same frames or set other values for the number of frames to playback.
Again, as long as you don't record again, the number of recorded frames stays the same.

What's so difficult  to understand about this?

--- End quote ---

If the documentation says that "function A reads value X, and function B sets value X", then how is it a bug when your use of B results in A reporting the value that you handed to B?

--- End quote ---

It doesn't. The documentation says  that "function A reads value X, and function B sets value Y".

:FUNCtion:WRECord:FEND sets or contains the number of recorded (or to be recorded) frames in memory.

Let's say, we set this value to 5. After that we start a recording. After the recording has finished, the memory contains 5 frames.

Now we can set the range of frames we want to playback by setting the start frame and the stop frame.
For that we use the commands :FUNCtion:WREPlay:FSTart and :FUNCtion:WREPlay:FEND.
Setting those commands does not alter the settings for recording.
We can playback as many times we want. We can also change the range of frames that we want to playback.
That doesn't alter the content of the memory as long as we don't start a new recording.
The maximum frame number for playback must be less than, or equal to, the max number of frames in memory.

The command :FUNCtion:WREPlay:FMAX tells us what is the maximum frame number we select for playback.
Obviously, the maximum frame number for playback must be less than, or equal to, the max number of frames in memory:

"Syntax :FUNCtion:WREPlay:FMAX?

Description Query the maximum number of frames can be played, namely the maximum number of frames recorded."

That's clear, the command returns the maximum frame number we set for the range of frames we want to playback.
Ofcourse that number can not be more than the number of frames in memory.

"Explanation Use the :FUNCtion:WRECord:FEND command to set the maximum number of frames recorded."

That's also clear. We have used this command before starting the recording in order to set the number of frames that must be
recorded.

Initially, when using the command :FUNCtion:WREPlay:FMAX? it tells us the correct maximum: the number of frames in memory.

Now let's say you use the command :FUNCtion:WREPlay:FEND to define the end frame for the range of frames to be played back,
and set it to a lower number.
When playing back again, the number of frames being played back are adjusted accordingly.

So far so good. Now use the command :FUNCtion:WREPlay:FMAX? again. Now it shows a lower number!
Somehow magically the number of frames in memory have been lowered! (Which isn't true by the way)

:FUNCtion:WREPlay:FEND != :FUNCtion:WRECord:FEND  !!

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod