Name the native signal
“Amps” or “pressure” is not an input specification. Identify the transmitter, CT, shunt, sensor, direct source or data interface and its real range.
The right custom digital panel meter is not the model with the most features. It is the least-complex exact configuration whose input, scale, performance, supply, outputs, panel fit, operator interface and release evidence match the application. Define the measurement first; customize only what improves the finished product.
SENTOP product-family illustration. The image shows format variety; it does not prove that every pictured model shares the same inputs, outputs, accuracy, approvals, customization scope or availability.
Write the requirement in this order: measured quantity and native signal; range, scaling and performance; supply, isolation, outputs and data; panel, environment and operator interface; then exact configuration, sample validation and change control. A logo or unit label comes after electrical fit.
“Amps” or “pressure” is not an input specification. Identify the transmitter, CT, shunt, sensor, direct source or data interface and its real range.
Input endpoints, display endpoints, unit text, resolution, accuracy, filtering, update behavior and readability are different requirements.
Input, supply, reference, isolation, relay, analog retransmission and communications each need a source, receiver, rating and test.
Release the exact part number, option codes, settings, artwork, drawings, firmware, sample result, test plan and approved-alternate rule.
Choose the lightest scope that meets the verified requirement. A new meter platform is rarely the fastest answer when a supported product can be configured and controlled.
Published settings such as range, scale, unit, color, alarms or filtering change inside a supported platform.
Control: exact manual, settings export, firmware and functional acceptance result.A published input, supply, output, display or certification option is selected as an orderable suffix.
Control: complete manufacturer part number, option code, current data and included accessories.Branding, bezel, overlay, display layout, labels, range, I/O mix, housing or workflow is changed for the OEM product.
Control: approved drawings/artwork, sample, test plan, revision and change-notification agreement.The electronics, mechanics, sensor interface, protocol, compliance path or other core architecture changes.
Control: requirements, design and qualification plan, manufacturing test, lifecycle and service strategy.Logo, bezel, unit legend, display color and screen layout can make an OEM product easier to use. They do not change what the input circuit accepts or make the measurement more accurate. Precision Digital’s PD6060 material, for example, describes a custom unit tag as a display aid that does not change the process value or meter operation.
Keep the custom UI, engineering scaling and electrical interface as separate controlled items. That makes artwork approval useful without letting a correct-looking label mask the wrong CT ratio, transmitter scale or decimal convention.

The order matters. Each step closes a different family of assumptions before the next layer is customized.
Name the quantity, source, location, normal/abnormal range, interface and decision use.
Deliverable: measurement and signal-interface statement.Separate input range, display mapping, accuracy, resolution, response, units and readability.
Deliverable: performance schedule and display map.Define supply, reference, isolation, outputs, communications and every receiving device.
Deliverable: electrical and I/O interface schedule.Freeze cutout, depth, environment, terminals, service access, UI, language and branding.
Deliverable: mechanical, environmental and UI specification.Approve the sample, part number, settings, artwork, tests, documents and change path.
Deliverable: reproducible production-release package.A useful one-sentence brief names the physical quantity, approved source, system location, normal and credible abnormal range, native electrical output and the decision the reading supports.
Example: “Display a 4–20 mA pressure-transmitter output as 0–250 psi at the pump-skid door for local operating awareness.” That is a scaling and loop-integration problem. It is not interchangeable with “Display motor current from a specified conventional 1 A or 5 A current-output CT secondary for an ordinary control alarm,” even if both screens eventually show a number and a unit.

Do not write only voltage, current or temperature. Specify the electrical form, range, reference and sensor conditions that arrive at the meter.
| Native source | Freeze before meter selection | Do not assume |
|---|---|---|
| 4–20 mA transmitter | Output/fault range, loop supply budget, every series device, scale endpoints, units and backlight condition. | That any analog meter is loop powered, isolated, HART transparent or acceptable within the available loop voltage. |
| Direct voltage/current | AC/DC nature, range, frequency/waveform where relevant, source impedance/reference, fault exposure, protection and measurement category where assigned by the manufacturer. | That a volts/amps label permits connection to every circuit or exposure category. |
| Shunt mV system | Full-scale millivolts, rated current/dissipation, sense leads, high- or low-side placement, common-mode/working-voltage limits, isolation, polarity and input impedance. | That an ampere label or low-level mV input makes a meter suitable for a high-side shunt. |
| CT or other current sensor | Separate a conventional 1 A/5 A current-output CT, 333 mV voltage-output sensor, shunt signal and Rogowski coil. Record ratio/output, burden or input impedance, frequency, phase/polarity, lead limits and scale. | That these interfaces are interchangeable. A Rogowski coil needs a documented dedicated meter input or a matched integrator whose specified output the meter accepts. |
| RTD, TC or bridge sensor | Sensor type/standard, lead arrangement, range, accuracy condition, cold-junction or bridge needs and fault detection. | That a universal-input headline covers every sensor and wiring arrangement. |
| Pulse/frequency/data | Signal level, maximum rate, pulse shape, K-factor/time base, protocol/map, timing and rate/total logic. | That a numerical display can convert any pulse or network value without an explicit supported interface. |
CT boundary. For conventional current-output CT systems, rated VA must cover meter burden and lead losses. For 333 mV or Rogowski-based systems, use the sensor or integrator’s specified input, load and cable limits instead of applying the 1 A/5 A burden model by analogy. Never open-circuit a conventional current-output CT secondary while primary current is present; exact equipment instructions and approved shorting/work methods control.
For a linear source, define both input endpoints and both engineering-display endpoints. Then specify accuracy, resolution, response and readability independently.
Planning example: define 4.000 mA = 0.0 psi and 20.000 mA = 250.0 psi; 12.000 mA maps to 125.0 psi. Also define behavior below and above the nominal span. This does not prove that a particular meter supports the input, accuracy or configuration method.
For every connection, name the source, receiver, signal, normal/abnormal condition, reference or isolation expectation and acceptance test.

A local display, ordinary alarm signal, retransmitted process value and network data path solve different problems. Start with the receiving device and required behavior, then select the exact output hardware and communications variant.
Do not infer isolation, relay contacts, Modbus TCP, register content or protocol performance from an RS485 label or a product-family image. Preserve the interface drawing, data map and interoperability result with the released configuration.
State direct, differential, isolated, transformer/sensor based or loop-powered input plus the grounding/reference context.
Evidence: source data, exact meter input data and interface drawing.Define voltage, AC/DC, frequency, tolerance, power-up/recovery behavior and whether the supply may share a reference.
Evidence: selected supply variant, budget and functional test.Identify input-to-supply, input-to-output, output-to-data or sensor-to-system separation only where required and documented.
Evidence: exact isolation specification plus system grounding/EMC review.Identify the exact hardware, form, rating, logic, delay, reset and fail behavior for the receiving circuit.
Boundary: a standard meter output is not a safety relay or protective function.Define active/passive behavior, signal range, compliance/load, scale, isolation, failure behavior and receiving device independently of the display.
Evidence: source-to-receiver loop drawing and scale test.Define RTU/TCP variant, physical interface, register map, byte/word order, address, function codes, update behavior and configuration ownership.
Evidence: interface-control document and interoperability test.
An exact electrical match can still fail the product if the meter does not fit the approved door, cannot be wired or serviced, becomes unreadable in the expected light, or uses ambiguous units and alert colors.
Freeze the cutout and tolerance, bezel dimensions, rear depth, retention method, panel thickness, terminals, cable bend, door clearance, exposed-face environment, temperature, viewing angle, character size/color, screen hierarchy, language, unit symbols and service access.
Use the panel-meter cutout-size guide for mechanical planning and the safe installation workflow for implementation boundaries.
A buyer, assembler, test technician and service team should be able to reproduce the approved behavior without tribal knowledge.
Manufacturer part number, every option/suffix, supply/input/output configuration, included accessories and approved substitutes.
Scale, alarms, tags, display behavior, I/O, addresses, map, firmware/software, source/export file and permissions.
Cutout, bezel/overlay, logo/color approval, terminal access, labels, revision mark and packaging where applicable.
Input/output scales, supply, reference/isolation, sensor ratios, data interfaces and controlled electrical drawings.
Normal range, endpoints, legibility, alarms/outputs, communications, power recovery, mechanical fit and service access.
Revision, PCN expectations, obsolescence, spares, approved alternatives, inspection focus and retained records.
These are planning examples, not customer cases, product recommendations or installation instructions.
The OEM defines the transmitter output, 0–250 psi map, decimal convention, loop/power architecture, viewing distance, alarm-color behavior, cutout/depth and front environment.
Likely scope: supported process meter plus approved logo/bezel, preloaded scale, unit text, configuration and sample.The machine builder freezes a conventional current-output CT, 333 mV voltage-output sensor, shunt, dedicated Rogowski input/matched integrator or supported direct input; then records ratio/output, limits, alarm role, supply/isolation, scale and panel fit.
Likely scope: sensor-compatible standard platform with controlled ratio, alerts, motor label and source-to-meter validation.Related machines use RTD, thermocouple and 0–10 V sources while the OEM wants a stable cutout, common UI and controlled model-specific configurations.
Likely scope: one configurable family only if its published input/options matrix covers every variant and the release prevents field drift.A useful request lets the supplier propose the fastest supported platform and clearly return what is standard, configurable, optional, customized or out of scope.
| Observed symptom or risk | Likely specification gap | Evidence to review |
|---|---|---|
| Correct-looking face, wrong value | Scale, unit, decimal, CT/shunt/transmitter ratio or nonlinear mapping was not independently controlled. | Native source, input/display endpoints, ratio/K-factor, settings export and endpoint test. |
| Fits cutout, cannot wire/service | Depth, terminal orientation, cable bend, clamp, panel thickness or door clearance was omitted. | Mechanical drawing, clearance review and representative panel sample. |
| 4–20 mA loop loses range | Meter voltage drop, supply, transmitter, barrier or other series load was missing from the loop budget. | Complete loop drawing and exact input/power/backlight data. |
| Current sensor is incompatible | Direct, conventional current-output CT, shunt mV, 333 mV or dedicated Rogowski/integrator interface was treated as a cosmetic variant. | Sensor/integrator data, matching meter input, ratio, burden/load/impedance and approved system design. |
| PLC receives the wrong interface | Relay, analog retransmission and digital communications were combined under “output.” | Receiver requirement, exact output rating/range, map and functional test. |
| Replacement behaves differently | Option code, firmware, settings, artwork, screen project or output card was not retained. | Exact part, BOM, configuration/source file, revision and alternate-review process. |
| Custom UI confuses operators | Units, language, status colors, alarm meaning, screen priority and viewing conditions were not validated. | Approved UI specification, operator review and representative usability test. |
A component data sheet, approval or family feature is one evidence layer. It does not automatically certify the sensor chain, customized variant, completed panel or end application.
Input, supply, outputs, isolation, accuracy conditions, mechanics, environment and option code for the quoted item.
Artwork, housing, display, range, I/O, firmware or workflow change plus supplier assessment and new revision.
Sensor compatibility, ratio, burden, reference, protection, total error, wiring design and validation.
Installation, environment, fault/SCCR context, markings, panel standard, inspection and authority/customer review.
Ordinary indication/control, quality, billing, settlement, protection or safety use and its required acceptance route.
Choose the measurand, native input, range, supply, display, outputs and environment before customization.
Open the selection guide →Review engineering-unit scaling, loop voltage budget and commissioning evidence for a process indicator.
Review the process-meter guide →Map power, voltage, sensor and communications paths after the correct configuration is selected.
Open the wiring guide →Compare dated public examples, capability drivers and total installed cost without treating price as a specification.
Compare price tiers →These answers define the specification boundary. Exact model data, project engineering and current supplier evidence still control.
“Custom” can mean a standard meter with controlled settings, an orderable input or output variant, a customized bezel, label, screen or I/O platform, or a ground-up design. State which electrical, mechanical, UI, documentation and commercial elements change; the word alone is not an orderable specification.
Start with the signal. Define the measured quantity, approved source, normal and abnormal range, native interface and performance need. Then design the display, branding, label and bezel to make that verified measurement clear to the operator.
Not by itself. A unit label or custom tag is normally a readability feature. Define input and display endpoints, ratio, K-factor or nonlinear mapping separately, confirm the exact meter supports it, and preserve the scale in the settings record and acceptance test.
No. Digit count describes display capacity, and displayed resolution is the smallest increment the display can show. Neither is an accuracy specification. Require the complete accuracy expression, applicable input range, temperature, calibration interval and filter/update settings, then include the sensor, transmitter, ratio or linearization, leads and meter in the acceptance tolerance.
Some universal platforms support a documented set of process and temperature inputs, but no generic meter accepts every signal. Confirm each type, range, lead arrangement, reference or isolation rule, supply and exact model limitation.
No. Distinguish electromechanical relay, SSR drive and open-collector outputs by exact form, rating and fail state; define analog retransmission by active/passive behavior, range, compliance/load, scaling and isolation; and define Modbus by RTU/TCP variant, physical interface, map, byte/word order, address, function codes and interoperability test. None is a protective or safety output unless the exact product and completed system are approved for that role.
Choose a customized platform when a supported meter can meet the measurement and integration needs with controlled changes such as branding, bezel, screen layout, range, outputs or preloaded settings. Consider ground-up development only when the required input, mechanics, function, compliance path or lifecycle cannot be met by a supported platform.
Release the exact part number and options, settings/source export, firmware/software, artwork revision, input/output scale, interface drawings, test record, password/permission policy, spares and approved replacement path. A service team should be able to reproduce the delivered behavior without guessing.
No. A custom display or multifunction meter is not automatically suitable for billing, revenue settlement, protective control or a safety function. State the purpose explicitly and meet the exact functional, accuracy, certification, installation and jurisdictional requirements for the complete application.
Manufacturer examples illustrate requirement categories; they do not transfer every feature, approval or rating to a different model, suffix or custom variant.
Send the measured quantity, source/sensor and range, input/display scale, supply/reference, accuracy basis, outputs/receivers, cutout, environment, UI/branding needs, target market, quantity, destination and timing. SENTOP can review the product match and identify missing configuration, accessory, sample or commercial fields; final system engineering and approval remain with the responsible project parties.
Product and project enquiry
Share the model, ratings, quantity and destination you already know. SENTOP will review the remaining selection details with you.
SENTOP Team
Typically replies within minutes
Do you want to learn more about our products or services?
Contact Us
🟢 Online | Privacy policy
Contact Us