BKG NTRIP client seems not to open com ports with higher numbers, e.g. COM11 or COM17

[carsten.stoeber@…]

We are using the BKG client to provide correction data streams to uBlox f9P receivers. We now faced the issue that it seems we can not open serial connections for com ports with higher numbers, e.g. COM17. This has been observed on multiple PCs.

The issue was discovered after we changed the test PC which needed re-installation of GNSS receivers (leading to different com port mapping for the same receivers compared to the old PC). The BKG client version was 12.xxx but we also now updated to the recent version.

On the PC multiple GNSS receivers are connected and the correct ports are used, i.e. RTCM corrections can be provided on this ports theoretically. While we can successfully open the connection to ports like COM4. Stopping the client and using the same settings for higher ports (multiple receivers are connected at same time with same settings) leads to the connection is not being accepted.

In the below example we automatically try to open the connection which fails. Than we manually just change the com port number from 17 (receiver 1) to Com5 (another receiver) and it immediately works (the name of the file coincidentally has "...Com5.bnc" in it on, on another PC it is between com11 not working and com4 working).

25-04-03 11:29:59 ========== Start BNC v2.13.2 (WIN32) ==========
25-04-03 11:29:59 Panel 'Serial Output' active
25-04-03 11:29:59 RS01: Cannot open serial port

25-04-03 11:29:59 RS01: Get data in RTCM 3.x format
25-04-03 11:29:59 Configuration read: tests/Gnss/RTK/BNC_Template_NTRIP_viaPort4022ToCom5.bnc, 1 stream(s)
25-04-03 11:32:09 ========== Start BNC v2.13.2 (WIN32) ==========
25-04-03 11:32:09 Panel 'Serial Output' active
25-04-03 11:32:09 RS01: Get data in RTCM 3.x format
25-04-03 11:32:09 Configuration read: tests/Gnss/RTK/BNC_Template_NTRIP_viaPort4022ToCom5.bnc, 1 stream(s)