Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getModuleInfo() fails for UBX-M10050-KB #55

Closed
amnn314 opened this issue Apr 18, 2024 · 2 comments · Fixed by #56
Closed

getModuleInfo() fails for UBX-M10050-KB #55

amnn314 opened this issue Apr 18, 2024 · 2 comments · Fixed by #56

Comments

@amnn314
Copy link

amnn314 commented Apr 18, 2024

Subject of the issue

I found that getModuleInfo() returns false for my UBX-M10050-KB device. I have also found out that it happened because the payload did't contain 'MOD=' substring.

Here's the debug output I get, showing that there's no such substring, while FWVER and PROTVER are present:

Sending: CLS:MON ID:0x4 Len: 0x0 Payload:
sendCommand: Waiting for No ACK response
Incoming: Size: 160 Received: CLS:MON ID:0x4 Len: 0xA0 Payload: 46 57 56 45 52 3D 53 50 47 20 35 2E 31 30 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 50 52 4F 54 56 45 52 3D 33 34 2E 31 30 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 47 50 53 3B 47 4C 4F 3B 47 41 4C 3B 42 44 53 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 53 42 41 53 3B 51 5A 53 53 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
packetCfg now valid
packetCfg classAndIDmatch
waitForNoACKResponse: valid data with CLS/ID match after 233 msec

I decoded it using the following Python one-liner:

>>> s = "46 57 56 45 52 3D 53 50 47 20 35 2E 31 30 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 50 52 4F 54 56 45 52 3D 33 34 2E 31 30 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 47 50 53 3B 47 4C 4F 3B 47 41 4C 3B 42 44 53 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 53 42 41 53 3B 51 5A 53 53 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0"
>>> "".join([chr(int(x, 16)) for x in s.split(' ')])
'FWVER=SPG 5.10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00PROTVER=34.10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00GPS;GLO;GAL;BDS\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00SBAS;QZSS\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
>>>

Expected result

Probably, DevUBLOXGNSS::getModuleInfo() could be fixed by not expecting all three items to be present.

@PaulZC
Copy link
Collaborator

PaulZC commented Apr 18, 2024

Hi @amnn314 ,

Thank you for reporting this.

I was worried initially that you might have a cloned part. But, looking at the M10 SPG 5.10 Interface Description, it says that the MOD is only reported if available. I guess the UBX-M10050-KB chip does not report MOD.

image

I will correct this in the next few minutes.

Best wishes,
Paul

PaulZC added a commit that referenced this issue Apr 18, 2024
@PaulZC PaulZC linked a pull request Apr 18, 2024 that will close this issue
PaulZC added a commit that referenced this issue Apr 18, 2024
@PaulZC
Copy link
Collaborator

PaulZC commented Apr 18, 2024

Hi @amnn314 ,

Please try v3.1.5. Let me know if it resolves your issue.

Best wishes,
Paul

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants