[Manageable Affordances TF] Safety Checks in Industrial Motor Drivers

[egekorkan]

Title: Safety Checks in Industrial Motor Drivers

Submitter(s):

Ege Korkan

Motivation:

Industrial devices like inverters, motor drivers etc. need to some checks with each state transition such as stopping a motor attached to the driver, reducing the load in an inverter.

Expected Participating Entities:

• A non-connected device like a motor
• A WoT Thing that is connected to the non-connected device
• A WoT Consumer

Workflow:

• Consumer sends a request (invokeaction) to change a state, e.g. stop motor, reduce load. The Consumer doesn't know that there is a state change, it is just a normal action for it

• The Thing receives the request, sends a simple acknowledgment back or no acknowledgment at all (in Modbus this is the case)

• When the Thing successfully changes to the desired state, a property would reflect this state.

• There is also a variant where there is a gateway that handles multiple state transitions and exposes a simple but long-running action to the Consumers.

Related Use Cases (if any):

None

Existing solutions:

None

Identified Requirements by the TF:

To be filled after submission. Examples of requirements include usage of specific communication protocols, media types, platforms, security and privacy mechanisms, or accesibility.

Comments:

A state machine of Modbus-based motor driver from Schneider Electric can be found here: https://download.schneider-electric.com/files?p_enDocType=User+guide&p_File_Name=ATV320_Modbus_manual_EN_NVE41308_01.pdf&p_Doc_Ref=NVE41308 . In page 42, you can see the state diagram where each transition has some physical checks behind.