1. Problem or fault description
**** company reported that for a machining center using the 32iB system, when the NC uses the DATASERVER interface, the screen cannot be switched and the NC becomes unresponsive.
2. Processing process: (Analysis methods, technical data, implementation steps)
(1) Fault observation
1) The company's technician demonstrates the operation process and uses DATASERVER for DNC processing. When the "Overview" soft key is pressed, the keys on the NC MDI become unresponsive, and switching to other pages does not respond. It remains in the DATASERVER program screen.
Screenshot 2016-05-19 9.16.40.png
In Figure 1, after the user presses the "List" (box 1) button on the PROG screen of 32iB, other MDI buttons on the NC have no response.
When users encounter this situation and switch POS PROG SYSTEM and other screens many times to no avail, they think it is an NC "crash" phenomenon. But through careful observation, in box 2 in Figure 1, DEVICE: DTSVR_HOST, and in box 3: DTSVR_FOLDER: DATA_SV// The DNC directory at this time is the host directory set by DATASERVER. Observe the NC mainboard LED, which displays "0". If you switch the MDI mode to the HANDLE handwheel mode at this time (the screen display will not switch), shake the handwheel, and the machine tool can move. This shows that the NC has not really crashed and can still control the movements of all axes, but the screen displayed by the NC has not switched.
2) Through user demonstration and observation, basically determine the pattern of fault occurrence and NC status. Shut down and restart the NC, check the DATASERVER board log: (via MESSAGE screen->Extended->LOG)
You can see the information recorded in the LOG when the NC "crash" before shutdown.
From this information, it can be judged that the NC "frozen" when connecting to the DATASERVER host, so the screen could not be switched. And the LOG information shows that E-0202 FTP server connection failed.
picture
After checking the manual, it can be determined that the NC cannot connect to the FTP server because the FTP server is not turned on.
3) In the PROG screen -> device selection, select the 5 devices in the lower left corner of the screen, click DTSVR to enter the CF card directory of DATASERVER, NC is normal. According to the user's operation and LOG information, it can be determined that the "non-response" phenomenon occurs when DATASERVER issues access to HOST1, that is, when entering the DTSVRHOST screen, NC will not respond.
Check the settings of HOST1. The IP is set to 192.168.1.2. After asking the user, there is no relevant FTP server setting. The mode of copying the program from the PC to the NC CF card has been used for processing (STORAGE mode of DATASERVER). On the DATASERVER screen, click on the host Select, you can select 3 hosts, HOST1 HOST2 HOST3, as shown in Figure 4. Among them, the host IPs in HOST2 HOST3 are not set and are blank.
At this time, set the host selection to HOST2, and then return to PROG-Device Selection-DTSVRHOST to access HOST. The phenomenon is different from the host selection of HOST1. After "SERCH" is displayed in the lower right corner of the screen, NC will prompt "Failed to read file list" instead of the unresponsive phenomenon like HOST1.
4) Delete the IP set by the HOST1 host, change it to blank, and re-enter DSVRHOST. The phenomenon becomes the same as that of HOST2. The prompt "Failed to read the file list" appears, and the "no response" phenomenon no longer occurs. The reason is that if an invalid IP is set in the host settings of the HOST, the 32iB system will continue to access the IP, causing the MDI interrupt request to be ignored and stay on the PROG screen, making the user mistakenly think that it has crashed.
3. Conclusion
In the HOST setting of the 31iB series DATASERVER, if an incorrect IP is set, or the IP does not have a corresponding host, MDI may not respond when you choose to access the HOST. If you do not need to access the HOST GET program, you need to set the incorrect IP address to blank to avoid accidentally pressing HOST to access, causing a "crash" and causing a misidentification failure.
