bugDataExplorer - Bugs: bug #50053, DEX doesn't recognize end of...

 
 

bug #50053: DEX doesn't recognize end of MC3000 program and creates one new dataset per second and slot after program has finished

Submitter:  None
Submitted:  Sat 14 Jan 2017 09:03:01 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  brueg
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sun 29 Jan 2017 07:40:25 PM UTC, comment #6: 

A new release of DEX is now available. Please verify if the problems reported are fixed.
Thanks in advance

Winfried Brügmann <brueg>
Group administrator
Mon 23 Jan 2017 05:29:10 PM UTC, comment #5: 

Thank you for pointing to this issue, I was able to reproduce according your last description. In meantime I have fixed the issue and run through a phase of testing.
I think you are right with the CPU usage numbers. I see the same using  a raspberry 3 (support in next upcoming release). On the graphics tab it is redrawing the curves every second right after gathering data from the device. The curves of the accumulated number of point needs to be drawn and connected. Even if I use double buffer technique this takes such CPU usage. If you switch to another tab only numbers needs to be refreshed and this does not take the same CPU usage as we will see it for the graphics.

I was not able to reproduce the flickering of the table you have described, I can only assume that the lazy writing of the rows does not work as it should be. I will add some logging to analysis this problem for you a bit deeper.

Winfried Brügmann <brueg>
Group administrator
Sat 21 Jan 2017 12:21:12 PM UTC, comment #4: 

I have also noticed that Li-Ion storage programs never end (if you select "Zero" current), but I don't think it has anything to do with DEX, this is an issue of the MC3000 firmware.

As I have written in the first post I get the error with both "MC3000" and "MC3000-Set" if "Continuous record set" is disabled (I have just retested this to make sure).
I think using "Continuous record set" is just a workaround, I don't think it fixes the bug.

I have noticed another small issue (not sure if this is related to the same bug): when I run a program with 4 batteries DEX uses a lot of CPU (25-30% on my system) and becomes slow to respond, but this happens only when I am on the "Graphic" tab, on any other tab (Statistics, Table...) DEX uses very little CPU (< 5%).
If I use the "Graphic" tab for a short while and the switch back to the "Table" tab the whole table flickers/blinks (as if it has to "catch up"), after a little while it calms down and stops flickering and the CPU usage goes down to the normal level (< 5%).
If I use the "Graphic" tab (with the excessively high CPU usage) for only a short time, the table equally only flickers for a short while, but if I use the "Graphic" tab for longer, then the table also flickers longer (sometimes several minutes) until it calms down and goes back to normal.

I am looking forward to the next version of DEX as well, thank you for your continued development of this very useful program.

Anonymous
Tue 17 Jan 2017 06:49:40 PM UTC, comment #3: 

I have also executed several testing including the update of MC3000 firmware. After the update I processed a never ending LiIo storage program, never ending will say more the 13 hours. Afterwards I processed a LiIO Refresh which also ended with the known termination message.

Thank you for processing the test executions on your side which ended in the conclusion if MC3000-Set is selected and continuous record set is set no problem occurs. Since using the -Set with the new upcoming release of DEX it will switch to continuous record set without selecting it in settings/preferences. At least this is one of the changes done. (Using continuous record set prevent sequences of records to keep this in sequence with the slot numbers)

Do you face the same problem as described with the MC3000, without the -Set as well?

So I am looking forward to release the next version of DEX to keep you as satisfied user of DEX.

Winne

Winfried Brügmann <brueg>
Group administrator
Mon 16 Jan 2017 06:57:41 PM UTC, comment #2: 

I have done some more testing and I believe I can now pinpoint the problem.

First I downgraded to FW 1.12, but the error still occurred (the firmware version doesn't seem to have an influence).

After that I upgraded to FW 1.13 again and, inspired by your screenshot, I tried the "Continuous record set" ("Fortlaufende Aufnahme") option, I hadn't tried that option before. With that option enabled the error did not occur. I got a graph very similar to the one in your screenshot: after the program ended, DEX continued to record data for 15min and then it stopped with the timeout message (I had not realized that MC3000 continues to send data for 15min after the last program has ended, I assumed DEX would stop recording data immediately after the program has ended).

The error only seems to occur with the "Continuous record set" option disabled in combination with a simple program with only one phase (for example charge or discharge). With a complex program with several phases (for example cycle with charge > pause > discharge) it does not matter if "Continuous record set" is enabled or disabled, both work fine.

In short: you should be able to reproduce the bug with a simple program (charge or discharge) and "Continuous record set" disabled.

Anonymous
Sun 15 Jan 2017 03:23:49 PM UTC, comment #1: 

I tried to reproduce with 3.2.8+. but was not able to do so. But I am still on FW 1.12, did not know there is a newer one. I will install firmware and repeat testing with my actual code base. It might be possible that I found the reported error and fixed it with ongoing development work.

My attached screenshot is showing with the message box that all processes are finished and no further action of the charger are detected (sorry for German).

Winne


Winfried Brügmann <brueg>
Group administrator
Sat 14 Jan 2017 09:03:01 PM UTC, original submission:  

I am experiencing the following issue wile using DEX 3.2.8 and MC3000 with FW 1.13:

When a program, e.g. charging or discharging, finishes (i.e. red light on slot button turns green) DEX does not seem to recognize the end of the program and keeps recording data and generates one new dataset per second and slot. Within a short amount of time you have hundreds or thousands of datasets (there should only ever be max 5 datasets) and DEX becomes unresponsive, (temporarily) freezes and sometimes crashes. The only way to stop the "madness" is to manually click the "Stop gathering" button.

In the attached example file I ran a simple discharge program with two batteries, you can see that DEX should have stopped recording data after 1min 45s and 1min 48s (slot 1 and 2 respectively), instead DEX kept recording data until I manually pressed the "Stop gathering" button after 2min 36s.

It does not seem to matter whether I use 1, 2, 3 or 4 batteries or if I use "MC3000" or "MC3000-Set", the error always happens.

I have tested both the 32 and 64 bit versions of DEX on Win 8.1 x64 and Win 10 x64 (with the latest Java), same result, the error happens every time.

other people are experiencing the same issue see post #4211 (and following posts on the same page) on the CPF thread
goo.gl/W8AHKH
As well as post #4249
goo.gl/JisKlZ

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #39477:  2017-01-14_DEX Bug.osd added by None (14KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by brueg (Updated the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-02-08 brueg Open/ClosedOpen Closed
    2017-02-02 brueg StatusIn Progress Fixed
    2017-01-23 brueg StatusNone In Progress
    2017-01-15 brueg Attached File- Added Screen Shot 2017-01-15 at 16.10.04.png, #39482
        Assigned toNone brueg
    2017-01-14 None Attached File- Added 2017-01-14_DEX Bug.osd, #39477

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code