Proteus-e module disconnects always

[ccaro]

Hi,

I am using a Proteus-e module from Wurth Elektronik for a project. This module contains a nRF52805 chip. I am using the nRF Connect app to send commands to configure GPIO pins. I get my module connected but not bonded (I don't know if that's an issue), then go to Unknown Service where it has the following UUID: 6E400001-C352-11E5-953D-0002A5D5C51B and the Unknown Characteristic 6E400002-C352-11E5-953D-0002A5D5C51B for writing and 6E400003-C352-11E5-953D-0002A5D5C51B for notifying. I have tried first with 02 10 0100 01 12 which is for FS_FWVersion request (or command, I don't really know the difference). I have set both options when sending it with byte array. I have tried with and without 12 which is the checksum. 

I always receive in Smart Commander tool from Wurth the same response (02 41 0200 0101 41) and later the module disconnects from the app. In the log in the app what I see is "Error 133 (0x85): GATT ERROR and just after it Error 8 (0x8): GATT CONN TIMEOUT. 

I don't know what's going on but I get similar issues with third-parties app. Fortunately, it doesn't happen for WE Bluetooth LE Terminal but I want to try it with another app. 

Thanks in advance.

Carlos 

[Jared]

Hi,

Are you using any specific samples from the SDK or is this a custom application?

It seems that the issue is that you get a different result by using  WE Bluetooth LE Terminal versus when you use other third-party application nRF Connect app included? 

regards

Jared 

[ccaro]

Hi Jared,

I am not sure what you mean in your first question but I am sending the commands in the format that Wurth specify in their manual PROTEUS-E 2612011024000. I haven't developed anything, just using their hardware which is connected to the PC and from nRF Connect app via BT I send their own commands. 

Jared said:

It seems that the issue is that you get a different result by using  WE Bluetooth LE Terminal versus when you use other third-party application nRF Connect app included? 

More than a different result it works perfectly in WE Bluetooth LE Terminal but it fails to respond and disconnects after it. It is also happening to me with the Serial Bluetooth Terminal by Kai Morich.

regards,

Carlos