PROFIBUS Diagnostic Tools
Keep your PROFIBUS Network up and running
PROFIBUS is one of the most widely used automation protocols in the world. With our many years of know-how and our PROFIBUS product portfolio, we support PROFIBUS users in ensuring worry-free and reliable plant operation in the best possible way. As a PROFIBUS specialist, we offer you numerous products and solutions, from PROFIBUS connectors to complete PROFIBUS monitoring solutions.
Emergency Service: +46 705 122 705
General Questions: +46 406 368 038
PROFIBUS Tester PB-Q One
Fast and Precise Quality Diagnosis
PROFtest II XL
For reliable cable test in PROFIBUS
EMCheck LSMZ I
Measuring and avoiding shield currents
PROFIBUS Diagnostic Duo
Online & offline analysis in a set
PROFIBUS Diagnostic Set III
All essential diagnostic tools in one set
PROFIBUS INspektor NT
Monitors the logical data exchange
Since 2002 Indu-Sol of Germany is offering the most comprehensive and recognized solutions in the industry for PROFIBUS diagnostics, monitoring and troubleshooting of PROFIBUS networks to improve reliability and stability of your PROFIBUS network.
Our best-of-breed solutions are accompanied by a variety of accessories, from PROFIBUS repeaters, PROFIBUS connectors and PROFIBUS cable.
PROFIBUS allows to offer diagnostic information with the following benefits:
- Preventing expensive downtime
- Speeding-up troubleshooting
- Allowing predictive maintenance
- Creating condition monitoring
Indu-Sol solutions offer different easy-to-use PROFIBUS diagnostic and troubleshooting tools to accomplish those tasks. The tools are available for PROFIBUS DP and PROFIBUS PA applications and monitor the entire communication network with all its components (without the need of accessing the project in the PLC).
The following PROFIBUS network errors generally occur:
-
Ghost issues
-
Wiring errors (swapped wires, broken wires, short circuit, open shield, missing or excessive termination, segment length and reflections)
-
Voltage issues
-
Device failures (not knowing which device)
-
Topology missing (not having proper machine documentation)
-
Error Telegrams
-
Telegram repetition
-
Bus cycle times off
-
Restarts