Commit 496486c5 authored by 潘栩锋's avatar 潘栩锋 🚴

修复 KSL 由于 吹膜测厚360 改变,接口的变化

parent 105db657
......@@ -12,13 +12,7 @@ namespace FLY.KSL.Common
{
ERRNO_PLC_DISCONNECTED = new ERRNO() { Code = 255, Descrption = "加热PLC连接断开" };
#region 收卷
ERRNO_NO_FAN = new ERRNO() { Code = 0, Descrption = "风机没开,不能加热" , OffIsError=true};
ERRNO_OPEN_CIRCUIT = new ERRNO() { Code = 1, Descrption = "加热棒断路" };
ERRNO_SHORT_CIRCUIT = new ERRNO() { Code = 2, Descrption = "加热控制板短路" };
ERRNO_POWER_OFF = new ERRNO() { Code = 3, Descrption = "电源没开启或电流计损坏" };
ERRNO_NO_VELOCITY = new ERRNO() { Code = 4, Descrption = "线速度=0,没生产" };
#endregion
}
#region 报警类型
/// <summary>
......
......@@ -25,7 +25,7 @@ namespace FLY.KSL.Server
#region 服务器数据--------------------------------------------------------------
FLY.Thick.Blowing.Client.BlowingServiceClient blowingServiceClient;
FLY.Thick.Blowing360.Client.BlowingDetect360EncoderServiceClient bDetect;
FLY.Thick.Blowing.Client.BlowingDetectServiceClient bDetect;
FLY.Thick.Blowing.Client.BulkDbServiceClient bulkDbServiceClient;
/// <summary>
/// 报警系统
......@@ -70,7 +70,7 @@ namespace FLY.KSL.Server
blowingServiceClient = new FLY.Thick.Blowing.Client.BlowingServiceClient(FLY.Thick.Blowing360.OBJ_INTERFACE.OBJ_INTERFACE_ID.RENZIJIA_ID, "blowing");
bDetect = new FLY.Thick.Blowing360.Client.BlowingDetect360EncoderServiceClient(FLY.Thick.Blowing360.OBJ_INTERFACE.OBJ_INTERFACE_ID.BDETECT360EN_ID, "blowing");
bDetect = new FLY.Thick.Blowing.Client.BlowingDetectServiceClient(FLY.Thick.Blowing360.OBJ_INTERFACE.OBJ_INTERFACE_ID.BDETECT_ID, "blowing");
bulkDbServiceClient = new FLY.Thick.Blowing.Client.BulkDbServiceClient(FLY.Thick.Blowing360.OBJ_INTERFACE.OBJ_INTERFACE_ID.BULKDB_ID, "blowing");
#endregion
......
......@@ -19,8 +19,6 @@ namespace FLY.Thick.Blowing360.OBJ_INTERFACE
public const UInt32 BDETECT_ID = 30010;
public const UInt32 SCANWARNING_ID = 30011;
public const UInt32 BULKDB_ID = 30012;
public const UInt32 BDETECT360EN_ID = 30020;
/// <summary>
/// 3个
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment