What a Point Map Is
A point map is a configuration table that defines how data points are translated between source and destination protocols in a gateway. Each row maps a source address to a destination address, specifying the data type, scaling, and read/write direction.
Point maps are the core of every QuickServer and FieldServer configuration.
Typical Point Map Columns
| Column | Description |
|---|---|
| Source address | Register, object, or data table reference on the source side |
| Destination address | Register, object, or data table reference on the destination side |
| Data type | UINT16, FLOAT32, binary, enum, etc. |
| Scaling | Multiplier, offset, or unit conversion |
| R/W direction | Read-only, write-only, or bidirectional |
| Description | Human-readable point name |
Best Practices
- Get the register map first — mapping without vendor documentation is guesswork
- Classify R/W before mapping — especially critical for EtherNet/IP (DATA_TABLE_READ vs WRITE)
- Verify data types — mismatched types between source and gateway produce corrupt values
- Validate with known values — after mapping, verify at least one point against a physically measurable value
[!TIP] Start with a small subset of critical points (5–10), validate end-to-end, then expand. This catches configuration issues early.