This article is about installing a compile cycle in a Siemens NC in order to send axes data from the NC to the ToolScope.
The ToolScope supports communication with a Siemens NC based on two compile cycles: the compile cycles
Short comparison of both options:
- Using TPM means that you use an established industry standard. Problem: it supports only data rates up to 100Hz. The ToolScope supports using undocumented ways for sampling with a higher frequency, but this will slow down the PLC.
- ADAS is the new technology (some years old) which Siemens tried to bring into the market as successor of TPM. It especially supports the usage of more signals and supports frequencies up to 1kHz.
Please follow one of the above links to get instructions for an installation of the compile cycle.
Note: Only one of the two must be installed. Avoid mixing both compile cycles.
Siemens software errors have been observed, which mean that the remains of an installation of one of the cycles must be completely removed from the NC before the respective other cycle should be installed. It was at some NC versions necessary to export an NC archive from the control system and manually delete the machine data for the compile cycle installation from this. The modified archive then had to be imported again.
The fact that the machine data was not displayed due to the deactivation of the compile cycle was irrelevant for triggering of the software error. The error resulted in a complete crash of the Siemens NCU.