Read my post on this.
What is full line to you? How it is defined?
"message" as you call it is application level concept. Scope looks at electrical level there is no application protocol parser in it.
It would be sufficient, to just have the quick button change format. But one thing that would really be helpful, is, having a complete packet of values/characters shown on one line UART I2C or else it would apply (less columns that would mean - for this option).
Read my post on this.
What is full line to you? How it is defined?
"message" as you call it is application level concept. Scope looks at electrical level there is no application protocol parser in it.
Please add to bug list:
Sequence is restart when menus are opened and closed (Either by hand or automatically).
It should be easy to reproduce. If not, send me a pm, and i put my setupfile in here.
Read my post on this.
What is full line to you? How it is defined?
"message" as you call it is application level concept. Scope looks at electrical level there is no application protocol parser in it.
Which post? Links would help a lot.
What "full line"? Cant remember/find having used these words.
Where did i mention "message"
I would count the decode feature as an application protcol parser.
Please add to bug list:
Sequence is restart when menus are opened and closed (Either by hand or automatically).
It should be easy to reproduce. If not, send me a pm, and i put my setupfile in here.
No, I can't reproduce this. I can open and close menus at my heart's content and the sequence keeps acquiring. Only if I change something in a menu which affects acquisition, the sequence will restart -- as it should in that case, I think.
Please be specific about the steps you take, and which menu(s) you are opening, and maybe share your setup.
Please add to bug list:
Sequence is restart when menus are opened and closed (Either by hand or automatically).
It should be easy to reproduce. If not, send me a pm, and i put my setupfile in here.
No, I can't reproduce this. I can open and close menus at my heart's content and the sequence keeps acquiring. Only if I change something in a menu which affects acquisition, the sequence will restart -- as it should in that case, I think.
Please be specific about the steps you take, and which menu(s) you are opening, and maybe share your setup.
Because the menu is in embedded mode, closing the menu will affect waveform acquisition.
Read my post on this.
What is full line to you? How it is defined?
"message" as you call it is application level concept. Scope looks at electrical level there is no application protocol parser in it.
Which post? Links would help a lot.
What "full line"? Cant remember/find having used these words.
Where did i mention "message"
I would count the decode feature as an application protcol parser.
My post few posts above.
https://www.eevblog.com/forum/testgear/sds800x-hd-bugswanted-features/msg5426231/#msg5426231
You used words, and I quote "having a complete packet of values/characters shown on one line".
So my question was how do you define what you define as one complete line of yours? One message? Simple question, really.
And you can count anything as anything but that won't change how industry defines things for 30+ years.
Scope decode is electric level decoder of voltage levels to binary values. Since some protocols have address, or CRC or something defined on wire level that gets decoded.
On UART, full data packet is single 7/8 bit serially encoded binary value. There are start/stop bits and optional parity bits.
There is no interpretation of data whatsoever.
Even option to display value as anything more than binary number, like hex or ASCII is already additional interpretation of data added
to ease reading.
Because the menu is in embedded mode, closing the menu will affect waveform acquisition.
Please add to bug list:
Sequence is restart when menus are opened and closed (Either by hand or automatically).
It should be easy to reproduce. If not, send me a pm, and i put my setupfile in here.
No, I can't reproduce this. I can open and close menus at my heart's content and the sequence keeps acquiring. Only if I change something in a menu which affects acquisition, the sequence will restart -- as it should in that case, I think.
Please be specific about the steps you take, and which menu(s) you are opening, and maybe share your setup.
Because the menu is in embedded mode, closing the menu will affect waveform acquisition.
Could you please explain this?
Please add to bug list:
Sequence is restart when menus are opened and closed (Either by hand or automatically).
It should be easy to reproduce. If not, send me a pm, and i put my setupfile in here.
No, I can't reproduce this. I can open and close menus at my heart's content and the sequence keeps acquiring. Only if I change something in a menu which affects acquisition, the sequence will restart -- as it should in that case, I think.
Please be specific about the steps you take, and which menu(s) you are opening, and maybe share your setup.
Because the menu is in embedded mode, closing the menu will affect waveform acquisition.
Could you please explain this?I'll check it again
Read my post on this.
What is full line to you? How it is defined?
"message" as you call it is application level concept. Scope looks at electrical level there is no application protocol parser in it.
Which post? Links would help a lot.
What "full line"? Cant remember/find having used these words.
Where did i mention "message"
I would count the decode feature as an application protcol parser.
My post few posts above.
https://www.eevblog.com/forum/testgear/sds800x-hd-bugswanted-features/msg5426231/#msg5426231
You used words, and I quote "having a complete packet of values/characters shown on one line".
So my question was how do you define what you define as one complete line of yours? One message? Simple question, really.
And you can count anything as anything but that won't change how industry defines things for 30+ years.
Scope decode is electric level decoder of voltage levels to binary values. Since some protocols have address, or CRC or something defined on wire level that gets decoded.
On UART, full data packet is single 7/8 bit serially encoded binary value. There are start/stop bits and optional parity bits.
There is no interpretation of data whatsoever.
Even option to display value as anything more than binary number, like hex or ASCII is already additional interpretation of data added
to ease reading.
He probably wants the effect of RTB2004.
https://www.eevblog.com/forum/testgear/sds800x-hd-bugswanted-features/msg5413091/#msg5413091
Please add to bug list:
Sequence is restart when menus are opened and closed (Either by hand or automatically).
It should be easy to reproduce. If not, send me a pm, and i put my setupfile in here.
No, I can't reproduce this. I can open and close menus at my heart's content and the sequence keeps acquiring. Only if I change something in a menu which affects acquisition, the sequence will restart -- as it should in that case, I think.
Please be specific about the steps you take, and which menu(s) you are opening, and maybe share your setup.
Because the menu is in embedded mode, closing the menu will affect waveform acquisition.
Could you please explain this?I'll check it again
I can reproduce this phenomenon
1. Open sequence
2. Menu mode selection embedded
3. Open measurement
4. On/off menu, the sequence will be restart
I can reproduce this phenomenon
1. Open sequence
2. Menu mode selection embedded
3. Open measurement
4. On/off menu, the sequence will be restart
For me, this only restarts the sequence the first time you open the measurement menu (i.e. when it also switches measurements ON at that time). I then can close and re-open that menu (or other menus) without restarting the sequence.
I would not consider that a bug. Switching on measurements is actually a change to the acquisition, so it makes sense to me that it restarts the sequence.
You can set the sequence frame higher, such as 1000(Convenient observation), and then click on the menu title area in the upper right corner to switch the menu on and off.
But maybe the option to specify a timeout duration would be useful? I.e. if bytes follow each other with less than the timeout interval inbetween, group them into a single line in the message list;
Happens at mine when open/closing decode, aquire, measure, cursor... (Havent tried any more)
BTW:
i added the setupfile for the sequence bug. In the original post.
But maybe the option to specify a timeout duration would be useful? I.e. if bytes follow each other with less than the timeout interval inbetween, group them into a single line in the message list;
That is what i call a packet, a packet consisting of closely following bytes.
But when this would be implemented, it could then also be implemented to SPI and I2C?
Please do not talk about terminology anymore here. Use PM or something. This is topic is getting loaded with too much . And if some use the wrong words when quoting others, it gets really messy. My head is already spinning with my prototype and these bugs.
BTW:
i added the setupfile for the sequence bug.
Happens at mine when open/closing decode, aquire, measure, cursor... (Havent tried any more)
BTW:
i added the setupfile for the sequence bug. In the original post.
good, Added to bug No.12
Happens at mine when open/closing decode, aquire, measure, cursor... (Havent tried any more)
BTW:
i added the setupfile for the sequence bug. In the original post.
good, Added to bug No.12Ok, I could now reproduce it too, starting with eTobey's setup. And it does indeed depend on embedded vs. floating menu style -- only opening/closing embedded menus will restart a sequence. This detail should be added to the bug report to make sure the problem can be reproduced and located.