Hi all,
I'm building a small prototype: a Raspberry Pi reads a data block from an S7 via Snap7 (read-only) and logs every change from "running" to "fault" with a timestamp and fault code into a database. It works against a simulated S7.
Now I'm stuck on the real-world side, where you have far more experience than I do:
1. Where does the reason for a stop come from on your machines? Is it a fault code in the PLC, only an alarm text on the HMI, or does someone have to enter it by hand?
2. How do you separate micro-stops (a jam, a light barrier briefly blocked) from real faults? Is there a fixed time threshold?
3. Have you seen this kind of logging actually used day to day, or does the evaluation die out after a few weeks?
Background: I'm checking with a friend whether this could become a startup. just want to hear about some experiences.
Thanks,
Oskar
I'm building a small prototype: a Raspberry Pi reads a data block from an S7 via Snap7 (read-only) and logs every change from "running" to "fault" with a timestamp and fault code into a database. It works against a simulated S7.
Now I'm stuck on the real-world side, where you have far more experience than I do:
1. Where does the reason for a stop come from on your machines? Is it a fault code in the PLC, only an alarm text on the HMI, or does someone have to enter it by hand?
2. How do you separate micro-stops (a jam, a light barrier briefly blocked) from real faults? Is there a fixed time threshold?
3. Have you seen this kind of logging actually used day to day, or does the evaluation die out after a few weeks?
Background: I'm checking with a friend whether this could become a startup. just want to hear about some experiences.
Thanks,
Oskar
