LabVIEW
How to communicate with a device through "xml telegrams"
The manual is pretty sparse in information. It only documents the XML messages and not very systematically but rather as a dump of possible messages. The manual has "Prelimenary version" on each page, for some reason.
It says nothing about what communication method is used for the USB connection. I would hesitate to even make an estimate for needed work to communicate with it through USB because of that. Definitely forget about VISA USB Raw, if you have to go that path you can better stop now instead of getting yourself frustrated. It never really was the solution for almost any problem communicating to an USB device, but definitely isn't nowadays as the manufacturers almost never are willing to document their low level USB protocol and to make things even more complicated, modern OSes require driver signing so you have to purchase a certificate to sign your VISA USB Raw driver in order to let Windows (or MacOS) load it at all.
My prefered method would be to use the network connection. That has some chance to be actually workable with the information contained in this "manual". For USB there is simply not enough information available unless you can get Mettler Toledo to provide you a much more technical document.
The challenge will be to generate the correct XML messages to send to the device and to parse the response. That is always a very "fun" business. LabVIEW comes with an XML library but you still have to build the XML message structure explicitly and to specify the x-Path to the parsing function to retrieve specific elements. Doable but quite tedious. Unfortunately there is not a much easier way also in other programming languages. XML was once hailed as the solution to everything including sliced bread, toasters and vendor independent communication protocols. People overlooked that while XML is indeed text based (and rather verbose in that) it is also encoding the entire data structure as well and anyone trying to build or interpret XML messages needs to understand that schema exactly. XML schema descriptions were supposed to solve that but really just moved the actual problem onto a different level.
JSON eventually was used more. It has the same difficulty of incorporating the data type schema as XML has, but is a lot more concise and compact and actually easier to read for humans with minimal training about the JSON format. And parsing libraries also tend to be significantly easier to use with JSON.
