GLONASS ambiguity resolution for CORS base supported?

[Kozuch]

I have a question regarding the NS-HP-GL RTK receiver. Does it support GLONASS ambiguity resolution when a non-matching receiver (something else than NS-HP-GL) is used as a base station - for example a Leica, Trimble etc. on a CORS/UNAVCO base sites? I have not found the acceptance of RTCM 1230 or 1033 messages in NS-HP docs which are needed for GLONASS AR to take care of the inter-channel biases.

These are the messages in question:
1033 - Receiver and Antenna Descriptors
1230 - GLONASS L1 and L2 Code-Phase Biases

Thanks!

[Alex Lin]

Sorry, NS-HP can't support RTCM 1033 and 1230 messages.

[Kozuch]

Ok if those messages are not supported by the rover then GLONASS AR will not work with a CORS base station, am I right?

[Jason Lin]

When using with public RTK base station, only GPS portion works, GLONASS portion will have issue due to GLONASS FDMA inter-channel bias issue, and requires configuring receiver GNSS constellation type to GPS-only. Once the locally setup base antenna position is surveyed using public base station, the base/rover pair can work in GPS/GLONASS mode and have much better 24hr RTK fix availability due to more combined number of GPS & GLONASS satellites to use.