Non-Trimble DC software for Trimble unit?

Why is that surprising??ÿ?ÿ They control how all the equipment works together... and it WORKS.?ÿ?ÿ I'm at a new gig now, with a mish mash of Leica robots and GPS, Carlson collectors and a few ancient Topcons ?ÿ What a pain in the ass.?ÿ?ÿ Give me an S6 and TSC3 any day.?ÿ I can make that stuff dance.?ÿ?ÿ

Its a technical question not a rhetorical or theoretical question. As in whats stopping non trimble software to communicate with the device and possible solutions for this

I do believe there is a way...When testing I set my R10 to output NMEA over a network connection...there are a number of "sentences" available. One could at least get position, accuracy, fix status, satellites, etc out of it.?ÿ

I wish it was that easy.?ÿ In order for us to work with the equipment, Trimble has to let us know about function calls the equipment expects, and gives in return.?ÿ Based on that information, we can build a driver for the hardware to communicate with our software.?ÿ I can understand their reasoning, it's just frustrating for those of us on this side of it.?ÿ Want MicroSurvey or Carlson to work with your gear??ÿ Let Trimble know; I would be happy to see it incorporated.?ÿ Our benefit is that we are owned by Hexagon so we have much better access to the same information from Leica and other Hexagon equipment.

Ok so its a matter of not giving enough information to software devs, i thought it was more of an encyption-encoded information kind of a thing, that did not allow code to be written at all on other platforms not owned by Trimble.

On the other hand, how is ti possible that you can feed data to rtklib and get an ntrip server running.?ÿ