Results

Supplementary conditions

"boot_job" folder

If the "boot_job" folder is not generated automatically, restart the control, and create the directory manually under: /var/tmp, or C:\temp for PCU.

An online script update during ongoing operation can result in loss of data

Error description:

During the update of scripts that contain the execution logic on the control, it cannot be guaranteed that the data will be recorded continuously over the stopping and restarting period of the scripts.

Remedy:

No remedy possible.

Variables of the type "STRING" are not visualized in the aspect view

Error description:

When freely configuring variables, defined variables of the data type "STRING" are not displayed in one aspect. The display shows "No Data available".

Remedy:

No remedy possible.

Crash of SINUMERIK Operate caused by update of the application logic

Error description:

Updating the application logic by means of an update of the system at the server end can very occasionally cause SINUMERIK Operate to crash.

Remedy:

Restart SINUMERIK Operate.

Display of the "operational performance monitors"

Error description:

An additional license is required for recording the axis-specific operational performance monitors: path length evaluation, 6FC5800-0AM53-0YB0.

Remedy:

Contact your sales representative to obtain the additional license.

Data buffering when no Internet connection is available

Information:

If your control has no Internet connection or if MindSphere is not accessible (e.g. due to an Internet failure), the data is buffered on the controller.

The size of this buffer is limited to 50 MB.

The length of period during which data can be buffered without loss of data depends on the number and type of variables, frequency of changes, and the recording rhythms.

Occurrence of sporadic faulty behavior on the user interface

Error description:

After the MindSphere or one of the components in the user interface has been updated, the user interface may behave incorrectly.

Remedy:

Delete your browser cache, e.g. with the key combination <Shift> + <F5>.

Changing the "ePSConfig.user.xml" file

Information:

Changes to the file "ePSConfig.user.xml" may only be performed after consultation with the Hotline, Service, Development, or PM.

No 1:n connections released for the SINUMERIK Integrate client

Information:

The SINUMERIK Integrate client does not support any 1:n connections. That is to say, no access to a further control is possible via the SINUMERIK Integrate client.

The Asset Manager only supports German and English

Error description:

If a language other than German or English is set, the Asset Manager pages will not be fully loaded.

Remedy:

Use only English or German as the browser language.

It is not possible to delete aspects and variables

Error description:

Deleting aspects via the user interface is no longer possible due to a current error in MindSphere.

Remedy:

Delete aspects and variables via the web service interface of MindSphere.

Connection to MindSphere must be established via TLS 1.2

Error description:

For security reasons, MindSphere requests a connection that satisfies the TLS 1.2 standard. For the versions of SINUMERIK Integrate client that do not support TLS 1.2, a reverse proxy that supports TLS 1.2 is required.

The connection of SINUMERIK controls to MindSphere and "Manage MyMachines" must meet the highest security standards.

SINUMERIK versions that do not meet these standards are not part of the product. For these versions, additional security measures must be taken.

Customers are solely responsible for preventing unauthorized access to their plants, systems, machines and networks. Systems, machines and components should only be connected to the company's network or the Internet if and to the extent necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place.

Remedy:

The machines can be integrated with the aid of a reverse proxy between the company network and the Internet.

You can read about further actions in the application examples: Manage MyMachines – Installation in existing control environments.

System crash when etc/host file is changed

Error description:

Use of the SINUMERIK Integrate client with a changed etc/host file leads to unexpected system crashes.

Remedy:

No remedy possible.

Display problems on tablet devices

Error description:

The display in portrait format is not supported for tablets. Display problems can also occur when the landscape format is used.

Remedy:

Use the display in landscape format on your tablet device if problems occur with the portrait format display. If problems also occur in the landscape format, use your PC browser for this operating step.

Blank e-mail entries are not validated

Error description:

When the user selects the option "Send email" and leaves the email address field blank, there is no check as to whether or not the email is entered.

Remedy:

Enter a valid email address.

Incorrect asset storage location on the card

Error description:

The storage location of an asset is not correctly displayed on the card.

Remedy:

If the asset storage location on the card appears to be incorrect, change the storage location directly in the "Fleet Manager". Click on the "Edit" icon and specify the correct storage location.

There must be sufficient memory for the buffering of data

Error description:

If there is not sufficient memory space on the CF card, the data will no longer be written to the CF card and the entire data recording process will be stopped.

Remedy:

Ensure that there is sufficient memory space. If this problem arises, delete the buffer on the 2nd level.

Aspects and variables cannot be deleted

Error description:

Due to an error in MindSphere, components can no longer be deleted via the user interface.

Remedy:

Delete the components and variables via the service interface of MindSphere.

The machine cannot be reconnected using the "cert.key" file

Error description:

The machine can no longer establish a connection if you again attempt to connect the machine to MindSphere using the existing "cert.key" file.

Remedy:

If you want to connect the machine to MindSphere, delete the existing "cert.key" file and insert a new "onboard.key" file.

The file name "onboard.key" should not contain any numbers

Error description:

If the user downloads the file multiple times during a download process, the browser provides them with successive incremental numbers. The name of the copied "onboard.key" file under the machine (/var/tmp/boot_job) should not contain any numbers. For example: The file name should not be "onboard (1).key".

Remedy:

Make sure that an "onboard.key" file copied under the machine (/var/tmp/boot_job) does not contain any numbers. Ensure that the file name is "onboard.key".

Internet Explorer is only partially supported.

Error description:

Internet Explorer is only partially supported.

Remedy:

Use the latest version of the Chrome or Firefox browser.

An update of the time zone is not automatically visible in the alarm time

Error description:

If the time zone is changed (UTC or +X), this is not automatically visible in the alarm time.

Remedy:

Reload the file. After this, the updated time values for the new time zone are displayed on the page.

Variables of the type "BOOLEAN" are not displayed in the component expansion

Error description:

If variables are freely configured, defined variables of the data type "BOOLEAN" are not displayed in a component. The message "No data available" is displayed.

Remedy:

No remedy possible

Disconnection is only possible after deleting the cert.key file

Error description:

The existing "cert.key" file cannot be used to disconnect the machine from MindSphere.

Remedy:

Delete the cert.key file from the <TempDir>/boot_job-directory folder.

Only one rule is available

Error description:

If the threshold value was exceeded, then the number of rules for trigger notifications is limited to "1".

Remedy:

The "Fleet Manager" rules can be upgraded for a fee.

Newly created aspects are not displayed.

Error description:

Aspects newly created in MindSphere are not immediately displayed. This involves the export of variables, the display of values for newly configured variables as well as variable-triggered data transfer into "Manage MyMachines".

Remedy:

The data is available in MindSphere after approximately 1 hour.

Events cannot be deleted in "Manage MyMachines"

Error description:

You cannot delete events. The status of the events cannot be changed.

It is only permissible to assign aspect names once

Error description:

When using identical aspect names, an error message is not displayed. However, assigning identical aspect names results in errors.

Remedy:

The aspect name for a tenant may be assigned once for all assets irrespective of the asset type.

Under "Asset Manager" > "Aspects", search for the names that were already assigned to other aspects. Only use names that were not assigned for other aspects.

If the names are used a multiple number of times, then you must delete the aspect.

onboard.key cannot be downloaded in Mozilla Firefox

Error description:

If, in Mozilla Firefox, you click on "Connect SINUMERIK with MindSphere" under "MTA Asset Config" to establish a connection, then the "onboard.key" file is not downloaded.

Remedy:

After you have clicked on "Connect SINUMERIK with MindSphere", a text appears in the browser window that starts with "privateKey".

Copy the complete text to the clipboard (Ctrl+C). Then insert this into a text editor, and save the file under the "onboard.key" name. You can now use the "onboard.key" file to establish a connection.

Alternatively, you can use Google Chrome to download the "onboard.key" file. You can then use Mozilla Firefox again for "Manage MyMachines".

Using the OPC UA server with "Manage MyMachines"

You need an OPC UA server to connect your device to MindSphere via MindConnect Nano.
By default, OPC UA does not provide alarms, does not verify the accessibility of the machine, and does not determine the online status of the MMM Dashboard.

Information on the commissioning of OPC UA can be found in your device documentation.

Controls connected via SINUMERIK Integrate

Information:

"Online status" and "Machine model" are not transferred into assets which are connected to the control via SINUMERIK Integrate.

In the hierarchical representation, the overview page does not show the correct asset list

Error description:

MindSphere does not send the correct asset list when the hierarchical asset view is selected. Therefore, the correct asset list does not appear on the "Manage MyMachines" overview page.

Remedy:

No remedy possible.

Switch from the on-board MindSphere computer to the SINUMERIK Integrate server

Error description:

SINUMERIK can no longer be connected to an Integrate server after being connected to MindSphere.

Remedy:

To enable the connection, delete the following files from the cache memory:

  • /user/sinumerik/hmi/cfg/machineConfig.xml

  • /user/sinumerik/hmi/cfg/machineConfig_backup.bak

The Gateway asset "Activate the payment function" is not shown in the Asset Manager

Error description:

The Gateway asset "Activate the payment function" is not shown in the Asset Manager.

Remedy:

No remedy possible.

Deleted Gateway Assets cannot be restored.

Error description:

MindSphere does not have a function to restore deleted assets.

Remedy:

Do not delete any Gateway assets because they cannot be restored.

Restriction on path length for file uploads in MindSphere

Error description:

Files larger than 8 MB with a path longer than 60 characters cannot be loaded with MindSphere.

Remedy:

If files are larger than 8 MB, ensure that the total number of characters of the file name and the file path is less than 40 characters. 20 characters is the storage length of the time stamp name of the file.

Special characters are not supported in MindSphere

Error description:

MindSphere does not currently support any special characters in path names.

Remedy:

Do not use the following characters: ?, :, *, &, ", $, |, ', <, >, +, !

Imprecise information in the log file "File Upload error.log"

Error description:

As MindSphere does not contain all the information about potential errors when uploading a file, the log file "File Upload error.log" does not show the precise reason for the error.

Remedy:

No remedy possible.

Machine model not connected to the SINUMERIK Gateway

Error description:

The "online" status of machines connected to the SINUMERIK Gateway is not associated with the machine model.

Remedy:

No remedy possible.

Error message when displaying data from the functional gateway

Error description:

The following error can be displayed if data is transferred from the AMC server to "Manage MyMachines" using the "Gateway" functionality: "No data for the selected time period".

Remedy:

Data is correctly displayed if you split up the time period into smaller units.

White border when square images are loaded

Error description:

As MindSphere does not have any scaling options, there are blank white spaces at the left and right margins when square images are uploaded.

Remedy:

No remedy possible.

An image cannot be uploaded multiple times

Error description:

If you try to upload an image that has already been uploaded, MindSphere generates an error message and the image is not uploaded.

Remedy:

Ensure that the image has not already been uploaded before trying to upload an image to MindSphere.

Alarm descriptions in Korean are not displayed correctly on the MMM Dashboard.

Error description:

Because of certain aspects in SINUMERIK Integrate client, alarm messages cannot be correctly displayed in Korean.

Remedy:

No remedy possible.

GUD variables are not displayed in MindSphere

Error description:

The current connection cannot support GUD variables, and GUD variables are therefore not loaded into MindSphere.

Remedy:

No remedy possible.

Error message after double-clicking the "Save" button.

Information:

If you double-click the "Save" button, the error message "Item cannot be saved" appears, although the item will be successfully saved.

Displaying the assets in the overview

Error description:

Only 8 assets are displayed in the overview.

Remedy:

Scroll down to load all assets.

Displaying graphs on the Aspects page

Error description:

If "date/time" is changed on the Aspects page, the graphs are closed.

Remedy:

Reopen the display.

Displaying the alarms

Error description:

All the MindSphere alarms are displayed in one line on the Aspects page.

Remedy:

No remedy possible.

Displaying graphs on the MindSphere Aspects page

Error description:

The units are not displayed graphically on the MindSphere aspect page.

Remedy:

No remedy possible.

Zoom on the Aspect page

Error description:

The Zoom icon is missing from the Aspect page.

Remedy:

Pressing the "Ctrl" key and the Scroll keys enables zooming.

Installation with the 3rdPartyController

Requirement

Uninstall the previous Fanuc version before making an installation with the 3rdPartyController.

Available users in MindSphere Alibaba

Information:

In MindSphere Alibaba, only the following users are available:

  • Standard users

    • mmmdashboard.user

  • Administrator

    • mmmdashboard.admin

The "mmmalarms.user", "mmmoverview.user", "mmmalarms.admin" and "mmmoverview.admin" users are not supported.

MindSphere Alibaba does not support any spindles with Sensor Module SMI24

MindSphere Alibaba does not support the display of spindles with Sensor Modul SMI24

Remedy:

No remedy possible.

Determining the address of a spindle with Sensor Module SMI24

You can read off the position of the spindle in the SINAMICS topology on the title bar of the drive parameter.

The information is displayed as follows:

<number of machine axis>:<name of machine axis>/<identifier of machine axis>

The <identifier of machine axis> comprises:

<character string>_<bus number>.<slave number>:<DO number>

  1. Note down the "Bus number" and "Slave number" of the spindle.

  2. In the "SINUMERIK presets" window of the Asset Manager, you require both of these values as well as the drive number from the "Machine Configuration" list.

Additional information to address the spindle using the SMI24 Sensor Module is provided in:

Function Manual MindSphere Application Manage MyMachines, Manage MyMachines /Spindle Monitor

Configuring the spindle with the Sensor Module SMI24-variable

Make the following configuration, if you wish to capture the data of an SMI24 module with SINUMERIK Integrate Gateway in MindSphere:

  1. Create a variable monitor with the name "SpindleMonitorConfig".
    You can find additional information on "Aspects" in:
    Function Manual MindSphere Application Manage MyMachines, Manage MyMachines /Spindle Monitor

  2. For example, take the following variables and a time-based trigger, which sends data to MindSphere at a rate of 1 minute.

    Address 14,4,3 changes as a function of the machine configuration.

    Variable name

    Address

    Data source

    AMC data type

    MindSphere data type

    MindSphere unit

    ActualClampingTimeWithoutTool

    5049[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    ClampingTime

    5049[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    FaultKTY2TempExcNum

    5061[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    FaultKTY2TempLastTime

    5063[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    FaultKTY2TempTotTime

    5062[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    FaultMotorTempExcNum

    5061[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    FaultMotorTempLastTime

    5063[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    FaultMotorTempTotTime

    5062[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_0

    5088[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_1

    5088[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_10

    5088[10],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_11

    5088[11],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_12

    5088[12],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_13

    5088[13],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_14

    5088[14],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_15

    5088[15],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_16

    5088[16],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_17

    5088[17],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_18

    5088[18],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_19

    5088[19],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_2

    5088[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_20

    5088[20],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_21

    5088[21],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_22

    5088[22],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_23

    5088[23],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_24

    5088[24],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_25

    5088[25],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_26

    5088[26],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_27

    5088[27],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_28

    5088[28],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_29

    5088[29],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_3

    5088[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_30

    5088[30],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_31

    5088[31],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_32

    5088[32],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_33

    5088[33],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_34

    5088[34],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_35

    5088[35],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_4

    5088[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_5

    5088[5],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_6

    5088[6],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_7

    5088[7],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_8

    5088[8],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixOpsHours_9

    5088[9],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    MatrixSpeedThresholdNumber

    5082,14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_0

    5084[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_1

    5084[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_2

    5084[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_3

    5084[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_4

    5084[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_5

    5084[5],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_6

    5084[6],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_7

    5084[7],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixSpeedThrs_8

    5084[8],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixTorqueThresholdNumber

    5083,14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    MatrixTorqueThrs_0

    5085[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    MatrixTorqueThrs_1

    5085[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    MatrixTorqueThrs_2

    5085[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    MatrixTorqueThrs_3

    5085[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    MatrixTorqueThrs_4

    5085[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    MatrixTorqueThrs_5

    5085[5],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    MatrixTorqueThrs_6

    5085[6],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    MatrixTorqueThrs_7

    5085[7],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    MatrixTorqueThrs_8

    5085[8],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    nm

    Motor_temp

    35,14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    °C

    NumOfClamping

    5045[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    NumOfClampingOpsOutOfTol

    5045[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    NumOfClampingOpsWithTol

    5045[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    NumOfFaultClamping

    5045[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OpHoursControl

    5052,14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    OpHoursSpeed

    5051,14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    OrderNumber_0

    5021[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_1

    5021[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_10

    5021[10],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_11

    5021[11],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_12

    5021[12],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_13

    5021[13],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_14

    5021[14],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_15

    5021[15],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_16

    5021[16],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_17

    5021[17],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_2

    5021[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_3

    5021[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_4

    5021[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_5

    5021[5],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_6

    5021[6],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_7

    5021[7],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_8

    5021[8],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    OrderNumber_9

    5021[9],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    ProdDate

    5023,14,4,3

    Sinamics Drive

     

    STRING

    -

    PTCMotorTempExcNum

    5061[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    PTCMotorTempLastTime

    5063[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    PTCMotorTempTotTime

    5062[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    RefClampingTimeAvg

    5046[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    RefClampingTimeMax

    5046[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    RefClampingTimeMin

    5046[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    ReferenceClampingTimeWithoutTool

    5042[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    SerialNumber_0

    5022[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    SerialNumber_1

    5022[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    SerialNumber_2

    5022[2],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    SerialNumber_3

    5022[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    SpindleSuppTemp

    4105,14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    °C

    SuppTempLabel

    4107[0],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    TrendClampingTime24

    5046[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    TrendClampingTime240

    5046[4],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    TrendClampingTime2400

    5046[5],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    ms

    WarningKTY2TempExcNum

    5061[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    WarningKTY2TempLastTime

    5063[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    WarningKTY2TempTotTime

    5062[3],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

    WarningMotorTempExcNum

    5061[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    WarningMotorTempLastTime

    5063[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    -

    WarningMotorTempTotTime

    5062[1],14,4,3

    Sinamics Drive

    FLOAT

    DOUBLE

    s

Gantt chart display on the machine dashboard

Error description:

If different states are sent to the machine dashboard at 15-second intervals, they can no longer be displayed in the Gantt chart as soon as the maximum of 1 600 data points is attained.

Remedy:

No remedy possible.

"Cross-Tenancy" function

You have the option of releasing assets for other tenants using the "Cross Tenancy" function.

NOTE

Data and configuration visible in shared assets

In your role as "Tenant‐Admin", when using function "Cross-Tenancy", it is especially important that you take note of the description in the appropriate MindSphere Manual.

If the "Manage MyMachines" application is used with function "Cross‐Tenancy", then data and configurations can also be read-accessed in those tenants whose assets have been shared.

Carefully check to what extent the criticality of the data and configurations, which are used by you or the users of the received tenant, allows sharing such as this to be made possible.

The following options are not possible using the "Cross-Tenancy" function:

  • Upload files

  • Insert machine image

  • Display location

"Machine off" status

Error description:

"Machine off" status is not displayed in window "Machine aspects", but is calculated on the "Manage MyMachines" interface during the runtime and is displayed in window "Machine dashboard" under tab "Machine status".

Remedy:

No remedy possible.

Chap. 3.3