Hi,
I would like to process a lot of ubx files created by u-center using Matlab.
The parser almost does which I need.
The output(:).time.msss field is always zero, however in the u-center the UTC time has 100 ms resolution.
I need this precision. Please fix the code to read with this precision.
see: fUBXparse
line 30-35:
rover.time.year=msg(i+4)+msg(i+5)*256;
rover.time.month=msg(i+6);
rover.time.day=msg(i+7);
rover.time.hour=msg(i+8);
rover.time.min=msg(i+9);
rover.time.sec=msg(i+10);
line 70:
rover.time.msss=double(typecast(uint8(msg(i+12:i+15)),'uint32'));
Is msss data available in the UBX_NAV_PVT message?
The UBX_NAV_STATUS contains the msss parameter of line 70 is a bug?
In UBX_NAV_PVT message I tried:
rover.time.msss=double(typecast(uint8(msg(i+11:i+14)),'uint32'));
but failed.
Is the specification of the ubx format available to extend the parsing with additional parameters available in the u-center tool, eg.: COG, SOG, X,Y,Z, etc.
Thank you for your help!
Róbert
Hi,
I would like to process a lot of ubx files created by u-center using Matlab.
The parser almost does which I need.
The output(:).time.msss field is always zero, however in the u-center the UTC time has 100 ms resolution.
I need this precision. Please fix the code to read with this precision.
see: fUBXparse
line 30-35:
rover.time.year=msg(i+4)+msg(i+5)*256;
rover.time.month=msg(i+6);
rover.time.day=msg(i+7);
rover.time.hour=msg(i+8);
rover.time.min=msg(i+9);
rover.time.sec=msg(i+10);
line 70:
rover.time.msss=double(typecast(uint8(msg(i+12:i+15)),'uint32'));
Is msss data available in the UBX_NAV_PVT message?
The UBX_NAV_STATUS contains the msss parameter of line 70 is a bug?
In UBX_NAV_PVT message I tried:
rover.time.msss=double(typecast(uint8(msg(i+11:i+14)),'uint32'));
but failed.
Is the specification of the ubx format available to extend the parsing with additional parameters available in the u-center tool, eg.: COG, SOG, X,Y,Z, etc.
Thank you for your help!
Róbert