Custom Query (104 matches)
Results (22 - 24 of 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #153 | fixed | BNC is unable to open serial port | ||
| Description |
I am using BNC v2.12.18 under Windows 10 64-bit. I have configured it to receive an NTRIP stream containing RTCM3 messages from a local caster, and this appears to be working. I now wish to configure BNC to forward the RTCM3 messages to a serial-connected GNSS receiver. The GNSS receiver is an embedded module (mini-PCIe form factor) which appears in Windows as a virtual serial port (COM49). I have entered the mountpoint, port name and baud rate on the Serial Output tab, but BNC is consistently unable to open the port. I have confirmed that the baud rate is correct and that the port exists in Device Manager. I have confirmed that no other application has opened a connection to the port. I have attached my BNC config file (with my credentials removed), a log file, and two screenshots. What am I doing wrong? |
|||
| #38 | fixed | bnc --key onTheFlyInterval "": seems to be ignored | ||
| Description |
I'm trying to make the command line input override the configuration file with regard to the onTheFlyInterval setting. The config file has onTheFlyInterval=1 day while at the prompt I'm calling bnc -nw --key onTheFlyInterval "". I faced this problem using bnc to convert ntrip to rinex. Files were no longer being saved to disk after midnight UTC. I could get the intended behavior (files being saved uninterruptedly across day boundaries) changing the original setting onTheFlyInterval=1 day to onTheFlyInterval= in the config file. I could NOT get the intended behavior having onTheFlyInterval=1 day in the config file and bnc -nw --key onTheFlyInterval "" in the command line. It seems that the empty value "" is being ignored by bnc or perhaps even discarded by the shell itself. |
|||
| #165 | fixed | BNC Posibility to disable the epoch check | ||
| Description |
BNC automatically checks the epoch and does not generate observations output to the Feed Engine nor Ephemerids if the epoch is not aligned with the systems local. Instead, only a "Wrong observation epoch(s)" message appears in the log. This makes BNC useless for anything that is not real-time. I would suggest there should be a "yes/no" option (set to yes by default) that allows the user to choose whether or not to perform this check. |
|||
