Belt Class
2/27/2008
Defines the programmatic interface for a UPOS Belt Device.
Namespace: Microsoft.PointOfService
Assembly: Microsoft.PointOfService (in microsoft.pointofservice.dll)
Syntax
'Declaration
Public MustInherit Class Belt
Inherits PosCommon
public abstract class Belt : PosCommon
public ref class Belt abstract : public PosCommon
public abstract class Belt extends PosCommon
public abstract class Belt extends PosCommon
Remarks
Required Version
The Belt class requires POS for .NET version 1.12 or later versions.
Capabilities
The Belt class supports the following methods to do the following:
Move the belt in forward direction.
Stop and reset the belt.
The Belt class may support several additional methods. These enable moving in backward direction, moving with different speeds, light barriers, security flap, controlling an automatic stop, and emergency stop. See the "General Model" section and the capabilities properties for specific information.
General Model
The general model of a Belt class is as follows:
After the belt is enabled, an application can call the MoveForward and StopBelt methods to control the motion.
If the CapMoveBackward property is true, the application may also call the MoveBackward method. The CapSpeedStepsBackward and CapSpeedStepsForward properties define how many speed steps the belt motor supports in backward and forward direction.
Because of safety regulations, a belt is usually equipped with security flaps at the end of the belt at both ends, if it can move backward. The CapSecurityFlapBackward and CapSecurityFlapForward properties indicate whether a device has a backward and forward security flap.
The P:Microsoft.PointOfService.Belt.CapAutoStopBackward and CapAutoStopForward properties indicate whether a belt supports an automatic motor stop in backward and forward direction.
Whether the application wants to use this feature can be controlled by setting the AutoStopBackward and AutoStopForward properties. The belt is stopped if an automatic stop condition is true. Usually such a condition is controlled by light barriers. However, it can also correspond to an internal state of the device which is not exposed. The condition is device-specific and has to be explained in the device documentation.
Light barriers may be available for handling an automatic stop feature. The CapLightBarrierBackward and CapLightBarrierForward properties indicate whether a device has a backward and forward light barrier.
If the CapAutoStopForwardItemCount property is true, the application may control the automatic stop feature depending on several items passing the light barrier or any other item counting mechanism in forward direction by calling the AdjustItemCount and ResetItemCount methods. In this case, the belt is automatically stopped if the AutoStopForwardItemCount property is zero and an additional item is detected. This feature may be also available for backward direction.
If the CapAutoStopForward property is true, an application may also delay automatic stop in forward direction by setting the AutoStopForwardDelayTime property. The delay time starts when an automatic stop condition becomes true. The belt is stopped when the delay time has expired. During delay time, automatic stop is canceled if the automatic stop condition becomes false. This feature may be also available for backward direction.
The application is informed about any status change with a StatusUpdateEvent event. All corresponding status properties are updated before event delivery.
An emergency stop occurs if one of the security flaps is open or the operator presses an emergency button. In this case, technical help is needed and the application has to reset the belt by calling the ResetBelt method. A security stop occurs if the belt has been stopped because of safety requirement regulations, but no technical help is needed.
Inheritance Hierarchy
System.Object
Microsoft.PointOfService.PosDevice
Microsoft.PointOfService.PosCommon
Microsoft.PointOfService.Belt
Microsoft.PointOfService.BasicServiceObjects.BeltBasic
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread-safe. Any instance members are not guaranteed to be thread-safe.