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

[Jared]

Hi,

ccaro said:

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. 

What fw is flashed to the nRF52805?Do you have access to the source code?

Are you connecting to the module from the nRF Connect mobile application and trying to control the GPIOs by writing to BLE service on the module?

Please elaborate more!

"Error 133 (0x85): GATT ERROR and just after it Error 8 (0x8): GATT CONN TIMEOUT. 

Error 133 is used as a generic error and unfortunately does not specify the error source. Do you have access to debug logs directly from the module?

regards

Jared 

[ccaro]

Hi Jared,

Jared said:

What fw is flashed to the nRF52805?Do you have access to the source code?

It's the fw that uses Wurth v. 1.1.0. The source code is not accessible but the manual is here: https://www.we-online.com/components/products/manual/2612011024000_Proteus-e%2026120011024000%20Manual_rev1.6.pdf

Jared said:

Are you connecting to the module from the nRF Connect mobile application and trying to control the GPIOs by writing to BLE service on the module?

Yes, that's it. But first I am trying to ask for the FW version as a first try. I send start byte (02), command byte (10), length (0100), payload (01) and checksum (12). I should receive or at least it should be shown up in their Smart Commander tool "02 50 0400 00000101 56" but I obtain, no matter what I send (even just a byte) "02 41 0200 0101 41" which is the CMD_GETSTATE_CNF response. According to the manual:  The module will send a CMD_GETSTATE_CNF (0x02 41 02 00 01 01 41) to indicate "ready for operation" after the /RESET pin was released".

Jared said:

Do you have access to debug logs directly from the module?

I don't think so, but there is a tab in the nRF Connect app for debugging but haven't used it.

Do you need screenshots for further information? Please ask for it.

Regards,

Carlos