This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1310: Sensor Controller Studio stops immediately after start

Part Number: CC1310


I have tried to install Sensor Controller Studio on my PC, or rather I have tried to install it on two different ( Windows 10 ) machines. The installation goes without any problems, but the program will not run on either machine. The behaviour is the same: when started the mostly black Texas Instrument splash screen is shown followed by what seems to be the normal GUI, but this is only shown for a few tenth of a second whereafter the program stops.  I have also tried with a few different versions of SCS, but the result is the same.

I guess I have something installed on my computers that conflicts with SCS but what?

Windows own event log system does not report anything when the SCS is started.

Does SCS write any logs, which can be used to identify the problem?

Regards,

Klaus Roy-Poulsen

  • This is not something we have observed or gotten any reports on.
    - I assume that this is the latest version downloaded from TI.com?
    - Do you have any issues with SmartRF Studio or Flash Programmer 2? The reason I ask is that those tools share a number of libraries with SCS.
    - Could you try the command line interface for SCS?

    Unfortunately the program does not generate a log.
  • Yes, it is the latest version - 2_4_0_793 dowloaded 4 days ago - as well as a few older versions, all behaving equally bad.

    SmartRF Studio works ok, apart from the fact that loading saved configurations does not work correctly - the editable field are filled out on the screen, but I have to manually enter the same values before they are used. But I guess that is another issue.

    I haven't used the Flash Programmer 2, so I can't comment on that.

    The command line interface seems to work, although I curently have nothing worthwhile for it to do, but it outputs version and help information.

    /krp

  • Some more questions:

    Does sensor_controller_studio.exe appear in any logs of your anti-virus tool?

    Does your computer run any tool that manages privileges and application control?

    When you see the main window appear, does it contain any GUI elements, or is it completely white?

    When you installed SCS, did you enable the "Check for updates at each startup" option on the last page of the installer? Please reinstall, and make sure that this option is disabled.

    Please try to run help_viewer.exe. Does the help viewer appear, and are you able to browse the documents? Or does it behave in the same way as SCS?

    There's no logging during startup of SCS in the application itself, but it's possible to monitor accesses to the file system and the Windows Registry. To do this:
    • Download Process Monitor from docs.microsoft.com/.../procmon
    • Unzip and run Procmon.exe
    • Access the "Process Monitor Filter" window. If it does not appear at startup, open it from the Filter -> Filter... (menu)
    • Remove any existing include actions (green icon)
    • Add "Process Name" "is" "sensor_controller_studio.exe" then "Include"
    • If there's need to send us the log, please zip the PML file
  • Okay, disabling the "Check for update at each startup" option solved it. Manually checking for updates still makes the program stop.

    Even though the problem is solved - mostly - you might still be interested in the answers to your other questions:

    1) No, the anti-virus tools does not report anything.

    2) One computer has privileges and application control, the other has not. Both gives same result.

    3) The window comes with all GUI elements.

    4) Well, that did solved the problem.

    5) help_viewer runs without a hitch.

    I have output from Process Monitor, but I guess you probably do not need it as it seems you have a good idea of what might be going wrong. I can send it if you need it.

    Regards,

    Klaus Roy-Poulsen

  • Thank you for the testing/ feedback. It's important to us to be deliver a product that does not crash.

    Please try the following:
    ·         Start SCS with automatic check for updates disabled
    ·         Press Ctrl+P to access the Preferences panel
    ·         Near the bottom of the preferences list there's a setting called "Internet connection". Change this from "Auto-detect system proxy settings" to "Direct connection".
    ·         Press "Apply" (large button at the bottom of the panel)
    ·         In the Start Page panel, press the "Check for Updates" button in the top-right corner
    ·         Does SCS still crash?
     
    Until we have resolved the issue, you can check for and install patches manually. Double-click on "Sensor Controller Studio Patches (Manual Installation)" in the Start Page panel (http://software-dl.ti.com/lprf/sensor_controller_studio/updates/manual_patch_installation.html).
  • It still crashes.

    Just to be sure the preference change was not delayed to the next start, I tried it a few times and also checked the change was remembered in the setup. But it still stops when the "Check for update" is activated.

    Regards,

    Klaus

  • Thanks for the feedback, the developer is going to go through the code to see if he can figure out what is going on.
  • We have made a special version of Sensor Controller Studio that will create log files after the crash. Would you be willing to run this version to see if we can see why it crashes? If so I can send an invitation to box to the mail address you have registered with at TI.com

  • Yes, of course.

    /krp

  • Did you manage to generate log files from the version you downloaded?
  • I have run the test and uploaded the result to Box. Only one log file 
    was generated, the "patches" directory does not exist.
    
    Regards
    
    Klaus
  • Could you attach the log file here since I believe you only have download and not upload rights on box.
  • UpdService::startUpdInfoDownload(0, "", "", "", "", "", 1, 0)
    UpdService::startUpdInfoDownload(): m_state = 1
    UpdService::startUpdInfoDownload(): Using default URL http://software-dl.ti.com/lprf/sensor_controller_studio/updates/upd_info.xml
    UpdService::startUpdInfoDownload(): setNwkProxy()
    UpdService::startUpdInfoDownload(): setNwkProxy() done
    UpdService::startUpdInfoDownload(): resetDownloadUpdInfo()
    UpdService::startUpdInfoDownload(): resetDownloadUpdInfo() done
    UpdService::startUpdInfoDownload(): new UpdFile()
    UpdService::startUpdInfoDownload(): new UpdFile() done
    UpdService::startUpdInfoDownload(): startDownload()
    UpdFile::startDownload()
    UpdFile::startDownload(): downloadFile()
    
    Well, the log file is available on Box, but I have attached it here as well

  • Thanks for the log file. The update service crashes when the HTTP get request (for upd_info.xml) is started.

    We think that the issue is due to two missing DLL files for OpenSSL, libeay32.dll and ssleay32.dll, or that SCS uses an outdated version or mixed versions of these files on your computers. Most computers have many instances of these files, as they are used by many applications, and a few of these applications are included in the system PATH. In my case, SCS finds the missing DLLs in the "Intel Management Engine" software, which is used to support the Intel chipset. This is probably the case for most (if not all) Intel-based computers.

    Due to export regulations, we cannot (easily) ship these DLLs directly to you. To check if the missing DLLs is the problem, can you try to locate the DLLs elsewhere on your hard drive, and copy them (from the same directory) into the SCS "bin" directory? (same directory as sensor_controller_studio.exe). Make sure to select a file pair with version number (File Properties... -> Details) 1.0.0 or higher.

    We plan to include these files in the next release of SCS, which will probably be released in July.
  • Did you look at/ search for the DLL?