How to use the CubeMonitor in snapshot mode without trigger supported?

[SZENG.1]

I instrumented the code with the supplied code, and it works fine in STM Studio, but when used in CubeMonitor, after started, the dashbord just displays 'Acquisition started, waiting for value'. I've checked the data flow from STLink and found that only 'x' value present in the data payload, but without 'y' value.

Is there a way to trigger the data sample manually? Or supporting trigger is mandatory in snapshot mode?

[Landry]

Dear SZENG.1,

Did you configure the node "variables" as expected ?

You have to :

-> select your monitored variables from the executable file

->select the snapshot mode (and verify that header address is detected )

-> select ( if you need it, it's not mandatory) a trigger variable and additional parameters of triggering ( value and start mode ).

Please come back to me if it's still not working.

Landry

[SZENG.1]

Hi Landry,

Here is the situation:

The trigger function in the firmware code is not enabled, as it's not required and for saving RAM and ROM space;

The variables should have been configured correctly:

If the trigger is selected as 'off' like above, ​after clicked 'Start', the dashboard just shows 'waiting for value:

While, if trigger has been selected other than 'off' like below:

the acq in & out will show an error after started:

[Landry]

-Your node "variables" configuration is correct .

-In snapshot mode, the first point sent ( to set the first timestamp ) is an x only value, so this is also correct.( it means that the start is taking into account ).

-When you don't manage the trigger mode in your embedded application , the message "The trigger mode is not supported" is also correct.

So everything seems ok on CubeMonitor side.

Can you link the error output of your "acquisition in" node to debug node to see if you have some messages available ?

thank you

[Christophe]

Hi SZENG.1,

The acquisition doesn’t start because you embedded application you are using (dataAcq files) was modified. The Size of buffer is defined with the formula: #define SNP_TRC_BUFFER_SIZE (50*(SNP_TRC_NB_MAX_WORD_VAR+1)) and unfortunatly Stm32cubemonitor doesn't allow modification on it. If the default buffer size is not enough large, I advice the increase the parameter SNP_TRC_NB_MAX_WORD_VAR (defined at 10 by default).

[Mbert.1]

hi, my goal is to verify a variable named "b" which is increased up to 1000 and then reset to zero, the increase takes place via an interrupt that is generated every 100 ns and check on CubeMonitor in snapshot mode the value of the variable. Inside the installation folder of the CubeMonitor program I found the dataAcq.c and dataAcq.h files. Inside the dataAcq.c file I found that I had to set SNP_TRC_TIMESTAMP_VALUE (with a value between 1 and 1000) and did not modify NP_TRC_BUFFER_SIZE (50 * (SNP_TRC_NB_MAX_WORD_VAR + 1)). in the dataAcq.h SNP_TRC_NORD_ORD_MAX_ORD_MAR_MAX file.

how should these values be determined? In CubeMonitor I found other values to set in the variable medu (sampling frequenty, trigger treshord). how can i determine these values?

[Mbert.1]

I need to understand how to set SNP_TRC_BUFFER_SIZE in order to display 100 points on the STM STUDIO, setting the quantity of variables to 9 (SNP_TRC_NB_MAX_WORD_VAR = 9). In STM STUDIO I set the Start in (Manual) and the Stop (when buffer full). if I set SNP_TRC_BUFFER_SIZE (10 * (SNP_TRC_NB_MAX_WORD_VAR + 1)) I don't find myself in STM STUDIO 100 points but I find myself with 32 points. How can I get 100 points, how should the variables be set.

[Richard.Chvr]

No update since a while, closing the post.