Internal register
A storage register held by the printer, with no other function. The PLC and software on the printer can both read and write it, which makes it a simple mailbox between the two.
| Property | Value |
|---|---|
| Data types | UINT16, INT16, UINT32, INT32, STRING, BLOCK |
| Access | R, or RW if the mapping is writable |
There are two kinds:
- Named internal registers can also be read and written through the Aurora API Modbus methods, for example by an extension. Their values are saved, and kept when the printer restarts.
- Anonymous internal registers, with no name, are only reachable over Modbus. Their values are not saved, and are 0 after a restart.
A read-only named register is written only by software on the printer, so the PLC can use it to read results. A writable register can be written by both.
A BLOCK item holds raw 16-bit words, for data that the PLC and the software
agree on, for example a packed structure.
Software on the printer can wait for the PLC to write a named register with waitModbusValue. Every write from the PLC or the API counts, even one that writes the same value.
Example
In the example mapping list, the PLC writes
requests to plc_request at 100, and an extension answers in aurora_reply
at 101, which is read-only for the PLC:
| Step | Who | Does |
|---|---|---|
| 1 | PLC | Writes 7 to register 100. |
| 2 | Extension | Sees the write with waitModbusValue {"name": "plc_request", ...}, and handles request 7. |
| 3 | Extension | Calls setModbusValue {"name": "aurora_reply", "value": 7}. |
| 4 | PLC | Reads 7 from register 101, and knows the request is done. |
See Exchanging data with an extension for the full example.