Looking into extracting axis sensor temperatures, Curtemp did not seem to update automatically, and was not in the registerary at all when I looked on a 2022-installation. Anyone who knows how?
The idea was to continuously extract temperature information through a timed event, meaning that access could occur while the machine is running, or when no program is open. I get an error when trying to create a tempcomp object myself (constructor may not be public, which is understandable), and doing it through the commands interface requires adding it to a program. Tricky...
Not having access to PC-Dmis systems since retirement, I can't be sure of some aspects of this request without some testing. But I do know that if PC-Dmis Automation is used in a C#/VB to access Temp comp data, the C#/VB application needs a connection to a running session of PC-Dmis (of which only one session at a time can be running on the PC controlling the CMM) and a PC-Dmis program needs to be loaded in the session but not necessarily running. Referring to the PCDLRN Object Hierarchy Chart, you can see that access to the Temp Comp Object is obtained via the loaded PC-Dmis program.
I know that I can connect a C#/VB application to a running session of PC-Dmis, but I've only done so when the PC-Dmis session was not running a measurement program. So, I don't know what the consequences of connecting to a session actively running a measurement program. I also don't know what the consequences of trying to actively access the Temp Comp object while the measurement program is running. These are issues I would have to resolve if I were tasked with developing an application to capture Temp Comp values.
Someone give this man access to your offline license server! I totally would with some sort of agreement... use between X and Y time and share some of your dev. It's a win <-> win!
