search

septentrio-gnss / septentrio_gnss_driver

ROS 1 & 2 driver for Septentrio GNSS & INS receivers
BSD 3-Clause "New" or "Revised" License
71 stars 37 forks source link

Serial ID of mosiac go heading not constant #129

Closed rajsurya1012 closed 1 month ago

rajsurya1012 commented 1 month ago

Hey, I have a MOSIAC GO heading evaluation kit. When searching for the device using "serial/by-id", I have two names for one device. Only when the connection is established using one of the ids, I am able to receive ROS messages. When using the other id, connection is established but there are no messages. Moreover, the id through which the messages are received is not constant and changes between the two upon restart.

How do I fix it and why is it happening?

Thank you!

thomasemter commented 1 month ago

Hi,

I am sorry to hear that since I am not really sure what is going on. I always use the RNDIS connection (i.e. ethernet via USB which I also recommend over serial via USB), so I am not so familiar with the serial connections. There are indeed two serial devices by design - USB1 and USB2, see manual. On my system assignments to the two /dev/serial/by-id are always constant.

Regarding message reception, I have tried both and have the same experience as you: only on USB2 message reception is possible. But this is also constant.

Maybe you could also contact Septentrio's support for assistance since this seems not to be related to the ROS driver.

thomasemter commented 1 month ago

With USB1 the streams do show up in the web UI correctly. Strangely enough, after reactivating them manually in the web UI, message reception via the driver worked on both connections afterwards .

rajsurya1012 commented 1 month ago

ok, thank you!