Roland rotary printing machine INTERBUS bus fault four diagnostic methods
We are a big printing company in Shenzhen China . We offer all book publications, hardcover book printing, papercover book printing, hardcover notebook, sprial book printing, saddle stiching book printing, booklet printing,packaging box, calendars, all kinds of PVC, product brochures, notes, Children's book, stickers, all kinds of special paper color printing products, game cardand so on.
For more information please visit
http://www.joyful-printing.com. ENG only
http://www.joyful-printing.net
http://www.joyful-printing.org
email: info@joyful-printing.net
BUSSYSTEM95 is a network integration with components connected via a communication cable. Depending on the function and network type, BUSSYSTEM95 is divided into three layers: Ethernet (Ethernet) layer, Arcnet layer and execution layer (Interbus layer). As the closest network to operators and mechanical devices, Interbus has a higher probability of failure. If you can master some methods of fault diagnosis and use it flexibly in use and maintenance, you can do more with less.
Interbus is a kind of field bus system. It is an open serial bus system, which is quite different from the traditional parallel system. This brings some inconvenience to the maintenance work of the maintenance personnel who are accustomed to the parallel system. In practice, the author has a total of some Interbus bus fault diagnosis methods for the reference of peers, hoping to play a role in attracting jade.
Roland printing machine bus fault diagnosis method
There are two types of Interbus buses in Roland's rotary presses: one is the G4 control board as the bus controller's whole bus, which connects the drive part of the whole machine to the input/output (I/O) and each printing department (or The operation panel of the folding machine) and each paper holder. The other is to use the MS-1000 VMEMCI board as the local bus of the bus controller, connected to the various parts of the printing department (or folding machine) valve, motor controller and sensor. Regardless of which part of the bus machine has a problem with the bus, its bus controller will generate a "bus fault" error message, which will be transmitted to the industrial computer of the console via the ARCNET network, and then transmitted to the operation display by the Ethernet after processing by the industrial computer. come out. When the "Interbus bus fault" is displayed on the operation display, you can find the fault location in the main control cabinet or printing unit according to its detailed information.
1. Using fault display LEDs
The Interbus network consists of a bus controller, node devices (Interbus modules) and cables. Possible failures are: bus controller damage, Interbus module damage, cable breaks or poor connections. Since the bus controller and various Interbus modules have LEDs with status indication, the door of the control cabinet can be opened in the event of an Interbus bus failure, and the fault indicator LEDs of the bus controller and Interbus module are checked one by one according to the Interbus structure diagram. . There are a number of different color (mainly red and green) LEDs on the Interbus bus controller VMEMCI board and node device (Interbus module). The different states of the LEDs correspond to different Interbus bus conditions. According to the information given by the LED, the Interbus bus fault location can be analyzed and replaced, and the faulty Interbus module can be replaced to repair the rotary press. This method is more suitable for smaller Interbus networks. If you use this method to diagnose large-scale networks or networks with dispersed Interbus modules, it will take time and effort. Of course, this method was used in previous years when there were no diagnostic conditions. It is worth mentioning that some fault indication LEDs can flash at a variety of different frequencies to indicate different fault conditions, must be carefully observed and carefully identified.
2. Using the fault display
This method is similar to the method of using fault display LEDs, but since only some Interbus network bus controllers on the Roland printer can use this method, and the fault display function is far more powerful than the fault indication LED, it is listed separately. Come out to explain.
The bus controller G4 control board of Siemens S5-155 in the main control cabinet has fault diagnosis and display function, which can diagnose and display the fault of the connected Interbus network. Normally it is displayed as "RUN" and a looping rectangle, the background light is green (in the event of a fault, its background light turns red and shows the fault type, fault location and fault code. The fault type is "LBUS", Indicates local bus fault; 29.1 is the address information of Interbus; fault code "0D21" indicates that there is a problem with the input of the specific Interbus module. In addition, the types of faults that may be encountered during maintenance are: "CTRL"--bus controller fault; "RBUS"--remote bus fault; "LBUS"--local bus fault; "OUT1", "OUT2"--output fault; "BUS"--a bus loop fault, but not precise positioning; "DEV"- - Interbus module failure; "PF" - bus peripheral device failure, etc. The fault code can tell further fault information, and may encounter other various fault codes in the work, no more details will be described here. You can refer to the Interbus fault diagnosis instruction manual, and according to the address information of Interbus, you can find detailed information such as the specific module name, location, address and drawing number on the Interbus structure diagram, so as to quickly eliminate the fault. .
The G4 control board also has a history of fault memory, which can be used to trace faults or soft faults that have been reset by the operator. It is worth noting that the Interbus address in these historical fault records uses a 4-digit hexadecimal number. This 4-digit hexadecimal number is divided into two parts, the high number of bits indicates which bus loop, and the low digits indicate the position in the bus loop. It should be converted to a decimal number and then found on the Interbus structure diagram. For example, the fault address 29.1 mentioned above is recorded as 1D01 in the historical fault record.
3.XTALK program diagnostic method
XTALK is an early communication software between computers and computers. The unit controller MS-1000 of the Roland printer does not have peripherals such as monitors and keyboards, so the diagnostics in the MS-1000 require external commands to be executed. These external commands are sent by the laptop that communicates with them. .
The Interbus network of the printing department, paper holder and folding machine is controlled by the bus controller on the VMEMCI board on the unit computer MS-1000. This bus controller has no display screen. When the Interbus fails, the fault code is not visible. At this time, you can run XTALK to diagnose the network through the unit computer. The specific method is: use a dedicated cable to connect the COM1 port of the laptop to the RS232 communication port of the MS-1000. After running XTALK under DOS, type "TIBS" (note all capital letters) and press Enter. , and then type "C" (configuration), you can get the diagnosis results similar to Figure 4, Figure 5. When all node devices are normal, the location of ERR-CODE is O.K. When Interbus is not normal, the position of ERR-CODE displays "0000", and the fault information is given at the bottom of the dialog window: "Error[0d21]atlocation11.1(DIO-1)[Date=2002/10/16Time= 16:36:32]", meaning a fault was found at bus address 11.1 and the fault code was "Od21". According to the Interbus structure diagram, the module with the bus address 11.1 can be found as a digital input/output module. The cause of the fault can be found in and around the input/output module with fault information. Compared with the method of using the fault indicating LED, this method can save a lot of fault finding time, and is particularly suitable for use in the distributed printing section and the folding machine of the Interbus module. However, the fault location given by this method is sometimes not very accurate, which requires finding faults before and after the diagnostically determined position.
Unit computer and laptop communication can also use "super terminal" in Windows or other communication software such as NCTERMINAL95, etc., the specific use method is similar to XTALK, limited to the space here will not be detailed.
4. Diagnosis with IBSCMDG4
IBSCMDG4 software is the Interbus application software developed by the company. It can be used to diagnose Interbus: connect the COM1 port of the notebook computer and the serial port of the bus controller with the communication cable, double-click the IBSCMDG4 icon to run the IBSCMDG4 software, and select Open under the File menu. In the "OpenProject" dialog box, select the name of the Interbus network file to be diagnosed, and then press OK. You can see the window similar to the Interbus structure diagram. In fact, the Interbus structure diagram is printed with the IBSCDGG4 software. Press the function key F3, then select Diagnose in the "OperatingState" dialog box to diagnose the connected Interbus network. When Interbus is normal, all node devices and their connections are green; in case of failure, the faulty node device (Interbus module) turns red. This software can also automatically record historical fault information by letting the diagnostic program always Run and connect to the bus controller. Historical fault information is helpful for finding the location of the Interbus bus soft fault.
The IBSCMDG4 software diagnostics can be used on almost all Interbus networks of the Rolander printing machine and can locate faults more accurately. After installing the software, remember to copy the Interbus graphic files from Roland to prevent some modules from being displayed.
In general, Interbus faults can be found using any of the above four methods, and only one of them is skillfully mastered to handle various Interbus bus faults. However, with a single fault diagnosis method, the fault may only be determined to a small extent, and the fault cannot be locked to a certain module very accurately. When time and conditions permit, it is recommended to try a variety of diagnostic methods and compare the results to achieve the purpose of accurately locating the fault, while also increasing the experience of diagnosis.
Regardless of which method is used to diagnose Interbus bus faults, you need to be familiar with the structure of the Interbus network. Because once the fault is diagnosed, it is necessary to find the corresponding fault module immediately. If you can't read the Interbus structure diagram, even if you can quickly diagnose the fault, you can't quickly find the faulty module on such a large web offset press, and delay the precious repair and printing time.
It is worth noting that each loop of Interbus needs to go through each node. When one of the node devices (Interbus module) fails, the entire network cannot run. Using a traditional short or skipping this node does not work. Short-circuiting or skipping this node device requires a change in the bus controller settings to allow the Interbus bus to re-run.