wxmplot | wxPython plotting widgets using matplotlib | Data Visualization library

I'm not entirely sure what you expect to happen.

It seems like you probably intend for the FigureCanvas to be not on the main panel (self) but on your Graph_section. If so, then changing

I think you should not need to use Threads or Queues instead of wx.Timers. But, I also think you actually need only 1 wx.Timer that checks for and grabs data from the serial port (or other data source). I would suggest that the handler for the wx.Timer events (probably running at ~2Hz if you expect data at 1Hz) should do the following:

1. check for new data. if there is not new data, return immediately, waiting for next wx.Timer event.

2. if there is new data, parse and do the calculations based on that data right away and append it to the data arrays within that event handler. Just drop all the storing and later deleting of temporary data and have you self.x1, self.y1 etc up-to-date when the data-event-handler ends. All those del XXX in your code -- especially since one event handler deletes data created in another place - look like they could be a problem.

3. and then update the plots. If you believe the plotting will be slow, you could use a second timer event that looks at whether the length of self.x1 has changed and remake the plot(s). But, I believe you should not need to use a second timer, and can just update the plots in the data-event-handler.

For an example of how this might be done, see https://github.com/newville/wxmplot/blob/master/examples/stripchart.py That uses just one wx.Timer that fetches new data and updates the plot. Note that it uses wxmplot.PlotPanel.update_line() which is much faster at updating an existing plot than redoing wxmplot.PlotPanel.plot() for each new data set.

The next_data() function in that example is a bit simpler and more deterministic than what you would need to do to read data from the serial port. But you're already doing that part and what you're doing doesn't look too hard or slow.

Your WorkerThread class is derived from NewTaskWindow so when you create WorkerThread you also create a new invisible NewTaskWindow

In

wx.CallAfter(self.UpdateMedia1, str(i))

the self refers to the invisible second frame and therefore its (invisible) text control is updated.

Solution

Don't inherit NewTaskWindow in WorkerThread and call the UpdateMedia1 of the visible frame object instead (you already gave it as parameter when creating WorkerThread).

The x and y data should be numpy arrays.

I think that you trying to overwrite the items that are already loaded into the splitter window.
Try this instead:
Note: I have no idea what wxmplot is, so I've commented it out

Can it be like this?