TY - GEN
T1 - A solution for remotely diagnosing fieldbus networks across the internet
AU - Watterson, Conal
AU - Heffernan, Donal
AU - Kaghazchi, Hassan
PY - 2006
Y1 - 2006
N2 - 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.
AB - 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.
KW - Diagnostic testing
KW - Network operating systems
KW - Process control
KW - Remote consoles
UR - http://www.scopus.com/inward/record.url?scp=33644662646&partnerID=8YFLogxK
U2 - 10.1108/01445150610645666
DO - 10.1108/01445150610645666
M3 - Article
AN - SCOPUS:33644662646
SN - 0144-5154
VL - 26
SP - 54
EP - 58
JO - Assembly Automation
JF - Assembly Automation
ER -