SUMMERY

This FAQ explains the relation between Machine and RSProduction


GENERAL FAQ



Q1: What is captured on E2?  Timestamps of high signals?

    A1: Timestamps of cycles, cycle amounts, high/low signals


Q2: Does E1 pulls data from E2?  Or does E2 pushes data to E1?

    A2: E1 is reading data from E2 every second.


Q3: Does E4 pulls from E1 or E1 pushes to E4?

    A3: E1 is sending data to E4


Q4: Is there an Acknowledgement process between E1 and E2 that the data is successfully transferred?

    A4: There are 2 ways to check if a connection is established. In Operator Tools in the header field there is a machine connection indicator and in Office 

Tools under Hardware you can see if the PLC have contact and when the latest contact was. If the connection is down the PLC have a cycle counter that 

will reset when reaching 9999 cycles from the last known number of registered cycles in the PLC.


Q5: Is there an Acknowledgement process between E4 and E1 that the data is successfully transferred?

    A5: If the status indicator in the left/right bottom corner in the client is green in the bottom, server connection is established. If the color is yellow in the bottom 

of the status indicator there is no server connection to E4 and data is saved in the client E1. If the upper part of the status indicator is yellow there is a que of 

the data transfer and is trying to send data to E4 continuously. Blue color is transferring data. All green is that there is no data to transfer at the moment.


Q6: Is the data removed from E2 only after there is confirmation that the data is already stored in the cloud?

    A6: Timestamps and cycles is saved up to 9999 cycles before the counter is resetting. High/low signals is transferred directly and is not buffered in the

PLC. If the connection is going down to E2 the latest known high/low signal will be known to E1.



IF C1 IS DISCONNECTED


Q7: What message(s) will be shown on E1?

    A7: Machine contact in the header field is not OK (No contact)


Q8: How long after disconnection before the message is shown?

    A8: Instantaneously


Q9: If an order was running before disconnection, will it be registered as a Stop?

    A9: If there is a cycle signal there will be a stop when the stop time limit reaches. If there is a production time signal the latest known signal will be 

the status. We have functionality that check the latest known signal of the blackbox inputs so there will be a minimum of “faulty” signal status if the

connection goes down.


Q10: How long after disconnection before the Stop start to register?

    A10: Depending on the settings on the measure point / article


Q11: If C1 is reconnected subsequently, how long before E1 and E2 know they are reconnected?

    A11: E2 is never disconnected, only if the power is off. E1 is reading from E2 every second.


Q12: After reconnection, how long before E1 pulls data from E2 ( or E2 starts sending buffered data to E1)?

    A12: 1 second


Q13: After receiving the buffered data, does RSP reconcile the information to remove the triggered Stop?

    A13: As soon as the Operator Tools client get data from the PLC and there is an ongoing production, the stop will end. If the machine is not 

producing, cycles will be transferred to the client and the stop will end but if the machine is not producing there will be a new stop. Is it a 

production time signal the stop will end if the machine signal is high.  



IF THE E1 PANEL IS SWITCH OFF OR NOT RESPONSIVE


Q14: Is there any auto-alert mechanism (through the cloud) to know that E1 is no longer responsive?

    A14: We don’t have this functionality today but there is a possibility to build with observations (Not included in standard edition of RS Production)


Q15: When E1 is not responsive, E2 will buffer the data from E3, correct?

    A15: Yes, but only the amount of cycles, not timestamps or production time signals (high/low)


Q16: If an order was running before E1 goes off / hangs, will it be registered as a Stop?

    A16: If it is a cycle signal it will registered as stop until it gets contact. It it uses a Production time signal (high/low) last known status will be shown.


Q17: How long after E1 goes off/hangs before the Stop start to register?

    A17: Depending on the measure point / article settings


Q18: After E1 come back on, how long before E1 pulls data from E2 ( or E2 starts sending buffered data to E1)?

    Q18: As soon as Operator Tools is logged in.


Q19: After receiving the buffered data, does RSP reconcile the information to remove the triggered Stop?

    A19: As soon as the Operator Tools client get data from the PLC and there is an ongoing production, the stop will end. 

If the machine is not producing, cycles will be transferred to the client and the stop will end but if the machine is not producing there will be a new stop. 

Is it a production time signal the stop will end if the machine signal is high.  



IF THE C3 IS DISCONNECTED



Q20: What message(s) will be shown on E1?

    A20: Status indicator in the right bottom corner will be yellow at the bottom


Q21: How long after disconnection before the message is shown?

    A21 Couple of seconds , up to 10 seconds


Q22: Where will the data be buffered? E1 or E2?

    A22: E1


Q23: If stored on E1, what happens if E1 is restarted or hangs after C3 is disconnected?

    A23: Data is stored on the hard drive. Data will be stored and transferred to the cloud when E1 is reconnected.


Q24: If an order was running before disconnection, will it be registered as a Stop?

    A24: No, as long as E1 have a connection to E2


Q25: How long after disconnection before the Stop start to register?

    A25: The disconnection (C3) to E4 have nothing to do with the data collection from E2 and will not affect stops


Q26: After re-connection, how long before buffered data starts to transfer?

    A26: Data is sent every ~10 second and begin to transfer when Operator Tools is logged in


Q27: After receiving the buffered data, does RSP reconcile the information to remove the triggered Stop?

    A27: C3 disconnection have nothing to do with stops in E1. But other clients will not get updated data from the affected client that 

is temporarily disconnected from the cloud



IF THE C2 IS DISCONNECTED





Q28: The only way to realize this visually is by looking at the LED indicators on the PLC, correct?

    A28: Yes, the inputs of the blackbox will not pulsate and the COMM lamp will not pulsate as frequently as before


Q29: If an order is running before C2 goes down, it will be registered as a Stop?

    A29: Yes


Q30: If an order is runnig before C2 goes down, is there an indicator or message on RSP to show no data is coming in from PLC after certain amount of time?

    A30: No message will occur. There will be a stop depending on the measure point / article settings. E1 is only looking on the connection status to E2, not to E3.