| ... | ... | @@ -291,17 +291,23 @@ front-end hardware version of the OpenLab oscilloscope. This message is also use |
|
|
|
identify the device as a FPGA-based oscilloscope. This is necessary for calibrating some
|
|
|
|
functions of the GUI.
|
|
|
|
|
|
|
|
{empty} +
|
|
|
|
|
|
|
|
* REPLY_SWV
|
|
|
|
|
|
|
|
This state is similar to the REPLY_HWV state. The only difference is that the current
|
|
|
|
version number of the FPGA design is sent instead of the hardware version.
|
|
|
|
|
|
|
|
{empty} +
|
|
|
|
|
|
|
|
* ACK
|
|
|
|
|
|
|
|
The ACK state is reached every time a command of the OpenLab protocol needs confirmation.
|
|
|
|
For example, if parameters of the trigger settings or channel settings are changed.
|
|
|
|
After complete execution of this state, the next state will be the IDLE state.
|
|
|
|
|
|
|
|
{empty} +
|
|
|
|
|
|
|
|
* NACK
|
|
|
|
|
|
|
|
This state is reached if a received command cannot be further processed by the FPGA.
|
| ... | ... | @@ -309,6 +315,7 @@ The NACK state will be activated if a header or payload CRC error occurred. This |
|
|
|
also the case if a not supported or unknown command was sent by the GUI. The NACK
|
|
|
|
message also includes an error code which helps to identify the cause of the problem.
|
|
|
|
|
|
|
|
{empty} +
|
|
|
|
|
|
|
|
|
|
|
|
== https://es.technikum-wien.at/openlab/openlab_wiki/wikis/home[Home] | https://es.technikum-wien.at/openlab/openlab_wiki/wikis/board_TIVAC[<Microcontroller-based TIVAC] | https://es.technikum-wien.at/openlab/openlab_wiki/wikis/sig_proc_osci_hardware[Signal Processing Front-End (XMC,TIVAC,DE0-Oscilloscope)>] |
