M8N and the what() serial baudrate // failed MonVER

[jurriandoornbos]

What is exactly going on with the what() errors. Is it a problem with the M8N, or has it to do with firmware versions, as ublox has apparently scrambled some things around in the 3.01 firmware. In U-center it shows FWVER:3.01 and protver 18.00.

basic yaml config: debug: 1 device: /dev/ttyS0 uart1: baudrate: 9600 in: 7 out: 1 hz: 1 I have changed the baud-rate in u-center to 38400, and confirmed it still has that baud-rate after connecting and disconnecting. Changed this in the yaml file to 38400. Still nothing. Changed the hz and nav_rate around, nothing still. Changed the config_on_startup: false and then it throws the MonVER error.

Another M8N I had laying around also has the exact same issues.

Furthermore, the nmea_navsat_driver also does not work with the M8N, with 9600 baud or 38400 baud.

Then I came across the article above, and was wondering if the different firmware and ublox standard have anything to do with my failures the past few days.

Can anyone here shine a light on the details of the MonVER or baud problem and the M8N?

[Mario2407]

Hi, I am also struggling with the same error and the M8N on ROS. Is there still no solution?