The following limitations of the SINUMERIK Connector application have to be considered:
Limited support of SINUMERIK ONE with the following technical restrictions
Full support of SINUMERIK ONE GIV up to V6.23 (for 6.24 and newer the HF_Probe will not work)
PLC password protection (aka PLC Access Level; PAL) must be deactivated in the TIA Portal project for HMI access
If the HMI would need a password to access PLC data, the SINUMERIK Connector will not be able to connect to the controller.
Invalid HF data points - rejected by HF_Probe - will not be added to rejected_data point field during create subscription
If you have configured e.g. “ENC_POS|7”, but an axis “7” does not exist on your machine, the configuration is accepted without any issue, but you will never get data for such a data point.
Data_Events and HF data do not use same time source. Therefore, timestamps can be different. Subscribe to the CYCLE and SYNC_CYCLE_HF to be able to synchronize the data based on the CycleCounter.
According to the General Payload Specification, CYCLE is used as STRING on IE Databus even when we push it as DT_UINT64. Relevant for consumer app.
For more information, refer to the IE Databus Reference document.
Data Event subscription like '/channel/parameter/r[u1,1,#2]' with array length greater 1 will not work. Relevant for the consumer app. To solve this, add 2 data events like '/channel/parameter/r[u1,1,#1]' and '/channel/parameter/r[u1,2,#1]'.
The same restriction applies to Low Frequency data subscriptions.
Data events and low frequency data points are only published as STRING, independent of their real datatype. This will change in one of the upcoming versions of SINUMERIK Connector.
A subscription to a data event is only sending any value if the value changes on the data source. The initial value is not sent to the subscription.
If the IED is under high load SINUMERIK Connector may drop data which is not processed by the client application(s) fast enough, to avoid internal buffer overflow.
If you have configured any invalid low frequency data point address, the current version of SINUMERIK Connector does not recognize this on configuration time. That can lead to the problem that you will not get any or at least not each of the configured low frequency data point values.
If the configuration of the SINUMERIK Connector is changed using the IEM functionality "Update configuration" instead of using the Common Configurator, it is neccessary to restart the SINUMERIK Connector application manually to activate the new configuration.