Proteus-e module disconnects always

RE: Proteus-e module disconnects always

Jared — Fri, 29 Nov 2024 15:19:33 GMT

Hi,

If you don't have access to the source code then it's very difficult for us to support you. Preferably you would direct this question to Wurth who made the fw.

[quote user="ccaro"]

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.

[/quote]

You need to connect serially to read out the debug logs. But if you don't have access to the source code then it's difficult as you wouldn't know what pins/backend that are used by the firmware for logging.

regards

Jared

RE: Proteus-e module disconnects always

ccaro — Thu, 28 Nov 2024 14:27:43 GMT

Hi Jared,

[quote userid="73165" url="~/f/nordic-q-a/116810/proteus-e-module-disconnects-always/512579"]What fw is flashed to the nRF52805?Do you have access to the source code?[/quote]

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

[quote userid="73165" url="~/f/nordic-q-a/116810/proteus-e-module-disconnects-always/512579"]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?[/quote]

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".

[quote userid="73165" url="~/f/nordic-q-a/116810/proteus-e-module-disconnects-always/512579"]Do you have access to debug logs directly from the module?[/quote]

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

RE: Proteus-e module disconnects always

Jared — Thu, 28 Nov 2024 12:59:59 GMT

Hi,

[quote user="ccaro"]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. [/quote]

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!

[quote user=""]"Error 133 (0x85): GATT ERROR and just after it Error 8 (0x8): GATT CONN TIMEOUT. [/quote]

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

RE: Proteus-e module disconnects always

ccaro — Thu, 28 Nov 2024 10:27:08 GMT

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.

[quote userid="73165" url="~/f/nordic-q-a/116810/proteus-e-module-disconnects-always/512549"]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? [/quote]

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

RE: Proteus-e module disconnects always

Jared — Thu, 28 Nov 2024 10:16:54 GMT

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