A linux-based ToolScope Server with an linux-based Operate as HMI supports all apps, which the normal ToolScope supports.
On windows-based server OR a windows-based HMI TS-PM and TS-AFC have unreliable reaction times and thus may not be treated as working correctly.
The standard interface between the machine and the ToolScope Server supports much less sensor signals as a standard ToolScope installation.
The following signals are offered in the product standard. The signals are able to give a monitoring for 1 NC channel.
Ambassador servers are limited to a measuring frequency of 100Hz. The Ambassador connector software may be configured to measure with a higher frequency, but we recommend not to use that.
Trigger, Trigger 2
Two signals from the NC can be transferred from the NC as start and stop trigger.
Program number, Process number, Tool number in the format in which the NC supports R parameters. A 7-digits decimal value can be expected. More digits may work, but are dependent on the control configuration.
- Torque / Load / Current
The monitoring signal should be torque, load or current of engine of the tool. The torque values can always be read with the solution line control system. A power line control system can only give a torque value under special circumstances. It should be possible to get the torque value for a 611d engine, if the control system supports them. The other values should always work.
Override value from the ambassador instance; this is mostly a value from an AFC.
- Alarm number, Channel number of an alarm
Alarm number and sending monitoring window, which transmits the alarm. The.alarm number is parsed automatically by the TS_ON/TS_OFF-cycle and leads to an error message in the HMI.
Internally used for the transmission protocol between the Ambassador instance and the TS_ON/TS_OFF-cycle.
ToolScope errors are handed out as NC alarms via SETAL