Failed to poll MonVER & set relevant settings about ublox HOT 4 OPEN

Also experiencing this. In general this node is quite difficult to use with F9P, even with config_on_startup: false and manual configuration in u-center.

Frequent issue on startup:

[ INFO] [1666109469.028044469]: U-Blox: Opened serial port /dev/ttyACM0
terminate called after throwing an instance of 'std::runtime_error'
  what():  Failed to poll MonVER & set relevant settings

Also, after a successful startup and shutdown of the node, it rarely connects successfully a second time.

from ublox.

I find the reason is "callbacks_.read(message, timeout);" always return false.
because "handler->wait(timeout)" timeout .

but I don't know how to fix it. my OS is Ubuntu 16.04.

code as below:
template
bool Gps::read(T& message, const boost::posix_time::time_duration& timeout) {
if (!worker_) return false;
return callbacks_.read(message, timeout);
}

template
bool read(T& message, const boost::posix_time::time_duration& timeout) {
bool result = false;
// Create a callback handler for this message
callback_mutex_.lock();
CallbackHandler_* handler = new CallbackHandler_();
Callbacks::iterator callback = callbacks_.insert(
(std::make_pair(std::make_pair(T::CLASS_ID, T::MESSAGE_ID),
boost::shared_ptr(handler))));
callback_mutex_.unlock();

// Wait for the message
if (handler->wait(timeout)) {
  message = handler->get();
  result = true;
}

// Remove the callback handler
callback_mutex_.lock();
callbacks_.erase(callback);
callback_mutex_.unlock();
return result;

from ublox.

I'm having the exact same problem. I do have the ZED-F9P connected to u-center via USB and am attempting to read out the GPS data via UART1.

Any help on this issue would be greatly appreciated.

from ublox.

right, but what can be done with this issue? because on ROS2 Humble the problem also occurs, when using u-center configuration saved in non-volatile memory and parameter config_on_startup: false :/

from ublox.