Plotting graphs

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Plotting graphs

      Hello,

      I would need to use and integrate STemWin graphics functions in my project, but I would like to learn how to do this.
      The STemWin chapter is a new subject for me, so any information / tutorials / recommandations are greatly appreciated.

      Here is my information :
      1. Tools : CubeMX + Atollic TrueStudio + STemWin
      2. Board : STM32F429I Disc1

      Purpose of project :
      3. Measuring a value with ADC, then plotting it as a graph using STemWin.

      Please feel free to comment if you need further information.

      I thank you in advance for your reply and with kind regards,

      Sue

    • Hi,

      Take a look to the example below. It is very basic. I create a window and display a graph. How you feed the buffer for the graph is up to you.

      C Source Code

      1. #include "DIALOG.h"
      2. #include <stdlib.h>
      3. #include <string.h>
      5. /*********************************************************************
      6. *
      7. * Typedef
      8. *
      9. **********************************************************************
      10. */
      11. typedef struct {
      12. U16 * pData;
      13. int NumElements;
      14. } GRAPH_INFO;
      16. /*********************************************************************
      17. *
      18. * Static data
      19. *
      20. **********************************************************************
      21. */
      22. static GRAPH_INFO _GraphInfo;
      24. /*********************************************************************
      25. *
      26. * Static code
      27. *
      28. **********************************************************************
      29. */
      30. /*********************************************************************
      31. *
      32. * _GetADValue
      33. */
      34. static int _GetADValue(void) {
      35. return (rand() % 80 + 1) - 40;
      36. }
      38. /*********************************************************************
      39. *
      40. * _UpdateData
      41. */
      42. static void _UpdateData(void) {
      43. int i;
      44. //
      45. // Shift elemts in buffer
      46. //
      47. for (i = 0; i < _GraphInfo.NumElements - 1; i++) {
      48. *(_GraphInfo.pData + i) = *(_GraphInfo.pData + i + 1);
      49. }
      50. //
      51. // Add new value
      52. //
      53. *(_GraphInfo.pData + _GraphInfo.NumElements - 1) = _GetADValue();
      54. }
      56. /*********************************************************************
      57. *
      58. * _cbWinADV
      59. */
      60. static void _cbWinADV(WM_MESSAGE * pMsg) {
      61. int yPos;
      63. switch (pMsg->MsgId) {
      64. case WM_PAINT:
      65. //
      66. // Clear window with white
      67. //
      68. GUI_SetBkColor(GUI_WHITE);
      69. GUI_Clear();
      70. GUI_SetColor(GUI_RED);
      71. //
      72. // Draw graph
      73. //
      74. if (_GraphInfo.pData) {
      75. yPos = WM_GetWindowSizeY(pMsg->hWin) / 2;
      76. GUI_DrawGraph(_GraphInfo.pData, _GraphInfo.NumElements, 0, yPos);
      77. }
      78. break;
      79. default:
      80. WM_DefaultProc(pMsg);
      81. break;
      82. }
      83. }
      85. /*********************************************************************
      86. *
      87. * _cbBk
      88. */
      89. static void _cbBk(WM_MESSAGE * pMsg) {
      90. switch (pMsg->MsgId) {
      91. case WM_PAINT:
      92. GUI_SetBkColor(GUI_BLACK);
      93. GUI_Clear();
      94. break;
      95. default:
      96. WM_DefaultProc(pMsg);
      97. break;
      98. }
      99. }
      101. /*********************************************************************
      102. *
      103. * Public code
      104. *
      105. **********************************************************************
      106. */
      107. /*********************************************************************
      108. *
      109. * MainTask
      110. */
      111. void MainTask(void) {
      112. int xSize;
      113. int ySize;
      114. WM_HWIN hWin;
      115. memset((void *)&_GraphInfo, 0, sizeof(GRAPH_INFO));
      117. GUI_Init();
      118. WM_MULTIBUF_Enable(1);
      119. WM_SetCallback(WM_HBKWIN, _cbBk); // A callback which clears the background for regions without a window
      120. //
      121. // Get the size of the screen
      122. //
      123. xSize = LCD_GetXSize();
      124. ySize = LCD_GetYSize();
      126. //
      127. // Create a window which should show the AD value, the value gets drawn in the callback function _cbWinADV()
      128. //
      129. hWin = WM_CreateWindowAsChild(10, 10, xSize - 20, ySize - 10, WM_HBKWIN, WM_CF_SHOW, _cbWinADV, 0);
      130. //
      131. // Init a buffer which can hold enough points for the graph
      132. //
      133. xSize = WM_GetWindowSizeX(hWin);
      134. _GraphInfo.pData = malloc(xSize * sizeof(U16)); // Init points with 0
      135. memset((void *)_GraphInfo.pData, 0, xSize * sizeof(U16));
      136. _GraphInfo.NumElements = xSize;
      137. //
      138. // Super loop, GUI_Delay() keeps the application alive, returns after 100ms
      139. //
      140. while (1) {
      141. GUI_Delay(100);
      142. _UpdateData();
      143. WM_InvalidateWindow(hWin);
      144. }
      145. }
      147. /*************************** End of file ****************************/
      Display All
      Regards,

      Sven
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Hi Sven,

      I thank you very much for your quick reply and your helpful help.

      So, I have created the project using CubeMX 5.0.1 + Atollic TrueStudio + STemWin. In the Graphics / STemWin section, I click the execute button to open GUI Builder and create Framewin c file, then generate the code.
      Using Atollic, I have FramewinDLG and GUI_App files. And the code creates the skeleton of graphics on the screen. So far, it is okay.

      I have then worked and tried to integrate the code you had given me, so that I can create the graph. But, I have experienced some troubles to know how to integrate the code in my project. And the questions I have now are the following :
      1. How should I use the code in my project ?
      2. Which part of the code should be placed in the FramewinDLG ? And which code for GUI_App ?
      3. What is about the function CreateFramewin ?

      Please feel free to comment if you need further or detailed information about it.

      I thank you in advance for your technical help and with kind regards,

      Sue
      Files

      • FramewinDLG.txt

        (3.64 kB, downloaded 827 times, last: )

      • GUI_App.txt

        (3.32 kB, downloaded 934 times, last: )

    • Hi,

      try the code below.

      Simply call CreateFramewin() from GRAPHICS_MainTask(). Every 100ms a timer expires and calles the callback function _cbDialog(). Here I react on WM_TIMER and get a new AD value. This value gets set as new point for the data object attached to the graph.

      C Source Code

      1. /*********************************************************************
      2. * *
      3. * SEGGER Microcontroller GmbH & Co. KG *
      4. * Solutions for real time microcontroller applications *
      5. * *
      6. **********************************************************************
      7. * *
      8. * C-file generated by: *
      9. * *
      10. * GUI_Builder for emWin version 5.44 *
      11. * Compiled Nov 10 2017, 08:53:57 *
      12. * (c) 2017 Segger Microcontroller GmbH & Co. KG *
      13. * *
      14. **********************************************************************
      15. * *
      16. * Internet: www.segger.com Support: support@segger.com *
      17. * *
      18. **********************************************************************
      19. */
      21. // USER START (Optionally insert additional includes)
      22. #include <stdlib.h>
      23. // USER END
      25. #include "DIALOG.h"
      27. /*********************************************************************
      28. *
      29. * Defines
      30. *
      31. **********************************************************************
      32. */
      33. #define ID_FRAMEWIN_0 (GUI_ID_USER + 0x00)
      34. #define ID_GRAPH_0 (GUI_ID_USER + 0x01)
      37. // USER START (Optionally insert additional defines)
      38. // USER END
      40. /*********************************************************************
      41. *
      42. * Static data
      43. *
      44. **********************************************************************
      45. */
      47. // USER START (Optionally insert additional static data)
      48. // USER END
      50. /*********************************************************************
      51. *
      52. * _aDialogCreate
      53. */
      54. static const GUI_WIDGET_CREATE_INFO _aDialogCreate[] = {
      55. { FRAMEWIN_CreateIndirect, "Framewin", ID_FRAMEWIN_0, 0, 0, 240, 320, 0, 0x0, 0 },
      56. { GRAPH_CreateIndirect, "Graph", ID_GRAPH_0, 15, 23, 200, 63, 0, 0x0, 0 },
      57. // USER START (Optionally insert additional widgets)
      58. // USER END
      59. };
      61. /*********************************************************************
      62. *
      63. * Static code
      64. *
      65. **********************************************************************
      66. */
      68. // USER START (Optionally insert additional static code)
      69. /*********************************************************************
      70. *
      71. * _GetADValue
      72. */
      73. static I16 _GetADValue(void) {
      74. return (I16)(rand() % 50 + 1);
      75. }
      77. /*********************************************************************
      78. *
      79. * _cbBk
      80. */
      81. static void _cbBk(WM_MESSAGE * pMsg) {
      82. switch (pMsg->MsgId) {
      83. case WM_PAINT:
      84. GUI_SetBkColor(GUI_BLACK);
      85. GUI_Clear();
      86. break;
      87. default:
      88. WM_DefaultProc(pMsg);
      89. break;
      90. }
      91. }
      92. // USER END
      94. /*********************************************************************
      95. *
      96. * _cbDialog
      97. */
      98. static void _cbDialog(WM_MESSAGE * pMsg) {
      99. // USER START (Optionally insert additional variables)
      100. int xSize;
      101. WM_HWIN hItem;
      102. static GRAPH_DATA_Handle hData;
      103. // USER END
      105. switch (pMsg->MsgId) {
      106. // USER START (Optionally insert additional message handling)
      107. case WM_INIT_DIALOG:
      108. //
      109. // Init a buffer which can hold enough points for the graph
      110. //
      111. xSize = WM_GetWindowSizeX(pMsg->hWin);
      112. hData = GRAPH_DATA_YT_Create(GUI_RED, xSize, NULL, xSize);
      114. hItem = WM_GetDialogItem(pMsg->hWin, ID_GRAPH_0);
      115. GRAPH_AttachData(hItem, hData);
      117. WM_CreateTimer(WM_GetClientWindow(pMsg->hWin), 0, 100, 0);
      118. break;
      119. case WM_TIMER:
      120. GRAPH_DATA_YT_AddValue(hData, _GetADValue());
      121. WM_RestartTimer((WM_HTIMER)pMsg->Data.v, 0);
      122. break;
      123. // USER END
      124. default:
      125. WM_DefaultProc(pMsg);
      126. break;
      127. }
      128. }
      130. /*********************************************************************
      131. *
      132. * Public code
      133. *
      134. **********************************************************************
      135. */
      136. /*********************************************************************
      137. *
      138. * CreateFramewin
      139. */
      140. WM_HWIN CreateFramewin(void);
      141. WM_HWIN CreateFramewin(void) {
      142. WM_HWIN hWin;
      144. hWin = GUI_CreateDialogBox(_aDialogCreate, GUI_COUNTOF(_aDialogCreate), _cbDialog, WM_HBKWIN, 0, 0);
      145. return hWin;
      146. }
      Display All

      Regards,
      Sven
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Hi Sven,

      I thank you very much for your reply and support with my issues. This is nice of you.

      So, I started the project with CubeMX + GUI Builder + Atollic, then generated the code. I then copied the code you have given me in the FramewinDLG.c of the project.
      The code compiled successfully without error. However, the display screen is the same between before and after the implementation of the last code. Even the background screen did not change its colour to BLUE, as the code written after WM_PAINT in the _cbBK callback routine. I can not attach the picture of the display screen as its size is too big.

      So, my questions are the following :
      #1. Did I misunderstand something ? Or, did I miss to code something ?
      #2. How can I learn this part of the emWIN efficiently, so that I will have a good understanding of the subject ?

      Any suggestions or tips are greatly appreciated, as I have got stuck technically with this matter.

      I thank you in advance and with kind regards,

      Sue
      Files

      • FramewinDLG.txt

        (4.56 kB, downloaded 702 times, last: )

      • GUI_App.txt

        (3.3 kB, downloaded 734 times, last: )

    • Hi,

      The callback function _cbBk() is not used, therefore it won't do anything. This was a mistake of mine because _cbBk() was a leftover of the previous example.

      But the dialog with the GRAPH widget should work. Try to set a breakpoint into WM_TIMER. If you don't get there you should check the timing functions GUI_X_GetTime() and GUI_X_Delay(). Those functions are most likely located in a file named GUI_X<*>.c and required for any timing related functionalities of emWin.

      The code in WM_TIMER takes care about updating the GRAPH widget. If you never end up there the GRAPH widget doesn't change.

      One very important point with emWin is Window Manager especially the callback mechanism (more in chapter 18 of the emWin user manual). Every widget (and the dialogs created with the GUIBuilder) is based on the Window Manager. Also, sometimes it can be handy to create a WM-window (WM_CreateWindowAsChild()) instead of a predefined widget.

      In my first example I have set up a single WM-window and used it to draw a graph.

      So I recommend to take a look into the chapter about the Window Manager and how it works.

      Regards,
      Sven
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Good morning Sven,

      I thank you a lot for your reply, and also for your recommendation. Indeed, I learn and get to know more about emWin and Window Manager on your detailed manual. It helps to better understanding about the subject.

      So, here are the steps that I have been taking :
      #1. Using GUI Builder to make simple and progressive samples, with the help of the manual.
      #2. Taking back the samples you have given me and implement them in my project.

      It is a bit difficult for me to say when I would get back to give you the feedback about the samples. I have been working to make all these points to function correctly.

      I thank you for your support and see you soon.

      With kind regards,

      Sue

    • Hi Sven,

      I hope that you enjoyed your weekend.

      So, IT SIMPLY WORKS! And I am a happy guy. :)

      Firstly, I followed your suggestion about the timer and checked those 2 files. Activating the Systick handler had resolved this issue.
      Secondly, I made a step-by-step approach to work on the display. And yes, I am now able to display an image and also a window for the graph.
      Third step, I implemented your 2nd code in the graph window and can see its graph.
      So, that is a good step forward for me and I THANK YOU very much for your helpful support and assistance. That is really great! :thumbsup:

      These days I have been learning to implement the reading input via ADC, and then display the values on the graph.
      And I have this question which is not obvious for me :
      #1. Where should I put my codes in the files generated by CubeMX + GUI Builder + STemWin ? The dedicated space for "user code" seems to be very limited.
      #2. Where is the super loop for "the user code" ?

      Again, I thank you in advance for your help and reply, and have a nice day.

      With kind regards,

      Sue
      Files

      • GUI_App.txt

        (3.59 kB, downloaded 696 times, last: )

      • main.txt

        (18.21 kB, downloaded 933 times, last: )

      • WindowDLG.txt

        (4.09 kB, downloaded 716 times, last: )

    • Hi,

      The super loop is the while loop in GRAPHICS_MainTask() you will never return from it and it calls periodically GUI_Delay(). I would replace the HAL_Delays by GUI_Delays. The two HAL Delay() will cause a pause of 2 seconds. In this pause emWin has no chance to update the screen.

      Not sure about the CubeMX procedure to generate code. This is an ST tool and I'm not really familiar with it. Regarding the GUIBuilder. You should place the code between the 'user code' sections.

      To be honest, I use the GUIBuilder only to create a starting point for dialogs. The main part is done manually. For a beginner this might be a bit harder, but it gives you way more flexibility.

      In most cases I create a dialog with the GUIBuilder and copy paste the required parts into my real application.

      Regards,
      Sven
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Good morning Sven,

      I thank you for your helpful reply.

      So, your explication confirms my understanding about the super loop and also the several C files generated by CubeMX and GUI Builder.
      Using CubeMX 5.0.1 and GUI Builder to start a project, there are main, GUI_App, WindowDLG / FramewinDLG and also other files generated. The super loop in function GRAPHICS_MainTask() is not clearly dedicated for 'user code'. And consequently, when the same project is regenerated with CubeMX, all the codes that are implemented in the super loop are deleted.

      I have got one question regarding this :
      #1. Is there a method to implement the codes within the super loop that will NOT be deleted ?
      My understanding is that adding the 'user section' in this super loop would be necessary and important.

      I thank you in advance for your answer and have a nice day.

      With kind regards,

      Sue

    • Hi,

      CubeMX is not a SEGGER tool. I can't say if there is a place where the user can place code in the super loop. I suggest to contact ST.
      But I agree with you that this should be possible.

      The GUIBuilder is a SEGGER tool and it shouldn't touch the user code (between the marks) in c-files generated by this tool.

      You could get around this by setting up a timer in the dialog. Each time the timer expires you can poll the AD values (not that elegant but should work).

      In WM_INIT_DIALOG call this:

      WM_CreateTimer(pMsg->hWin, YOUR_TIMER_ID, Period, 0);

      Add another case, WM_TIMER, to react on the timer message. In this case do something like this:

      Id = WM_GetTimerId((WM_HTIMER)pMsg->Data.v);
      if (Id == YOUR_TIMER_ID) {
      ADValue = GetADValue();
      WM_RestartTimer((WM_HTIMER)pMsg->Data.v, Period);
      }

      This way you can use the AD value directly within the dialog.

      Regards,
      Sven
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Hey Sven,

      I thank you very much for your reply and also for your recommendation tip about the super loop issues. I am going to work on using the timer to update the values.

      The super loop without dedicated 'user section' is situated in GUI_App.c file; and I going to post this in ST forum to resolve the issues.
      And I will get back here to let you know the results.

      My project has been progressing fine, and I am so happy about it.
      So, BIG thank you for supporting my technical issues with STemWin. Your helps are really helpful and precise.

      I will certainly come back here in near future as my project goes.....

      Have a nice day and with kind regards,

      Sue

    • Hi Sven,

      I hope that you have been doing okay....

      So, I have been experiencing some technical difficulties with the graphical display of my project.
      And here are the points :
      #1. I can manage to measure and to display 2 graphs on the same window, however I am not able to make them suitable to my project.
      #2. The graphs of my project should correspond to the attached file below : photovoltaics I-U measurement.
      #3. And here are the detailed steps :
      #3.1. There are 2 measurements : the current I (via ADC) and the voltage U (via DAC). There is a potentiostat module for this. The power graph is the result of voltage x current.
      #3.2. The measurement starts by activating a push button once. It is a single sequence measurement.
      #3.3. The next push button will refresh the values / the displays and start another measurement.

      My questions are the following :
      #4. How should I proceed to make a single sequence measurement ?
      #5. What are the differences between GRAPH_DATA_YT (used in my codes) and GRAPH_DATA_XY ?
      #6. Do you think that I should use GRAPH_DATA_XY functions for my project ?

      I thank you in advance for your useful help and with my kind regards,

      Sue
      Images

      • 171_Mpp.jpg

        22.1 kB, 470×320, viewed 692 times

    • Hi,

      Attached is an example on how something like on the image can be realized. It is not complete (no scale, most likely to small, etc.), but should give you an idea on how to start.

      I just use 3 points for my data, you should use a point for every pixel in x-direction. After getting the data from ADC the data should be reprocessed to fit to the graph.

      Unfortunately, the GRAPH is not able to plot the data with anti aliased lines. In this case you should use our spline API (available since version 5.44).

      Regards,
      Sven
      Files

      • GraphSample.zip

        (20.34 kB, downloaded 733 times, last: )
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Hey Sven,

      I thank you very much for your reply to my question. That is really great.

      I will require some times to take your example and make it work into my project, as I have been experiencing some technical issues with Atollic IDE, these last days.....
      But, as soon as I can make some progress on it, I will get back to you.

      Thank you again and have a nice day. :)

      With kind regards,

      Sue

    • Hi,


      as I have been experiencing some technical issues with Atollic IDE, these last days.....
      Did you tried our IDE, Embedded Studio?
      segger.com/products/development-tools/embedded-studio/

      For evaluation purpose it is completely free without any limitations.

      Regards,
      Sven
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Hello Sven,

      I am going to install and use Embedded Studio IDE, and understanding how it works.....

      Regarding your reply, my understanding is the following then :
      #1. The measurements start once an interrupt input (button) is activated. It is a single sequence measurement.
      #2. Read the ADC current and DAC voltage inputs.
      #3. Save the values in arrays : current, voltage and power points.
      #4. Reprocess these values and plot / display them on the screen window.
      #5. End of sequence.
      Please feel free to comment as your advice will be greatly appreciated. :thumbsup: Thank you.

      So far, I still can not make "the touch screen" function working on my STM32F429 board. Hence, there is still no chance to load your last code.

      Have a nice afternoon and with my kind regards,

      Sue

    • Hi,

      Yes, I would do it the same way.

      Attached is a touch configuration I use on a STM32F429 Discovery. It makes use of the ST library for this board. In the configuration file we create a dedicated task to poll the touch input, but you could also call PID_X_Exec() from within super loop.

      Regards,
      Sven
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Dear Sven,

      Great and thank you for your feedback : it assures me that my method is correct.

      As for the Touch Screen configuration with STemWin, I have been collecting the questions+answers about this subject from Segger forum. And even though there are still some unclear points for me, I have gotten better understandings about the subject.

      I am afraid that the Touch Configuration file has not been attached. So, may I ask you to send me this file ? :)

      I thank you a lot for your help and wish you a nice weekend.

      With kind regards,

      Sue

    • Hi,

      I'm sorry, I forgot the attachment.

      Regards,
      Sven
      Files

      • PidConf.zip

        (1.44 kB, downloaded 638 times, last: )
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.