Consistency information in standard references PX1122R.

[ESPrtk]

Hello Navspark team.
The PX1122R full support update on our ESPrtk is in progress but was interrupted by reference issue.
Below are the latest findings, we hope Navspark team will fix it as soon as possible with more correctly datasheet release.

• CONFIGURE BINARY MEASUREMENT DATA OUTPUT – Configure binary measurement data output (0x1E)
• QUERY BINARY MEASUREMENT DATA OUTPUT STATUS – Query the status of binary measurement data
  output (0x1F)
• BINARY MEASUREMENT DATA OUTPUT STATUS– Status of Binary Measurement Data output (0x89)

This feature is described in the datasheet (AN0039.pdf) but is not available on GNSSViewer V2.1.042.

• CONFIGURE BINARY RTCM DATA OUTPUT – Configure binary measurement data output (0x20)
• QUERY BINARY RTCM DATA OUTPUT STATUS – Query the status of binary RTCM data output (0x21)
• BINARY RTCM DATA OUTPUT STATUS– Status of Binary RTCM Data output (0x8A)

This feature is available on GNSSViewer V2.1.042 with lots of new setting fields but is not described correctly and completely in the datasheet (AN0039.pdf)


The second important configuration fields :

• [RAW tab]Missing Configure / Query RTK Base Position in datasheet.
• [RTK tab]Missing Configure / Query RTK Slave Serial Port Baudrate in datasheet.
• [RTK tab] Missing Configure / Query RTK GLONASS Carrier-Phase Inter-Frequency Bias
  in datasheet.
  
• [RTK tab] Missing Configure / Query RTK Precisely Kinematic Base Serial Port Baud Rate
  in datasheet.
• [RTK tab] Missing Configure / Query RTK Reference Static Started Position
  in datasheet.
  
• [1PPS timing tab] Missing Configure / Query 1PPS Frequency Output Mode in datasheet.
• [Venus8 tab] Missing some Configure / Query for PSTI004 to PSTI0070 in datasheet.
• [Phoenix] Missing all Configure / Query command in datasheet.

We advise ESPrtk users Ver 3.9.8.2 ( and older versions ) not to use the configuration fields listed above for your PX1122R in ESPrtk Navspark GNSSViewer tab until we have merged with the correct configuration in the modified datasheet versions.(This does not affect users with NS-HP-XX or PX1120R).

[Andrew Hsu]

Hello ESPrtk team,

Thanks for your feedback,

We are looking into this.

Best regards,

Andrew

[ESPrtk]

Hello Andrew.
Thanks for your quick response.
I will follow your activity and will continue to report if new issues are found.

[ESPrtk]

Hi Andrew Hsu and Navspark Team .
Do you have any news?
Will the updated documentation be available in the next few days before 1/1/2021?

[Andrew Hsu]

Hello ESPrtk,

Yes:
We are trying to make the documentation available before 1/1/2021.

As I know, Configure/Query Binary RTCM data output has some new field definitions, I think this is the most critical part for you, is it right?

You mentioned, Configure/query binary measurement data output are not available in the Viewer 1.0.42. We checked it and it is already in the Viewer. Can you verify it?

Besides, Configure / Query RTK Reference Static Started Position is obsolete, we no longer need it.

Configure/Query PSTI interval are already in the document and each PSTI number can be referenced in different product datasheet.

Best regards,

Andrew

[ESPrtk]

Hi Andrew.

We are trying to make the documentation available before 1/1/2021.

That is great. Thanks for the efforts.

As I know, Configure/Query Binary RTCM data output has some new field definitions, I think this is the most critical part for you, is it right?

We need to integrate all of your configurations as much as possible. As long as ESPrtk has enough space to do it.
RTK profiles and frequently used fields are are prioritized for support first.

You mentioned, Configure/query BINARY MEASUREMENT DATA OUTPUT are not available in the Viewer 1.0.42.
We checked it and it is already in the Viewer. Can you verify it?

Yes.
In the datasheet AN0039 say that field #7 (Subframe Enabling of
different constellation) add 2 new bits for GNSS type of system are QZSS and IRNSS.
While GNSSViewer does not have that. Does that mean it's unavailable on GNSSViewer or the documentation is wrong ?
This confuses us.

There's more .
The 'Binary measurement output rate' field has a configuration value of 0-1-2-3-4-5-6 corresponding to 1-2-4-5-10-20-8 Hz.
While its Query value is 0-1-2-3-4-5-Other corresponding to 1-2-4-5-10-20-20 Hz.

Besides, Configure / Query RTK Reference Static Started Position is obsolete, we no longer need it.

We are not informed about this. We just realized it was missing in the new document while it still appeared in GNSSViewer software version v2.0.296 and V2.1.042 (from 2017 to 2020 ).
Is it intended for backward support for previous generation modules?
If so, we still need you to provide information about the configuration protocol if you can because it was missing on older documents such as the AN0028 and AN0030.

PSTI

Previously, we had to deduce ourselves that PSTI004 means its configuration ID is 4 in decimal. Similar to PSTI030, PSTI032, PSTI033 will have IDs 30, 32,33 in decimal.
The document makes no mention of this and we had to probe the response Byte code from our NS-HP-BD to confirm it.

The configuration value may not represent the number spelling like the case with the output frequency configuration described above.

We think it's time to discuss this with you when we see new support messages such as PSTI007,020,063,066,067,068,070 was continue added in GNSSViewer software V2.1.042 while nothing is added in the new document.

We need you to explicitly describe in the datasheet something like a configuration ID with a value equal 4 would correspond to the PSTI004.

Phoenix

On GNSSViewer exported a new main tab named 'Phoenix'.
Including many Query commands and 1 Configure command for NMEA String Interval.
We want to integrate this feature.
What will its protocol details be?

[Andrew Hsu]

Hello ESPrtk,

The latest document and Viewer are made available from below:

http://navspark.mybigcommerce.com/conte ... elease.zip

http://navspark.mybigcommerce.com/content/AN0037.pdf

http://navspark.mybigcommerce.com/content/AN0039.pdf


Best regards,

Andrew

[ESPrtk]

Whoa. There is work to do here. The start of a busy new year.
Thank you so much for all the efforts.

Happy New Year to all of you and the Navspark community.

[Andrew Hsu]

Happy New Year!

Thanks for your feedback again.

[ESPrtk]

Yes. Thank you so much - Andrew Hsu and Navspark team.
For ESPrtk / PX1122R users. We have also updated the ESPrtk firmware to accommodate the new datasheet provided by Navspark.
Please see here:

• P1: viewtopic.php?f=22&t=1766
  
• P2: viewtopic.php?f=22&t=1761