Master Emulator go crazy after a connect fail

RE: Master Emulator go crazy after a connect fail

Eric YY — Mon, 30 May 2016 09:17:06 GMT

I've tried the nRF Uart, still no luck... Seems the only work-around is close() then open() again...

RE: Master Emulator go crazy after a connect fail

Bjørn Inge — Tue, 24 May 2016 11:12:31 GMT

I can see that the log file is having duplicate entries, it's not a good sign though it's not necessarily a problem. I'm not sure why reset is not working, another approach would be to use Close()/Open(), though that requires running PerformPipeSetup() and Run() again. You could also try to use a different example project, nRF Uart is the most recent project.

RE: Master Emulator go crazy after a connect fail

Eric YY — Tue, 24 May 2016 08:57:00 GMT

Seems Reset() doesn't work, I amended the program to:

Public Sub startDeviceDiscovery() Dim scanPara As BtScanParameters = New BtScanParameters scanPara.ScanType = BtScanType.ActiveScanning

If Not g.masterEmulator.IsDeviceDiscoveryOngoing Then
    If Not g.masterEmulator.StartDeviceDiscovery(scanPara) Then
        g.masterEmulator.Reset()
        g.isBusy = False
        MainForm.updateUI()
        Exit Sub
    End If
End If

g.isBusy = False
MainForm.updateUI()

End Sub

But it still failed after Reset(). You can have a look on the log.txt at: www.dropbox.com/.../log.txt

RE: Master Emulator go crazy after a connect fail

Bjørn Inge — Tue, 24 May 2016 07:26:39 GMT

It might be that MasterEmulator IsConnected state is not updated properly (by MasterEmulator itself) after a connection establishment has failed, and consequently the code that sets IsDeviceDiscoveryOngoing is unreachable. A log file (%ProgramData%/Nordic Semiconductor/MasterEmulator/log.txt) would be helpful.
As for workaround you could call Reset()

RE: Master Emulator go crazy after a connect fail

Eric YY — Fri, 13 May 2016 01:50:45 GMT

Well, the IsDeviceDiscoveryOngoing is one of the property reported by the masterEmulator library... I expect it to be correctly set to false after the connection failed... Should I need to do something?

BTW, seems this is a ReadOnly prperty, there's no way I can set it...

RE: Master Emulator go crazy after a connect fail

Bjørn Inge — Thu, 05 May 2016 19:04:40 GMT

Could it be that the IsDeviceDiacoveryOngoing is out of sync, meaning it has not been correctly set to false when a connection establishment has failed?