Mosaic-Go SBF Loop Stuck

ArduCopter Copter 4.3
1

Hi all,

I am trying to configure the latest Mosaic-Go Dev Kit single head, I have followed all the guide that are presented on github, but the firmware stuck on detecting the Baud Rate, I saw that this problem isnt new and it was discovered years ago, but I think that nobody have fixed it. I have tested also the latest Ardurover firmware but the problem persist.

Also the GPS seems detected, but it give the same message also when it is disconnect. I hope that someone have solve this problem. Thanks in advance

GPS Loop SBF
GPS Loop SBF513Ă—670 70.6 KB

2

Hi! Did you manage to solve this problem? I encountered the same

3

I have same problem :pensive:

4

Unfortunately not yet, I have to put the project in pause and change GPS module, but I will came back soon, hope that someone have solved the problem.

5

Update:

Ok thanks to the Septentrio Support I finally get the Mosaic-Go working with the Arducopter and Ardurover firmware. I upload the mosaic-go config and the full paramter list.
MissionPlanner_config.param (16.6 KB)

MissionPlanner_MosaicGo_01.PNG
MissionPlanner_MosaicGo_01.PNG1920Ă—1040 281 KB

MissionPlanner_MosaicGo_02
MissionPlanner_MosaicGo_02971Ă—527 32.5 KB

mosaic-H_3641786_Current_2023-07-05-160207.txt (137 Bytes)

6

Hey @xVanish69, can you share a wiring diagram? I’mhaving the same issue but I wasn’t able to solve it with your parameters, mainly because I’m not trying a heading configuration.

7

Hi xVanish69,
we have a Mosaic-Go single antenna module connected to Serial Port 3 (GPS 1 port) of our “Cube Orange” autopilot.
We tried to upload your parameter to our “Cube Orange” autopilot with Arducopter ( 4.2.2 version) and we noted some strange behaviour that i list below:

  1. We connected the Mosaic-GO module on GPS1 port but we obtain the “3D-FIX” message on GPS2 and not on GPS (as in the image that you posted). Does it means that both the serial port (GPS1 and GPS2) are busy with the Mosaic-GO module ?

image

  1. On the HUD we have the following message “Unhealty GPS signal” that we can’t fix.
    image

  2. On the “Messages” tab we see a strange infinite loop of messages relate to the baudrate of the GPS1 as you can see in the following image:
    image

Also if the “GPS-HDOP2” and “Sat count 2” parameter are good, we would like to solve the proble above before try to takeoff.
image

Best regards

1 Like
10

Hello @riccardo.pecora Did you ever find a solution?

I am using an Orange Cube with a Mosaic Go (non heading).

I have the mosaic plugged into GPS1 on the Cube.

In the full parameters, I have both GPS1 and GPS2 configured on. If I turn off GPS2, it doesnt work. My Mosaic is plugged into GPS1 but only shows SATS on GPS2.

My issue is pretty much exactly like that forum post above

  1. A constant loop showing this: GPS 1: detected as SBF at xxx baud

  2. The gps is plugged into gps 1 on the cube but only shows satellites on gps 2 (if I turn off gps 2 in the parameters I get a false error and it doesn’t work)

  3. If I try to go into loiter or guided mode or position hold etc it gets a prearm check warning for gps 1.

If you need screenshots, or logs etc just let me know

Using firmware 4.3 on Septentrio Github for MP.

@WickedShell do you have any solutions?

@xVanish69 curious how you got the baud rate to not be stuck in the loop.

hexa.param (17.0 KB)

3/7/2024 8:48:29 AM : GPS 1: detected as SBF at 9600 baud
3/7/2024 8:48:25 AM : GPS 1: detected as SBF at 460800 baud
3/7/2024 8:48:21 AM : GPS 1: detected as SBF at 230400 baud
3/7/2024 8:48:17 AM : GPS 1: detected as SBF at 57600 baud
3/7/2024 8:48:13 AM : GPS 1: detected as SBF at 38400 baud
3/7/2024 8:48:09 AM : GPS 1: detected as SBF at 19200 baud
3/7/2024 8:48:05 AM : GPS 1: detected as SBF at 4800 baud
3/7/2024 8:48:01 AM : GPS 1: detected as SBF at 115200 baud
3/7/2024 8:47:57 AM : GPS 1: detected as SBF at 9600 baud
3/7/2024 8:47:53 AM : GPS 1: detected as SBF at 460800 baud