Technology / Engineering guide
Wind Controller Protocols & Register Maps
A communication connector identifies only part of an integration interface. Useful controller data require a defined transport, protocol and version-specific map of meanings. Request and review those layers separately before treating a value as an engineering measurement or a supported control function.
Make every received value traceable to its definition.
Use an interface record that connects device version, address notation, data format, units and access rights.
01 / Interface layers
Separate the connector from the application language.
A physical interface, such as an RS-485 interface in a generic example, does not establish which application protocol a device uses.
A physical interface, such as an RS-485 interface in a generic example, does not establish which application protocol a device uses. A protocol name also leaves its transport and implemented variant to be identified. These descriptions belong in separate fields.
The Modbus Organization distinguishes its application protocol from serial-line implementation details. This is an example of layered documentation, not a claim that a MARSTON controller implements Modbus, CAN, an Ethernet interface or any other specific communication option.
02 / Version identity
Match the map to the actual device.
Record the controller identity, relevant hardware and firmware versions, and the protocol-map revision.
Record the controller identity, relevant hardware and firmware versions, and the protocol-map revision. A map for another model or firmware may describe a different quantity, address or access condition even where the connector looks identical.
Retain the document’s status and scope: supported standard map, optional integration document or project-specific definition. The document-control guide provides a way to track those revisions and keep a superseded map from remaining in use.
03 / Address semantics
Retain the notation behind the number.
A register description needs its object or register class, address convention and quantity of data elements.
A register description needs its object or register class, address convention and quantity of data elements. A human-readable label and a transmitted address may use different notation. Store the stated convention rather than assuming that every document counts addresses in the same way.
Also identify how a device or endpoint is named within the selected interface. An address label does not establish network discovery, physical access or permission to communicate. This guide provides no scan commands, guessed addresses or device-writing instructions.
04 / Value decoding
Keep format, scale and units together.
Retain signed or unsigned type, length, byte and word ordering where applicable, unit, scale, offset and any invalid-value codes.
Retain signed or unsigned type, length, byte and word ordering where applicable, unit, scale, offset and any invalid-value codes. A numerical value becomes useful only when those definitions are matched to the correct quantity.
In a hypothetical map, a raw value of 2500 with scale 0.01 and offset zero represents 25 of the stated unit. This is an illustrative calculation, not a MARSTON register. An omitted unit or invalid-value definition can make a correctly received number misleading.
05 / Data context
Distinguish reception from measurement meaning.
Identify whether a value represents a current observation, an average, a cumulative quantity or a status.
Identify whether a value represents a current observation, an average, a cumulative quantity or a status. Retain the update basis, timestamp meaning and handling of unavailable data from the actual documentation.
The monitoring-data guide addresses the project data dictionary. A protocol map supplies the encoding and interface semantics needed to obtain those defined quantities. Receiving a field does not establish sensor accuracy, complete event history or a particular remote-monitoring service.
06 / Access boundary
Separate readable data from authorised actions.
Record access rights and supported functions from the actual map.
Record access rights and supported functions from the actual map. A readable status is different from a writable parameter, and an available write function is different from project authorisation to use it. A communication link does not bypass control or protection responsibilities.
Keep remote control requirements explicit in the equipment enquiry and retain the applicable integration evidence. No MARSTON protocol, remote command capability or public register map is confirmed here. Provide the intended data needs using the controller selection guide.
Continue the review with Wind Project Engineering Documents: Revisions & Review Status.
Continue the review with Wind Power Export Limits & Zero-Export Requirements.
Continue the review with Grid-Following & Grid-Forming Wind Converters.
Review analogue and digital sensor interfaces, timestamps, time zones and intervals and energy counters and reset records alongside the protocol and register documentation.
General background: Modbus Organization: application, serial-line and TCP/IP specification documents · Modbus Organization serial-line guide: protocol-layer and physical-interface distinction. These references explain industry concepts; they are separate from the applicable MARSTON product and project documents.
Prepare the information for this review.
Use the checklist to organise the project information. Mark unavailable items and retain document references.
| Review item | Information to provide | Purpose |
|---|---|---|
| Layer definition | Physical interface, transport, application protocol and variant | Avoid guessing from a connector. |
| Map identity | Device, firmware, map revision and document status | Use applicable definitions. |
| Address convention | Object class, notation basis and data length | Make references unambiguous. |
| Data semantics | Type, order, scale, offset, unit and invalid codes | Interpret values correctly. |
| Access and time | Rights, update basis, timestamps and supported scope | Separate data receipt from authority. |
Engineering questions.
Does RS-485 mean a controller supports Modbus?
No. A physical interface does not establish the application protocol.
Does this guide confirm MARSTON Modbus or CAN support?
No. Any proposed communication interface needs actual device documentation.
Why does the firmware version matter?
The applicable map, meanings and supported functions may depend on the device version.
Can a raw numerical value be treated as a measurement?
Only after its type, scale, unit, validity and time basis are understood.
Does a register map authorise remote control?
No. Supported access and project permission are separate from the existence of a data map.
What should a register-map request include?
Device identity, required quantities, intended integration interface and the relevant version information.
Technical enquiry
Bring your project information to the discussion.
A communication connector identifies only part of an integration interface. Share the available information and the equipment scope you want reviewed in a technical quotation.