connection problem with Android apk

powered the module (no DEV) by 3.3V and connect UART interface to PC. But when i try to connect by tablet to 2 nodes i dont see nodes, only

[ERROR] GATT_REPRESENTATION
[…] problem while decoding Node statistics characteristic (0eb2bc59-baf1-4c1c8535-8a0204c69de5) expectibg at least 136 bytes, received 109 instead.

i try 1 node anchor and 1 tag, 2 anchors and 2 anchors (1 int, 1 slave), it doesnt matter.
First think i wanna try demo - 1 anchor, 1 tag, 4 anchor, 1 tag.
What i do wrong? :blush: :smiley:


[hr]

[code]FIRST!!!

8.772: [DSRY] discovered new FD:B9:AC:A8:D3:BD, serviceData = ServiceData{operationMode=ANCHOR, initiator=false, bridge=true, online=false, changeCounter=24}
11.066: [FD:B9:AC:A8:D3:BD] onConnectionStateChange: status = 0, current state = CONNECTING, newConnectionState = CONNECTED
11.068: [FD:B9:AC:A8:D3:BD] just connected, scheduling service discovery (600ms pause)
11.680: [FD:B9:AC:A8:D3:BD] discovering service (600ms pause)
13.544: [FD:B9:AC:A8:D3:BD] onServicesDiscovered: status = 0, current state = DISCOVERING_SERVICES
13.544: [FD:B9:AC:A8:D3:BD] services discovered, letting know the callback
13.558: [FD:B9:AC:A8:D3:BD] initiating MTU change
13.609: [FD:B9:AC:A8:D3:BD] onMtuChanged: status = 0, current state = CHANGING_MTU, mtu = 110
13.610: [FD:B9:AC:A8:D3:BD] successfully changed MTU
13.610: [FD:B9:AC:A8:D3:BD] MTU changed, letting know the callback
13.633: [FD:B9:AC:A8:D3:BD] initiating CHRs read
13.634: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Operation mode’ load (3f0afd88-7770-46b0-b5e7-9fc099598964)
13.716: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0xD4A0
13.717: [FD:B9:AC:A8:D3:BD] read CHR ‘Operation mode’
13.718: [FD:B9:AC:A8:D3:BD] CHRs read, letting know the callback
13.735: [FD:B9:AC:A8:D3:BD] initiating CHRs read
13.741: [FD:B9:AC:A8:D3:BD] initiating CHR ‘MAC status’ load (28d01d60-89de-4bfa-b6e9-651ba596232c)
13.776: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0x0A080000
13.777: [FD:B9:AC:A8:D3:BD] read CHR ‘MAC status’
13.777: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Location data mode’ load (a02b947e-df97-4516-996a-1882521e0ead)
13.828: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0x02
13.829: [FD:B9:AC:A8:D3:BD] read CHR ‘Location data mode’
13.829: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Cluster info’ load (17b1613e-98f2-4436-bcde-23af17a10c72)
13.892: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0x0001000000
13.892: [FD:B9:AC:A8:D3:BD] read CHR ‘Cluster info’
13.894: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Node statistics’ load (0eb2bc59-baf1-4c1c-8535-8a0204c69de5)
13.950: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0x04000000200B000015000000000000007B050000000000002B060000000000000000000000000000000000000000000000000000190000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001
13.950: [FD:B9:AC:A8:D3:BD] read CHR ‘Node statistics’
13.952: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Proxy positions’ load (f4a67d7d-379d-4183-9c03-4b6ea5103291)
13.997: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value =
13.999: [FD:B9:AC:A8:D3:BD] read CHR ‘Proxy positions’
13.999: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Argo Network ID’ load (80f9d8bc-3bff-45bb-a181-2d6a37991208)
14.062: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value =
14.064: [FD:B9:AC:A8:D3:BD] read CHR ‘Argo Network ID’
14.064: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Location data’ load (003bbdf2-c634-4b3d-ab56-7ec889b89a37)
14.114: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0x000000000000000000E803000064
14.114: [FD:B9:AC:A8:D3:BD] read CHR ‘Location data’
14.114: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Anchor list’ load (5b10c428-af2f-486f-aee1-9dbd79b6bccb)
14.177: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0x01165C
14.178: [FD:B9:AC:A8:D3:BD] read CHR ‘Anchor list’
14.178: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Operation mode’ load (3f0afd88-7770-46b0-b5e7-9fc099598964)
14.228: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0xD4A0
14.228: [FD:B9:AC:A8:D3:BD] read CHR ‘Operation mode’
14.228: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Label’ load (00002a00-0000-1000-8000-00805f9b34fb)
14.281: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0x445735433136
14.282: [FD:B9:AC:A8:D3:BD] read CHR ‘Label’
14.282: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Device info’ load (1e63b1eb-d4ed-444e-af54-c1e965192501)
14.346: [FD:B9:AC:A8:D3:BD] onCharacteristicRead: status = 0, current state = READING_CHARACTERISTICS, value = 0x165C61BA7F52CADE2A00CADE0005010101050101E039A437A1E83EF800
14.347: [FD:B9:AC:A8:D3:BD] read CHR ‘Device info’
14.347: [FD:B9:AC:A8:D3:BD] CHRs read, letting know the callback
14.358: [FD:B9:AC:A8:D3:BD] problem while decoding Node statistics characteristic (0eb2bc59-baf1-4c1c-8535-8a0204c69de5), expecting at least 136 bytes, received 109 instead, errorCode 10: GATT_REPRESENTATIONcom.decawave.argomanager.exception.GattCharacteristicDecodeException: problem while decoding Node statistics characteristic (0eb2bc59-baf1-4c1c-8535-8a0204c69de5), expecting at least 136 bytes, received 109 instead
at com.decawave.argomanager.util.gatt.GattDecoder.decodeStatistics(GattDecoder.java:179)
at com.decawave.argomanager.util.gatt.GattDecoder.access$lambda$2(GattDecoder.java)
at com.decawave.argomanager.util.gatt.GattDecoder$$Lambda$7.apply(Unknown Source)
at com.decawave.argomanager.util.gatt.GattDecoder$MappingBuilder.lambda$map$1(GattDecoder.java:554)
at com.decawave.argomanager.util.gatt.GattDecoder$MappingBuilder$$Lambda$2.call(Unknown Source)
at com.decawave.argomanager.util.gatt.GattDecoder.decodeCharacteristicAsPropertyValues(GattDecoder.java:585)
at com.decawave.argomanager.util.gatt.GattDecoder.decode(GattDecoder.java:406)
at com.decawave.argomanager.argoapi.ble.connection.NetworkNodeBleConnectionImpl.lambda$fireGetOtherSideEntityReadRequests$4(NetworkNodeBleConnectionImpl.java:450)
at com.decawave.argomanager.argoapi.ble.connection.NetworkNodeBleConnectionImpl$$Lambda$5.call(Unknown Source)
at com.decawave.argomanager.argoapi.ble.connection.ReadCharacteristicOperation.lambda$new$1(ReadCharacteristicOperation.java:48)
at com.decawave.argomanager.argoapi.ble.connection.ReadCharacteristicOperation$$Lambda$2.call(Unknown Source)
at com.decawave.argomanager.argoapi.ble.connection.AsynchronousGattOperation$1.onSuccess(AsynchronousGattOperation.java:48)
at com.decawave.argomanager.argoapi.ble.connection.SequentialGattOperationQueueImpl.onGattSuccess(SequentialGattOperationQueueImpl.java:136)
at com.decawave.argomanager.argoapi.ble.connection.NetworkNodeBleConnectionImpl.onOperationComplete(NetworkNodeBleConnectionImpl.java:1253)
at com.decawave.argomanager.argoapi.ble.connection.NetworkNodeBleConnectionImpl.access$100(NetworkNodeBleConnectionImpl.java:79)
at com.decawave.argomanager.argoapi.ble.connection.NetworkNodeBleConnectionImpl$2.onCharacteristicReadComplete(NetworkNodeBleConnectionImpl.java:217)
at com.decawave.argomanager.argoapi.ble.connection.GattInteractionToConnectionWrapperCallback$$Lambda$1.call(Unknown Source)
at com.decawave.argomanager.argoapi.ble.connection.GattInteractionToConnectionWrapperCallback.delegateSuccessToConnection(GattInteractionToConnectionWrapperCallback.java:137)
at com.decawave.argomanager.argoapi.ble.connection.GattInteractionToConnectionWrapperCallback.onCharacteristicReadComplete(GattInteractionToConnectionWrapperCallback.java:65)
at com.decawave.argomanager.argoapi.ble.GattInteractionFsmImpl$GattInteractionInternalWrappedCallback.onCharacteristicReadComplete(GattInteractionFsmImpl.java:929)
at com.decawave.argomanager.argoapi.ble.GattInteractionFsmImpl.lambda$null$21(GattInteractionFsmImpl.java:1072)
at com.decawave.argomanager.argoapi.ble.GattInteractionFsmImpl$$Lambda$34.run(Unknown Source)
at eu.kryl.android.common.fsm.impl.FiniteStateMachineImpl$5.run(FiniteStateMachineImpl.java:252)
at eu.kryl.android.common.fsm.impl.FsmScheduler.handleMessage(FsmScheduler.java:224)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:194)
at android.app.ActivityThread.main(ActivityThread.java:5742)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1104)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:870)

14.374: [FD:B9:AC:A8:D3:BD] initiating CHRs write
14.386: [FD:B9:AC:A8:D3:BD] initiating CHR ‘Disconnect request’ write (ed83b848-da03-4a0a-a2dc-8b401080e473), value = 0x01
14.438: [FD:B9:AC:A8:D3:BD] onCharacteristicWritten: status = 0, current state = WRITING_CHARACTERISTICS
14.438: [FD:B9:AC:A8:D3:BD] written CHR ‘Disconnect request’
14.439: [FD:B9:AC:A8:D3:BD] CHRs written, letting know the callback
14.441: [FD:B9:AC:A8:D3:BD] initiating disconnect
14.455: [FD:B9:AC:A8:D3:BD] onConnectionStateChange: status = 0, current state = DISCONNECTING, newConnectionState = CLOSED
14.455: [FD:B9:AC:A8:D3:BD] resource cleanup

REPEAT of connection with one more error!!! Look at time!

21.587: [DSRY] discovered FD:B9:AC:A8:D3:BD, nextConnectAttempt elapsed, connecting, newServiceData = ServiceData{operationMode=ANCHOR, initiator=false, bridge=true, online=false, changeCounter=26}
24.329: [FD:B9:AC:A8:D3:BD] onConnectionStateChange: status = 0, current state = CONNECTING, newConnectionState = CONNECTED[/code]
I have this error 2 times in repeat of connection, after turn on node. Who can help?

No solution here, but I have just experienced the same problem on my phone.

It happens to work on someone else’s phone so we just used that.

Hi There,
What android version are you using?
Only version 6 or higher will work.
This is also described in our documentation eg MDEK KIT user manual and quick start guide delivered with the MDEK
/L

Thanks ::slight_smile: Yesterday we found that think, but forgot write about it. The error is not obvious.