Smart RF Studio crash after 30 hours, each time when dumping data to file.

Thanks for the feedback.

Are you able to read the file after the crash?

It would be interesting to know the size of the file when it crash. It could be that there are no space left on the hard disk. An improvement from our side would be to check available space before writing to file. Except for the disk space, I don't know other thinks that can be done to avoid this problem. I will file a bug report in order to have a closer look at this. 

Regards,
Øyvind

Yes, I can read the file after crash.

The size of file after crash +/- 120 Kbyte.

The a lot of free space on the disk.

The app crashed on each PCs that I tried (I tried at least 6 different PCs), on different versions of Windows (7,8,10).

The file report attached.

Log Name:      Application
Source:        Application Error
Date:          29/11/2016 04:32:00
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Sharona
Description:
Faulting application name: device_control_panel.exe, version: 2.3.0.0, time stamp: 0x5672a725
Faulting module name: Qt5Gui.dll, version: 5.5.0.0, time stamp: 0x55911d00
Exception code: 0xc0000005
Fault offset: 0x000e2671
Faulting process ID: 0x309c
Faulting application start time: 0x01d24940ef19ca32
Faulting application path: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Studio 7\bin\device_control_panel.exe
Faulting module path: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Studio 7\bin\Qt5Gui.dll
Report ID: 0b2dc173-b60c-4f15-95eb-255dd31b9a6f
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-11-29T02:32:00.495955800Z" />
    <EventRecordID>5270</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Sharona</Computer>
    <Security />
  </System>
  <EventData>
    <Data>device_control_panel.exe</Data>
    <Data>2.3.0.0</Data>
    <Data>5672a725</Data>
    <Data>Qt5Gui.dll</Data>
    <Data>5.5.0.0</Data>
    <Data>55911d00</Data>
    <Data>c0000005</Data>
    <Data>000e2671</Data>
    <Data>309c</Data>
    <Data>01d24940ef19ca32</Data>
    <Data>C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Studio 7\bin\device_control_panel.exe</Data>
    <Data>C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Studio 7\bin\Qt5Gui.dll</Data>
    <Data>0b2dc173-b60c-4f15-95eb-255dd31b9a6f</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Unfortunately it is not that simple. We don't release the source code of SmartRF Studio.

The problem is difficult to reproduce since it take some time before it hits the fan. With the information about the file size and available disk space, that is more or less ruled out. The handling of the "file dump" is very simple. Each received packet is parsed and the formatted text is passed on to a text stream associated with a file. 

Have you observed the  same behavior without the "file dump" being enabled?

Do you know approximately how many packets you have received when it crash?

Do you receive many packets with crc errors? 

1. Yes, the same behavior (app crash) without the "file dump".

2. Yes, about 1393348 packets app receive (see attached screenshot for details).

3. Yes, app receive 4573 packets with CRC errors (see attached screenshot for details).

P.S. We have about 8 devices transmitted packets each half second and about 8 devices transmitted each 4 second.

There could be a problem with the data that is shown in the Packet RX tab. Even though you have specified a file dump, the data is shown in the panel. The number of packets is quite high. All packets will be kept. A better solution would probably be to turn off the view of the packets when "dump to file" has been selected.

What kind of device do you use? 

Would you be interested in trying a patch where I turn off the "packet view"?

Regards,

Øyvind

I use SmartRF04EB kit with CC1101 module.

Yes, I interested in trying a patch where you turn off the "packet view".

Okey, 4 days the app run w/o crush (see attached screenshot below)!

Amazing!

What the next steps?

I guess next step would be to have a closer look at the code handling the print out on screen. The first thought is that there are some limits of the components we are using for this and that the code does not do a properly check on the limit before attempting to print more data.

I also think we could add an option where the user can select not to display the packets on screen. In your use case I guess that would be fine.

Can't promise anything about when this would be implemented though, but I hope you can live with the patch for the time being?

Regards,
Øyvind

Yes, I can live with the patch (temporary).

It will be nice to have a feature to enable/disable print out on screen during writing packets to the file.

I don't need the packets ALL the time on the screen, I need them ONLY if I want to check something (in other words for DEBUGGING purpose).