UBX-CFG-TP5 Always Rejected

0 votes
When I try to send UBX-CFG-TP5 to LEA-M8 with u-center 8.27 it is always rejected (the "period" text fields are painted red). Desired values I am trying to enter are Period=1000000us, Length=100000us , Align...=ON, Cable Delay=50ns.

18:45:49  0000  B5 62 06 31 20 00 00 01 00 00 32 00 00 00 40 42  µb.1 .....2...@B
          0010  0F 00 00 00 00 00 A0 86 01 00 00 00 00 00 00 00  ...... .........
          0020  00 00 B3 00 00 00 F5 4E                          ..³...õN.
          
18:45:49  0000  B5 62 06 31 01 00 00 38 E5                       µb.1...8å.
          
18:45:49  0000  B5 62 05 00 02 00 06 31 3E 63                    µb.....1>c.
          
18:45:49  0000  B5 62 06 31 20 00 00 01 00 00 32 00 00 00 00 00  µb.1 .....2.....
          0010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
          0020  00 00 B7 00 00 00 41 3E                          ..·...A>.
          
18:45:49  0000  B5 62 05 01 02 00 06 31 3F 68                    µb.....1?h.
          

I noticed that byte 7 is always 1 while the protocol says the version must be 0.

Just in case this is UBX-MON-VER output:

8:48:39  0000  B5 62 0A 04 DC 00 32 2E 32 30 20 28 38 31 32 38  µb..Ü.2.20 (8128
          0010  39 29 00 00 00 00 00 00 00 00 00 00 00 00 00 00  9)..............
          0020  00 00 00 00 30 30 30 38 30 30 30 30 00 00 32 2E  ....00080000..2.
          0030  30 31 20 28 37 35 33 33 31 29 00 00 00 00 00 00  01 (75331)......
          0040  00 00 00 00 00 00 00 00 00 00 00 00 50 52 4F 54  ............PROT
          0050  56 45 52 20 31 36 2E 30 30 00 00 00 00 00 00 00  VER 16.00.......
          0060  00 00 00 00 00 00 00 00 00 00 46 49 53 20 30 78  ..........FIS 0x
          0070  45 46 34 30 31 35 20 28 37 39 31 38 39 29 00 00  EF4015 (79189)..
          0080  00 00 00 00 00 00 00 00 4D 4F 44 20 4C 45 41 2D  ........MOD LEA-
          0090  4D 38 46 2D 30 00 00 00 00 00 00 00 00 00 00 00  M8F-0...........
          00A0  00 00 00 00 00 00 46 54 53 20 31 2E 30 31 00 00  ......FTS 1.01..
          00B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
          00C0  00 00 00 00 47 50 53 3B 53 42 41 53 3B 47 4C 4F  ....GPS;SBAS;GLO
          00D0  3B 42 44 53 3B 51 5A 53 53 00 00 00 00 00 00 00  ;BDS;QZSS.......
          00E0  00 00 AE F5                                      ..®õ.
by olebon asked May 16
86 views
0 votes
>>I noticed that byte 7 is always 1 while the protocol says the version must be 0.

Protocol Spec R14 describes TWO versions of the message packet, Version 0, and Version 1, this would be the latter.

 

In R15 it is on page 224 "Message version (0x01 for this version)"

https://www.u-blox.com/sites/default/files/products/documents/u-blox8-M8_ReceiverDescrProtSpec_%28UBX-13003221%29_Public.pdf
by clive1 answered May 16
Any idea why it never works?
No, not sufficiently familiar with LEA-M8F options/functionality. Can confirm that the EVK-M8F here seems to provide a negative-ACK, so apparently doesn't like one or more parameters.

You should perhaps discuss with the FAE supporting your project/account.
Thank you Clive, I just sent them an e-mail. The phone support is limited to the message that there is no phone support :(
For the X4 bitflag field at byte 28 why do you have bit 7 6 reversed - why B3 instead of 73?
And with LEA-M8F, the timepulse output is only available on TIMEPULSE2 hence the timepulse index (field at 0) should be set to 01.  Your command tpIdx of 00 addresses Timepulse 1.
uCenter pushing back the data polled seems to precipitate the failure, didn't dig deeper. But suggests either form or framing. I might try framing the exact same data tomorrow.

The TP1 vs TP2 makes sense as a possible cause here.
Clive, Grampy thanks for the help. The issue was caused by trying to setup TIMEPULSE instead of TIMEPULSE2.
website banner