diff --git a/WARNING-문제점.md b/WARNING-문제점.md new file mode 100644 index 0000000..cd4ddd1 --- /dev/null +++ b/WARNING-문제점.md @@ -0,0 +1,163 @@ +# 경고: async 메서드에서 await 미사용 (CS1998) + +## 경고 요약 + +``` +warning CS1998: This async method lacks 'await' operators and will run synchronously. +Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' +to do CPU-bound work on a background thread. +``` + +## 문제 설명 + +C#에서 `async` 키워드를 붙인 메서드 내부에 `await`가 하나도 없습니다. +이 경우 컴파일러는 경고를 출력하고, 메서드는 **동기적으로 실행**됩니다. +`async/await`의 비동기 이점을 전혀 살리지 못하는 상태입니다. + +## 발생 위치 및 상세 + +### 1. Hc900DbContext.cs:1306 - `ClearRecordsAsync()` + +```csharp +public async Task ClearRecordsAsync() +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +- **문제**: `async Task` 반환형인데 `await` 없음. `throw`는 동기 연산. +- **원인**: OPC UA 관련 메서드로서 HC900Crawler에서는 사용하지 않는 스텁 메서드. + +### 2. Hc900DbContext.cs:1311 - `BuildMasterFromRawAsync()` + +```csharp +public async Task BuildMasterFromRawAsync(bool truncate = false) +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +- **문제**: 동일하게 `async` 키워드만 있고 `await` 없음. +- **원인**: OPC UA 기반 빌드 메서드, HC900Crawler에서는 미사용. + +### 3. Hc900DbContext.cs:1319 - `GetNameListAsync()` + +```csharp +public async Task> GetNameListAsync() +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +- **문제**: `async` 키워드만 있고 `await` 없음. +- **원인**: OPC UA 관련 메서드, HC900Crawler에서는 미사용. + +### 4. Hc900DbContext.cs:1324 - `GetMasterStatsAsync()` + +```csharp +public async Task GetMasterStatsAsync() +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +- **문제**: `async` 키워드만 있고 `await` 없음. +- **원인**: OPC UA 관련 메서드, HC900Crawler에서는 미사용. + +### 5. Hc900DbContext.cs:1337 - `BuildRealtimeTableAsync()` + +```csharp +public async Task BuildRealtimeTableAsync(IEnumerable groups) +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +- **문제**: `async` 키워드만 있고 `await` 없음. +- **원인**: PointBuilder 관련 메서드, HC900Crawler에서는 미사용. + +### 6. Hc900DbContext.cs:1342 - `PreviewRealtimeBuildAsync()` + +```csharp +public async Task PreviewRealtimeBuildAsync( + IEnumerable<(string GroupKey, PointBuilderGroupDto Group)> groups) +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +- **문제**: `async` 키워드만 있고 `await` 없음. +- **원인**: PointBuilder 관련 메서드, HC900Crawler에서는 미사용. + +### 7. Hc900DbContext.cs:1726 - `QueryMasterAsync()` + +```csharp +public async Task QueryMasterAsync( + int? minLevel, int? maxLevel, string? nodeClass, + IEnumerable? names, string? nodeId, string? dataType, + int limit, int offset) +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +- **문제**: `async` 키워드만 있고 `await` 없음. +- **원인**: OPC UA 노드 맵 쿼리 메서드, HC900Crawler에서는 미사용. + +### 8. Hc900DbContext.cs:1735 - `GetRealtimeNodeDataTypesAsync()` + +```csharp +public async Task> GetRealtimeNodeDataTypesAsync() +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +- **문제**: `async` 키워드만 있고 `await` 없음. +- **원인**: OPC UA 관련 메서드, HC900Crawler에서는 미사용. + +## 수정 방안 + +### 권장: `async` 키워드 제거 (가장 단순하고 명확) + +`throw`만 하는 스텁 메서드는 `async`가 필요 없습니다. `async` 키워드를 제거하고 `Task`를 직접 반환하면 됩니다. + +```csharp +// 수정 전 +public async Task ClearRecordsAsync() +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} + +// 수정 후 +public Task ClearRecordsAsync() +{ + throw new NotImplementedException("OPC UA method not applicable in HC900Crawler"); +} +``` + +`Task.FromResult()`로 감쌀 필요도 없습니다. `throw`는 즉시 예외를 발생시키므로 `Task` 래핑이 필요 없으며, 호출 측에서 `await` 시에도 정상적으로 예외가 전파됩니다. + +### 대안: `async` 유지 + `Task.FromResult()` 사용 (불필요한 오버헤드) + +```csharp +public async Task ClearRecordsAsync() +{ + return Task.FromResult(0); +} +``` + +- **비추천**: 불필요한 상태 기계(state machine) 생성 오버헤드 발생. +- `throw`만 하는 메서드에 `async`는 전혀 의미가 없음. + +## 수정 대상 파일 + +- `src/Infrastructure/Database/Hc900DbContext.cs` + - 라인 1306, 1311, 1319, 1324, 1337, 1342, 1726, 1735 + - 총 8개 메서드에서 `async` 키워드 제거 + +## 수정 후 기대 효과 + +1. CS1998 경고 8건 모두 제거 +2. 불필요한 async 상태 기계 생성 오버헤드 제거 (매 호출마다 ~수십 바이트 스택 할당 제거) +3. 코드 가독성 향상 (async가 진짜 비동기 연산이 있는 곳에만 사용됨) diff --git a/docs/Controller.csv b/docs/Controller.csv new file mode 100644 index 0000000..4a13cce --- /dev/null +++ b/docs/Controller.csv @@ -0,0 +1,11 @@ +ItemName,Class,Tag,TagDeleted,ItemNumber,ItemDescription,DownloadedName,Target,DateModified,DateDownloaded,DynamicScan,DynamicScanPeriod,AssociatedAsset,IPAddress2,IPAddress1,ControlDelay,WriteDelay,TimeSync,DiagAddress,Flags,BaudRate,Code4PacketLimit,Code3PacketLimit,Code2PacketLimit,Code1PacketLimit,ControllerDeviceType,ControllerDataTable,ControllerOffset,ControllerDeviceID,ControllerMarginal,ControllerFail,ControllerChannelName,DisableAlternatePolling +C1,UniversalModbusController,FALSE,FALSE,RTU00001,,,,2025-07-23T15:51:10.310,2025-06-14T18:52:51.660,FALSE,1,$UNASSIGNEDITEMS,192.168.1.250,192.168.0.250,,,,,,,,,,,HC900,Holding Registers Lower,0,1,5,10,CHAUNI0,FALSE +C2,UniversalModbusController,FALSE,FALSE,RTU00002,,,,2025-07-23T15:51:10.313,2025-06-14T18:52:51.660,FALSE,1,,192.168.1.230,192.168.0.230,,,,,,,,,,,HC900,Holding Registers Lower,0,1,5,10,CHAUNI0,FALSE +C3,UniversalModbusController,FALSE,FALSE,RTU00003,,,,2025-07-23T15:51:10.317,2026-05-02T17:01:26.080,FALSE,1,,192.168.1.240,192.168.0.240,,,,,,,,,,,HC900,Holding Registers Lower,0,1,5,10,CHAUNI0,FALSE +C4,UniversalModbusController,FALSE,FALSE,RTU00004,,,,2025-07-23T15:51:10.317,2025-06-14T18:52:51.660,FALSE,1,,192.168.1.220,192.168.0.220,,,,,,,,,,,HC900,Holding Registers Lower,0,1,5,10,CHAUNI0,FALSE +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +ItemName,Class,Tag,TagDeleted,ItemNumber,ItemDescription,DownloadedName,Target,DateModified,DateDownloaded,DisableAlternatePolling,DynamicScan,DynamicScanPeriod,AssociatedAsset,ControllerMarginal,ControllerFail,ControllerChannelName,ControllerBaseNode,ControllerStaleLastUsable,ControllerUseOpcTimestamp,LinkAEndpointUrl,LinkBEndpointUrl,SecurityMode,SecurityLevel,LoginType,,,,,,,, +CONOUA1,OPCUAController,FALSE,FALSE,RTU00007,,,,2026-04-26T18:27:17.520,2026-04-26T18:27:24.007,FALSE,TRUE,1,,5,10,CHAOUA1,,FALSE,FALSE,192.168.0.132:4841,0.0.0.0:4840,NONE,,ANONYMOUS,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +ItemName,Class,Tag,TagDeleted,ItemNumber,ItemDescription,DownloadedName,Target,DateModified,DateDownloaded,TransactionIDForModbusTCP,DynamicScan,DynamicScanPeriod,AssociatedAsset,MODUSEFN16,AsciiNoCRLF,ModiconDiagnostic,IPAddress2,IPAddress1,IPPortNumber1,IPPortNumber2,ModiconProtocol,ModiconType,ModiconStationID,ModiconOffset,ControllerMarginal,ControllerFail,ControllerChannelName,DisableAlternatePolling,,,, +DBSVR,ModiconController,FALSE,FALSE,RTU00005,Database Server Status check Controller ModbusTCP,,,2026-02-07T20:53:33.317,2026-02-07T20:53:40.740,TRUE,FALSE,1,,FALSE,FALSE,0,192.168.1.0,192.168.0.70,5020,5020,Modbus TCP,Holding Register,1,0,25,50,CHAMOD0,FALSE,,,, diff --git a/docs/HC900-PID.txt b/docs/HC900-PID.txt new file mode 100644 index 0000000..a9d98b1 --- /dev/null +++ b/docs/HC900-PID.txt @@ -0,0 +1,137 @@ +Home > Function Block Information > Function Block Directory > Loop Blocks > PID + +PID +PID.gif + +Description + +The PID label stands for Proportional, Integral, and Derivative (3-mode) control action. This block is part of the Loop Blocks category. + +Function + +Provides Proportional (P, Integral (I and Derivative (D, (3-mode) control action based on the deviation or error signal created by the difference between the setpoint (SP) and the Process Variable analog input value (PV). + +It provides two digital output signals for alarms based on configured parameters. + +The PID function block provides for Feedforward, Cascade, and Ratio control. + +Automatic tuning with Fuzzy Logic Overshoot Suppression can be configured. + +Digital inputs may be used to set control mode, select the setpoint source, change control action plus other discrete actions. + +Inputs + +PV = Process Variable Analog Input value in Engineering Units to be controlled + +RSP = Remote Setpoint Analog Input value in Engineering Units or Percent to provide external setpoint + +FFV = Feedforward value in percent. The Feedforward value is multiplied by the Feedforward Gain, then directly summed into the output of the PID block + +TRV = Output Track value in Percentage (PID Output = TRV Input when TRC = ON.) + +TRC = Output Track Command [ON, OFF (On -Enables TRV.) (Mode = Local Override) + +BIAS = Remote Bias value for Ratio PID + +SWI = Switch Inputs (from SWO on LPSW function block) + 0 = No Change + 1 = Initiate Autotuning + 2 = Change Control Action + 4 = Force Bumpless Transfer + 8 = Switch to Tune Set 1 + 16 = Switch to Tune Set 2 + +MDRQI = External Mode request (typically connected to the MDRQO output of a MDSW function block that encoded discrete switch inputs). + + 0 = No Change + 1 = Manual Mode Request + 2 = Auto Mode Request + 4 = Local Mode Request + 8 = Remote Mode Request + +BCI = Back Calculation Input (for blocks used as Cascade Primary + +Outputs + +OUT = Control Output + +WSP = Working Setpoint in Engineering Units for monitoring + +AL1 = Alarm 1 - Digital Signal + +AL2 = Alarm 2 - Digital Signal + +DIRECT = Direct Acting control (ON = Direct, OFF = Reverse Acting) + +ATI = Autotune Indicator (ON = Autotune in Progress) + +MODE = Loop mode status (typically connected to the Mode Flags block for encoding). Value indicates modes as follows: + 0.0 RSP AUTO + 1.0 RSP MAN + 2.0 RSP Initialization Manual (See Note 1) + 3.0 RSP Local Override (See Note 1) + 4.0 LSP AUTO + 5.0 LSP MAN + 6.0 LSP Initialization Manual (See Note 1) + 7.0 LSP Local Override (See Note 1) + +BCO - Back Calculation Output (for blocks used as Cascade Secondary)—See Note 2. + +NOTE 1. +When a request to change from Auto to manual is received and: + - the request comes from the operator Interface, the request is ignored. + + - the request comes from the Mode Switch (MDSW) function block, the request is retained + and when leaving the Initialization Mode or Local Override Mode the loop will go to manual. + +NOTE 2. +BCO output is provided for applications where the block is used as a cascade secondary. +BCI input is provided for applications where the block is used as a cascade primary. When the BCO output of a secondary loop is connected to the BCI input of a primary loop, bumpless transfer is achieved when the secondary is switched into remote setpoint (i.e., cascade) mode. In addition, the primary loop is prevented from reset windup when the secondary is de-coupled from the process. The secondary is de-coupled from the process when it is in local setpoint mode or manual output mode or has reached a setpoint or output limit or is integral limiting because of its BCI input. + + + +Operation details + +The PV Hi/Lo range values configured in the PID-Range/Limit Tab determine the points at which the block status changes to a fail condition, driving the output to the configured failsafe value. There is no dead band for these PID block limits. To prevent the loop from going to failsafe, the user can adjust the PV Hi/Lo settings to allow for slight variations of the PV value from an AI channel that operates at or near these limits. Additionally, if the PV value exceeds the configured limits, the PID block will indicate a PV out of range status and will cause the bad block pin of the system monitor block to energize. + +When the control mode is switched from Manual to Automatic, the mode switchover is bumpless and the PID loop's integration time is set to zero. Control Action is then determined by the control loop configuration and tuning. + +In version 4.X controller firmware, the system default is set to cause a manual mode to override the Track command; the user has the option to change this setting in HC Designer to allow the Track command to override the Manual mode output. This action is a master setting and cannot be configured per loop. Loop Mode Priority + +When the output of a PID loop is driven to the Hi or Lo Output limit, the integral value is clamped to prevent reset wind up. + + + +Configurable Parameters + +The PID properties dialog box is divided into 7 tab cards + +Click on the tab name below to access the Configurable Parameters for that tab. + +GENERAL +START/RESTART +RSP +RANGE/LIMIT +TUNING +ACCUTUNEIII +ALARMS + + + +Other Control Blocks + +CARB - Carbon Potential + +TPSC - Three Position Step + +ONOFF - + +AMB - Auto/Manual Bias + + + +Associated Blocks + +Setpoint Programmer Blocks + +Setpoint Scheduler Blocks diff --git a/docs/HW_Universal_Modbus/Concepts/About_configuring_history_backfill-QB5.htm b/docs/HW_Universal_Modbus/Concepts/About_configuring_history_backfill-QB5.htm new file mode 100644 index 0000000..61e8cbf --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/About_configuring_history_backfill-QB5.htm @@ -0,0 +1,252 @@ + + + + + + + + About configuring history backfill + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

About configuring history backfill

+

+ Most of the configuration tasks associated with using the HC900 Hybrid controller. history backfill functionality must be performed at the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. level using the HC (Hybrid Control) Designer software. This involves configuring a Trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. Rate function block Also known as FB. An executable software object that performs a specific task, such as measurement or control, with inputs and outputs that connect to other entities in a standard way. They can be connected and grouped together to construct simple or complex control strategies. You can view function blocks as a symbol, configuration form, as part of a strategy, or as a user-defined view in an operator schematic. See also: function block configuration form, function block faceplate, function block symbol. and several Trend Point function blocks on the controller. Refer to the HC (Hybrid Control) Designer documentation for further details.

+

After you have assigned points to the Trend Point function block A unit of data and operation within Experion. Experion uses blocks as the component from which control strategies are built. The two categories of blocks are hardware entities and functional entities. in the controller, these points must also be assigned to standard history The type of history that collects one-minute snapshots of point parameter values, as well as a number of averages based on those one-minute snapshots. Compare: exception history, extended history, fast history. See also: history, point parameter. on the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS.. This can be done using Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. (recommended) or directly in Station Experion's main operator interface. Station presents information using a series of displays. See also: display. via the History Assignment displays. You can optionally configure History Archiving (see the topic "History Archiving" in the Server and Client Configuration Guide).

+

Configuring history backfill

+

To allow the history backfill process to operate, you need to change some server settings. Use Station to make these changes.

+

ATTENTION: Selecting to enable history backfill using the steps below does not trigger a backfill of history; it only enables the history backfill option.

To trigger a backfill of history for a particular controller, go to that controller’s status display and clear the Enable History Backfill check box for at least one minute. Then, select the Enable History Backfill check box. This will trigger history backfill for that controller.

In HC (Hybrid Control) Designer, when configuring Trend Backfill Log Point Selection, you must select Use Modbus Address.

+

To configure history backfill:

+
    +
  1. +

    From the Station menu, choose ConfigureSystem HardwareServer Wide Settings.

    +
    2. +
  2. +

    Select the History Backfill tab.

    +
    3. +
  3. +

    Select the Enable history backfill check box to enable history backfill.

    +
    4. +
  4. +

    In the Maximum number of days to backfill box, enter the maximum number of days that history can be backfilled (23 recommended).

    +

    Any event data older than this number of days will be discarded and will not be inserted into history. This maximum number of days must not exceed the number of days of standard history snapshots that is configured for the system.

    +
    5. +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/About_history_backfill-QB5.htm b/docs/HW_Universal_Modbus/Concepts/About_history_backfill-QB5.htm new file mode 100644 index 0000000..f2ad829 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/About_history_backfill-QB5.htm @@ -0,0 +1,241 @@ + + + + + + + + About history backfill + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ About history backfill

+

HC900 Hybrid controller. firmware versions later than v4.4 support an historical data collection function. The Trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. Point function blocks added to the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. configuration allow the controller to buffer point values that are collected at configurable rates.

+

When this function is configured in the controller, the buffered data can be used to populate history on the Experion server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. if a controller is disconnected from the server and cannot collect point values via normal scanning. The process used is called history backfill and is initiated when the controller comes back online after it has been disconnected for more than one minute. This disconnection could be due to:

+
    +
  • the controller failing due to a communications failure
    • +
  • the controller being diabled (Out of service)
    • +
+

The history backfill function only supports standard history The type of history that collects one-minute snapshots of point parameter values, as well as a number of averages based on those one-minute snapshots. Compare: exception history, extended history, fast history. See also: history, point parameter. 1 minute snapshots for analog and status points. When history is backfilled, value/timestamp pairs are read from all configured trend buffers in the controller. These are then inserted into standard history snapshots as if they were read by the server at the value's timestamp.

+

The history backfill function is a licensable option.

+
CAUTION: For points that have history backfill configured: +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Architectures_for_Honeywell_Universal_Modbus-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Architectures_for_Honeywell_Universal_Modbus-QB5.htm new file mode 100644 index 0000000..702c5b8 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Architectures_for_Honeywell_Universal_Modbus-QB5.htm @@ -0,0 +1,232 @@ + + + + + + + + Architectures for   Universal Modbus + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Architectures for Honeywell Universal Modbus

+

Many different types of controllers can be connected to the same Universal Modbus network. The only requirements are that every controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. on the same network uses the same connection type, the same baud, and that each controller has a unique device identification number. 

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Configuring_SPP_monitoring-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Configuring_SPP_monitoring-QB5.htm new file mode 100644 index 0000000..b7d841a --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Configuring_SPP_monitoring-QB5.htm @@ -0,0 +1,374 @@ + + + + + + + + Configuring SPP monitoring + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Configuring SPP monitoring

+

The user may view and control the current state of set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. programs in the HC900 Hybrid controller. and UMC800 controllers from one of three monitoring displays. The SPP Setpoint in percent. See also: setpoint parameter. Summary displays allows the user to monitor the first four programmers in a given HC900 or UMC800 controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC.. This display provides information about the SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. programmers, including their current state and segment number, the segment time remaining, and a history of the current program.

+

The SPP Program display allows the user to view the program configuration of a specific programmer. This display is very similar to the Profile Configuration display in that it shows a time-based program of 2 to 50 segments in length, where each segment of the program can be a ramp or soak except the last segment that must be a soak. The difference is that the SPP Program display reads and writes a set point program from an SP programmer, and does not store the program in the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. database.

+

The SPP Trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. display allows the user to view the history of an SP programmer and compare it to the ideal profile. To collect history, a point needs to be built for each SP programmer in a controller. These points are used to monitor the process PVs driven by the primary 1. For Regulatory Control blocks in a cascade strategy: A primary is an upstream block from which an initializable input is fetched. A block has one primary for each initializable input. See also: block. 2. The controller (or chassis) that is currently controlling the redundant process by carrying out the assigned functions. Compare: secondary. See also: assigned function, chassis, controller redundancy. and auxiliary outputs of the programmers, collecting the values and storing them in history.

+

Building points for SPP monitoring

+

Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. can be used to build the points for monitoring the SP programmers. The points must be of 'Analog' type, and a unique point must be created for each programmer. The source addresses used to monitor SP Programmer 1 in an HC900 or UMC800 controller are described below.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

Table 5-1: SP Programmer 1 Parameter Definition

+
Parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter. + + Source Address +
+

PV The process variable. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. +

+ 		+

Address the PV being driven by the output of SPP 1 in your process. See below for an example.

+
+

AL1

+ 		+

PV high value

+
+

AL2

+ 		+

PV low value

+
+

SP

+ 		+

SPP 1 OUT

+
+

A1

+ 		+

Address the PV being driven by the auxiliary output of SPP 1 in your process. See below for an example.

+
+

AL3

+ 		+

A1 high value

+
+

AL4

+ 		+

A1 low value

+
+

A2

+ 		+

SPP_ADD 1 AUX_OUT

+
+

A3

+ 		+

SPP 1 STATUS_HOLD

+
+

A4

+ 		+

SPP 1 STATUS_END

+
+

The point should also be configured with:

+ +

The following diagram illustrates a typical HC900/UMC800 configuration. In this example, when configuring a point in Station Experion's main operator interface. Station presents information using a series of displays. See also: display. to track programmer block A unit of data and operation within Experion. Experion uses blocks as the component from which control strategies are built. The two categories of blocks are hardware entities and functional entities. SPP3, you should configure the point's PV parameter to read the PV of loop PID2, and its A1 parameter to read the calculated PV from CARB5.

+

Figure 5-1: Example SPP Implementation

+

+ +

+

To monitor the other SP programmers, create a new point for each programmer and replace the '1' in the Source Address with the given programmer number (valid 1 to 4). Each point must have a unique name. Repeat this process until you have created points for each programmer. When all points have been built, download them to the server database. See the Server and Client Configuration Guide for information on points.

+

To configure SPP monitoring

+
    +
  1. +

    Disable the HC900 HC900 & UMC800 channels.

    +
    2. +
  2. +

    Select ConfigureApplicationsHC900/UMC800Programmer Operation.

    +

    The SPP Summary display opens.

    +
    3. +
  3. +

    For each HC900 and UMC800 controller, enter each point configured for this controller in the appropriate slot.

    +
    4. +
  4. +

    Enable the channels.

    +

    You can verify the SPP monitoring by checking that the primary and auxiliary SP follow that of the programmers (displayed on the controller faceplate A specialized pop-up that shows a subset of the details shown on the matching point detail (or template) display. It typically shows the point's runtime values and control settings. A faceplate appears when an operator clicks an object that is linked to a point. See also: point, point detail display.).

    +
    5. +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Configuring_a_combined_recipe-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Configuring_a_combined_recipe-QB5.htm new file mode 100644 index 0000000..ae446b8 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Configuring_a_combined_recipe-QB5.htm @@ -0,0 +1,270 @@ + + + + + + + + Configuring a combined recipe + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Configuring a combined recipe

+

A combined recipe is a combination of a recipe, up to two set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. profiles, and a list of Compatible Destinations.

+

Each combined recipe can be associated with a number of destinations, any one of which can be selected by the operator as a target for the combined recipe. Each destination includes an HC900 Hybrid controller. or UMC800 controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC., a set point programmer for each profile in the combined recipe, and an optional variable suffix. This suffix is appended to every variable in the recipe component of a combined recipe, before it is sent to a controller. This allows the same recipe to be used for more than one set of variables in a single HC900 or UMC800 controller if the controller is used to control multiple, similar processes. It is up to the user to configure the Variable tag names with the proper suffixes in the controller configuration so that the recipe with values for the Variables with these suffixes can be loaded from the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. database. An error is posted if these Variable tag names are not found on download.

+

When a combined recipe is loaded to a controller, the SPP Setpoint in percent. See also: setpoint parameter. profiles are loaded into the specified programmers and the recipe is loaded to the controller's configuration.

+

Up to 1,000 combined recipes can be created and maintained using the Station Experion's main operator interface. Station presents information using a series of displays. See also: display. HC900/UMC800 Combined Recipe Configuration displays.

+

To configure a combined recipe

+
    +
  1. +

    In Station, select Configure>Applications>HC900/UMC800>Combined Recipes. The Combined Recipe Selection display opens.

    +
    2. +
  2. +

    Select the combined recipe that you want to configure or modify, or click a blank slot to create a new combined recipe.

    +
    3. +
  3. +

    Click on its name to load the combined recipe.

    +
    4. +
+

The Combined Recipe Configuration display allows combined recipes to be configured and stored in the server database. Changes made to configuration are applied immediately to the stored combined recipe, but do not have any immediate effect on profiles or variable values currently loaded in HC900 or UMC800 controllers.

+

There are three optional components to a combined recipe. The first is a recipe selected from the 1,000 recipes stored in the server database (see the topic titled "Configuring a recipe" for information on recipes). The remaining components are up to two SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. profiles, selected from the 1,000 profiles stored in the server database (see the topic titled "Configuring an SP profile" for information on SP profiles). A combined recipe may include any, some, or none, of these components.

+

Destination list

+

Each combined recipe may be configured with up to 20 Compatible Destinations. This allows a single combined recipe to drive a number of processes in a given plant. For example, the same combined recipe may be used to operate three furnaces – where a different SP programmer in a controller, and a different set of variables, control each furnace. The recipe Variable suffix allows the same Combined Recipe to be directed to another set of Variables with the same function for a similar process in the controller.

+

Name

+

Each destination may be given a name to more easily identify the process it drives.

+

Controller

+

Each destination has a controller to which each component of the combined recipe is downloaded.

+

Prog A & B

+

These identify the SP programmers in the destination controller to which profiles A and B will be downloaded.

+

Var. Suffix

+

Identifies a short string that will be appended to every variable name in the recipe component of a combined recipe before it is downloaded. This allows the same recipe to be loaded to a number of subsets of variables within the same controller.

+

For example, assume the recipe contains the variables TEMP, VOLUME, and PRESS.

+
    +
  • +

    If destination FURNACE1 has a variable suffix of 1 and destination FURNACE2 has a variable suffix of 2, then when the combined recipe is downloaded to FURNACE2, the variables updated will be TEMP2, VOLUME2, and PRESS2.

    +
    • +
  • +

    If the destination had been FURNACE1, then TEMP1, VOLUME1, and PRESS1 would have been updated.

    +
    • +
+

Download

+

See the topic titled "Downloading a combined recipe" for information on downloading a combined recipe.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Configuring_a_recipe_HW_UM.htm b/docs/HW_Universal_Modbus/Concepts/Configuring_a_recipe_HW_UM.htm new file mode 100644 index 0000000..9a32d8c --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Configuring_a_recipe_HW_UM.htm @@ -0,0 +1,253 @@ + + + + + + + + Configuring a recipe + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Configuring a recipe

+

A recipe is a collection of 50 Variable signal tags and their values or states. Each Variable is either a digital or analog element in a control configuration, acting as an input to any connected function blocks. When a recipe is loaded, the values or states of the signal tags in the recipe replace the values of those signals in the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC.'s configuration.

+

Up to 1,000 recipes can be created and maintained using the Station Experion's main operator interface. Station presents information using a series of displays. See also: display. HC900 Hybrid controller. and UMC800 Recipe Configuration displays.

+

To configure a recipe

+
    +
  1. +

    In Station, select ConfigureApplicationsHC900/UMC800Recipes (Variables Only).

    +

    The Recipe Selection display opens.

    +
    2. +
  2. +

    Click the recipe that you want to configure or modify, or click a blank slot to create a new recipe.

    +
    3. +
  3. +

    Click on the recipe name to load its configuration.

    +
    4. +
+

When the Recipe Configuration display opens, the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. attempts to read a list of all variables from the currently selected Compatible controller. If the controller is not a valid HC900 or UMC800 controller or the upload fails, an alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. is raised.

+

The variable list does not overwrite any of the variables configured in the current recipe, nor do variables in the recipe need to be members of the list. Instead, the list is used to provide default selections in the 'Variable' boxes to help when configuring a recipe.

+

By changing the controller selection from the Compatible controller drop-down list, the server attempts to read a new list of variables from the controller. If the controller is not a valid HC900 or UMC800 controller or the upload fails, an alarm is raised.

+

ATTENTION: Only the first 75 variables configured on an HC900 are used to populate the variable list. While additional variables (up to 255) are not visible in the list, they can still be added to a recipe.

HC900 controllers prior to Rev 4.0 firmware support 8–character variable names. HC900 controllers Rev 4.0 and above support 16–character variable names.

The recipe download will fail if the variable name does not exist in the controller or a variable name is repeated in the recipe.

+

Download to controller

+

Allows the user to download the current recipe to an HC900 or a UMC800 controller. A recipe can be downloaded to any controller, not just the 'Compatible controller.' See the topic titled "Downloading a recipe" for information on downloading a recipe.

+

See the topic titled "Configuring a combined recipe" for information on configuring a recipe for use in a combined recipe.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Configuring_an_SP_profile-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Configuring_an_SP_profile-QB5.htm new file mode 100644 index 0000000..ff3f71e --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Configuring_an_SP_profile-QB5.htm @@ -0,0 +1,257 @@ + + + + + + + + Configuring an SP profile + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Configuring an SP profile

+

An SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. profile is a time-based program typically used as the set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. of a control loop. Each program may be from 2 to 50 segments in length, where each segment of the program may be a ramp or a soak, except the last segment, which must be a soak.

+

In addition to the main output value, a second analog value is available for each step of the program. This output is a fixed soak value, which may be used as an input to another function or to provide a set point for a secondary 1. A Regulatory Control block whose control input is pushed from another Regulatory Control block. See also: block. 2. The controller (or chassis) in a redundant configuration that would assume primary status and responsibility of the assigned functions if the previous primary controller failed. See also: assigned function, chassis, controller, primary. control loop in the process, such as pressure or % carbon.

+

A set point guarantee function is provided that holds the program if a process variable Normally abbreviated as PV. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. exceeds a predefined deviation from the set point. The set point guarantee can be selected to be active for the entire program, for soaks only, or for user specified segments.

+

Up to 1,000 profiles can be created and maintained using the Station Experion's main operator interface. Station presents information using a series of displays. See also: display. HC900 Hybrid controller. and UMC800 Profile Configuration displays.

+

To configure an SP profile

+
    +
  1. +

    In Station select Configure>Applications>HC900/UMC800>Set Point Programs>Profile Setup.

    +

    The Profile Selection display opens.

    +
    2. +
  2. +

    Select the profile that you want to configure or modify, or click a blank slot to create a new profile.

    +
    3. +
  3. +

    Click the profile name to load its configuration.

    +
    4. +
+

The Profile Configuration display allows all the details of an SP profile to be edited from a single display. Changes made to configuration are applied immediately to the stored profile, but do not have any effect on profiles that are currently loaded into HC900 and UMC800 controllers.

+

Program control

+

Values such as Restart Rate and Loop Segment control the dynamic execution of a program. These values can be shown or hidden using the Show/Hide button.

+

Clone a profile

+

Allows the user to copy all the details of another of the 1,000 stored profiles to the current profile slot. The Name field is not copied and made blank.

+

Upload from controller

+

Allows the user to upload the profile currently loaded in an HC900 or UMC800 SP programmer into the profile slot currently being edited.

+

Download to controller

+

Allows the user to download the current profile or changes to program segments to an HC900 SP programmer, provided the programmer is in the Ready or Hold mode. See the section 'Downloading an SP profile' for information on downloading a profile.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Honeywell_Universal_Modbus_connections-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Honeywell_Universal_Modbus_connections-QB5.htm new file mode 100644 index 0000000..d5fec81 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Honeywell_Universal_Modbus_connections-QB5.htm @@ -0,0 +1,423 @@ + + + + + + + +   Universal Modbus connections + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Honeywell Universal Modbus connections

+

Control Products controllers are designed to communicate using the Modbus TCP Modbus is a serial communications protocol. Ethernet, RS485, or RS-232 specification. See the User Manual specific to your Control Products controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. for information about cabling requirements.

+

Devices using RS-232 can be connected directly to a RS-232 port on the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS., or to a terminal server A terminal server allows you to connect several controllers and Stations to a LAN even though they only have serial or parallel ports. Most terminal servers also provide a range of serial connection options, such as RS-232, RS-422, and RS-485. See also: controller, LAN, Station..

+

Two methods are supported for connecting the server to an RS-485 network of Control Products controllers:

+
    +
  • +

    Using an RS-232 to RS-485 converter (see the section below titled "Using an RS-232/RS-485 converter")

    +
    • +
  • +

    Directly connecting the server to the RS-485 network via an add-in card (see the section below titled "Using an RS-485 adapter")

    +
    • +
+

You can also connect to Ethernet TCP/IP Transmission control protocol/internet protocol. A standard network protocol. networks using Modbus/TCP Transmission Control Protocol. protocol using two methods:

+
    +
  • +

    Direct Ethernet Connection (HC900 Hybrid controller., single or redundant networks, Trendview/X-Series Paperless Recorder)

    +
    • +
  • +

    Ethernet - Modbus bridge (internal option for UMC800, DPR180, and DPR250)

    +
    • +
+

Make sure that you read the User Manual specific to your Control Products controller before connecting your controllers to the network.

+

Using an RS-232/RS-485 converter

+

Honeywell recommends that you use the Black Box LD485-HS RS-232/RS-485 Interface Converter, model number ME837A, or a Black Box IC109A-R2. These converters have been qualified by Honeywell. Use of another converter might produce unexpected results.

+

Figure 1-1: RS-232 to RS-485 converter

+

+ +

+

Connect an RS-232 port on the server to the RS-232 port on the Black Box converter using a standard RS-232 straight through cable. Then connect the Black Box converter and the Control Products controllers to the RS-485 network as shown below.

+

Black Box connections

+

Figure 1-2: Black Box (2-wire) connections

+

+ +

+

Figure 1-3: Black Box (4-wire) Connections

+

+ +

+

Ensure that the Black Box switches are configured with the following settings.

+

An asterisk (*) designates the factory-preset jumper A movable device for providing an electrical connection or short between two points on a circuit board for the purpose configuring the equipment for a specific function or operation. settings.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Switch A multiport device that moves Ethernet packets at full wire speed within a network. A switch may be connected to another switch in a network. See also: Ethernet, network. + + Setting + + Description +
+

XW1A

+ 		+

jumper in*

+ 		+

Configure RS-232 port as DCE.

+
+

XW1B

+ 		+

jumper out

+ 		+

Do not configure RS-232 port as DTE Data terminal equipment..

+
+

W8

+ 		+

B-C

+ 		+

2-wire (half-duplex) operation.

+
+

W9

+ 		+

C*

+ 		+

0 ms RTS/CTS Request to send/clear to send. delay.

+
+

W15

+ 		+

B-C

+ 		+

RS-485 transmitter enabled by data.

+
+

W5

+ 		+

A-B*

+ 		+

RTS/CTS normal.

+
+

W17

+ 		+

C

+ 		+

2 ms transmitter enabled time. This is good for 9600 baud. Decrease for higher baud; increase for lower baud.

+

A - 30 ms

+

B* - 7 ms

+

C - 2 ms

+

D - 0.7 ms

+

E - 0.15 ms

+
+

W16

+ 		+

B*

+ 		+

0.1 ms delay before receiver enabled.

+
+

Term

+ 		+

ON

+ 		+

RS-485 receiver terminated.

+
+

Bias

+ 		+

OFF*

+ 		+

Line bias off.

+
+

Using an RS-485 adapter

+

Honeywell recommends using the Stallion EasyConnection 8/32 ISA 1.Industry standard architecture. 2. International Society of Automation. Mission is to maximize the effectiveness of ISA members and other practitioners and organizations worldwide to advance and apply the science, technology, and allied arts of instrumentation, systems, and automation in all industries and applications. For more information, refer to http://www.isa.org/., 8/32 PCI, 8/64 ISA, or 8/64 PCI adapters with the Stallion RS-232 to RS-485 8-port dual interface asynchronous module In SafeView, the file name and path of an executable file name. An application's module is one of the three means by which an application's display window can be “matched” and thus managed by SafeView. The other two are window title and window category.. Honeywell has qualified this adapter. Use of another adapter may produce unexpected results.

+

Figure 1-4: Stallion EasyConnection Adapter

+

+ +

+

Installing the Stallion EasyConnection serial adapter

+

Stallion EasyConnection serial adapters are suitable for connection to RS-232, RS-422, and RS-485 devices.

+

Install the adapter, port module, and driver in the server as described in the Stallion documentation.

+

Connect a port on the Stallion port module directly to the RS-485 network as shown below. Next, connect your Control Products controllers to the RS-485 network.

+

Figure 1-5: Stallion RS-485 (2-wire) connections

+

+ +

+

Figure 1-6: Stallion RS-485 (4-wire) connections

+

+ +

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Migration_conversion_requirements-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Migration_conversion_requirements-QB5.htm new file mode 100644 index 0000000..6bc813c --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Migration_conversion_requirements-QB5.htm @@ -0,0 +1,264 @@ + + + + + + + + Migration conversion requirements + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Migration conversion requirements

+

The 1,000 SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. profiles and recipes stored in the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. database supersede the HC900 Hybrid controller.'s and the UMC800's own set of stored profiles and recipes. This section details how to migrate the existing profiles and recipes into the server database from a controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC..

+

Set point profiles

+

To migrate existing profiles from a controller, a utility transfers the stored profiles to a block A unit of data and operation within Experion. Experion uses blocks as the component from which control strategies are built. The two categories of blocks are hardware entities and functional entities. within the server database of 1,000 profiles.

+

The utility is named umc800export, and may be run from the command line.

+

To migrate profiles

+
    +
  1. +

    From a command line, type C:> umc800export and then press Enter.

    +

    The UMC800 Profile Export 1. In relation to Station displays, this refers to the process of registering a display with the server so that it can be called up in Station. See also: display, server, Station. 2. In relation to Quick Builder, this refers to the process of converting the configuration data in a project file into text files for use with other applications. See also: application, project, Quick Builder. Utility starts.

    +
    2. +
  2. +

    Enter a valid controller number.

    +
    3. +
  3. +

    Enter the starting profile number.

    +
    4. +
  4. +

    Enter y to proceed.

    +
    5. +
+

For example:

+

**** UMC800 Profile +Export Utility **** +Enter valid controller number: 1 +Enter profile number to start from (1 to 931): 1 +All profiles in Controller 1 will exported to profiles 1 to 70 +Do you want to proceed (Y/N) ? y +Profile 70 of 70 +Exported all profiles +C:> +

+

Recipes

+

No utility exists to transfer existing recipes from an HC900 or a UMC800 controller to the server database of 1,000 recipes. Recipes need to be recreated manually in Station Experion's main operator interface. Station presents information using a series of displays. See also: display..

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Operational_aspects_of_history_backfill-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Operational_aspects_of_history_backfill-QB5.htm new file mode 100644 index 0000000..45f9444 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Operational_aspects_of_history_backfill-QB5.htm @@ -0,0 +1,249 @@ + + + + + + + + Operational aspects of history backfill + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Operational aspects of history backfill

+
CAUTION: + For points that have history backfill configured: +
+

A history backfill will be initiated for a controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. when any of the following events occur:

+
    +
  • If the controller has been in the 'Failed' or 'Marginal' state for more than 1 minute and hen returns to the OK state. History backfill needs to be enabled as well.
    • +
  • +

    If the controller has been Disabled (Out of Service) for more than 1 minute and is then enabled (In service) and returns to the OK state. History backfill needs to be anebled as well.

    +
    • +
  • If the controller is in the OK state and history backfill has been disabled for more than 1 minute and is then re-enabled.
    • +
+

ATTENTION: History samples will only be backfilled if they have not been collected by the Server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. by normal scanning. +

+

Timestamps

+

If a Trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. Rate function block Also known as FB. An executable software object that performs a specific task, such as measurement or control, with inputs and outputs that connect to other entities in a standard way. They can be connected and grouped together to construct simple or complex control strategies. You can view function blocks as a symbol, configuration form, as part of a strategy, or as a user-defined view in an operator schematic. See also: function block configuration form, function block faceplate, function block symbol. has been configured in the controller, up to three buffers are allocated in the controller to store the data that is collected. Each of these buffers has two timestamps; one to indicate the oldest sample it stores and another to indicate the most recent sample it stores.

+

These timestamps can be viewed on the Controller Status display for the HC900 Hybrid controller. controller. These timestamps are only updated when the controller is enabled (In Service).

+

Alarms and events

+

When a history backfill occurs an event is raised to indicate the controller that was backfilled. If any missed samples are detected (that is, neither the controller nor the server collected the samples) an alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. is raised indicating the controller, the point and the time period when samples were missed.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Overview_of_SPP_and_recipe_support-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Overview_of_SPP_and_recipe_support-QB5.htm new file mode 100644 index 0000000..6d303d1 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Overview_of_SPP_and_recipe_support-QB5.htm @@ -0,0 +1,259 @@ + + + + + + + + Overview of SPP and Recipe Support + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Overview of SPP and Recipe Support

+

The HC900 Hybrid controller. and UMC800 SPP Setpoint in percent. See also: setpoint parameter. and Recipe Support is an application that enables you to configure and control Set Point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. (SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable.) programmers and variables in one or more HC900 and/or UMC800 controllers through Station Experion's main operator interface. Station presents information using a series of displays. See also: display.. The application allows operators to easily configure set point profiles and Variable-based recipes offline, before downloading to a specific controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC.. Also supported is the monitoring and configuration of running set point programs. The HC900/UMC800 application provides an easy alternative to configuring, monitoring, and loading SP programs and recipes from the controller operator interface.

+

In particular, the HC900/UMC800 SPP and Recipe Support includes:

+
    +
  • +

    Configuration and maintenance of recipe definitions using Variables in Station.

    +
    • +
  • +

    Downloading recipes to HC900 and UMC800 controllers.

    +
    • +
  • +

    Configuration and maintenance of SP profiles through Station displays.

    +
    • +
  • +

    Configuration and maintenance of combined recipe definitions in Station. A combined recipe includes a recipe with a defined list of Variables and/or up to two SP profiles.

    +
    • +
  • +

    Download a combined recipe to a compatible HC900 or UMC800 controller. (In an HC900 controller, profiles may only be sent to the first four programmers.)

    +
    • +
  • +

    Upload and download of SP profiles between the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. database and HC900/UMC800 SP programmers. (In an HC900 controller, profiles can be sent to the first four programmers only.)

    +
    • +
  • +

    View and modify online the first four HC900/UMC800 SP programmers in a controller (configuration and 'current state').

    +
    • +
+

ATTENTION: + Set point programs and recipe management The control activity that includes the control functions needed to create, store, and maintain general, site, and Master Recipes. are not available from Console A logical grouping of Console Stations and Console Extension Stations. See also: Console Extension Station, Console Station. Stations. +

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Resource_requirements-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Resource_requirements-QB5.htm new file mode 100644 index 0000000..7b10f9f --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Resource_requirements-QB5.htm @@ -0,0 +1,242 @@ + + + + + + + + Resource requirements + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Resource requirements

+

This section details the requirements and restrictions for the HC900 Hybrid controller./UMC800 application.

+

Set point profile and recipe slots

+

The server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. database allows you to configure and store up to 1,000 SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. profiles. These profiles can be downloaded to HC900 and UMC800 SP programmers in the same manner as profiles stored locally in the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC..

+

The system overwrites Profiles 1 to 4 in the HC900's and the UMC800's own pool of stored profiles. Apart from these four profiles, it is possible, although strongly not recommended, to use the remaining profile slots internal to the controller in parallel with the 1,000 server database profiles.

+

The server database also allows you to configure and store up to 1,000 recipes. These recipes can then be downloaded to HC900 and UMC800 controllers in the same manner as recipes stored locally in the controller.

+

The system overwrites Recipe 1 in the HC900's and the UMC800's own pool of stored recipes. Apart from this recipe, it is possible, although strongly not recommended, to use the remaining recipe slots in parallel with the 1,000 server database recipes.

+

Set point program history

+

The history of an SP program can be viewed on a standard trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. and compared to its ideal pre-plotted profile. To collect history, a point needs to be built for each programmer in an HC900 and a UMC800 controller. These points are used to monitor the primary 1. For Regulatory Control blocks in a cascade strategy: A primary is an upstream block from which an initializable input is fetched. A block has one primary for each initializable input. See also: block. 2. The controller (or chassis) that is currently controlling the redundant process by carrying out the assigned functions. Compare: secondary. See also: assigned function, chassis, controller redundancy. and auxiliary PV The process variable. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. outputs of the processes driven by the programmers, collecting the values and storing them in history.

+

Note that only the first four programmers in an HC900 can be monitored. This means that a maximum of four points, one for each programmer, are required for each HC900 and UMC800 controller in the system.

+

Display locking

+

For safety reasons and data integrity, recipes and SP programmers can only be configured and maintained by one user at a time. Any users who try to access these displays while they are in use are locked out. A message indicating the lockout is displayed, indicating the Station Experion's main operator interface. Station presents information using a series of displays. See also: display. number that is currently using the display. These displays remain locked until the Station either exits the displays or is disconnected.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/TCP_IP_devices-QB5.htm b/docs/HW_Universal_Modbus/Concepts/TCP_IP_devices-QB5.htm new file mode 100644 index 0000000..06c0d48 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/TCP_IP_devices-QB5.htm @@ -0,0 +1,233 @@ + + + + + + + + TCP/IP devices + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ TCP/IP devices

+

Ensure every controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. or TCP/IP Transmission control protocol/internet protocol. A standard network protocol. bridge device on the Ethernet network has a unique IP address. Make a list showing what IP addresses have been associated with each controller or bridge device. You will need this information when using Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. to configure the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. to use your Control Products controllers.

+

Note that any serial Control Products controllers connected to a TCP Transmission Control Protocol. bridge must also conform to communications parameters for RS-485 devices. Each must also have a unique physical address on the RS-485 network.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/TCP_connection_for_Honeywell_Universal_Modbus-QB5.htm b/docs/HW_Universal_Modbus/Concepts/TCP_connection_for_Honeywell_Universal_Modbus-QB5.htm new file mode 100644 index 0000000..507dbc7 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/TCP_connection_for_Honeywell_Universal_Modbus-QB5.htm @@ -0,0 +1,273 @@ + + + + + + + + TCP connection for   Universal Modbus + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

TCP connection for Honeywell Universal Modbus

+

To connect controllers to the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. communicating using the Universal Modbus TCP Modbus is a serial communications protocol. protocol, you are required to have a network interface card Also known as: NIC. An expansion board inserted into a computer so that the computer can be connected to a network. Most NICs are designed for a particular type of network and media. See also: network. (NIC Network interface card. An expansion board inserted into a computer so that the computer can be connected to a network. Most NICs are designed for a particular type of network and media. See also: network.) connected to an Ethernet network on both the server as well as the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC.. An external TCP/IP Transmission control protocol/internet protocol. A standard network protocol. bridge (Lantronix DR1-IAP) can also be used for RS-485 network connection to Ethernet.

+

Figure 1-7: Non-redundant Universal Modbus TCP Network Architecture

+

+ +

+

C70 and C70R redundant communication and redundant controller architectures

+

The C70 and C70R models of the HC900 Hybrid controller. allow for redundant communication, and the C70R also allows for redundant controllers.

+

The following sections outline common architectures that involve these features. While a Backup Server is shown in each of these diagrams, the Backup Server is not required, and is included to show how a Backup Server would be connected if one existed.

+

Redundant controller

+

You are required to have a network interface card (NIC) on each server, and the E1 port on both controllers, connected to an Ethernet network via a switch A multiport device that moves Ethernet packets at full wire speed within a network. A switch may be connected to another switch in a network. See also: Ethernet, network..

+

Figure 1-8: Redundant controller Universal Modbus TCP network architecture

+

+ +

+

Redundant controller and network

+

This is the same as the Redundant controller architecture, except that you require a second network adapter on each server, and the E2 port on both controllers, to be connected to a separate network (designated as LAN/WAN Wide area network. A general term to refer to a piece of a network and its components that are used to interconnect multiple LANs over a wide area. See also: LAN, network. #2 below) via a second switch.

+

LAN/WAN #2 must be configured as a different subnet Also known as link. A collection of nodes with unique addresses. See also: node..

+

Figure 1-9: Redundant controller and network Universal Modbus TCP network architecture

+

+ +

+

Redundant controller on FTE

+

When connecting a HC900 to an FTE Fault Tolerant Ethernet is a Honeywell product that provides network redundancy using standard Ethernet hardware. It is the control network designed to provide not only fault-tolerance, but also the fast response, determinism, and security required for industrial control applications. See also: Ethernet, network, redundancy. network with redundant controllers, there must be two network connections on each server connected via FTE switches to the FTE network. The E1 port on the HC900s must be connected to the FTE Yellow switch.

+

The ports on the FTE switch must be configured to:

+ +

Figure 1-10: Redundant controller on FTE Universal Modbus TCP network architecture

+

+ +

+

Redundant controller and network on FTE

+

This is the same as the Redundant controller on FTE architecture, except that you require a third network adapter on each server, and the E2 port on both controllers, to be connected to a separate network (designated as Non-FTE LAN below) via a third switch.

+

Non-FTE LAN must be configured as a different subnet.

+

Figure 1-11: Redundant controller and network on FTE Universal Modbus TCP network architecture

+

+ +

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Concepts/Testing_Honeywell_Universal_Modbus_communications_with_the_server-QB5.htm b/docs/HW_Universal_Modbus/Concepts/Testing_Honeywell_Universal_Modbus_communications_with_the_server-QB5.htm new file mode 100644 index 0000000..4f7ca20 --- /dev/null +++ b/docs/HW_Universal_Modbus/Concepts/Testing_Honeywell_Universal_Modbus_communications_with_the_server-QB5.htm @@ -0,0 +1,286 @@ + + + + + + + + Testing   Universal Modbus communications with the server + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Testing Honeywell Universal Modbus communications with the server

+

Use the test utility umbtst to test the communications.

+

Before using the utility, make sure that:

+ +

To use the test utility, open a Command Prompt window and type: umbtst.

+

When prompted for the channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool. number, type chn0001 for channel 1 and so on.

+

Example

C:\>umbtst
+
+Enter LRN or device name of channel
+chn0001
+Enter Controller number
+1
+Enter command:
+?
+READ i,a,n,p - read device i address a for n address
+and p passes
+WRITE i,a,d,p - write device i address a data d for p passes
+DUMP i,a,b - read device i address a to address b
+FIND i,j - find device with id i to j
+DELAY n - set delay between passes to n ms
+FORMAT f - display registers in format f (DEC,HEX,or IEEEFP)
+FO filename - direct output to file
+! - execute last command
+Q - quit
+Enter command:
+find 1,4
+
+FIND device with id   1 to   4, at 28-May-12  14:06:52
+Device   1 ?
+Device   2 ?
+Device   3 ? ...responding
+Device   4 ?
+Enter command:
+q
+

The FIND command is used with serial connected devices to check if the devices are present. This command locates all Universal Modbus devices on the channel with IDs between a and b. This command is not applicable on LAN-connected devices.

+

If you do not know the device name of your channel, select ViewSystem StatusChannels from the Station Experion's main operator interface. Station presents information using a series of displays. See also: display. menu. To the left of the channel name is the channel number. The device name of the channel will be the letters chn followed by the channel number. For example, your Universal Modbus channel COM3 might be channel number 1. Its device name will be chn0001.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/HC900_and_UMC800_SPP_and_recipe_support-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/HC900_and_UMC800_SPP_and_recipe_support-QB5.htm new file mode 100644 index 0000000..8dc11d1 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/HC900_and_UMC800_SPP_and_recipe_support-QB5.htm @@ -0,0 +1,234 @@ + + + + + + + + HC900 and UMC800 SPP and recipe support + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ HC900 and UMC800 SPP and recipe support

+

This section describes set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. programmers and recipe support for HC900 Hybrid controller. and UMC800.

+ +
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/HC900_history_backfill-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/HC900_history_backfill-QB5.htm new file mode 100644 index 0000000..26b18a0 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/HC900_history_backfill-QB5.htm @@ -0,0 +1,234 @@ + + + + + + + + HC900 history backfill + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ HC900 history backfill

+

Some versions of HC900 Hybrid controller. support historical data collection. This section describes how to configure and enable history backfill for supported HC900 controllers.

+ +
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Honeywell_Universal_Modbus_channel_and_controller_reference-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/Honeywell_Universal_Modbus_channel_and_controller_reference-QB5.htm new file mode 100644 index 0000000..594dca2 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Honeywell_Universal_Modbus_channel_and_controller_reference-QB5.htm @@ -0,0 +1,233 @@ + + + + + + + +   Universal Modbus channel and controller reference + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Honeywell Universal Modbus channel and controller reference

+

This section describes the configuration and addressing information specific to Honeywell Universal Modbus channels and controllers.

+  
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Honeywell_Universal_Modbus_points_reference-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/Honeywell_Universal_Modbus_points_reference-QB5.htm new file mode 100644 index 0000000..10515a7 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Honeywell_Universal_Modbus_points_reference-QB5.htm @@ -0,0 +1,235 @@ + + + + + + + +   Universal Modbus points reference + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Honeywell Universal Modbus points reference

+

This section describes how to configure points for a Honeywell Universal Modbus controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. using Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point..

+

Different addresses are available depending on the type of device to which you are connected. Addresses that are read-only can only be used as source addresses. Addresses that are write-only can only be used as destination addresses. Addresses that are available for both read and write operations can be used as both source and destination addresses.

+ +
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Numbered_addresses-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/Numbered_addresses-QB5.htm new file mode 100644 index 0000000..fe54b66 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Numbered_addresses-QB5.htm @@ -0,0 +1,232 @@ + + + + + + + + Numbered addresses + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Numbered addresses

+

The section describes numbered addresses for Honeywell Universal Modbus controllers.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Operation-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/Operation-QB5.htm new file mode 100644 index 0000000..b809c43 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Operation-QB5.htm @@ -0,0 +1,234 @@ + + + + + + + + Operation + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Operation

+

This section describes how to use the HC900 Hybrid controller./UMC800 SPP Setpoint in percent. See also: setpoint parameter. and Recipe Support on a routine basis. Standard tasks include downloading recipes and SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. profiles, and issuing commands to the SP programmers. After reading this section, you will be able to control HC900 and UMC800 controllers from Station Experion's main operator interface. Station presents information using a series of displays. See also: display..

+

Prerequisites

+

It is assumed that you have successfully completed the configuration procedure detailed in the previous section and that all prerequisites have been met.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Planning for Honeywell Universal Modbus controllers.htm b/docs/HW_Universal_Modbus/Navtopics/Planning for Honeywell Universal Modbus controllers.htm new file mode 100644 index 0000000..a382c70 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Planning for Honeywell Universal Modbus controllers.htm @@ -0,0 +1,359 @@ + + + + + + + + Planning considerations for installing and configuring   Universal Modbus controllers + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

Planning for Honeywell Universal Modbus controllers

+

+ This reference provides the information you need to set up, configure, and test Universal Modbus controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. communications with the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS..

+

Revision history

+ + + + + + + + + + + + + + + + + + +
+ Revision + + Date + + Description +
+

A

+ 		+

September 2024 +

+ 		+

Initial release of document.

+
+

How to use this guide

+

These are the steps for connecting and configuring a Honeywell Universal Modbus controller. Complete each step before commencing the next.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Steps + + Go to +
+

Connect and set up the Universal Modbus controller according to the controller's user manual's instructions

+ 		+

Architectures for Honeywell Universal Modbus +

+
+

Use Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. to define channels

+ 		+ +
+

Use Quick Builder to define controllers

+ 		+ +
+

Download channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool. and controller definitions to the server

+ 		+

"Downloading items" topic in the Quick Builder User’s Guide

+
+

Enable channels and test communications

+ 		+

Testing Honeywell Universal Modbus communications with the server +

+
+

Troubleshoot communication errors

+ 		+

Troubleshooting Honeywell Universal Modbus configuration errors +

+
+

Use Quick Builder to define points

+ 		+

Defining a Honeywell Universal Modbus address for a point parameter Also known as parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter.

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Planning-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/Planning-QB5.htm new file mode 100644 index 0000000..d3d1842 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Planning-QB5.htm @@ -0,0 +1,232 @@ + + + + + + + + Planning + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Planning

+

This section describes the planning and design-related issues concerned with configuring HC900 Hybrid controller. and UMC800 SPP Setpoint in percent. See also: setpoint parameter. and Recipe Support. After reading this section, you will be able to plan for the configuration process.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Recipe_configuration-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/Recipe_configuration-QB5.htm new file mode 100644 index 0000000..7c1bbdf --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Recipe_configuration-QB5.htm @@ -0,0 +1,248 @@ + + + + + + + + Recipe configuration + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Recipe configuration

+

In this section, you will learn how to configure HC900 Hybrid controller. and UMC800 recipes, SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. profiles, and combined recipes. Configuration requirements for setting up the set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. programmer monitoring displays are also presented.

+

Prerequisites

+

Before configuring the HC900/UMC800 SPP Setpoint in percent. See also: setpoint parameter. and Recipe Support, ensure that you have:

+ +

Considerations

+

Each recipe, SP profile, and combined recipe stored in the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. database must have a unique name (respectively).

+

SP profiles must have zero length/rate segments only at the end of the profile.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Troubleshooting_Honeywell_Universal_Modbus_configuration_errors-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/Troubleshooting_Honeywell_Universal_Modbus_configuration_errors-QB5.htm new file mode 100644 index 0000000..88d2d09 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Troubleshooting_Honeywell_Universal_Modbus_configuration_errors-QB5.htm @@ -0,0 +1,231 @@ + + + + + + + + Troubleshooting   Universal Modbus configuration errors + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Troubleshooting Honeywell Universal Modbus configuration errors

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Navtopics/Troubleshooting_Honeywell_Universal_Modbus_issues-QB5.htm b/docs/HW_Universal_Modbus/Navtopics/Troubleshooting_Honeywell_Universal_Modbus_issues-QB5.htm new file mode 100644 index 0000000..ccc0267 --- /dev/null +++ b/docs/HW_Universal_Modbus/Navtopics/Troubleshooting_Honeywell_Universal_Modbus_issues-QB5.htm @@ -0,0 +1,234 @@ + + + + + + + + Troubleshooting   Universal Modbus issues + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Troubleshooting Honeywell Universal Modbus issues

+

This section describes tasks for the Universal Modbus controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. that you perform either on the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. or from any Station Experion's main operator interface. Station presents information using a series of displays. See also: display..

+ +
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Address_syntax_for_Honeywell_Universal_Modbus_controllers-QB5.htm b/docs/HW_Universal_Modbus/References/Address_syntax_for_Honeywell_Universal_Modbus_controllers-QB5.htm new file mode 100644 index 0000000..7355b45 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Address_syntax_for_Honeywell_Universal_Modbus_controllers-QB5.htm @@ -0,0 +1,276 @@ + + + + + + + + Address syntax for   Universal Modbus controllers + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Address syntax for Honeywell Universal Modbus controllers

+

For source, and destination addresses, the format for a Universal Modbus controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. address is:

ControllerName Address
+ + + + + + + + + + + + + + + + + + + +
+ Part + + Description +
+

ControllerName +

+ 		+

The name of the Universal Modbus controller.

+
+

Address +

+ 		+

The address in the controller where the value is recorded. The syntax depends on the address type:

+
    +
  • +

    Named addresses. See the topic titled "Address syntax for named addresses" for more information.

    +
    • +
  • +

    Non-named addresses. See the topic titled "Address syntax for non-named addresses" for more information.

    +
    • +
+
+

If you would like help with the address, you can use the Address Builder. To display the Address Builder, click next to Address.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Address_syntax_for_named_addresses-QB5.htm b/docs/HW_Universal_Modbus/References/Address_syntax_for_named_addresses-QB5.htm new file mode 100644 index 0000000..fcd7ca6 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Address_syntax_for_named_addresses-QB5.htm @@ -0,0 +1,865 @@ + + + + + + + + Address syntax for named addresses + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

Address syntax for named addresses

+

Named addresses can be either:

+
    +
  • +

    Non-numbered address

    +
    • +
  • +

    Numbered address

    +
    • +
+

Non-numbered address

+

For addresses that occur in only one location, specify the name of a register within your controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. simply using the syntax:

AddressName [Format]
+
+ + + + + + + + + + + + + + + + + + + +
+ Part + + Description +
+

AddressName +

+ 		+

Matches an address from the table of non-numbered addresses.

+
+

Format +

+ 		+

(Optional) Specify only if the device does not use the default format for that address. Different addresses will have different default formats.

+
+

Numbered address

+

For address types that occur multiple times within the device (for example, more than one analog input), use the syntax:

AddressName Number [SubAddressName][Format]
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Part + + Description +
+

AddressName +

+ 		+

Name of the address, for example, loop. For address names see the topic titled "Numbered addresses."

+
+

Number +

+ 		+

The number of the address. For address numbers see the topic titled "Numbered addresses."

+
+

SubAddress Name +

+ 		+

(Optional) Some types of numbered addresses can have sub-addresses. For example, every loop has a Process Variable Normally abbreviated as PV. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. (PV The process variable. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period.) and a Set Point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. (WSP).

+
+

Format +

+ 		+

(Optional) Specify only if the device does not use the default format. See the topic titled "Data formats."

+
+

+

Examples

+

The following example addresses the Process Variable (PV) of the second loop:

LOOP 2 PV
+
+

Process variable for loop 1:

LOOP 1 PV
+
+

+

+

Typical control loop parameter addressing (where n is the loop number)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

Process Variable (PV)

+ 		+

LOOP n PV +

+ 		+

Not configurable

+
+

Set Point (SP)

+ 		+

LOOP n WSP1 +

+ 		+

LOOP n WSP +

+
+

Output (OP)

+ 		+

LOOP n OPWORK2 +

+ 		+

LOOP n OPWORK +

+
+

MODE (MD)

+ 		+

LOOP n LOOPSTAT +

+ 		+

LOOP n MODEIN +

+
+

+

+

Loop tuning constants (possible AUX parameters for a loop point)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

Gain

+ 		+

LOOP n GAIN1 +

+ 		+

LOOP n GAIN1 +

+
+

Reset

+ 		+

LOOP n RESET1 +

+ 		+

LOOP n RESET1 +

+
+

Rate

+ 		+

LOOP n RATE1 +

+ 		+

LOOP n RATE1 +

+
+

+

+

Digital Output values (used on a status point)

+
ATTENTION: Attention: +

+ Digital Output values reside in table 0. Therefore, they are not applicable for controllers with a Data Table setting of Holding Registers Lower or Holding Registers Upper.

+
+ + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

PV

+ 		+

DO n +

+ 		+

Not configurable

+
+

OP

+ 		+

DO n +

+ 		+

DO n3 +

+
+

+

+

Digit Input values (used on a status point)

Attention: +

Digital Input values reside in table 0. Therefore, they are not applicable for controllers with a Data Table setting of Holding Registers Lower or Holding Registers Upper.

+ + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

PV

+ 		+

DI n +

+ 		+

Not configurable

+
+

+

Extended loop support for HC900

+

ATTENTION: + This section is not applicable for controllers with a Data Table setting of Holding Registers Lower or Holding Registers Upper. +

+

Note that for LOOPX parameters, you must reference a controller with an Offset of 6,000. For more information about offsets, see the section "HC900 Hybrid controller. and UMC800 controller OFFSET addresses" in the topic titled "Main properties for a Honeywell Universal Modbus controller."

+

For the HC900 controller, loops 25-32 must be addressed using the LOOPX parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter.. Loop 32 Mode is only supported for Auto/Manual (AUTO-LSP and MAN-LSP). Loop 32 addresses must be added via the custom Modbus map for full support of Mode.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

Process Variable (PV)

+ 		+

LOOPX n PV +

+ 		+

Not configurable

+
+

Set Point (SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable.)

+ 		+

LOOPX n WSP +

+ 		+

LOOPX n WSP or LOOPX n LSP1

+
+

Output (OP)

+ 		+

LOOPX n OP or LOOPX n OPWORK

+ 		+

LOOPX n OP or LOOPX n OPWORK

+
+

Mode (MD Mode parameter. Also known as mode. - A point parameter that determines whether or not the operator can control the point value. - In a status point, the MD determines whether the operator can control the output parameter. - In an analog point, the MD determines whether the operator can control the setpoint parameter. See also: analog point, output parameter, point parameter, setpoint parameter, status point.)

+ 		+

LOOPX n LOOPSTAT +

+ 		+

LOOPX n MODEIN +

+
+

Loop Tuning constants (possible AUX parameters for a loop point) for loops 25-32:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

Gain

+ 		+

LOOPX n GAIN1 +

+ 		+

LOOPX n GAIN1 +

+
+

Reset

+ 		+

LOOPX n RESET1 +

+ 		+

LOOPX n RESET1 +

+
+

Rate

+ 		+

LOOPX n RATE1 +

+ 		+

LOOPX n RATE1 +

+
+

Signal tag and variable named address support for the HC900 and UMC800

+

Signal Tags (read only) with TAG as the named parameter and Variables (read/write) with MATH_VAR as the named parameter may be assigned to analog (floating point) or digital status points. The Variable and Signal Tag list (Tag Information) should be printed out from the controller configuration to obtain the sequential number listing and the data type (Analog or Digital) so that the proper point assignment may be made.

+

+

Analog signal tag example

+ + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

PV

+ 		+

TAG n +

+ 		+

Not Configurable

+
+

+

+

Digital signal tag example

+ + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

PV

+ 		+

TAG n +

+ 		+

Not Configurable

+
+

+

+

Digital variable example

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

PV

+ 		+

MATH_VAR n +

+ 		+

Not Configurable

+
+

OP

+ 		+

MATH_VAR n +

+ 		+

MATH_VAR n +

+
+

+

+

Analog variable example

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter + + Source Address + + Destination Address +
+

PV

+ 		+

MATH_VAR n +

+ 		+

Not Configurable

+
+

SP

+ 		+

MATH_VAR n +

+ 		+

MATH_VAR n +

+
+

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Address_syntax_for_nonnamed_addresses-QB5.htm b/docs/HW_Universal_Modbus/References/Address_syntax_for_nonnamed_addresses-QB5.htm new file mode 100644 index 0000000..beab47d --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Address_syntax_for_nonnamed_addresses-QB5.htm @@ -0,0 +1,460 @@ + + + + + + + + Address syntax for non-named addresses + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Address syntax for non-named addresses

+

Addresses without names can be addressed directly using the format:

n:0xA [Format]
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+ Part + + Description +
+

n +

+ 		+

Table number. See the section below titled "Table types" for table descriptions and their number.

+
+

A +

+ 		+

Address within the table (in hexadecimal).

+
+

Format +

+ 		+

(Optional) Only used for Input and Holding register tables (3 and 4). If a format is not specified, the format defaults to IEEEFP.

+
+

For signal tags above 1,000, you must use hexadecimal addressing.

+

Table types

+

ATTENTION: For controllers with a Data Table setting of Holding Registers Lower or Holding Registers Upper, you can only use Table 4. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Table Description + + Table Number + + Point Type + + Address Type +
+

Digital Output (also known as Coil)1

+ 		+

0

+ 		+

Status

+ 		+

Source/Destination2

+
+

Digital Input

+ 		+

1

+ 		+

Status

+ 		+

Source

+
+

Input Registers

+ 		+

3

+ 		+

Status/Analog/Accumulator

+ 		+

Source

+
+

Holding Registers (Upper and Lower)

+ 		+

4

+ 		+

Status/Analog/Accumulator

+ 		+

Source/Destination

+
+

+

Non-named address examples (for HC900)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter + + Point Type + + Address Type + + Point Table/Address/Format + + Controller OFFSET Address3
+

Signal Tag 1001

+ 		+

Analog

+ 		+

Source

+ 		+

4:0x4330 IEEEFP

+ 		+

4,000

+
+

Analog In, Slot 2, Channel 2, of Rack 24

+ 		+

Analog

+ 		+

Source

+ 		+

3:0x112 IEEEFP

+ 		+

0

+
+

Digital In, Slot 8, Channel 3, of Rack 12

+ 		+

Status

+ 		+

Source

+ 		+

1:0x72

+ 		+

0

+
+

Step Number of Sequencer 1

+ 		+

Analog

+ 		+

Source

+ 		+

4:0x5AA9 UINT2

+

(16-bit Integer)

+ 		+

4,000

+
+

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Alarm_set_point_value_group-QB5.htm b/docs/HW_Universal_Modbus/References/Alarm_set_point_value_group-QB5.htm new file mode 100644 index 0000000..23b5028 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Alarm_set_point_value_group-QB5.htm @@ -0,0 +1,401 @@ + + + + + + + + Alarm set point value group + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Alarm set point value group

+

Devices supported

+

The following table lists the devices that support the Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Set Point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. Value group, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

ALMSP [n] [param]

+ 		+

[n] = 1 to 48

+
+

DPR250

+ 		+

ALMSP [n] [param]

+ 		+

[n] = 1 to 64

+
+

DR4300

+ 		+

ALMSP [n] [param]

+ 		+

[n] = 1 to 2

+
+

DR4500

+ 		+

ALMSP [n] [param]

+ 		+

[n] = 1 to 6

+
+

UDC2300

+ 		+

ALMSP [n] [param]

+ 		+

[n] = 1 to 2

+
+

UDC3300

+ 		+

ALMSP [n] [param]

+ 		+

[n] = 1 to 2

+
+

Parameters

+

The following table lists the details of the Alarm Set Point Value Group parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Alarm Set Point Value

+ 		+

ALMSP [n] VALUE1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DPR180, DPR250

+
+

Alarm Set Point #1

+ 		+

ALMSP [n] SP12

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+

Alarm Set Point #2

+ 		+

ALMSP [n] SP22

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Alarm_status-QB5.htm b/docs/HW_Universal_Modbus/References/Alarm_status-QB5.htm new file mode 100644 index 0000000..9ccb0d6 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Alarm_status-QB5.htm @@ -0,0 +1,369 @@ + + + + + + + + Alarm status + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Alarm status

+

Devices supported

+

The following table lists the devices that support the Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Status, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

ALMSTAT [n] [param]

+ 		+

[n] = 1 to 2

+
+

DR4500

+ 		+

ALMSTAT [n] [param]

+ 		+

[n] = 1 to 6

+
+

UDC2300

+ 		+

ALMSTAT [n] [param]

+ 		+

[n] = 1 to 2

+
+

UDC3300

+ 		+

ALMSTAT [n] [param]

+ 		+

[n] = 1 to 2

+
+

UMC800

+ 		+

ALMSTAT [n] [param]

+ 		+

[n] = 1 to 120

+
+

HC900 Hybrid controller. +

+ 		+

ALMSTAT [n] [param]

+ 		+

[n] = 1 to 120

+
+

Parameters

+

The following table lists the details of the Alarm Status parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Alarm Status

+ 		+

ALMSTAT [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Alarm_status_analog-QB5.htm b/docs/HW_Universal_Modbus/References/Alarm_status_analog-QB5.htm new file mode 100644 index 0000000..468a9b0 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Alarm_status_analog-QB5.htm @@ -0,0 +1,324 @@ + + + + + + + + Alarm status analog + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Alarm status analog

+

Devices supported

+

The following table lists the devices that support the Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Status Analog, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

ALMSTAT_ANALOG [n] [param]

+ 		+

[n] = 1 to 24

+
+

DPR250

+ 		+

ALMSTAT_ANALOG [n] [param]

+ 		+

[n] = 1 to 64

+
+

Parameters

+

The following table lists the details of the Alarm Status Analog parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Alarm Status

+ 		+

ALMSTAT_ANALOG [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DPR180, DPR250

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Alarm_status_channel-QB5.htm b/docs/HW_Universal_Modbus/References/Alarm_status_channel-QB5.htm new file mode 100644 index 0000000..da37154 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Alarm_status_channel-QB5.htm @@ -0,0 +1,324 @@ + + + + + + + + Alarm status channel + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Alarm status channel

+

Devices supported

+

The following table lists the devices that support the Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Status Channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool., and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

ALMSTAT_CHANNEL [n] [param]

+ 		+

[n] = 1 to 24

+
+

DPR250

+ 		+

ALMSTAT_CHANNEL [n] [param]

+ 		+

[n] = 1 to 64

+
+

Parameters

+

The following table lists the details of the Alarm Status Channel parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Alarm Status

+ 		+

ALMSTAT_CHANNEL [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DPR180, DPR250

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Alarm_status_communications-QB5.htm b/docs/HW_Universal_Modbus/References/Alarm_status_communications-QB5.htm new file mode 100644 index 0000000..0f472c0 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Alarm_status_communications-QB5.htm @@ -0,0 +1,324 @@ + + + + + + + + Alarm status communications + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Alarm status communications

+

Devices supported

+

The following table lists the devices that support the Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Status Communications, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

ALMSTAT_COM Component Object Model. [n] [param]

+ 		+

[n] = 1 to 24

+
+

DPR250

+ 		+

ALMSTAT_COM [n] [param]

+ 		+

[n] = 1 to 32

+
+

Parameters

+

The following table lists the details of the Alarm Status Communications parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Alarm Status

+ 		+

ALMSTAT_COM [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DPR180, DPR250

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Alarm_status_digital-QB5.htm b/docs/HW_Universal_Modbus/References/Alarm_status_digital-QB5.htm new file mode 100644 index 0000000..6704acb --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Alarm_status_digital-QB5.htm @@ -0,0 +1,324 @@ + + + + + + + + Alarm status digital + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Alarm status digital

+

Devices supported

+

The following table lists the devices that support the Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Status Digital, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

ALMSTAT_DIGITAL [n] [param]

+ 		+

[n] = 1 to 36

+
+

DPR250

+ 		+

ALMSTAT_DIGITAL [n] [param]

+ 		+

[n] = 1 to 48

+
+

Parameters

+

The following table lists the details of the Alarm Status Digital parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Alarm Status

+ 		+

ALMSTAT_DIGITAL [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DPR180, DPR250

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Alarm_status_event-QB5.htm b/docs/HW_Universal_Modbus/References/Alarm_status_event-QB5.htm new file mode 100644 index 0000000..cebcf45 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Alarm_status_event-QB5.htm @@ -0,0 +1,324 @@ + + + + + + + + Alarm status event + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Alarm status event

+

Devices supported

+

The following table lists the devices that support the Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Status Event, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

ALMSTAT_EVENT [n] [param]

+ 		+

[n] = 1 to 6

+
+

DPR250

+ 		+

ALMSTAT_EVENT [n] [param]

+ 		+

[n] = 1 to 6

+
+

Parameters

+

The following table lists the details of the Alarm Status Event parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Alarm Status

+ 		+

ALMSTAT_EVENT [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DPR180, DPR250

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Alarm_status_math-QB5.htm b/docs/HW_Universal_Modbus/References/Alarm_status_math-QB5.htm new file mode 100644 index 0000000..6389a06 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Alarm_status_math-QB5.htm @@ -0,0 +1,324 @@ + + + + + + + + Alarm status math + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Alarm status math

+

Devices supported

+

The following table lists the devices that support the Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Status Math, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

ALMSTAT_MATH [n] [param]

+ 		+

[n] = 1 to 24

+
+

DPR250

+ 		+

ALMSTAT_MATH [n] [param]

+ 		+

[n] = 1 to 32

+
+

Parameters

+

The following table lists the details of the Alarm Status Math parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Alarm Status

+ 		+

ALMSTAT_MATH [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DPR180, DPR250

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Analog_input-QB5.htm b/docs/HW_Universal_Modbus/References/Analog_input-QB5.htm new file mode 100644 index 0000000..6aa7209 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Analog_input-QB5.htm @@ -0,0 +1,401 @@ + + + + + + + + Analog input + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Analog input

+

Devices supported

+

The following table lists the devices that support Analog Inputs, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

AI Analog Input. Compare: DI. [n] [param]

+ 		+

[n] = 1 to 1

+
+

DR4500

+ 		+

AI [n] [param]

+ 		+

[n] = 1 to 4

+
+

DPR180

+ 		+

AI [n] [param]

+ 		+

[n] = 1 to 24

+
+

DPR250

+ 		+

AI [n] [param]

+ 		+

[n] = 1 to 64

+
+

UDC2300

+ 		+

AI [n] [param]

+ 		+

[n] = 1 to 2

+
+

UDC3300

+ 		+

AI [n] [param]

+ 		+

[n] = 1 to 3

+
+

UMC800

+ 		+

AI [n] [param]

+ 		+

[n] = 1 to 64

+
+

HC900 Hybrid controller. +

+ 		+

AI [n] [param]

+ 		+

[n] = 1 to 641

+
+

TrendView

+ 		+

AI [n] [param]

+ 		+

[n] = 1 to 32

+
+

Parameters

+

The following table lists the details of the Analog Input parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Analog Input Value Read-only values that are usually scanned from the controller registers but can be from other server addresses. Input values can represent eight discrete states. Up to three values can be read from an address in order to determine a state. See also: controller, scanning.

+ 		+

AI [n] VALUE2

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, DPR180, DPR250, UDC2300, UDC3300, UMC800, HC900, TV

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Bauds_supported_by_Honeywell_Universal_Modbus-QB5.htm b/docs/HW_Universal_Modbus/References/Bauds_supported_by_Honeywell_Universal_Modbus-QB5.htm new file mode 100644 index 0000000..b609e36 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Bauds_supported_by_Honeywell_Universal_Modbus-QB5.htm @@ -0,0 +1,477 @@ + + + + + + + + Bauds supported by   Universal Modbus + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Bauds supported by Honeywell Universal Modbus

+

The following table lists the devices and their supported bauds.

+

ATTENTION: Bauds are not applicable to HC900 Hybrid controller. and TrendView devices; these devices use Ethernet connections. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Bauds Supported +
+ 300 + + 600 + + 1200 + + 2400 + + 4800 + + 9600 + + 19,200 + + 38,400 +
+

DR4300

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+
+

DR4500

+ 		   +

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		 
+

DPR180

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+
+

DPR250

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+
+

UDC2300

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		 
+

UDC3300

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		 
+

UMC800

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+ 		+

Yes

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Communication_or_constant_value_group-QB5.htm b/docs/HW_Universal_Modbus/References/Communication_or_constant_value_group-QB5.htm new file mode 100644 index 0000000..eac1511 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Communication_or_constant_value_group-QB5.htm @@ -0,0 +1,334 @@ + + + + + + + + Communication or constant value group + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Communication or constant value group

+

Devices supported

+

The following table lists the devices that support the Communication or Constant Value group, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

CN [n] [param]

+ 		+

[n] = 1 to 24

+
+

DPR250

+ 		+

CN [n] [param]

+ 		+

[n] = 1 to 32

+
+

TrendView

+ 		+

CN [n] [param]

+ 		+

[n] = 1 to 32

+
+

Parameters

+

The following table lists the details of the Communication or Constant Value Group parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Communication Value

+ 		+

CN [n] VALUE1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DPR180, DPR250, TV2

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Data_formats-QB5.htm b/docs/HW_Universal_Modbus/References/Data_formats-QB5.htm new file mode 100644 index 0000000..c5443d6 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Data_formats-QB5.htm @@ -0,0 +1,301 @@ + + + + + + + + Data formats + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Data formats

+

The data format A format applied to the raw parameter value being read from a controller. Data formats are used for scaling, and to read values that are floating point or other. To apply a data format, you type it as the last part of the controller address for the parameter value. See also: controller, parameter. tells the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. how to interpret the register value. The possible formats are:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Data Format + + Description + + Point Type +
+

IEEEFP +

+ 		+

32-bit IEEE Institute of Electrical and Electronic Engineers. floating point value (Big Endian).

+ 		+

Status, Analog, Accumulator

+
+

n +

+ 		+

Bit field. n represents the starting bit (0–15). This cannot be used with a named address.

+ 		+

Status

+
+

MODE +

+ 		+

Informs the server that the address is a mode parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter..

+ 		+

Status, Analog, Accumulator

+
+

UINT2 +

+ 		+

Unscaled 16-bit integer.

+ 		+

Status, Analog, Accumulator

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Defining_a_Honeywell_Universal_Modbus_address_for_a_point_parameter-QB5.htm b/docs/HW_Universal_Modbus/References/Defining_a_Honeywell_Universal_Modbus_address_for_a_point_parameter-QB5.htm new file mode 100644 index 0000000..8ae6113 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Defining_a_Honeywell_Universal_Modbus_address_for_a_point_parameter-QB5.htm @@ -0,0 +1,276 @@ + + + + + + + + Defining a   Universal Modbus address for a point parameter + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Defining a Honeywell Universal Modbus address for a point parameter

+

For source and destination addresses the format for a Honeywell Universal Modbus controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. address is:

ControllerName Address
+ + + + + + + + + + + + + + + + + + + +
+ Part + + Description +
+

ControllerName +

+ 		+

The name of the Universal Modbus controller.

+
+

Address +

+ 		+

The address in the controller where the value is recorded. The syntax depends on the address type:

+
    +
  • +

    Named addresses

    +
    • +
  • +

    Non-named addresses

    +
    • +
+
+

If you would like help with the address, you can use the Address Builder. To display the Address Builder, click next to Address.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Devices_supported_by_the_Honeywell_Universal_Modbus_interface-QB5.htm b/docs/HW_Universal_Modbus/References/Devices_supported_by_the_Honeywell_Universal_Modbus_interface-QB5.htm new file mode 100644 index 0000000..b34f33e --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Devices_supported_by_the_Honeywell_Universal_Modbus_interface-QB5.htm @@ -0,0 +1,262 @@ + + + + + + + + Devices supported by the   Universal Modbus interface + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Devices supported by the Honeywell Universal Modbus interface

+

This following devices are supported by the Universal Modbus controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC.:

+
    +
  • +

    DR4300

    +
    • +
  • +

    DR4500

    +
    • +
  • +

    DPR180

    +
    • +
  • +

    DPR250

    +
    • +
  • +

    UDC2300

    +
    • +
  • +

    UDC3300

    +
    • +
  • +

    UMC800

    +
    • +
  • +

    HC900 Hybrid controller. +

    +
    • +
  • +

    Trendview/X-Series

    +
    • +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Digital_input_table-QB5.htm b/docs/HW_Universal_Modbus/References/Digital_input_table-QB5.htm new file mode 100644 index 0000000..226927f --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Digital_input_table-QB5.htm @@ -0,0 +1,411 @@ + + + + + + + + Digital input table + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

Digital input table

+

Devices supported

+

ATTENTION: + Digital Input values reside in table 1. Therefore, they are not applicable for controllers with a Data Table setting of Holding Registers Lower or Holding Registers Upper. +

+

The following table lists the devices that support the Digital Input Table, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

DI Digital input. Compare: AI. See also: input. [n] [param]

+ 		+

[n] = 1 to 36

+
+

DPR250

+ 		+

DI [n] [param]

+ 		+

[n] = 1 to 48

+
+

DR4300

+ 		+

DI [n] [param]

+ 		+

[n] = 1 to 2

+
+

DR4500

+ 		+

DI [n] [param]

+ 		+

[n] = 1 to 2

+
+

UDC3300

+ 		+

DI [n] [param]

+ 		+

[n] = 1 to 2

+
+

UMC800

+ 		+

DI [n] [param]

+ 		+

[n] = 1 to 256

+
+

HC900 Hybrid controller. +

+ 		+

DI [n] [param]

+ 		+

[n] = 1 to 256

+
+

TrendView

+ 		+

DI [n] [param]

+ 		+

[n] = 1 to 32

+
+

Parameters

+

The following table lists the details of the Digital Input Table parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Digital Input Value Read-only values that are usually scanned from the controller registers but can be from other server addresses. Input values can represent eight discrete states. Up to three values can be read from an address in order to determine a state. See also: controller, scanning.

+ 		+

DI [n] VALUE1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DPR180, DPR250

+
+

Digital Input Value

+ 		+

DI [n] VALUE2

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC3300, UMC800, HC9003, TV

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Digital_output_control_strategies-QB5.htm b/docs/HW_Universal_Modbus/References/Digital_output_control_strategies-QB5.htm new file mode 100644 index 0000000..0075348 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Digital_output_control_strategies-QB5.htm @@ -0,0 +1,242 @@ + + + + + + + + Digital output control strategies + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Digital output control strategies

+

Some controllers support the use of digital outputs as destination addresses. However, this functionality may have unintended consequences.

+

Digital outputs are typically controlled by the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. itself. If you use a digital output in a destination address, the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. value will always override the value the controller expects to use. Once the output has been forced by the server, control cannot be returned to the controller. (that is, the server value will always have precedence).

+

Because of this potential problem, the use of the digital output as a destination address has been disabled for the UMC800. Instead, if you have a control strategy as shown below, rather than use 'Digital Output' as the destination of a server point parameter Also known as parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter., use the strategy shown in below. This strategy uses two server destination addresses, Force Value and Force Enabled. Force Enabled enables you to switch A multiport device that moves Ethernet packets at full wire speed within a network. A switch may be connected to another switch in a network. See also: Ethernet, network. between the local value, Calculated Value, and the server value, Force Value.

+

Figure 3-1: Digital Output Control Strategy - Example 1

+

+ +

+

Figure 3-2: Digital Output Control Strategy - Example 2

+

+ +

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Digital_output_table-QB5.htm b/docs/HW_Universal_Modbus/References/Digital_output_table-QB5.htm new file mode 100644 index 0000000..d7f294d --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Digital_output_table-QB5.htm @@ -0,0 +1,439 @@ + + + + + + + + Digital output table + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

Digital output table

+

Devices supported

+

ATTENTION: + Digital Output values reside in table 0. Therefore, they are not applicable for controllers with a Data Table setting of Holding Registers Lower or Holding Registers Upper. +

+

The following table lists the devices that support the Digital Output Table, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DPR180

+ 		+

DO Digital output. Compare: AO. See also: output. [n] [param]

+ 		+

[n] = 1 to 36

+
+

DPR250

+ 		+

DO [n] [param]

+ 		+

[n] = 1 to 48

+
+

DR4300

+ 		+

DO [n] [param]

+ 		+

[n] = 1 to 2

+
+

DR4500

+ 		+

DO [n] [param]

+ 		+

[n] = 1 to 6

+
+

UDC2300

+ 		+

DO [n] [param]

+ 		+

[n] = 1 to 3

+
+

UDC3300

+ 		+

DO [n] [param]

+ 		+

[n] = 1 to 3

+
+

UMC800

+ 		+

DO [n] [param]

+ 		+

[n] = 1 to 256

+
+

HC900 Hybrid controller.

+ 		+

DO [n] [param]

+ 		+

[n] = 1 to 256

+
+

TrendView

+ 		+

DO [n] [param]

+ 		+

[n] = 1 to 32

+
+

Parameters

+

The following table lists the details of the Digital Output Table parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Digital Output Value

+ 		+

DO [n] VALUE1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DPR180, DPR250

+
+

Digital Output Value

+ 		+

DO [n] VALUE2

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

DR4300, DR4500

+
+

Digital Output Value

+ 		+

DO [n] VALUE 1

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UDC2300, UDC3300, UMC800, HC9003, TV

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Main_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm b/docs/HW_Universal_Modbus/References/Main_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm new file mode 100644 index 0000000..f6afde6 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Main_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm @@ -0,0 +1,409 @@ + + + + + + + + Main properties for a   Universal Modbus channel + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Main properties for a Honeywell Universal Modbus channel

+

The Main tab defines the basic properties for a Honeywell Universal Modbus channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool..

+

For information about how to create a channel, see "Building controllers and channels" in the Quick Builder User’s Guide.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Property + + Description +
+

Name

+ 		+

The unique name of the channel. A maximum of 10 alphanumeric characters (no spaces or double quotes). Note: In Station Experion's main operator interface. Station presents information using a series of displays. See also: display. displays, underscore characters ( _ ) appear as spaces.

+
+

Description

+ 		+

(Optional) A description of the channel. A maximum of 132 alphanumeric characters, including spaces.

+
+

Associated Asset An entity representing fixed plant equipment, facilities, or buildings. All assets have a tag name, an item name, and a full item name. An asset can be assigned to an operator or Station for the purposes of scope of responsibility, that is, for the purposes of controlling what an operator or Station can view or control in your Experion system. Previously known as an area.

+ 		+

The Tag Name A unique identifier given to a point or an asset. Compare: item name. See also: asset, point. of the Asset to be associated with the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC..

+
+

Marginal Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Limit

+ 		+

The communications alarm marginal limit at which the channel is declared to be marginal. When this limit is reached, a high priority alarm is generated. To change the priority of the alarm system wide, see the topic titled "Configuring system alarm priorities" in the Server and Client Configuration Guide. To change the priority of the alarm for one channel, see the topic titled "About configuring custom system alarm priorities for an individual channel or controller" in the Server and Client Configuration Guide.

+

A channel barometer monitors the total number of requests and the number of times the controller did not respond or response was incorrect. The barometer increments by two or more, depending on the error, and decrements for each good call.

+

To calculate an acceptable marginal alarm limit, use the formula In ISA-S88.01 terms, a category of recipe information that includes process inputs, process parameters, and process outputs. In Honeywell terms, the recommended implementation of a formula is through using Phase block formula and report parameters.: Square root of the number of controllers on the channel × Marginal Alarm Limit defined on those controllers (Normally, you specify the same value for all controllers on a channel).

+

For example, if there are 9 controllers on the channel and their Marginal Alarm Limit is set to 25, the value would be 3 (which is the square root of 9) × 25 = 75.

+
+

Fail Alarm Limit

+ 		+

The communications alarm fail limit at which the channel is declared to have failed. When this barometer limit is reached, an urgent alarm is generated. To change the priority of the alarm system wide, see the topic titled "Configuring system alarm priorities" in the Server and Client Configuration Guide. To change the priority of the alarm for one channel, see the topic titled "About configuring custom system alarm priorities for an individual channel or controller" in the Server and Client Configuration Guide.

+

Set this to double the value specified for the channel Marginal Alarm Limit.

+
+

Write Delay

+ 		+

If the channel is on a serial port, the length of time (in milliseconds) that the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. waits before writing to the Port and the Redundant Port of any controller on the channel. The default value is 10 milliseconds for both the Port and the Redundant Port. You can set different values for these two ports.

+

For redundant HC900 Hybrid controller. networks, the suggested Write Delay is 0.

+
+

Connect Timeout

+ 		+

The time (in seconds) the server waits to connect to the Port and the Redundant Port of the controller before abandoning the connection. The default is 10 seconds for both the Port and the Redundant Port. You can set different values for these two ports.

+

Use the default values unless the communications lines have a high error rate or you are using modems.

+

For redundant HC900 networks, the suggested Connect Timeout is 1.

+
+

Read Timeout

+ 		+

The time (in seconds) that the server waits for a reply from the Port and the Redundant Port of the controller. The default is 2 seconds for both the Port and the Redundant Port. You can set different values for these two ports.

+

Use the default values unless the communications lines have a high error rate or you are using modems.

+

For redundant HC900 networks, the suggested Read Timeout is 1.

+
+

Item Type

+ 		+

The type of channel specified when this item was created.

+
+

Last Modified

+ 		+

The date and time the channel properties were modified.

+
+

Last Downloaded

+ 		+

The date and time the channel was last downloaded to the server.

+
+

Item Number

+ 		+

The unique item number currently assigned to this channel, in the format CHNcccc, where cccc is the channel number.

+

You can change the Item Number if you need to match your current server database configuration. The number must be between 0001 and the maximum number of channels allowed for your system. For more information about setting the maximum value, see the topic titled "Adjusting sizing of non-licensed items" in the Supplementary Installation Tasks Guide. Note that the maximum number of channels that may be used in a system is defined in the Experion specification for that Experion release, This number is likely to be less than the maximum number that can be configured in the database as shown in "Adjusting sizing of non-licensed items."

+
+

Channel write delay settings

+

Serial devices using the RS-485 protocol require a minimum period during which no communications occur. Different devices have different requirements. You should configure the write delay to be the largest value required by any device on your RS-485 network. See the following table for requirements of individual devices.

+

Where a delay is specified in number of characters, convert the value to milliseconds using this formula:

Time(ms) = (1,000 × characters)/baud
+
+

Write delay should be rounded up to the nearest whole number.

+

For example, 3.5 chars at 9600 baud = (1,000 × 3.5)/9600 = 3.6 ms (round to 4 ms)

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ UMC800 + + DPR100, DPR180, DPR250 + + DR4300 + + DR4500 + + UDC3300, UDC2300 +
+

3.5 Chars

+ 		+

3.5 Chars

+ 		+

V 4: 20 ms

+

V 5 or later: 3.5 Chars + 2 ms

+ 		+

V 57 and 58: 20 ms

+

V 59 or later: 3.5 Chars + 2 ms

+ 		+

20 ms

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Main_properties_for_a_Honeywell_Universal_Modbus_controller-QB5.htm b/docs/HW_Universal_Modbus/References/Main_properties_for_a_Honeywell_Universal_Modbus_controller-QB5.htm new file mode 100644 index 0000000..cb94e99 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Main_properties_for_a_Honeywell_Universal_Modbus_controller-QB5.htm @@ -0,0 +1,793 @@ + + + + + + + + Main properties for a   Universal Modbus controller + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

Main properties for a Honeywell Universal Modbus controller

+

The Main tab defines the basic properties for a Honeywell Universal Modbus controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC..

+

For information about how to create a controller, see "Building controllers and channels" in the Quick Builder User’s Guide.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Property + + Description +
+

Name

+ 		+

In the case of communications redundancy when the IP Addresses are not defined in Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point., the IP Address 1 and 2 must be specified in the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. hosts file. The host name for IP Address 1 is then the Name property with an 'A' appended to it and the host name for IP Address 2 is the Name property with a 'B' appended to it.

+
+

Description

+ 		+

(Optional) A description of the controller. A maximum of 132 alphanumeric characters, including spaces.

+
+

Channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool. Name

+ 		+

The name of the channel on which the controller communicates with the server.

+

(You must have already defined a channel for it to appear in this list.)

+
+

Marginal Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Limit

+ 		+

The communications alarm marginal limit at which the controller is declared to be marginal. When this limit is reached, a high priority alarm is generated. To change the priority of the alarm system wide, see the topic titled "Configuring system alarm priorities" in the Server and Client Configuration Guide. To change the priority of the alarm for one controller, see the topic titled "About configuring custom system alarm priorities for an individual channel or controller" in the Server and Client Configuration Guide.

+

A controller barometer monitors the total number of requests and the number of times the controller did not respond or response was incorrect. The barometer increments by two or more, depending on the error, and decrements for each good call.

+

The default value is 25.

+
+

Fail Alarm Limit

+ 		+

The communications alarm fail limit at which the controller is declared to have failed. When this barometer limit is reached, an urgent alarm is generated. To change the priority of the alarm system wide, see the topic titled "Configuring system alarm priorities" in the Server and Client Configuration Guide. To change the priority of the alarm for one controller, see the topic titled "About configuring custom system alarm priorities for an individual channel or controller" in the Server and Client Configuration Guide.

+

Set this to double the value specified for the controller Marginal Alarm Limit.

+

The default is 50.

+
+

Dynamic Scanning

+

Fastest Scan Period The time interval between successive scans. See also: scan.

+ 		+

Select the Dynamic Scanning check box to enable dynamic scanning of all point parameters on this controller. The default setting for this check box is selected.

+

Define the fastest possible scan period (in seconds) that dynamic scanning will scan point parameters on this controller. The default is 15 seconds.

+

The dynamic scanning period does not affect the static scanning rate for a parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter.. For example, if the scanning rate for a parameter is 10 seconds, and the dynamic scanning rate for the controller is 15 seconds, the parameter will still be scanned at a period of 10 seconds.

+
+

Device Type

+ 		+

Select from the list, or enter the acronym for, the type of controller you are using. See the section below titled "Available device types."

+

When the device type is HC900 Hybrid controller., the Data Table list appears.

+
+

IP Address

+ 		+

If the channel Port Type is LANVendor, enter the controller's IP address here. If the IP address is not specified, the controller name is used as the TCP Transmission Control Protocol. host name. For more information see the Name property.

+

You can specify the port number to use. The ability to define a specific port enables multiple Modbus devices to be addressed behind a single IP address. If no port number is specified, port number 502 is used by default.

+
+

Device Identifier

+ 		+

The Universal Modbus identification number assigned to your device.

+
+

Data Table

+ 		+

Available for HC900 device types only.

+

The data table used to address the controller. For a description of available data tables, see the section below titled "Data Table types."

+
+

Offset

+ 		+

Enter the lowest address within the range you intend to use. See the section below titled "Using offsets."

+

By default use 0.

+

Note: Offset is not visible when Device Type is HC900 and Data Table is Holding Registers Lower or Holding Registers Upper.

+
+

Item Type

+ 		+

The type of controller specified when this item was created.

+
+

Last Modified

+ 		+

The date and time the controller properties were modified.

+
+

Last Downloaded

+ 		+

The date and time the controller was last downloaded to the server.

+
+

Item Number

+ 		+

The unique item number currently assigned to this controller, in the format RTUnnnnn.

+

You can change the Item Number if you need to match your current server database configuration. The number must be between 00001 and the maximum number of controllers allowed for your system.

+

For more information about setting the maximum value, see the topic titled "Adjusting sizing of non-licensed items" in the Supplementary Installation Tasks Guide.

+

+ Note that the maximum number of controllers that may be used in a system is defined in the Experion specification for that Experion release, This number is likely to be less than the maximum number that can be configured in the database as shown in "Adjusting sizing of non-licensed items." +

+
+

Data Table types

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Data Table + + Table Number + RTU Remote terminal unit. Also known as controller. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. Type + + Address Range +
+

All tables

+ 		+

0, 1, 3, 4

+ 		+

0

+ 		+

0x0–0x1fff (per table)

+
+

Holding Registers Lower

+ 		+

4

+ 		+

4

+ 		+

0x0–0x7fff

+
+

Holding Registers Upper

+ 		+

4

+ 		+

4

+ 		+

0x8000–0xffff

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Property + + Description +
+

Data Table

+ 		+

The name of the data table.

+
+

Table Number

+ 		+

The table number to which the Data Table can access. See the section titled "Table types" in the topic titled "Address syntax for named addresses."

+
+

RTU Type

+ 		+

A number the system uses internally to identify the Data Table.

+
+

Address Range

+ 		+

The range of addresses the Data Table can access.

+
+

Available device types

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Type Acronym + + Controller Device +
+

UDC2300

+ 		+

Universal Digital Controller 2300

+
+

UDC3300

+ 		+

Universal Digital Controller 3300

+
+

DR4300

+ 		+

DR4300 Circular Chart Recorder

+
+

DR4500

+ 		+

DR4500 Circular Chart Recorder

+
+

DPR180

+ 		+

Digital Process Recorder 180

+
+

DPR250

+ 		+

Digital Process Recorder 250

+
+

UMC800

+ 		+

UMC800 Controller

+
+

HC900

+ 		+

HC900 Controller

+
+

TV

+ 		+

Trendview/X-Series Paperless Recorder

+
+

Using offsets

+

+ The server can only access a maximum of 4,096 records in a particular file. Therefore if the server needs to access records beyond that limit, you may need to define several logical controllers in Quick Builder for a device, each with an appropriate offset.

+

For Universal Modbus, use an offset to reference addresses outside the range 0x0000 and 0x1FFF. For example, if you have to refer to addresses between 0x0000 and 0x4000 within a device, you will need to create two controllers, one with an OFFSET=0 (the default) for all addresses up to 0x1FFF, and one with OFFSET=2000 for all addresses between 0x2000 and 0x3FFF.

+

The exception to using offsets are those controllers with a Data Table setting of Holding Registers Lower or Holding Registers Upper. These controllers can access addresses 0x0000 to 0x7fff and 0x8000 to 0xffff respectively without using an offset.

+

HC900 and UMC800 controller OFFSET addresses

+

ATTENTION: This section is not applicable for controllers with a Data Table setting of Holding Registers Lower or Holding Registers Upper.

+

The Controller OFFSET address entry for the UMC800 and HC900 relative to parameter category is provided in the following table. For example, for an HC900, to access up to 24 control loops, all Variables, and up to 1,000 Signal Tags would require setup of two virtual controllers with offset entries of 0 and 2,000 respectively. HC900 control loops 25 through 32 parameters would require an offset entry of 6,000.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Parameter Category + + OFFSET Address for Controller + + Point Addressing +
+ UMC800 + + HC900 +
+

Control Loops

+ 		+

0 (loops 1–16)

+ 		+

0 (loops 1–24)

+ 		+

Named (acronyms)

+
+

Control Loops (25–32)1

+ 		+

Not applicable

+ 		+

6000

+ 		+

Named (acronyms)

+
+

Variables (MATH_VAR)

+ 		+

0 (all Variables, 1–150)

+ 		+

0 (all Variables, 1–600)

+ 		+

Named (acronyms)

+
+

Variables (MATH_VARX)

+ 		+

Not applicable

+ 		+

8000 (Holding Registers Upper)

+ 		+

Named (acronyms)

+
+

SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. Programmers 1–4

+ 		+

0

+ 		+

0

+ 		+

Named (acronyms)

+
+

SP Programmers 5–8

+ 		+

Not applicable

+ 		+

Not supported

+ 		 
+

Signal Tags (TAG)

+ 		+

2000 (Signal Tags 1–500)

+ 		+

2000 (Signal Tags 1–1000)

+ 		+

Named (acronyms)

+
+

Signal Tags 1001–2000

+ 		+

Not applicable

+ 		+

4000

+ 		+

Modbus Hexadecimal codes

+
+

SP Scheduler A facility used to schedule the control of a point on either a periodic or once only (demand) basis. See also: demand scan, periodic scan, point. 1

+ 		+

2000

+ 		+

2000

+ 		+

Named (acronyms)

+
+

SP Scheduler 2

+ 		+

Not applicable

+ 		+

2000

+ 		+

Named (acronyms)

+
+

Sequencers 1–4

+ 		+

Not applicable

+ 		+

4000

+ 		+

Modbus Hexadecimal codes

+
+

Alternator, Stage, Ramp, HOA, Device Control Also known as DevCtl. This function block provides an operator representation and alarming functions for control of digital field devices, such as motors, valves, and pumps. It provides control for up to three outputs with processing based upon PV (process feedback) of up to four inputs. See also: function block, device.

+ 		+

Not applicable

+ 		+

6000

+ 		+

Modbus Hexadecimal codes

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Math_variable_or_calculated_value_group-QB5.htm b/docs/HW_Universal_Modbus/References/Math_variable_or_calculated_value_group-QB5.htm new file mode 100644 index 0000000..f127007 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Math_variable_or_calculated_value_group-QB5.htm @@ -0,0 +1,424 @@ + + + + + + + + Math variable or calculated value group + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Math variable or calculated value group

+

Devices supported

+

The following table lists the devices that support the Math Variable or Calculated Value group, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4500

+ 		+

MATH_VAR [n] [param]

+ 		+

[n] = 1 to 1

+
+

DPR180

+ 		+

MATH_VAR [n] [param]

+ 		+

[n] = 1 to 24

+
+

DPR250

+ 		+

MATH_VAR [n] [param]

+ 		+

[n] = 1 to 32

+
+

UDC3300

+ 		+

MATH_VAR [n] [param]

+ 		+

[n] = 1 to 2

+
+

UMC800

+ 		+

MATH_VAR [n] [param]

+ 		+

[n] = 1 to 150

+
+

HC900 Hybrid controller. +

+ 		+

MATH_VAR [n] [param]

+ 		+

[n] = 1 to 600

+
+

HC900

+ 		+

MATH_VARX [n] [param]

+ 		+

[n] = 601 to 2048

+
+

TrendView

+ 		+

MATH_VAR [n] [param]

+ 		+

[n] = 1 to 64

+
+

Parameters

+

The following table lists the details of the Math Variable or Calculated Value Group parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Math or Calculated Value

+ 		+

MATH_VAR [n] VALUE1

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500, DPR180, DPR250, UDC3300, TV2

+
+

Math or Calculated Value

+ 		+

MATH_VAR [n] VALUE

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC8003, HC900

+
+

Math or Calculated Value

+ 		+

MATH_VARX [n] VALUE

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC9004,

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Math_variable_or_calculated_value_status-QB5.htm b/docs/HW_Universal_Modbus/References/Math_variable_or_calculated_value_status-QB5.htm new file mode 100644 index 0000000..8eb998f --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Math_variable_or_calculated_value_status-QB5.htm @@ -0,0 +1,346 @@ + + + + + + + + Math variable or calculated value status + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Math variable or calculated value status

+

Devices supported

+

The following table lists the devices that support the Math or Calculated Value Status, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4500

+ 		+

MATH_STATUS [n] [param]

+ 		+

[n] = 1 to 1

+
+

DPR180

+ 		+

MATH_STATUS [n] [param]

+ 		+

[n] = 1 to 24

+
+

DPR250

+ 		+

MATH_STATUS [n] [param]

+ 		+

[n] = 1 to 32

+
+

UDC3300

+ 		+

MATH_STATUS [n] [param]

+ 		+

[n] = 1 to 2

+
+

Parameters

+

The following table lists the details of the Math or Calculated Value Status parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Math or Calculated Value Status

+ 		+

MATH_STATUS [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DR4500, DPR180, DPR250, UDC3300

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Nonnumbered_addresses-QB5.htm b/docs/HW_Universal_Modbus/References/Nonnumbered_addresses-QB5.htm new file mode 100644 index 0000000..3686119 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Nonnumbered_addresses-QB5.htm @@ -0,0 +1,764 @@ + + + + + + + + Non-numbered addresses + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Non-numbered addresses

+

The following table lists the details of the Non-numbered Address parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter. + + Address Line + + Param Format + + Access + + Devices +
+

Relay #1

+ 		+

RELAY1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DR4300

+
+

Relay #2

+ 		+

RELAY2

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300

+
+

Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. Relay #1

+ 		+

ALMRLY1

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4500

+
+

Alarm Relay #2

+ 		+

ALMRLY2

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4500

+
+

Control Relay #1

+ 		+

CR1

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4500

+
+

Control Relay #2

+ 		+

CR2

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4500

+
+

Control Relay #3

+ 		+

CR3

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4500

+
+

Control Relay #4

+ 		+

CR4

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4500

+
+

Control Relay

+ 		+

CR

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UDC2300, UDC3300

+
+

Alarm Relay #2

+ 		+

ALMRLY2

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UDC2300, UDC3300

+
+

Alarm Relay #1

+ 		+

ALMRLY1

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UDC2300, UDC3300

+
+

INSTMODE

+ 		+

INSTMODE

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900 Hybrid controller.

+
+

CONFIG_CLEAR

+ 		+

CONFIG_CLEAR

+ 		+

Floating Point

+ 		+

WO

+ 		+

HC900

+
+

LOAD_RECIPE

+ 		+

LOAD_RECIPE

+ 		+

Floating Point

+ 		+

WO

+ 		+

UMC800

+
+

CHART_SPEED

+ 		+

CHART_SPEED

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500

+
+

Pen #1 High Value

+ 		+

PEN1HI

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500

+
+

Pen #1 Low Value

+ 		+

PEN1LO

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500

+
+

Number of Chart Divisions

+ 		+

CHART_DIVS

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

CHART_STATUS

+ 		+

CHART_STATUS

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #1 Status

+ 		+

PEN1STAT

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #2 Status

+ 		+

PEN2STAT

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #2 High Value

+ 		+

PEN2HI

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #2 Low Value

+ 		+

PEN2LO

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #3 Status

+ 		+

PEN3STAT

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #3 High Value

+ 		+

PEN3HI

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #3 Low Value

+ 		+

PEN3LO

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #4 Status

+ 		+

PEN4STAT

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #4 High Value

+ 		+

PEN4_HIGH

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+

Pen #4 Low Value

+ 		+

PEN4_LOW

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4500

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Other_documentation_for_Honeywell_Universal_Modbus-QB5.htm b/docs/HW_Universal_Modbus/References/Other_documentation_for_Honeywell_Universal_Modbus-QB5.htm new file mode 100644 index 0000000..3ff7fc2 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Other_documentation_for_Honeywell_Universal_Modbus-QB5.htm @@ -0,0 +1,341 @@ + + + + + + + + Other documentation for   Universal Modbus + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Other documentation for Honeywell Universal Modbus

+

The following documents are available from Honeywell:

+
    +
  • +

    Modbus RTU Serial Communications User Manual (Part number 51‐52‐25‐66)

    +
    • +
  • +

    HC900 Modbus/TCP Communications User Manual (Part number 51-52-25-111)

    +
    • +
+

The controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. communication and configuration user manuals are listed below.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Instrument Model + + User Manual Part Number +
+

DR4300

+ 		+

51-52-25-71

+
+

DR4500

+ 		+

51-52-25-69

+
+

UDC2300

+ 		+

51-52-25-75

+
+

UDC3300

+ 		+

51-52-25-70

+

51-52-25-38 UDC3000 A Modbus 485 RTU Remote terminal unit. Also known as controller. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. Communication Manual

+
+

DPR180/DPR250

+ 		+

EN1I-6189 DPR180/DPR250 Communication Option Manual

+
+

UMC800

+ 		+

52-52-25-87 Modbus RTU Serial Communications User Manual

+
+

HC900 Hybrid controller. +

+ 		+

51-52-25-107

+

51-52-25-111 HC900 Hybrid Controller Chassis with a control processor module (CPM) installed. The processor works with a shared family of racks, power supplies, I/O modules, and communication cards. See also: C200 controller, control processor, controller, CPM. Communications User Guide

+
+

TrendView - Minitrend, Multitrend, ez Trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter.

+ 		+

43-TV-25-08 Communications Manual

+
+

Ethernet Bridge Card (UMC900, DPR180/DPR250)

+ 		+

51-52-25-96 Ethernet Interface Manual

+
+

X-Series Paperless Recorder

+ 		+

43-TV-25-30 Product Manual

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/PID_loop-QB5.htm b/docs/HW_Universal_Modbus/References/PID_loop-QB5.htm new file mode 100644 index 0000000..e3fb4e3 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/PID_loop-QB5.htm @@ -0,0 +1,1550 @@ + + + + + + + + PID loop + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ PID loop

+

Devices supported

+

The following table lists the devices that support PID Proportional, integral, and derivative control modes. Loops, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

HC900 Hybrid controller. +

+ 		+

LOOP [n] [param]

+ 		+

[n] = 1 to 24

+
+

HC900

+ 		+

LOOPX [n] [param]

+ 		+

[n] = 25 to 32

+
+

DR4300

+ 		+

LOOP [n] [param]

+ 		+

[n] = 1 to 1

+
+

DR4500

+ 		+

LOOP [n] [param]

+ 		+

[n] = 1 to 2

+
+

UDC2300

+ 		+

LOOP [n] [param]

+ 		+

[n] = 1 to 1

+
+

UDC3300

+ 		+

LOOP [n] [param]

+ 		+

[n] = 1 to 2

+
+

UMC800

+ 		+

LOOP [n] [param]

+ 		+

[n] = 1 to 16

+
+

Parameters

+

The following table lists the details of the PID Loop parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Active/Inactive LO

+ 		+

LOOP [n] STATUS_LO

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. #1 SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. #1

+ 		+

LOOP [n] AL1SP1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Alarm #1 SP #2

+ 		+

LOOP [n] AL1SP2

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Alarm #2 SP #1

+ 		+

LOOP [n] AL2SP1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Alarm #2 SP #2

+ 		+

LOOP [n] AL2SP2

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Anti-soot set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. limit enable

+ 		+

LOOP [n] ANTI_SOOT

+ 		+

Discrete (bits).

+

[Status Point Only]

+

Bit 0, 0 = Off, 1 = On

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Auto/Manual

+ 		+

LOOP [n] AMSTAT

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

BIAS

+ 		+

LOOP [n] BIAS

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Carbon Potential Dewpoint

+ 		+

LOOP [n] CPD

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Currently Selected Local or Remote In Honeywell terminology, refers to a device that is not physically connected to the Experion process control network. Set Point

+ 		+

LOOP [n] STATUS_RSP

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Currently Selected Set Point

+ 		+

LOOP [n] STATUS_SP

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Currently Selected Tune Set

+ 		+

LOOP [n] STATUS_TUNE

+ 		+

Discrete (bits).

+

[Status Point Only]

+

Bit 0, 0 = Tune Set 1, 1 = Tune Set 2

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Cycle Time #1

+ 		+

LOOP [n] CYCLE1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+

RO

+ 		+

UMC800, HC900

+
+

Cycle Time #2

+ 		+

LOOP [n] CYCLE2

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+

RO

+ 		+

UMC800, HC900

+
+

DB

+ 		+

LOOP [n] DB

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Demand Tune Request

+ 		+

LOOP [n] TUNE_REQ

+ 		+

Discrete (bits).

+

[Status Point Only]

+

Bit 0, 0 = Off, 1 = On

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Deviation

+ 		+

LOOP [n] DEV

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

DIR

+ 		+

LOOP [n] DIR

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Feed Forward Gain

+ 		+

LOOP [n] FF Foundation Fieldbus. An enabling technology for dynamically integrating dedicated field devices with digitally based control systems. It defines how all "smart" field devices are to communicate with other devices in the control network. The technology is based upon the International Standards Organization's Open System Interconnection (OSI) model for layered communications. See also: Fieldbus Foundation._GAIN

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Furnace Factor

+ 		+

LOOP [n] FFCTR

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Fuzzy State

+ 		+

LOOP [n] FUZZY_STATE

+ 		+

Discrete (bits).

+

[Status Point Only]

+

Bit 0, 0 = Disable, 1 = Enable

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Gain #1

+

(Prop Band #1 if active)

+ 		+

LOOP [n] GAIN1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Gain #2

+

(Prop Band #2 if active)

+ 		+

LOOP [n] GAIN2

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

IMAN Active/Inactive

+ 		+

LOOP [n] STATUS_IMAN

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Input #1

+ 		+

LOOP [n] INP1

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Input #2

+ 		+

LOOP [n] INP2

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+

Local Percent Carbon Monoxide

+ 		+

LOOP [n] PCTCO

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Local Set Point #1

+ 		+

LOOP [n] LSP1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Local Set Point #2

+ 		+

LOOP [n] LSP2

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Local Set Point #3

+ 		+

LOOP [n] LSP3

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+

Manual Reset

+ 		+

LOOP [n] MAN_RESET

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

On/Off Output Hysteresis

+ 		+

LOOP [n] OUT_HYST

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

OP High Limit

+ 		+

LOOP [n] OPHIGH

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Output

+ 		+

LOOP [n] OP

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Output Low Limit

+ 		+

LOOP [n] OPLOW

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Output Override Value

+ 		+

LOOP [n] OPOVR

+ 		+

Floating Point

+ 		+

RW

+ 		+

UDC2300, UDC3300

+
+

Output Working Value

+ 		+

LOOP [n] OPWORK

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Percent Hydrogen

+ 		+

LOOP [n] H2

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

PV The process variable. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. High Range

+ 		+

LOOP [n] PVHIGH

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

PV Low Range

+ 		+

LOOP [n] PVLOW

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Process Variable Normally abbreviated as PV. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. +

+ 		+

LOOP [n] PV1

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Process Variable Override Value

+ 		+

LOOP [n] PVOVR

+ 		+

Floating Point

+ 		+

RW

+ 		+

UDC2300, UDC3300

+
+

Prop Band #1

+ 		+

LOOP [n] PROP1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Prop Band #2

+ 		+

LOOP [n] PROP2

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Rate #1

+ 		+

LOOP [n] RATE1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

RATIO

+ 		+

LOOP [n] RATIO

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Read-only AUTO/MAN Mode

+ 		+

LOOP [n] STATUS_MODE

+ 		+

Discrete (bits).

+

[Status Point Only]

+

Bit 0, 0 = Man, 1 = Auto

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Read-only mode for the PID Loop

+ 		+

LOOP [n] LOOPSTAT

+ 		+

Mode Status - Bit 0 = Auto/Man State. Bit 2 = LSP/RSP State.

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Remote/Local Set Point State

+ 		+

LOOP [n] RSP_STATE

+ 		+

Discrete (bits).

+

[Status Point Only]

+

Bit 0, 0 = LSP, 1 = RSP

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Remote Set Point (RSP)

+ 		+

LOOP [n] RSP

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Reset #1

+ 		+

LOOP [n] RESET1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Reset #2

+ 		+

LOOP [n] RESET2

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Rate #2

+ 		+

LOOP [n] RATE2

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point #1

+ 		+

LOOP [n] SP1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point #2

+ 		+

LOOP [n] SP2

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Override Value

+ 		+

LOOP [n] SPOVR

+ 		+

Floating Point

+ 		+

RW

+ 		+

UDC2300, UDC3300

+
+

Set Point State

+ 		+

LOOP [n] SP_STATE

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UDC2300, UDC3300

+
+

Discrete (bits).

+

[Status Point Only]

+

Bit 0, 0 = SP1, 1 = SP2

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UMC800, HC900

+
+

SP Low Limit

+ 		+

LOOP [n] SPLOW

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

SP High Limit

+ 		+

LOOP [n] SPHIGH

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Temperature in carbon potential loop

+ 		+

LOOP [n] TEMP

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Three Position Step Motor Time

+ 		+

LOOP [n] MOTOR

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Tune Set State

+ 		+

LOOP [n] TUNE_SET_STATE

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Working Set Point (SPWORK)

+ 		+

LOOP [n] WSP

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500

+
+

RW

+ 		+

UDC2300, UDC3300, UMC800, HC900

+
+

Working Set Point (WSP)

+ 		+

LOOP [n] SPWORK

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+

Writable Controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. Mode

+ 		+

LOOP [n] MODEIN

+ 		+

Control Mode - Auto/Man State (bit 0) and LSP/RSP State (bit 2).

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Port_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm b/docs/HW_Universal_Modbus/References/Port_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm new file mode 100644 index 0000000..d362b92 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Port_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm @@ -0,0 +1,388 @@ + + + + + + + + Port properties for a   Universal Modbus channel + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Port properties for a Honeywell Universal Modbus channel

+

The Port tab defines the communication-related properties for a channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool.. The Port Type for Universal Modbus can be:

+ +

Serial port properties

+

ATTENTION: The Serial Port settings must match the settings on your communication devices. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Property + + Description +
+

Serial Port Name

+ 		+

The device name of the serial port.

+
+

Baud rate

+ 		+

The number of data bits per second.

+

The default is 9600.

+
+

Number of Data Bits

+ 		+

The number of data bits used for transmission.

+

The default is 8.

+
+

Stop Bits

+ 		+

The number of stop bits used for transmission

+

The default is 1.

+
+

Parity

+ 		+

Defines parity verification of each character and must match configuration on the end device.

+

The default is NONE.

+
+

Checksum

+ 		+

The type of checksum error detection used for the port.

+

Not applicable for this channel. Select NONE.

+
+

XON/XOFF

+ 		+

The type of XON/XOFF software flow control used to stop a receiver from being overrun with messages from a sender. The types are:

+
    +
  • +

    Input (use XON/XOFF to control the flow of data on the receive line)

    +
    • +
  • +

    None (default)

    +
    • +
  • +

    Output (use XON/XOFF to control the flow of data on the transmit line)

    +
    • +
+
+

Handshaking Options

+ 		+

RS-232 +

 

RS-422

  • No handshaking options are available for RS-422.

RS-485

 
+

Terminal Server port properties

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Property + + Description +
+

Terminal Server A terminal server allows you to connect several controllers and Stations to a LAN even though they only have serial or parallel ports. Most terminal servers also provide a range of serial connection options, such as RS-232, RS-422, and RS-485. See also: controller, LAN, Station. TCP Transmission Control Protocol. Host Name

+

Terminal Server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. TCP Port No

+ 		+

The name and port number of terminal server to which the channel is connected.

+

You can specify either a TCP host name or an IP address, but it must match the TCP host name used when you installed and internally configured the terminal server.

+
+

Idle Timeout

+ 		+

The time, in seconds, the channel waits for a successful connection to the server before closing the connection.

+

A value of 0 indicates that the connection is never closed.

+
+

Checksum

+ 		+

The type of checksum error detection used for the port.

+

Not applicable for this channel. Select NONE.

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/RS485_devices-QB5.htm b/docs/HW_Universal_Modbus/References/RS485_devices-QB5.htm new file mode 100644 index 0000000..3a9d0ab --- /dev/null +++ b/docs/HW_Universal_Modbus/References/RS485_devices-QB5.htm @@ -0,0 +1,282 @@ + + + + + + + + RS-485 devices + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ RS-485 devices

+

Before using your Control Products controllers, ensure that all communication parameters are configured correctly for each controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC.. Configure each controller to use the following communication parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
Parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter. + + Value +
+

Number of Start Bits

+ 		+

1

+
+

Number of Data Bits

+ 		+

8

+
+

Number of Parity Bits

+ 		+

0

+
+

Number of Stop Bits

+ 		+

1

+
+

Make sure that each controller on the RS-485 network is configured for the same baud. When you are ready to configure the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS., you will need to know at what baud each RS-485 network is using.

+

Every controller using the same connection to the server (RS-232 or RS-485) should have a unique Universal Modbus device identification number. Make a list showing what number has been associated with each of your controllers. You will need this information when using Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. to configure the server to use your Control Products controllers.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Redundant_port_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm b/docs/HW_Universal_Modbus/References/Redundant_port_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm new file mode 100644 index 0000000..afff757 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Redundant_port_properties_for_a_Honeywell_Universal_Modbus_channel-QB5.htm @@ -0,0 +1,232 @@ + + + + + + + + Redundant port properties for a   Universal Modbus channel + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Redundant port properties for a Honeywell Universal Modbus channel

+

A communication port used as a redundant link has the same channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool. name but a requires a different port name to its twin. All other entries are identical to those of the primary 1. For Regulatory Control blocks in a cascade strategy: A primary is an upstream block from which an initializable input is fetched. A block has one primary for each initializable input. See also: block. 2. The controller (or chassis) that is currently controlling the redundant process by carrying out the assigned functions. Compare: secondary. See also: assigned function, chassis, controller redundancy. port.

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Set_point_programmer-QB5.htm b/docs/HW_Universal_Modbus/References/Set_point_programmer-QB5.htm new file mode 100644 index 0000000..b9da66b --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Set_point_programmer-QB5.htm @@ -0,0 +1,990 @@ + + + + + + + + Set point programmer + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Set point programmer

+

Devices supported

+

The following table lists the devices that support the set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. programmer, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

SPP Setpoint in percent. See also: setpoint parameter. [n] [param]

+ 		+

[n] = 1 to 1

+
+

DR4500

+ 		+

SPP [n] [param]

+ 		+

[n] = 1 to 2

+
+

UDC2300

+ 		+

SPP [n] [param]

+ 		+

[n] = 1 to 1

+
+

UDC3300

+ 		+

SPP [n] [param]

+ 		+

[n] = 1 to 1

+
+

UMC800

+ 		+

SPP [n] [param]

+ 		+

[n] = 1 to 4

+
+

HC900 Hybrid controller. +

+ 		+

SPP [n] [param]

+ 		+

[n] = 1 to 4

+
+

Parameters

+

The following table lists the details of the set point program parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Set Point Programmer Output

+ 		+

SPP [n] OUT1

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Segment Time Remaining

+ 		+

SPP [n] SEG_TIME_REM

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Start

+ 		+

SPP [n] START

+ 		+

UINT2

+ 		+

WO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Hold

+ 		+

SPP [n] HOLD

+ 		+

UINT2

+ 		+

WO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Advance

+ 		+

SPP [n] ADV

+ 		+

UINT2

+ 		+

WO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Reset

+ 		+

SPP [n] RESET

+ 		+

UINT2

+ 		+

WO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Status - Ready

+ 		+

SPP [n] STATUS_READY

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Status - Run

+ 		+

SPP [n] STATUS_RUN

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Status - Hold

+ 		+

SPP [n] STATUS_HOLD

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Status - End

+ 		+

SPP [n] STATUS_END

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Status - Time Units in Seconds

+ 		+

SPP [n] STATUS_TIME_UNIT In the Experion Batch Manager context, a collection of associated control modules and/or equipment modules and other process equipment in which one or more major processing activities can be conducted. - This term applies to both the physical equipment and the equipment control. - Examples of major processing activities are react, crystallize, and make a solution._S

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Status - Time Units in Minutes

+ 		+

SPP [n] STATUS_TIME_UNIT_M

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Status - Time Units in Hours

+ 		+

SPP [n] STATUS_TIME_UNIT_H

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Elapsed Time

+ 		+

SPP [n] EL_TIME

+ 		+

Floating Point

+ 		+

RO

+ 		+

UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Status - Ramp Rate

+ 		+

SPP [n] STATUS_RAMP_RATE

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+

Set Point Programmer Status - Ramp Units

+ 		+

SPP [n] STATUS_RAMP_UNITS

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Set Point Programmer Current Segment Number

+ 		+

SPP [n] SEG_NO

+ 		+

Floating Point

+ 		+

RO

+ 		+

DR4300, DR4500, UDC2300, UDC3300

+
+

Set Point Programmer Current Segment Number

+ 		+

SPP [n] SEG_NO

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Set Point Programmer Status - Type of Hold

+ 		+

SPP [n] STATUS_HOLD_TYPE

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Status - Current Segment is a ramp

+ 		+

SPP [n] STATUS_RAMP

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #1

+ 		+

SPP [n] EV01

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #2

+ 		+

SPP [n] EV02

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #3

+ 		+

SPP [n] EV03

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #4

+ 		+

SPP [n] EV04

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #5

+ 		+

SPP [n] EV05

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #6

+ 		+

SPP [n] EV06

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #7

+ 		+

SPP [n] EV07

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #8

+ 		+

SPP [n] EV08

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #9

+ 		+

SPP [n] EV09

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #10

+ 		+

SPP [n] EV10

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #11

+ 		+

SPP [n] EV11

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #12

+ 		+

SPP [n] EV12

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #13

+ 		+

SPP [n] EV13

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #14

+ 		+

SPP [n] EV14

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #15

+ 		+

SPP [n] EV15

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Set Point Programmer Segment Event #16

+ 		+

SPP [n] EV16

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Set_point_programmer_1_profile_segment-QB5.htm b/docs/HW_Universal_Modbus/References/Set_point_programmer_1_profile_segment-QB5.htm new file mode 100644 index 0000000..919c584 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Set_point_programmer_1_profile_segment-QB5.htm @@ -0,0 +1,727 @@ + + + + + + + + Set point programmer #1 profile segment + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Set point programmer #1 profile segment

+

Devices supported

+

The following table lists the devices that support the Set Point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. Program #1 Profile Segment, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

SPP1_SEG [n] [param]

+ 		+

[n] = 1 to 24

+
+

DR4500

+ 		+

SPP1_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UDC2300

+ 		+

SPP1_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UDC3300

+ 		+

SPP1_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UMC800

+ 		+

SPP1_SEG [n] [param]

+ 		+

[n] = 1 to 50

+
+

HC900 Hybrid controller. +

+ 		+

SPP1_SEG [n] [param]

+ 		+

[n] = 1 to 50

+
+

Parameters

+

The following table lists the details of the Set Point Program #1 Profile Segment parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Ramp/Soak Segment

+ 		+

SPP1_SEG [n] SEG_TYPE

+

0 = Soak segment

+

1 = Ramp segment

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #1

+ 		+

SPP1_SEG [n] EV01

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #2

+ 		+

SPP1_SEG [n] EV02

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #3

+ 		+

SPP1_SEG [n] EV03

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #4

+ 		+

SPP1_SEG [n] EV04

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #5

+ 		+

SPP1_SEG [n] EV05

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #6

+ 		+

SPP1_SEG [n] EV06

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #7

+ 		+

SPP1_SEG [n] EV07

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #8

+ 		+

SPP1_SEG [n] EV08

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #9

+ 		+

SPP1_SEG [n] EV09

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #10

+ 		+

SPP1_SEG [n] EV10

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #11

+ 		+

SPP1_SEG [n] EV11

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #12

+ 		+

SPP1_SEG [n] EV12

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #13

+ 		+

SPP1_SEG [n] EV13

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #14

+ 		+

SPP1_SEG [n] EV14

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #15

+ 		+

SPP1_SEG [n] EV15

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #16

+ 		+

SPP1_SEG [n] EV16

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output

+ 		+

SPP1_SEG [n] AUX_OUT

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Time

+ 		+

SPP1_SEG [n] TIME1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Rate

+ 		+

SPP1_SEG [n] RATE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Ramp or Soak Value

+ 		+

SPP1_SEG [n] SEG_VALUE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Set_point_programmer_2_profile_segment-QB5.htm b/docs/HW_Universal_Modbus/References/Set_point_programmer_2_profile_segment-QB5.htm new file mode 100644 index 0000000..dcb045a --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Set_point_programmer_2_profile_segment-QB5.htm @@ -0,0 +1,715 @@ + + + + + + + + Set point programmer #2 profile segment + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Set point programmer #2 profile segment

+

Devices supported

+

The following table lists the devices that support the Set Point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. Program #2 Profile Segment, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

SPP2_SEG [n] [param]

+ 		+

[n] = 1 to 24

+
+

DR4500

+ 		+

SPP2_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UDC2300

+ 		+

SPP2_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UDC3300

+ 		+

SPP2_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UMC800, HC900 Hybrid controller.

+ 		+

SPP2_SEG [n] [param]

+ 		+

[n] = 1 to 50

+
+

Parameters

+

The following table lists the details of the Set Point Program #2 Profile Segment parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Ramp/Soak Segment

+ 		+

SPP2_SEG [n] SEG_TYPE

+

0 = Soak segment

+

1 = Ramp segment

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #1

+ 		+

SPP2_SEG [n] EV01

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #2

+ 		+

SPP2_SEG [n] EV02

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #3

+ 		+

SPP2_SEG [n] EV03

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #4

+ 		+

SPP2_SEG [n] EV04

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #5

+ 		+

SPP2_SEG [n] EV05

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #6

+ 		+

SPP2_SEG [n] EV06

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #7

+ 		+

SPP2_SEG [n] EV07

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #8

+ 		+

SPP2_SEG [n] EV08

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #9

+ 		+

SPP2_SEG [n] EV09

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #10

+ 		+

SPP2_SEG [n] EV10

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #11

+ 		+

SPP2_SEG [n] EV11

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #12

+ 		+

SPP2_SEG [n] EV12

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #13

+ 		+

SPP2_SEG [n] EV13

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #14

+ 		+

SPP2_SEG [n] EV14

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #15

+ 		+

SPP2_SEG [n] EV15

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #16

+ 		+

SPP2_SEG [n] EV16

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output

+ 		+

SPP2_SEG [n] AUX_OUT

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Time

+ 		+

SPP2_SEG [n] TIME1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Rate

+ 		+

SPP2_SEG [n] RATE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Ramp or Soak Value

+ 		+

SPP2_SEG [n] SEG_VALUE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Set_point_programmer_3_profile_segment-QB5.htm b/docs/HW_Universal_Modbus/References/Set_point_programmer_3_profile_segment-QB5.htm new file mode 100644 index 0000000..53636e4 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Set_point_programmer_3_profile_segment-QB5.htm @@ -0,0 +1,715 @@ + + + + + + + + Set point programmer #3 profile segment + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Set point programmer #3 profile segment

+

Devices supported

+

The following table lists the devices that support the Set Point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. Programmer #3 Profile Segment, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

SPP3_SEG [n] [param]

+ 		+

[n] = 1 to 24

+
+

DR4500

+ 		+

SPP3_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UDC2300

+ 		+

SPP3_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UDC3300

+ 		+

SPP3_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UMC800, HC900 Hybrid controller.

+ 		+

SPP3_SEG [n] [param]

+ 		+

[n] = 1 to 50

+
+

Parameters

+

The following table lists the details of the Set Point Program #3 Profile Segment parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Ramp/Soak Segment

+ 		+

SPP3_SEG [n] SEG_TYPE

+

0 = Soak Segment

+

1 = Ramp Segment

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #1

+ 		+

SPP3_SEG [n] EV01

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #2

+ 		+

SPP3_SEG [n] EV02

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #3

+ 		+

SPP3_SEG [n] EV03

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #4

+ 		+

SPP3_SEG [n] EV04

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #5

+ 		+

SPP3_SEG [n] EV05

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #6

+ 		+

SPP3_SEG [n] EV06

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #7

+ 		+

SPP3_SEG [n] EV07

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #8

+ 		+

SPP3_SEG [n] EV08

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #9

+ 		+

SPP3_SEG [n] EV09

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #10

+ 		+

SPP3_SEG [n] EV10

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #11

+ 		+

SPP3_SEG [n] EV11

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #12

+ 		+

SPP3_SEG [n] EV12

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #13

+ 		+

SPP3_SEG [n] EV13

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #14

+ 		+

SPP3_SEG [n] EV14

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #15

+ 		+

SPP3_SEG [n] EV15

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #16

+ 		+

SPP3_SEG [n] EV16

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output

+ 		+

SPP3_SEG [n] AUX_OUT

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Time

+ 		+

SPP3_SEG [n] TIME1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Rate

+ 		+

SPP3_SEG [n] RATE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Ramp or Soak Value

+ 		+

SPP3_SEG [n] SEG_VALUE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Set_point_programmer_4_profile_segment-QB5.htm b/docs/HW_Universal_Modbus/References/Set_point_programmer_4_profile_segment-QB5.htm new file mode 100644 index 0000000..c687ec5 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Set_point_programmer_4_profile_segment-QB5.htm @@ -0,0 +1,715 @@ + + + + + + + + Set point programmer #4 profile segment + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Set point programmer #4 profile segment

+

Devices supported

+

The following table lists the devices that support the Set Point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. Programmer #4 Profile Segment, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

SPP4_SEG [n] [param]

+ 		+

[n] = 1 to 24

+
+

DR4500

+ 		+

SPP4_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UDC2300

+ 		+

SPP4_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UDC3300

+ 		+

SPP4_SEG [n] [param]

+ 		+

[n] = 1 to 12

+
+

UMC800, HC900 Hybrid controller.

+ 		+

SPP4_SEG [n] [param]

+ 		+

[n] = 1 to 50

+
+

Parameters

+

The following table lists the details of the Set Point Program #4 Profile Segment parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Ramp/Soak Segment

+ 		+

SPP4_SEG [n] SEG_TYPE

+

0 = Soak Segment

+

1 = Ramp Segment

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #1

+ 		+

SPP4_SEG [n] EV01

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #2

+ 		+

SPP4_SEG [n] EV02

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #3

+ 		+

SPP4_SEG [n] EV03

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #4

+ 		+

SPP4_SEG [n] EV04

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #5

+ 		+

SPP4_SEG [n] EV05

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #6

+ 		+

SPP4_SEG [n] EV06

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #7

+ 		+

SPP4_SEG [n] EV07

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #8

+ 		+

SPP4_SEG [n] EV08

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #9

+ 		+

SPP4_SEG [n] EV09

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #10

+ 		+

SPP4_SEG [n] EV10

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #11

+ 		+

SPP4_SEG [n] EV11

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #12

+ 		+

SPP4_SEG [n] EV12

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #13

+ 		+

SPP4_SEG [n] EV13

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #14

+ 		+

SPP4_SEG [n] EV14

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #15

+ 		+

SPP4_SEG [n] EV15

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #16

+ 		+

SPP4_SEG [n] EV16

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output

+ 		+

SPP4_SEG [n] AUX_OUT

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Time

+ 		+

SPP4_SEG [n] TIME1

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Rate

+ 		+

SPP4_SEG [n] RATE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+

Ramp or Soak Value

+ 		+

SPP4_SEG [n] SEG_VALUE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC2300, UDC3300, UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Set_point_scheduler_1_segment-QB5.htm b/docs/HW_Universal_Modbus/References/Set_point_scheduler_1_segment-QB5.htm new file mode 100644 index 0000000..3e9b09f --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Set_point_scheduler_1_segment-QB5.htm @@ -0,0 +1,1050 @@ + + + + + + + + Set point scheduler #1 segment + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Set point scheduler #1 segment

+

Devices supported

+

The following table lists the devices that support the Scheduler A facility used to schedule the control of a point on either a periodic or once only (demand) basis. See also: demand scan, periodic scan, point. #1 Segment, and their formats.

+ + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

UMC800, HC900 Hybrid controller.

+ 		+

SCHED1_SEG [n] [param]

+ 		+

[n] = 1 to 50

+
+

Parameters

+

The following table lists the details of the Scheduler #1 Segment parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Soak Type #1

+ 		+

SCHED1_SEG [n] GUAR11

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Type #2

+ 		+

SCHED1_SEG [n] GUAR2

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Type #3

+ 		+

SCHED1_SEG [n] GUAR3

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Type #4

+ 		+

SCHED1_SEG [n] GUAR4

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Type #5

+ 		+

SCHED1_SEG [n] GUAR5

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Type #6

+ 		+

SCHED1_SEG [n] GUAR6

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Type #7

+ 		+

SCHED1_SEG [n] GUAR7

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Type #8

+ 		+

SCHED1_SEG [n] GUAR8

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #1

+ 		+

SCHED1_SEG [n] EVENT_01

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #2

+ 		+

SCHED1_SEG [n] EVENT_02

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #3

+ 		+

SCHED1_SEG [n] EVENT_03

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #4

+ 		+

SCHED1_SEG [n] EVENT_04

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #5

+ 		+

SCHED1_SEG [n] EVENT_05

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #6

+ 		+

SCHED1_SEG [n] EVENT_06

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #7

+ 		+

SCHED1_SEG [n] EVENT_07

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #8

+ 		+

SCHED1_SEG [n] EVENT_08

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #9

+ 		+

SCHED1_SEG [n] EVENT_09

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #10

+ 		+

SCHED1_SEG [n] EVENT_10

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #11

+ 		+

SCHED1_SEG [n] EVENT_11

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #12

+ 		+

SCHED1_SEG [n] EVENT_12

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #13

+ 		+

SCHED1_SEG [n] EVENT_13

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #14

+ 		+

SCHED1_SEG [n] EVENT_14

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #15

+ 		+

SCHED1_SEG [n] EVENT_15

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #16

+ 		+

SCHED1_SEG [n] EVENT_16

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Time

+ 		+

SCHED1_SEG [n] TIME Parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter. Format:

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Output #1

+ 		+

SCHED1_SEG [n] OUTPUT1

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Output #2

+ 		+

SCHED1_SEG [n] OUTPUT2

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Output #3

+ 		+

SCHED1_SEG [n] OUTPUT3

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Output #4

+ 		+

SCHED1_SEG [n] OUTPUT4

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Output #5

+ 		+

SCHED1_SEG [n] OUTPUT5

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Output #6

+ 		+

SCHED1_SEG [n] OUTPUT6

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Output #7

+ 		+

SCHED1_SEG [n] OUTPUT7

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Output #8

+ 		+

SCHED1_SEG [n] OUTPUT8

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output #1

+ 		+

SCHED1_SEG [n] AUX_SOAK_1

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output #2

+ 		+

SCHED1_SEG [n] AUX_SOAK_2

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output #3

+ 		+

SCHED1_SEG [n] AUX_SOAK_3

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output #4

+ 		+

SCHED1_SEG [n] AUX_SOAK_4

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output #5

+ 		+

SCHED1_SEG [n] AUX_SOAK_5

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output #6

+ 		+

SCHED1_SEG [n] AUX_SOAK_6

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output #7

+ 		+

SCHED1_SEG [n] AUX_SOAK_7

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Soak Value for Auxiliary Output #8

+ 		+

SCHED1_SEG [n] AUX_SOAK_8

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Number of Times to Recycle

+ 		+

SCHED1_SEG [n] RECYCLE

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Recycle Segment

+ 		+

SCHED1_SEG [n] RECYCLE_SEG

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Set_point_scheduler_2_segment-QB5.htm b/docs/HW_Universal_Modbus/References/Set_point_scheduler_2_segment-QB5.htm new file mode 100644 index 0000000..b3b00f5 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Set_point_scheduler_2_segment-QB5.htm @@ -0,0 +1,1051 @@ + + + + + + + + Set point scheduler #2 segment + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Set point scheduler #2 segment

+

Devices supported

+

The following table lists the devices that support the Scheduler A facility used to schedule the control of a point on either a periodic or once only (demand) basis. See also: demand scan, periodic scan, point. #2 Segment, and their formats.

+ + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

HC900 Hybrid controller. +

+ 		+

SCHED2_SEG [n] [param]

+ 		+

[n] = 1 to 50

+
+

Parameters

+

The following table lists the details of the Scheduler #2 Segment parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Soak Type #1

+ 		+

SCHED2_SEG [n] GUAR11

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RW

+ 		+

HC900

+
+

Soak Type #2

+ 		+

SCHED2_SEG [n] GUAR2

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Soak Type #3

+ 		+

SCHED2_SEG [n] GUAR3

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Soak Type #4

+ 		+

SCHED2_SEG [n] GUAR4

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Soak Type #5

+ 		+

SCHED2_SEG [n] GUAR5

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Soak Type #6

+ 		+

SCHED2_SEG [n] GUAR6

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Soak Type #7

+ 		+

SCHED2_SEG [n] GUAR7

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Soak Type #8

+ 		+

SCHED2_SEG [n] GUAR8

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #1

+ 		+

SCHED2_SEG [n] EVENT_01

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #2

+ 		+

SCHED2_SEG [n] EVENT_02

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #3

+ 		+

SCHED2_SEG [n] EVENT_03

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #4

+ 		+

SCHED2_SEG [n] EVENT_04

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #5

+ 		+

SCHED2_SEG [n] EVENT_05

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #6

+ 		+

SCHED2_SEG [n] EVENT_06

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #7

+ 		+

SCHED2_SEG [n] EVENT_07

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #8

+ 		+

SCHED2_SEG [n] EVENT_08

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #9

+ 		+

SCHED2_SEG [n] EVENT_09

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #10

+ 		+

SCHED2_SEG [n] EVENT_10

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #11

+ 		+

SCHED2_SEG [n] EVENT_11

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #12

+ 		+

SCHED2_SEG [n] EVENT_12

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #13

+ 		+

SCHED2_SEG [n] EVENT_13

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #14

+ 		+

SCHED2_SEG [n] EVENT_14

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #15

+ 		+

SCHED2_SEG [n] EVENT_15

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Event #16

+ 		+

SCHED2_SEG [n] EVENT_16

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

HC900

+
+

Time

+ 		+

SCHED2_SEG [n] TIME

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Output #1

+ 		+

SCHED2_SEG [n] OUTPUT1

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Output #2

+ 		+

SCHED2_SEG [n] OUTPUT2

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Output #3

+ 		+

SCHED2_SEG [n] OUTPUT3

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Output #4

+ 		+

SCHED2_SEG [n] OUTPUT4

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Output #5

+ 		+

SCHED2_SEG [n] OUTPUT5

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Output #6

+ 		+

SCHED2_SEG [n] OUTPUT6

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Output #7

+ 		+

SCHED2_SEG [n] OUTPUT7

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Output #8

+ 		+

SCHED2_SEG [n] OUTPUT8

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Soak Value for Auxiliary Output #1

+ 		+

SCHED2_SEG [n] AUX_SOAK_1

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Soak Value for Auxiliary Output #2

+ 		+

SCHED2_SEG [n] AUX_SOAK_2

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Soak Value for Auxiliary Output #3

+ 		+

SCHED2_SEG [n] AUX_SOAK_3

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Soak Value for Auxiliary Output #4

+ 		+

SCHED2_SEG [n] AUX_SOAK_4

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Soak Value for Auxiliary Output #5

+ 		+

SCHED2_SEG [n] AUX_SOAK_5

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Soak Value for Auxiliary Output #6

+ 		+

SCHED2_SEG [n] AUX_SOAK_6

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Soak Value for Auxiliary Output #7

+ 		+

SCHED2_SEG [n] AUX_SOAK_7

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Soak Value for Auxiliary Output #8

+ 		+

SCHED2_SEG [n] AUX_SOAK_8

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Number of Times to Recycle

+ 		+

SCHED2_SEG [n] RECYCLE

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+

Recycle Segment

+ 		+

SCHED2_SEG [n] RECYCLE_SEG

+ 		+

Floating Point

+ 		+

RW

+ 		+

HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Set_point_scheduler_values-QB5.htm b/docs/HW_Universal_Modbus/References/Set_point_scheduler_values-QB5.htm new file mode 100644 index 0000000..6baea81 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Set_point_scheduler_values-QB5.htm @@ -0,0 +1,1209 @@ + + + + + + + + Set point scheduler values + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Set point scheduler values

+

Devices supported

+

The following table lists the devices that support the Set Point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. Scheduler A facility used to schedule the control of a point on either a periodic or once only (demand) basis. See also: demand scan, periodic scan, point. Values, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

UMC800

+ 		+

SCHED [n] [param]

+ 		+

[n] = 1 to 1

+
+

HC900 Hybrid controller. +

+ 		+

SCHED [n] [param]

+ 		+

[n] = 1 to 2

+
+

Parameters

+

The following table lists the details of the Scheduler Values parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Output #1

+ 		+

SCHED [n] OUTPUT11

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Output #1

+ 		+

SCHED [n] OUTPUT2

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Output #1

+ 		+

SCHED [n] OUTPUT3

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Output #4

+ 		+

SCHED [n] OUTPUT4

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Output #5

+ 		+

SCHED [n] OUTPUT5

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Output #6

+ 		+

SCHED [n] OUTPUT6

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Output #7

+ 		+

SCHED [n] OUTPUT7

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Output #8

+ 		+

SCHED [n] OUTPUT8

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Auxiliary Output #1

+ 		+

SCHED [n] AUX_OUT1

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Auxiliary Output #2

+ 		+

SCHED [n] AUX_OUT2

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Auxiliary Output #3

+ 		+

SCHED [n] AUX_OUT3

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Auxiliary Output #4

+ 		+

SCHED [n] AUX_OUT4

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Auxiliary Output #5

+ 		+

SCHED [n] AUX_OUT5

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Auxiliary Output #6

+ 		+

SCHED [n] AUX_OUT6

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Auxiliary Output #7

+ 		+

SCHED [n] AUX_OUT7

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Auxiliary Output #8

+ 		+

SCHED [n] AUX_OUT8

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Current Program Number

+ 		+

SCHED [n] PROG_NO

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Current Segment Number

+ 		+

SCHED [n] SEG_NO

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Program Elapsed Time

+ 		+

SCHED [n] EL_TIME

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Segment Time Remaining

+ 		+

SCHED [n] TIME_REMAIN

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Schedule Save Request

+ 		+

SCHED [n] SCHED_SAVE

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Guaranteed Soak Limit #1

+ 		+

SCHED [n] SOAK_LIMIT_1

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Guaranteed Soak Limit #2

+ 		+

SCHED [n] SOAK_LIMIT_2

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Guaranteed Soak Limit #3

+ 		+

SCHED [n] SOAK_LIMIT_3

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Guaranteed Soak Limit #4

+ 		+

SCHED [n] SOAK_LIMIT_4

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Guaranteed Soak Limit #5

+ 		+

SCHED [n] SOAK_LIMIT_5

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Guaranteed Soak Limit #6

+ 		+

SCHED [n] SOAK_LIMIT_6

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Guaranteed Soak Limit #7

+ 		+

SCHED [n] SOAK_LIMIT_7

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Guaranteed Soak Limit #8

+ 		+

SCHED [n] SOAK_LIMIT_8

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Jog Segment

+ 		+

SCHED [n] JOG_SEG

+ 		+

Floating Point

+ 		+

RW

+ 		+

UMC800, HC900

+
+

Event #1

+ 		+

SCHED [n] EVENT_01

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #2

+ 		+

SCHED [n] EVENT_02

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #3

+ 		+

SCHED [n] EVENT_03

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #4

+ 		+

SCHED [n] EVENT_04

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #5

+ 		+

SCHED [n] EVENT_05

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #6

+ 		+

SCHED [n] EVENT_06

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #7

+ 		+

SCHED [n] EVENT_07

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #8

+ 		+

SCHED [n] EVENT_08

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #9

+ 		+

SCHED [n] EVENT_09

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #10

+ 		+

SCHED [n] EVENT_10

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #11

+ 		+

SCHED [n] EVENT_11

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #12

+ 		+

SCHED [n] EVENT_12

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #13

+ 		+

SCHED [n] EVENT_13

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #14

+ 		+

SCHED [n] EVENT_14

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #15

+ 		+

SCHED [n] EVENT_15

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Event #16

+ 		+

SCHED [n] EVENT_16

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Status

+ 		+

SCHED [n] STATUS

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RO

+ 		+

UMC800, HC900

+
+

Start Schedule

+ 		+

SCHED [n] START

+ 		+

UINT2

+ 		+

WO

+ 		+

UMC800, HC900

+
+

Hold Schedule

+ 		+

SCHED [n] HOLD

+ 		+

UINT2

+ 		+

WO

+ 		+

UMC800, HC900

+
+

Advance Schedule

+ 		+

SCHED [n] ADVANCE

+ 		+

UINT2

+ 		+

WO

+ 		+

UMC800, HC900

+
+

Reset Schedule

+ 		+

SCHED [n] RESET

+ 		+

UINT2

+ 		+

WO

+ 		+

UMC800, HC900

+
+

Time Units

+ 		+

SCHED [n] UNITS_TIME

+ 		+

Discrete (bits).

+

[Status Point Only]

+ 		+

RW

+ 		+

UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Setting_up_time_synchronization_for_UMC800_and_HC900_controllers-QB5.htm b/docs/HW_Universal_Modbus/References/Setting_up_time_synchronization_for_UMC800_and_HC900_controllers-QB5.htm new file mode 100644 index 0000000..7f3e548 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Setting_up_time_synchronization_for_UMC800_and_HC900_controllers-QB5.htm @@ -0,0 +1,260 @@ + + + + + + + + Setting up time synchronization for UMC800 and HC900 controllers + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Setting up time synchronization for UMC800 and HC900 controllers

+

Use the Time Sync Value field in the Advanced tab to set up time synchronization In dual redundancy control, the process of aligning the databases of two devices. Once two devices are synchronized, they must continue to track database changes, or else the secondary will revert to a disqualified state of readiness. See also: device, dual redundancy, readiness, secondary. for UMC800 and HC900 Hybrid controller. controllers.

+ + + + + + + + + + + + + + + +
+ Property + + Description +
+

Time Sync Value

+ 		+

Add the value 0, 1, or 2 to set up time synchronization, where:

+

0 = No time synchronization (default)

+

1 = UMC800 Time Sync using 4× registers 1be0–1be5

+

2 = HC900 Time Sync using 4× registers 1df0–1df5

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Tagged_signal-QB5.htm b/docs/HW_Universal_Modbus/References/Tagged_signal-QB5.htm new file mode 100644 index 0000000..678e5d4 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Tagged_signal-QB5.htm @@ -0,0 +1,324 @@ + + + + + + + + Tagged signal + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Tagged signal

+

Devices supported

+

The following table lists the devices that support Tagged Signal, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

UMC800

+ 		+

TAG [n] [param]

+ 		+

[n] = 1 to 500

+
+

HC900 Hybrid controller. +

+ 		+

TAG [n] [param]

+ 		+

[n] = 1 to 1,000

+
+

Parameters

+

The following table lists the details of the Tagged Signal parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Tagged Signal Value

+ 		+

TAG [n] VALUE1

+ 		+

Floating Point

+ 		+

RO

+ 		+

UMC800, HC900

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Totalizer_value_group-QB5.htm b/docs/HW_Universal_Modbus/References/Totalizer_value_group-QB5.htm new file mode 100644 index 0000000..ea0bbc9 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Totalizer_value_group-QB5.htm @@ -0,0 +1,345 @@ + + + + + + + + Totalizer value group + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Totalizer value group

+

Devices supported

+

The following table lists the devices that support the Totalizer Value group, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

TOTALIZER [n] [param]

+ 		+

[n] = 1 to 1

+
+

DR4500

+ 		+

TOTALIZER [n] [param]

+ 		+

[n] = 1 to 4

+
+

UDC3300

+ 		+

TOTALIZER [n] [param]

+ 		+

[n] = 1 to 1

+
+

TrendView

+ 		+

TOTALIZER [n] [param]

+ 		+

[n] = 1 to 64

+
+

Parameters

+

The following table lists the details of the Totalizer Value Group parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Totalizer Value

+ 		+

TOTALIZER [n] VALUE

+ 		+

Floating Point

+ 		+

RW

+ 		+

DR4300, DR4500, UDC3300

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Totalizer_value_status-QB5.htm b/docs/HW_Universal_Modbus/References/Totalizer_value_status-QB5.htm new file mode 100644 index 0000000..91c00a0 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Totalizer_value_status-QB5.htm @@ -0,0 +1,337 @@ + + + + + + + + Totalizer value status + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Totalizer value status

+

Devices supported

+

The following table lists the devices that support the Totalizer Value Status, and their formats.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Device + + Supported Address Format + + Range +
+

DR4300

+ 		+

TOTALIZER_STATUS [n] [param]

+ 		+

[n] = 1 to 1

+
+

DR4500

+ 		+

TOTALIZER_STATUS [n] [param]

+ 		+

[n] = 1 to 4

+
+

UDC3300

+ 		+

TOTALIZER_STATUS [n] [param]

+ 		+

[n] = 1 to 1

+
+

Parameters

+

The following table lists the details of the Totalizer Value Status parameters.

+ + + + + + + + + + + + + + + + + + + + + + + + +
+ Param + + Address Line + + Param Format + + Access + + Devices +
+

Totalizer Status

+ 		+

TOTALIZER_STATUS [n] STATUS1

+ 		+

Discrete (bits).

+

[Status Point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. Only]

+

0 = Totalizer Off

+

1 = Totalizer On

+ 		+

RO

+ 		+

DR4300, DR4500, UDC3300

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Troubleshooting_Honeywell_Universal_Modbus_common_problems-QB5.htm b/docs/HW_Universal_Modbus/References/Troubleshooting_Honeywell_Universal_Modbus_common_problems-QB5.htm new file mode 100644 index 0000000..40c0cd6 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Troubleshooting_Honeywell_Universal_Modbus_common_problems-QB5.htm @@ -0,0 +1,320 @@ + + + + + + + + Troubleshooting   Universal Modbus common problems + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

Troubleshooting Honeywell Universal Modbus common problems

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Error message or problem + + Description +
+

You see the following error in the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. log file:

+

Error code 0106 (Device Timeout) +

+ 		+

The server has not received a response from the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC..

+
+

You see the following error in the server log file:

+

Error code 8102 (MODBUS error 2 - illegal data address) +

+ 		+

You either specified an illegal address, or an illegal number of addresses.

+
+

You see the following error in the Station Experion's main operator interface. Station presents information using a series of displays. See also: display. Message Zone The line below Station's toolbar where explanatory messages and prompts appear. Compare: command zone. See also: Station. when you try to change the OP parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter.:

+

CONTROL - Illegal mode for control of parameter +

+ 		+

The point is in AUTO mode, or its equivalents (AUTO-LSP, CASC, AUTO-RSP). You must change the mode of the point to MAN or its equivalents (MAN-LSP, MAN-RSP).

+
+

You see the following error in the Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. output file:

+

Address is outside hardware cross reference table +

+ 		+

You have upgraded your database from a previous server version and there is not enough room to store the controller addresses.

+

To rectify the problem, follow these steps:

+
    +
  1. +

    Make a backup of \server\data.

    +
    2. +
  2. +

    Open a Command Prompt window and type:

    +

    sysbld -PRESERVE -FULL +

    +
    3. +
  3. +

    Answer Y to the first two queries.

    +
    4. +
  4. +

    When presented with the ability to change all sorts of database values, press ENTER until you see the following message:

    +

    There are 8192 addresses per rtu. Enter required number of addresses +

    +
    5. +
  5. +

    Change the number of addresses per RTU Remote terminal unit. Also known as controller. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. (controller) to 32766.

    +
    6. +
  6. +

    Keep pressing ENTER until the sysbld command terminates.

    +
    7. +
+
+

The address LOOP n SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. doesn't download.

+ 		+

The SP parameter is not a valid named address because there are a number of set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. types available, and a simple SP is ambiguous. WSP stands for working set point and SP1 stands for set point 1. In most cases, WSP works best.

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Troubleshooting_problems_with_specific_controller_models-QB5.htm b/docs/HW_Universal_Modbus/References/Troubleshooting_problems_with_specific_controller_models-QB5.htm new file mode 100644 index 0000000..a61e8fe --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Troubleshooting_problems_with_specific_controller_models-QB5.htm @@ -0,0 +1,560 @@ + + + + + + + + Troubleshooting problems with specific controller models + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

Troubleshooting problems with specific controller models

+

UDC3300 problems

+ + + + + + + + + + + + + + + +
+ Error message or problem + + Description +
+ + +

The communications link between the controller and server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. can become overwhelmed. The solution is to increase the COM Tx Delay on the controller faceplate.

+
+

UMC800 problems

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Error message or problem + + Description +
+ + +

The number shown on the top right-hand side of the PID block does NOT correspond with the loop number. You can find out the appropriate number by selecting FilePrintBlock Parameters in the Honeywell Control Builder The control building software, running on a Windows operating system, that provides an environment in which to build control strategies using function blocks for the Honeywell control processor. It includes Function Block Builder, SCM Builder, Function Block Symbols, SCM Symbols and Configuration Forms, SCM Blocks and Configuration Forms, Function Block Faceplate, and the Data Entry Mechanism. See also: control processor. configuration utility.

+

One of the properties printed out is Modbus ® loop number. Use this number for your loops.

+
+

The address PID n PV doesn't download.

+ 		+

The PID part of the address is not valid and doesn't appear in the Universal Modbus driver documentation.

+

You cannot use the names of control blocks within Control Builder as Universal Modbus addresses. You can only use the addresses listed in the Universal Modbus documentation.

+
+

You know that you should use the address AI n but you don't know what value to use for n.

+ 		+

The analog input number is calculated using the formula In ISA-S88.01 terms, a category of recipe information that includes process inputs, process parameters, and process outputs. In Honeywell terms, the recommended implementation of a formula is through using Phase block formula and report parameters.: n = (m-1) * 4 + c.

+

n = the analog input number.

+

m = the module In SafeView, the file name and path of an executable file name. An application's module is one of the three means by which an application's display window can be “matched” and thus managed by SafeView. The other two are window title and window category./slot number. The UMC800 has 16 slots, numbered 1 to 16.

+

c = the channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool. number (of the analog input). The analog input devices have up to four channels, numbered 1 to 4.

+
+

You know that you should use the address DI n or DO n but you don't know what value to use for n.

+ 		+

The digital input number is calculated using the formula: n = (m-1) * 16 + c.

+

n = the digital input or output number.

+

m = the module/slot number. The UMC800 has 16 slots, numbered 1 to 16.

+

c = the channel number (of the digital input or output). The digital I/O devices have up to 16 channels, numbered 1 to 16.

+
+

You want to write to a digital output.

+ 		+

Honeywell recommends against writing to a digital output because this forces the output to a particular state, which cannot be overridden using the UMC800 internal logic. (Since this practice is inherently dangerous, it is not supported.)

+

You can create a safer implementation using digital variables and some UMC800 logic blocks.

+
+

You see the error:

+

***** PNTBLD ERROR ***** illegal MODICON plc address +

+

in the Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. output when trying to download a signal tag as a source address (such as TAG 2) to the server.

+ 		+

+ You might be trying to download to a controller whose OFFSET address is not 0x2000. Refer to the Universal Modbus documentation for information about address ranges and OFFSET.

+
+

You see the error:

+

***** PNTBLD ERROR ***** illegal MODICON plc address +

+

in the Quick Builder output when trying to download a signal tag, such as TAG 2, as a destination address to the server.

+ 		+

Signal tags are read-only parameters, so cannot be used as destination addresses. Refer to the Universal Modbus documentation for information about read-only and write-only addresses.

+
+

You don't know what number to use for the signal tag using named address TAG or variable using named address MATH_VAR.

+ 		+
    +
  1. +

    Start the configuration utility Honeywell Control Builder configuration utility.

    +
    2. +
  2. +

    Select FilePrint.

    +
    3. +
  3. +

    Select Tag Properties, and then click OK.

    +
    4. +
  4. +

    Your printout should show your signal tags. To the right of the words 'Signal Tag' or 'Variable' you should see a number. This is the tag number you should use in the address TAG n or MATH_VAR n.

    +
    5. +
+
+

HC900 problems

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Error message or problem + + Description +
+

You see the log message:

+

Event nnn has bad address. Cannot History Backfill event +

+ 		+

This message occurs when points have been configured in HC (Hybrid Control) Designer with Use Signal Tag as the Trend Backfill Log Point Selectionand the backfill data cannot be matched to points built in Experion. If all the points on the controller are configured incorrectly like this, when backfill completes, the event that Experion raises will say that "No samples required backfilling into history."

+

To fix this problem, you must use HC (Hybrid Control) Designer to change the Trend Backfill Log Point Selection from Use Signal Tag to Use Modbus Address. If this is done after Trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. Point Function Blocks have been configured, you must also remove and re-add each of the points to the Trend Point Function Blocks and download the configuration to the controller. Note that doing this will also cause the controller to lose the backfill data it was storing.

+
+

You know you should use the address LOOP n parametername but you don't know what value to use for n.

+

You want to access the process variable of the only control loop that you have configured. You used the number n which appears on the upper-right hand corner of the PID block (LOOP n PV The process variable. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. for loops 1-24 and LOOPX n PV for loops 25-32), but the values shown by the server don't seem to match those values in your controller.

+ 		+

The block execution order number shown on the upper right-hand side of the block does NOT correspond with the loop number. The loop number corresponds with order of entry of the PID loop blocks only. You can find the appropriate number by selecting FilePrint Report Preview, then select the FBD icon and Modbus Register MapSummary Function Block Report in the Hybrid Control (HC) Designer configuration. The Loop Blocks are listed by number. Use this number for your loops.

+
+

For analog inputs in the first rack Chassis or cardfile capable of accepting plug-in modules. See also: chassis., you know that you should use the address AI Analog Input. Compare: DI. n but you don't know what value to use for n.

+ 		+

For the first rack only, the analog input number is calculated using the formula:

+

n = (m-1) * 8 + c.

+

n = the analog input number

+

m = the module/slot number. The HC900 Hybrid controller. has up to 12 slots depending on rack size, numbered 1 to 12.

+

c = the channel number (of the analog input).

+

The analog input cards have 8 channels, numbered 1 to 8. The 2nd AI channel for slot/module 2 in Rack 1 is AI 10.

+
+

I don't know to access analog inputs beyond the first rack.

+ 		+

A Signal Tag is the only way to access analog inputs on a Holding Register controller. Access to analog inputs directly using Non-Named hexadecimal addressing requires Table 3 (Input Register), whereas Signal Tags use Table 4 (Holding Register).

+

If you have provided a Signal Tag for the Analog Input block output, use this tag number and TAG as the address name, for example, TAG 45 for a controller with an OFFSET address of 2000. Otherwise, you must use Non-Named hexadecimal addressing for a controller with an offset of 0. The address ranges for the racks are as follows:

+

Rack 1: 0 - FF Foundation Fieldbus. An enabling technology for dynamically integrating dedicated field devices with digitally based control systems. It defines how all "smart" field devices are to communicate with other devices in the control network. The technology is based upon the International Standards Organization's Open System Interconnection (OSI) model for layered communications. See also: Fieldbus Foundation.

+

Rack 2: 100-1FF

+

Rack 3: 200 – 2FF

+

Rack 4: 300 – 3FF

+

Rack 5: 400 – 4FF

+

Zero-based addressing is used and two contiguous registers comprise the floating point data. Table 3 (Modbus Function Code 4) is used for access. The first analog channel for slot/module 1 in Rack 2 is: 3:x100 IEEEFP, channel 2 is 3:x102 IEEEFP, channel 8 is 3:x10E IEEEFP. There are 8 inputs per slot/module.

+
+

For analog inputs in the first rack, you know that you should use the address DI Digital input. Compare: AI. See also: input. n or DO Digital output. Compare: AO. See also: output. n but you don't know what value to use for n.

+ 		+

For the first rack only, the digital or output number is calculated using the formula:

+

n = (m-1) * 16 + c.

+

n = the analog input number

+

m = the module/slot number. The HC900 has up to 12 slots depending on rack size, numbered 1 to 12.

+

c = the channel number (of the digital input or output). The digital I/O cards have 8 or 16 channels, numbered 1 to 8 or 1 to 16. An allocation A form of coordination control that assigns a resource to a batch or unit. Note that an allocation can be for the entire resource or for portions of a resource. of 16 I/O is made for each slot/module regardless of type. The 2nd DI channel for slot/module 3 in Rack 1 is DI 34.

+
+

I don't know to access digital I/O beyond the first rack.

+ 		+

A Signal Tag is the only way to access digital inputs and outputs on a Holding Register controller. Access to digital inputs and outputs directly using Non-Named hexadecimal addressing requires Table 1 (Digital Input) and Table 0 (Digital Output), whereas Signal Tags use Table 4 (Holding Register).

+

If you have provided a Signal Tag for the Digital Input or Output block output, use this tag number and TAG as the address name, for example, TAG 56 for a controller with an OFFSET address of 2000. Otherwise, you must use Non-Named hexadecimal addressing for a controller with an offset of 0. The address ranges for the racks are as follows:

+

Rack 1: 0 - FF

+

Rack 2: 100-1FF

+

Rack 3: 200 – 2FF

+

Rack 4: 300 – 3FF

+

Rack 5: 400 – 4FF

+

Zero-based addressing is used and two contiguous registers comprise the floating point data. Table 1 is used for access to digital inputs and Table 0 is used for digital outputs. The 3rd digital input channel for slot/module 6 in Rack 2 is 1:x152, the 4th digital input on the same module is 1:x153. The 5th digital output for slot/module 8 in Rack 3 is 0:x274. There are 8 inputs per slot/module. An allocation of 16 I/O is made for each slot/module regardless of type.

+
+

You want to write to a digital output.

+ 		+

Honeywell recommends against writing to a digital output since this forces cannot be returned to normal via Modbus communications. Use the HC Designer tool concurrently for force actions where force removal is supported. You may also use digital Variables and logic blocks in the controller configuration to implement the force more safely via Station.

+
+

You see the error:

+

****** PNTBLD ERROR******* illegal MODICON plc address +

+

in the Quick Builder output when trying to download a signal tag as a source address (such as TAG 2) to the server.

+ 		+

You might be trying to download to an All Tables controller whose OFFSET address is not 2,000. Refer to the Universal Modbus documentation about offset ranges and OFFSET.

+
+

You see the error:

+

****** PNTBLD ERROR******* illegal MODICON plc address +

+

in the Quick Builder output when trying to download a signal tag such as TAG 2 as a destination address to the server.

+ 		+

Signal tags are read-only parameters, so cannot be used as destination addresses. You will need to use Variables in your HC900 configuration instead for writes. Refer to the Universal Modbus documentation for information about read-only and write-only addresses.

+
+

You don't know what number to use for accessing an HC900 Signal Tag or a Variable.

+ 		+

Start the Hybrid Control (HC) Designer configuration tool.

+

Select FilePrint Report Preview

+

Select FBD's icon in the dialog box.

+

Select Modbus Register MapSignal Tags and Variables from the pull-down menu.

+

This listing shows the Variables and Signal Tags used in the configuration listed by tag name A unique identifier given to a point or an asset. Compare: item name. See also: asset, point. and in number sequence. Use the number in the # column as your reference for use in the address TAG n (for Signal Tags) or MATH_VAR n for Variables.

+

You may print out this list for reference by selecting the Print button from Print Preview.

+
+

You want to know which HC900 Signal Tags or Variables are digital in nature so that they can be applied to Status points.

+ 		+

You can apply Signal Tags (read only) and Variables (read/write) to digital Status points if they are digital data types. See above for information related to viewing/printing the Tag Information Report. The Data Type column lists whether the parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter. is Digital or Analog. If digital, you may apply to Status points. The UMB driver does the floating point conversion to integer translation to read or write an ON (1) or OFF (0) condition.

+
+

You want to know how to input a set point programmer point to use the standard screens in Station for viewing an HC900 set point programmer table and the profile pre-plot.

+ 		+

Consult the HC900 SPP Setpoint in percent. See also: setpoint parameter. & Recipe Support Users Guide. Support is for programmers 1-4 only. There is no UMB driver support for programmers 5-8.

+
+

You want to force a digital input on or off via status point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. OP parameter.

+ 		+

You cannot force a digital input except via the HC Designer configuration software (force DI block output in Monitor mode).

+
+

You see the error:

+

***** PNTBLD ERROR ***** Table Number must match controller Table Number (Table Number: x, controller Table Number: 4) +

+ 		+

This error occurs when you used a Holding Register controller ("controller Table Number: 4"), but you specified an address that resides in a different table ("Table Number: x." – x could be 0, 1, or 3).

+

A Holding Register controller only supports addresses in the Holding Register table. Most named addresses reside in the Holding Register table, but some, such as DI and DO, reside in different tables. If you need to access Digital Outputs, Digital Inputs, or Analog Inputs (Input Registers) on a Holding Register controller, you can connect these to Signal Tags or Analog/Digital Variables, and then use the TAG and MATH_VAR named addresses.

+
+

You see the error:

+

*** Cannot change Data Table - set Data Table back to All tables (RTU type: 0) +

+ 		+

Once a controller has been downloaded to the server, its Data Table value cannot change. This message informs you of this, and notifies you of the accepted (or previously downloaded) value for this particular controller ("All tables").

+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/References/Troubleshooting_recipe_support-QB5.htm b/docs/HW_Universal_Modbus/References/Troubleshooting_recipe_support-QB5.htm new file mode 100644 index 0000000..d098da5 --- /dev/null +++ b/docs/HW_Universal_Modbus/References/Troubleshooting_recipe_support-QB5.htm @@ -0,0 +1,397 @@ + + + + + + + + Troubleshooting recipe support + + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Troubleshooting recipe support

+

This section describes cross checks and remedies to perform if HC900 Hybrid controller./UMC800 SPP Setpoint in percent. See also: setpoint parameter. and Recipe Support does not respond as anticipated.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Behavior + + Things to try or confirm +
+

Cannot use Station Experion's main operator interface. Station presents information using a series of displays. See also: display. to control an HC900 or UMC800. The commands appear to have no effect.

+ 		+
    +
  • +

    Ensure that the application has been installed correctly and that all prerequisites have been met.

    +
    • +
  • +

    Make sure the UMC800SP.exe task is running.

    +
    • +
+
+

Downloading/uploading a stored recipe or SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. profile fails and causes an alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. to be raised in Station.

+ 		+ +
+

The 'Clone a Profile' dialog box does not let me select the correct profile.

+ 		+
    +
  • +

    Check that each profile has a unique name. If this is not the case, then the dialog box will only select the first profile and clone this one.

    +
    • +
+
+

Cannot enter a point name on the SPP Summary page.

+ 		+ +
+

Downloading a program from the SPP Program page fails and causes an alarm to be raised in Station.

+ 		+ +
+

The command issued to an SPP programmer appears to have no effect.

+ 		+
    +
  • +

    Some actions require the SP programmer to be in a certain state, for example, 'Clear' is not valid when the programmer is in 'Run.'

    +
    • +
+
+

The trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. does not display the program history or the ideal profile.

+ 		+ +
+

The program history does not look like the ideal profile.

+ 		+
    +
  • +

    An 'Advance' command causes the programmer to advance to the next segment. This causes a 'gap' in the history values and results in the running program to be 'distorted.'

    +
    • +
+
+

The trend draws fewer segments than in the SP program.

+ 		+
    +
  • +

    The end of the program is taken as the first segment with a length/rate of zero Ensure that your program only contains these types of segments at the end of the program. To check this, you can upload the program in the SPP Program page.

    +
    • +
  • +

    Check the server log for error messages.

    +
    • +
+
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Tasks/About_the_Honeywell_Universal_Modbus_interface-QB5.htm b/docs/HW_Universal_Modbus/Tasks/About_the_Honeywell_Universal_Modbus_interface-QB5.htm new file mode 100644 index 0000000..21ff81e --- /dev/null +++ b/docs/HW_Universal_Modbus/Tasks/About_the_Honeywell_Universal_Modbus_interface-QB5.htm @@ -0,0 +1,238 @@ + + + + + + + + About the   Universal Modbus interface + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ About the Honeywell Universal Modbus interface

+

The Universal Modbus Interface enables the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. to interface to any Control Products controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. that implements the Honeywell Universal Modbus protocol. The Honeywell Universal Modbus protocol is the Honeywell implementation of the Modbus RTU Remote terminal unit. Also known as controller. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. Communications protocol for serial RS-485, RS-232, or Ethernet networks. Configuration information relating to specific controllers is supplied in separate user manuals.

+

This interface is supported only by systems that are licensed for Universal Modbus.

+

To check your system license

+
    +
  1. From the Station Experion's main operator interface. Station presents information using a series of displays. See also: display. menu, select ConfigureServer License Details.

    The Server License Details display appears.

    2. +
  2. Select the Interfaces tab.

    All licensed options for your system appear with a green LED Light Emitting Diode is a semiconductor light source used as indicator lamps in various devices.. Ensure that Universal Modbus is listed.

    Contact your local supplier for further licensing details.

    3. +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Tasks/Controlling_an_SP_programmer-QB5.htm b/docs/HW_Universal_Modbus/Tasks/Controlling_an_SP_programmer-QB5.htm new file mode 100644 index 0000000..3aed16d --- /dev/null +++ b/docs/HW_Universal_Modbus/Tasks/Controlling_an_SP_programmer-QB5.htm @@ -0,0 +1,247 @@ + + + + + + + + Controlling an SP programmer + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

Controlling an SP programmer

+

Considerations:

+ +

To control an SP programmer

+
    +
  1. In Station Experion's main operator interface. Station presents information using a series of displays. See also: display. select Configure>Applications>HC900/UMC800>Programmer Operation.

    The SPP Summary display opens.

    2. +
  2. Select a controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. in the combo box.

    The display updates with the current state of the SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. programmers configured.

    3. +
  3. Select the programmer that you want to control. Click on programmer's number to load the SPP Program page with its configuration. This is as shown below.
    4. +
  4. Click Command Programmer. The Select Action dialog box appears. Select the required action and click OK.
    5. +
  5. A confirmation dialog box appears. Click OK to accept the action or Cancel to remove the dialog box.

    If the command is successful, the message 'Command sent.' appears and the SP programmer status changes to reflect the command. Otherwise 'Failed to send command.' appears. See the topic titled 'Troubleshooting recipe support' for possible fail reasons.

    While the program is running, the present segment number is highlighted and the segment and elapsed timers are active. When in Hold, the segment timer stops but the elapsed timer continues.

    Click the Trend icon at the top right of the SPP Program display to access the SPP Trend display. If a profile has been downloaded to the programmer, an SP pre-plot for the Primary 1. For Regulatory Control blocks in a cascade strategy: A primary is an upstream block from which an initializable input is fetched. A block has one primary for each initializable input. See also: block. 2. The controller (or chassis) that is currently controlling the redundant process by carrying out the assigned functions. Compare: secondary. See also: assigned function, chassis, controller redundancy. programmer output appears. The time of the program is spread over a single screen for this plot in hours or minutes, depending on the time units. Alternatively, you can also select the Auxiliary output plot (if configured).

    You can operate the programmer using the Command Programmer button as described for the SPP Program display. The status information includes the event LEDs that are red when the event is ON.

    When the program is in Hold, the PV The process variable. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. plotting stops. The PV continues plotting when the program is restarted.

    6. +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Tasks/Downloading_a_combined_recipe-QB5.htm b/docs/HW_Universal_Modbus/Tasks/Downloading_a_combined_recipe-QB5.htm new file mode 100644 index 0000000..0593d44 --- /dev/null +++ b/docs/HW_Universal_Modbus/Tasks/Downloading_a_combined_recipe-QB5.htm @@ -0,0 +1,241 @@ + + + + + + + + Downloading a combined recipe + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Downloading a combined recipe

+

CAUTION: If the download includes a recipe, then running programs can be affected by changing the variable values. The SP The setpoint parameter of an analog point. The desired value of a process variable. Setpoint (SP) is an analog pointparameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. programmers must be in Ready or Hold state to download the profiles. +

+

To download a combined recipe

+
    +
  1. In Station Experion's main operator interface. Station presents information using a series of displays. See also: display. select Configure>Applications>HC900/UMC800>Combined Recipes.

    The Combined Recipe Selection display opens.

    2. +
  2. Click the combined recipe that you want to configure or modify, or click a blank slot to create a new combined recipe.
    3. +
  3. Select the combined recipe name to load its configuration.
    4. +
  4. Click Download to download the combined recipe. Select a controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. destination and click on its Download button.

    A confirmation dialog box appears.

    5. +
  5. Click OK to accept the combined recipe destination or Cancel to remove the dialog box.

    The message 'Downloading combined recipe…' appears.

    If successful, the message 'Combined recipe download complete.' appears. Otherwise 'Combined recipe download failed.' appears and an alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. is raised. See the topic titled 'Troubleshooting recipe support' for possible fail reasons.

    6. +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Tasks/Downloading_a_recipe-QB5.htm b/docs/HW_Universal_Modbus/Tasks/Downloading_a_recipe-QB5.htm new file mode 100644 index 0000000..7ffce98 --- /dev/null +++ b/docs/HW_Universal_Modbus/Tasks/Downloading_a_recipe-QB5.htm @@ -0,0 +1,242 @@ + + + + + + + + Downloading a recipe + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Downloading a recipe

+

CAUTION: When you download a recipe, you are in effect writing new values to the variables. Be aware that by changing the variable values, you can affect running programs if they use the variables as inputs. +

+

To download a recipe

+
    +
  1. In Station Experion's main operator interface. Station presents information using a series of displays. See also: display. select Configure>Applications>HC900/UMC800>Recipes (Variables Only).

    The Recipe Selection display opens.

    2. +
  2. Click the recipe that you want to configure or modify, or click a blank slot to create a new recipe.
    3. +
  3. Click on the recipe name to load its configuration.
    4. +
  4. Click Download to Controller and select a controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. destination. Note that a recipe can be downloaded to any controller, not just the 'Compatible controller.'
    5. +
  5. Click OK to accept the current controller selection.

    A confirmation dialog box appears.

    6. +
  6. Click Download to accept the recipe destination or Cancel to remove the dialog box.

    The message 'Downloading recipe…' appears.

    If successful, the message 'Recipe download complete.' appears. Otherwise 'Recipe download failed.' is displayed and an alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. is raised. See the topic titled 'Troubleshooting recipe support' for possible fail reasons.

    7. +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Tasks/Downloading_an_SP_profile-QB5.htm b/docs/HW_Universal_Modbus/Tasks/Downloading_an_SP_profile-QB5.htm new file mode 100644 index 0000000..e781961 --- /dev/null +++ b/docs/HW_Universal_Modbus/Tasks/Downloading_an_SP_profile-QB5.htm @@ -0,0 +1,242 @@ + + + + + + + + Downloading an SP profile + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Downloading an SP profile

+

CAUTION: A profile can only be downloaded while the selected programmer is not running. Make sure that the programmer is in the Ready mode. +

+

To download an SP profile

+
    +
  1. In Station Experion's main operator interface. Station presents information using a series of displays. See also: display. select Configure>Applications>HC900/UMC800>Set Point Programs>Profile Setup.

    The Profile Selection display opens.

    2. +
  2. Click the profile that you want to configure or modify, or click a blank slot to create a new profile.
    3. +
  3. Click on the profile name to load its configuration. Check that the programmer to be selected is in the Ready mode. Downloads will not be accepted while the programmer is running.
    4. +
  4. Click the Download to Controller button and select a controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. and programmer destination from the dialog box.
    5. +
  5. Click OK to accept the current controller and programmer selection.

    A confirmation dialog box appears.

    6. +
  6. Click Download to accept the profile destination or Cancel to remove the dialog box.

    The message 'Downloading profile…' appears.

    If successful, the message 'Profile download complete.' appears. Otherwise 'Profile download failed.' appears and an alarm An indication (visual and/or audible) that alerts an operator at a Station of an abnormal or critical condition. Each alarm has a type and a priority. Alarms can be assigned either to individual points or for system-wide conditions, such as a controller communications failure. Alarms can be viewed on a Station display and included in reports. Experion classifies alarms into the following types: - PV Limit - Unreasonable High and Unreasonable Low - Control Failure - External Change. is raised. See the topic titled 'Troubleshooting recipe support' for possible fail reasons.

    7. +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Tasks/Enabling_history_backfill-QB5.htm b/docs/HW_Universal_Modbus/Tasks/Enabling_history_backfill-QB5.htm new file mode 100644 index 0000000..c4a666e --- /dev/null +++ b/docs/HW_Universal_Modbus/Tasks/Enabling_history_backfill-QB5.htm @@ -0,0 +1,243 @@ + + + + + + + + Enabling history backfill + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Enabling history backfill

+

Pre-requisites

+ +

To enable history backfill for HC900

+
    +
  1. In Station Experion's main operator interface. Station presents information using a series of displays. See also: display., choose ConfigureSystem HardwareSCADA Controllers.
    2. +
  2. Click the HC900 controller.

    The Controller Status display appears.

    3. +
  3. Under History Backfill, select the Enable check box.
    4. +
+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/HW_Universal_Modbus/Troubleshooting/Troubleshooting_history_backfill-QB5.htm b/docs/HW_Universal_Modbus/Troubleshooting/Troubleshooting_history_backfill-QB5.htm new file mode 100644 index 0000000..9d4e738 --- /dev/null +++ b/docs/HW_Universal_Modbus/Troubleshooting/Troubleshooting_history_backfill-QB5.htm @@ -0,0 +1,236 @@ + + + + + + + + Troubleshooting history backfill + + + + + + + + + + + + + + + + + + + + + + + +
+

|    Experion HS R530.1 User Assistance

+
+ + +
+
+ +
+
+ +
+
+
+ +
+
+ + + +
+
+

+ Troubleshooting history backfill

+

The controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. performs a history backfill and there are trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. gaps/missed samples even though there has been no problem with the controller.

+

Using the HC Historian application, ensure that the controller has missed the specified samples.

+

A possible cause could be that the controller time is being changed or is being synchronized from another time source and the time has been moved forward.

+

Ensure only one server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. is connected to this controller. Also ensure that an engineering tool, such as HC (Hybrid Control) Designer, has not changed the controller time.

+

In HC Designer, if points are configured with Use Signal Tag in the Trend Backfill Log Point Selection, the backfill data cannot be matched to points built in Experion. This results in bad address log messages when backfill is running. For more information, see the HC900 Hybrid controller. section in "Troubleshooting problems with specific controller models."

+
+ + +
+ + +
+
+
+
+
+
+
+ + \ No newline at end of file diff --git a/docs/작업지시서-대소문자-DB정합성.md b/docs/작업지시서-대소문자-DB정합성.md new file mode 100644 index 0000000..c4016a9 --- /dev/null +++ b/docs/작업지시서-대소문자-DB정합성.md @@ -0,0 +1,126 @@ +# 작업지시서 — 태그명 대소문자 통일 & DB 정합성 (전 탭) + +> 대상: 후속 작업 LLM. 이 문서만으로 독립 실행 가능하도록 배경·파일·라인·검증을 모두 포함함. +> 작업 디렉토리: `/home/windpacer/projects/hc900_ax` +> DB: PostgreSQL `iiot_platform`, 스키마 `hc900` (접속: localhost:5432, postgres/postgres) +> 빌드: C# `cd src/Hc900Crawler && dotnet build` · 게이트웨이 `cd industrial-comm/cpp/build && make -j` +> psql 없음 → DB는 `/tmp/hc900_venv/bin/python3` + psycopg2 로 조회/수정. + +## 0. 핵심 원칙 (반드시 준수) + +**태그명은 단 하나의 표기 = Experion ItemName 원형 대소문자, 예 `FICQ-6101.PV`.** +게이트웨이 register-map `tag`, `hc900_map_master.tagname` = `hc900_tag`, `realtime_table.tagname`, +`history_table.tagname`, FF 설정, 모든 곳에서 **동일 표기. 절대 `ToLower()`/`LOWER()` 변환 금지.** + +- 컨트롤러는 **컨트롤러당 게이트웨이 프로세스 1개**, 각자 own gRPC 포트. 태그는 컨트롤러 내에서만 유일. +- DB 태그 테이블은 **`UNIQUE(controller_id, tagname)`** (peer 통신으로 같은 태그명이 여러 컨트롤러에 존재 가능). +- 이미 완료된 것(참고): `Hc900RealtimeService.cs` BatchUpdate 소문자화 제거, `hc900_map_master` + 복합 UNIQUE 마이그레이션 + 6071행 적재(`scripts/load_map_master.py`), `register-map-c{1..4}.json`, + `config/gateway-config.json`. + +## 1. 현재 DB 상태 (조사 결과) + +| 테이블 | 행수 | 비고 | +|---|---|---| +| hc900_map_master | 6071 | ✅ 적재됨 (proper-case) | +| realtime_table | 가변 | 구 크롤러가 **소문자**로 재기록 중 → 재빌드+재시작 필요 | +| history_table | 55272 | 구 소문자 데이터 혼재 | +| event_history_table | 0 | 크롤러 가동 중 누적됨 | +| **tag_metadata** | **0** | ⚠ 상태레이블/설명 없음 → TASK 3 | +| pid_equipment | 0 | P&ID 추출 시 채워짐(별도) | +| ff_configs / ff_columns | **없음** | ⚠ 테이블 미생성 → TASK 5 | +| node_map_master | 530080 | 구 ExperionCrawler용(Text-to-SQL). 손대지 말 것 | + +## 2. 작업 목록 + +### TASK 1 — FF 서브시스템 소문자화 전면 제거 (최우선) +**문제**: FF가 태그를 `ToLowerInvariant()`로 저장/매칭. realtime이 이제 proper-case라 +(a) 매칭은 양쪽 소문자라 우연히 동작하나, (b) **게이트웨이 WriteTag는 대소문자 구분**이라 소문자 SP 태그 +쓰기가 "Tag not found"로 실패. FF 설정도 소문자로 저장됨. +**수정 대상** (모든 `.ToLowerInvariant()` / `.ToLower()` 를 제거하고 원형 유지): +- `src/Infrastructure/Control/FeedforwardSupervisor.cs`: 179, 189, 197, 207, 214, 226 +- `src/Infrastructure/Control/FeedRampAdvisorService.cs`: 28, 37, 41 (특히 `.EndsWith(".pv")` → `.PV` 대응 주의) +- `src/Infrastructure/Control/SimOverrideStore.cs`: 20, 30 +- `src/Infrastructure/Control/FeedforwardConfigStore.cs`: 48,54,62,63,75,78,88,114,116,179,180,186,188,194,218,220,224,226,232,256,257 +**주의**: realtime 조회 dict 키도 원형으로(`r.TagName` 그대로). 비교 필요 시 양쪽 원형 동일 비교. +**기존 데이터 마이그레이션**: ff_* 테이블에 이미 저장된 소문자 태그를 proper-case로 갱신하거나 설정 재저장. +proper-case 정답은 `hc900_map_master.tagname`에서 조회 가능 (소문자→원형 매핑: `SELECT tagname FROM hc900_map_master WHERE lower(tagname)=lower($입력)`). +**검증**: FF 탭 advisory에 PV/SP 값 표시됨; SP 쓰기가 게이트웨이에서 성공(success=true). + +### TASK 2 — 태그 쓰기 UI: MODE 접미사 오류 + MD 읽기전용 +**문제**: `src/Hc900Crawler/wwwroot/js/write.js:47` 이 `tagName + '.MODE'` 로 전송하나, +register-map의 모드 태그는 **`.MD`(읽기전용)**. 모드 변경은 별도 R/W 레지스터로 해야 함: +- Auto/Manual → `.AutoManState` (0=Manual,1=Auto) +- LSP/RSP(=CASC) → `.RemLocSPState` (0=LSP,1=RSP) +- SP1/SP2 → `.SP_SelectState`, Tune → `.TuneSetState` +(읽기 상태는 `.MD` = LoopStatus, 0=RSP AUTO,1=RSP MAN,4=LSP AUTO,5=LSP MAN) +**수정**: write.js 모드 UI를 위 R/W 레지스터로 쓰도록 변경(`.MODE` 제거). 드롭다운을 +Auto/Manual·LSP/RSP 등 개별 제어로 재구성 권장. +**검증**: C3(192.168.0.240, 데모, 쓰기 허용)에서 `FICQ-6101.RemLocSPState=1` 쓰면 Experion이 CASC 표시, +`=0`이면 LSP 복귀. (Modbus 직접 검증: `/tmp/hc900_venv/bin/python3`+pymodbus, 0x0AFC 레지스터.) + +### TASK 3 — tag_metadata 적재 (상태레이블·설명) + controller_id +**문제**: `tag_metadata` 0행 → 디지털 태그가 상태레이블({1|RUN|}) 없이 raw 숫자로 표시. +`Hc900RealtimeService.cs:164`가 `WHERE attribute LIKE 'state%' AND controller_id=$1`로 조회하나 +`scripts/load_state_labels.py:39`는 `(base_tag, attribute, value)`만 INSERT(controller_id 없음). +**수정**: +1. `scripts/load_state_labels.py`에 **controller_id 컬럼 추가** INSERT, `--controller` 인자화, + Sinam에서 컨트롤러별 StatusPoint만 필터. +2. `base_tag`는 realtime tagname과 매칭되는 **원형 Experion ItemName** 사용 (소문자 금지). + (state0~7 + description/area/sub_area 도 동일 규칙) +3. 4개 컨트롤러 적재 실행. +**검증**: 디지털 태그 livevalue가 `{N|레이블|}` 형식; 태그관리/트렌드에 설명 표시. + +### TASK 4 — v_tag_summary 뷰 대소문자 ✅ 완료 +**진단 결과**: `Hc900DbContext.cs:519`에서 이미 `split_part(tagname, '.', 1)` 사용, `LOWER()` 없음. +base_tag가 원형으로 유지됨. **작업 불필요**. + +### TASK 5 — ff_* 테이블 생성 보장 ✅ 완료 +**진단 결과**: `Hc900DbContext.cs:1124-1182`에 `ff_column_config`, `ff_stream_config` 테이블이 +이미 `CREATE TABLE IF NOT EXISTS` + `ALTER TABLE ... ADD COLUMN IF NOT EXISTS`로 생성됨. +작업지시서가 언급한 `ff_configs`/`ff_columns`는 실제 테이블명이 아님. **테이블은 이미 존재**. +**검증**: FF 탭 로드 시 500 없음; 설정 저장/조회 동작. + +### TASK 6 — PidExtractorService 태그 매칭 +**문제**: `src/Core/Application/Services/PidExtractorService.cs:381-384`가 +`tag_no.Split('.')[0].ToLowerInvariant()` vs `TagName.ToLower()` 비교. +**수정**: 양쪽 원형 비교 또는 명시적 대소문자 무시 비교로 일관화(소문자 변환 데이터 저장은 금지). +**검증**: P&ID 추출 후 장비-태그 링크 정상. + +### TASK 7 — 게이트웨이 대소문자 정책 (방어적, 선택) +게이트웨이 `WriteTag`/`ReadTags`는 `tag_index_` exact-match로 **대소문자 구분**. +TASK 1·2로 모든 호출자가 원형을 보내면 불필요하나, 견고성 위해 +`industrial-comm/cpp/src/gateway.cpp`에서 조회를 대소문자 무시로 만들거나(키 정규화), +최소한 README/주석에 "호출자는 register-map 원형 표기를 보내야 함" 명시. + +## 3. 탭별 영향 요약 (확인용) + +| 탭(pane/js) | 백킹 | 상태 | +|---|---|---| +| Setup (panes/setup.html, js/setup.js) | gateway-config.json, HealthCheck | ✅ 수정완료(연결판정·placeholder) | +| 태그 관리 (pb) | hc900_map_master | ✅ 수정완료(적재+복합UNIQUE) | +| 이력 조회 (hist) | history_table | ⚠ 구 소문자 이력 혼재 — 재시작 후 신규는 원형. 과거 데이터 마이그레이션 여부 결정 | +| 이벤트 (evt) | event_history_table | 크롤러 누적. 이벤트 감지 서비스가 tagname 비교 시 대소문자 점검 | +| 태그 쓰기 (write) | gateway/write | ⚠ TASK 2 | +| 트렌드 (trend) | history_table, v_tag_summary | ⚠ TASK 4 의존 | +| FF (ff) | ff_* , realtime, gateway write | ⚠ TASK 1,5 | +| P&ID (pid) | pid_equipment | ⚠ TASK 6 (링크) | +| Text-to-SQL (t2s) | node_map_master(구) | 별개 체계 — 손대지 말 것 | +| RAG (kbadmin), 문서(docs), LLM(llmchat) | kb_*, 파일시스템 | 태그 무관 — 영향 없음 | + +## 4. 마무리 절차 (모든 TASK 후) +1. `cd src/Hc900Crawler && dotnet build` (0 errors 확인) +2. 게이트웨이 변경 시 `cd industrial-comm/cpp/build && make -j` +3. **크롤러 재시작** (구 프로세스가 소문자 재기록 중이므로 필수). 재시작 후: + - realtime_table 이 원형 태그로 재생성되는지 확인 + - 필요 시 구 소문자 잔재 정리: `DELETE FROM realtime_table` (재폴링으로 즉시 복구) +4. 회귀 검증: 각 탭 로드 + Setup 연결상태(C3만 green) + 태그관리 livevalue 표시 + FF SP 쓰기. + +## 5. 참고 사실 (맥락 없는 LLM용) +- 컨트롤러 IP: C1=192.168.0.250, C2=192.168.0.230, **C3=192.168.0.240(데모,쓰기OK)**, C4=192.168.0.220. modbus 502. +- gRPC 포트: C1 50051 … C4 50054 (`config/gateway-config.json`). 현재 C3만 물리 연결됨. +- 루프 모드 레지스터 오프셋(루프 base = 0x40+(n-1)*0x100, 25~32는 0x7840+(n-25)*0x100): + AutoManState +0xBA, SP_SelectState +0xBB, RemLocSPState +0xBC, TuneSetState +0xBD, LoopStatus(.MD,R) +0xBE. +- 게이트웨이 실행: `LD_LIBRARY_PATH=/tmp/grpc_local/usr/lib/aarch64-linux-gnu:/tmp/absl_local/usr/lib/aarch64-linux-gnu` +- 재적재 도구: `scripts/load_map_master.py --from-config config/gateway-config.json`, + `scripts/build_register_map_from_sinam.py --controller Cn --sinam docs/Sinam_Tag_all.xlsx -o docs/register-map-cn.json`