Identification of the knitting machines in the network
In the network each knitting machine has an IP address that is set on the knitting machine. This IP address may only be assigned once in the network. Since this differentiation alone is not sufficient to keep the live database consistent, the Stoll-knit report® software uses a definite machine identification - the machine GUID (Global Unique ID). The Stoll-knit report® software recognizes a machine on the basis of these machines GUID - even if the IP address on the machine has been changed.
If a machine has been included in the machine list by means of the Machine management administrator program, the definite machine identification is displayed in the Machine administration window in the column.
Each SKR3 central unit also has a unique identification - the SKR-3-GUID. When a machine has been included in an SKR3 combination, the SKR-3-GUID is stored on the machine. This allows a further SKR3 combination to determine whether a machine should be included that is already logged on at another SKR3 combination.
The following situations may arise (examples):
- The IP address is changed on a machine, for example because the machine was set up in a different production room.
| Consequence: | The machine is no longer found in the network. The data are stored temporarily on the machine for approx. four operating days. |
| Actions: | Correct the IP address for this machine within these four days by using the Machine management program (Machine - administration window). |
| Effect: | After the correction the machine data that were stored temporarily are called up by the SKR3 central unit. The data in the live database remain consistent. |
- The IP address is exchanged between two machines.
| Consequence: | The SKR3 central unit displays an error message because the software recognizes that two IP addresses have been exchanged. The data are stored temporarily on the machines for approx. four operating days. |
| Actions: | Correct the IP addresses for these machines within these four days by using the Machine management program (Machine - administration window). |
| Effect: | After the correction the machine data that were stored temporarily are called up correctly by the SKR3 central unit. The data in the live database remain consistent. |
- The computer on which the Stoll-knit report® software is installed, fails for a certain time, for example due to a defective power supply unit or unintentional switching off.
| Consequence: | The data are stored temporarily on the knitting machine for approx. four operating days. When the computer on which the Stoll-knit report® software is installed functions again, then the machine data that were stored temporarily are called up by the SKR3 central unit. |
| Actions: | Repair within four operating days. |
| Effect: | The data in the database may be corrupt for a certain period before the failure. |
- A machine was defective and has been repaired. During the repair the computer (IPC) and/or the hard disk has been replaced. The dongle data for the machine have finally been copied back.
| Consequence: | The machine is recognized correctly after the repair. |
| Effect: | The data in the database may be corrupt for a certain period before the failure. |
- A machine was defective and has been repaired. During the repair the computer (IPC) and/or the hard disk has been replaced. The dongle data have changed
| Consequence: | The SKR3 central unit displays an error message because the machine GUID for this machine has changed. |
| Actions: | Edit the IP address and activate the Transfer unique machine identification again check box. |
| Effect: | The data are recorded in the live database until the machine fails. The data may be corrupt if the recording was not interrupted in a defined manner. |
- A knitting machine fails. Operating system and machine can be shut down correctly. The machine is repaired and put back into operation.
| Effect: | The period between the failure and the repair is missing in the live database or may be corrupt. |
- A knitting machine fails without the operating system and the machine being shut down correctly.
| Effect: | The period between the failure and the repair is missing in the live database or may be corrupt. |
The list of examples cannot be complete because not all the cases can be foreseen. The live database can then always contain gaps or corrupt sections if undefined states occur during operation.