Byte 38+32*n of the RXM-RAWX message is identified as "reserved2". For protver 18+ with high precision or timesync firmware, version 0x01 of the message uses that field for sigId.
Changing line 3218 of ubxtypes_get.py from "reserved2" to "sigId" allows getting the signal frequency where available.
(It is also available from the NAV-SIG message, but I think there are a set of receivers that support RXM-RAWX v0x01 but not NAV-SIG.
At line 3218 of ubxtypes_get.py:
Byte 38+32*n of the RXM-RAWX message is identified as "reserved2". For protver 18+ with high precision or timesync firmware, version 0x01 of the message uses that field for sigId.
Changing line 3218 of ubxtypes_get.py from "reserved2" to "sigId" allows getting the signal frequency where available.
(It is also available from the NAV-SIG message, but I think there are a set of receivers that support RXM-RAWX v0x01 but not NAV-SIG.
Thanks! John