WorksManager

Worksmanager now supports 3rd party access to IBSS NTRIP streams.
I've got a SPS855 outputting 2 streams (CMRx and RTCM3.3 MSM) to Worksmanager.

Worksmanager is creating 2 NTRIP casters for them, where you can supposedly connect 100 devices to, on each of them.
I've got no problems to connect with my Trimble gear to either one of them.

But my DJI drone, Matrice 4E with Pilot 2, is unable to connect to the RTCM stream. It can however connect to a public stream with a base 50 km away.

My base is set to output

Worksmanager shows for that stream the following

Why is WM showing "legacy"?

Has anybody successfully connected DJI drones to a WM IBSS NTRIP stream?

The WorksManager UI has a caching problem, which got missed. I haven't worked out the exact time it caches, I would guess it is from when the stream was connected the first time.  With the way we name things it will only be a issue on RTCM V3 streams, sorry about that. 

You can use TrimbleTools.com https://trimbletools.com/IBSS/ibssdump.html to see that the rover will see. It is a worksmanager display problem only. 

On the DJI it was tested but there is a lot of variations of them out there.  A number of them only accept RTCM V3 Legacy.

Does it look like it is getting connected? If so it is most likely the RTCM V3 Legacy issue, if not drop me a line and we can look at the logs to see if we can work out what is happening. 

The drone is not the latest model but not that old, a Matrice 4E.

I believe I've figured it out.

Worksmanager and Trimbletools show this as the mount point.

But that is wrong!

Looking at Trimble Access it shows the following as mount point when connecting to that stream.

With that one DJI pilot 2 shows the base position, the satellites oddly stay at zero count but it seems to converge. Accommodation is too far away from site. I'll need to confirm on site tomorrow if it's able to fix it properly.

I agree the double __ is a little confusing and are pleased you got it going.  

The __wm_SWC you see when you are doing the 3rd party flow, you do not see it if you are using the normal device in WorksManager flow (unless you are using a shared base station)

It is done that way so that every base station name is unique.