Abstract
Purpose - To emphasise the need for remote fieldbus diagnostics and to show a technical solution based on industry standard approaches. Design/methodology/approach - The design and approach takes a Profibus fieldbus, as an example candidate, and captures the diagnostic data using an OPC model and then uses a Java RMI object broker to develop/ support the remote end clients. Findings - The findings show, by an implementation example, that it is possible to implement remote diagnostics for a fieldbus network, without interfering with the operation of the network. The findings also highlight the need for security in such a solution. Research limitations/implications - The implementation example is rather cumbersome, but the paper suggests that all the hardware and software could be implemented on a single embedded processor in a single box. The security issues are flagged as a possible limitation, but solution approaches are briefly suggested. Practical implications - The paper highlights the lack of standardisation around fieldbus Diagnostics. Even for the same fieldbus type, different manufacturers will use different diagnostic protocols and codes. This paper suggests a practical implementation, where the diagnostic codes can be interpreted a fixed stage and presented to an end client in a consistent manner. Originality/value - This work is based on a two year original research project. The solution makes heavy use of industry standard protocols but the work is original.
| Original language | English |
|---|---|
| Pages | 54-58 |
| Number of pages | 5 |
| Volume | 26 |
| No. | 1 |
| Specialist publication | Assembly Automation |
| DOIs | |
| Publication status | Published - 2006 |
Keywords
- Diagnostic testing
- Network operating systems
- Process control
- Remote consoles
Fingerprint
Dive into the research topics of 'A solution for remotely diagnosing fieldbus networks across the internet'. Together they form a unique fingerprint.Cite this
- APA
- Author
- BIBTEX
- Harvard
- Standard
- RIS
- Vancouver