Unipi Technology Edge E413 Modbus register map
Modbus TCP unit; the manual documents only the system registers (user LEDs, storage status, connection status)
- Official
- 12 registers
- Modbus TCP
- Revision 3 · 2026-11-10
Official: Written from the manufacturer's documentation, but not tested on a device yet. Check the map against the manufacturer's documentation before you write to a live device. Tested it? Report a test.
Communication
- Protocol
- Modbus TCP
- Unit ID
- 0
- TCP port
- 502
- Byte / word order
- CDAB · bytes big-endian, words low first (word swap)
- Addresses
- 0-based
Connection values are defaults: the device may be configured differently.
Map
- Registers
- 9 holding registers, 3 coils
- Groups
- 3
- Revision
- 3 · 2026-11-10
- Added
- ()
- File
- maps/unipi/edge-e413.mbmap.json · 3 KB · history
- SHA-256
- c18e192c5c28dd4184fe96f57cbc7f99359a8c9472c7cd8f3c13f1360e4a9bb3
- Manufacturer
- www.unipi.technology
Sources and notes
- Edge E413 Modbus map · version 2.0 Holding registers and Coils sheets (Unit ID 0), Description sheet
Source: Edge E413 Modbus map v2.0, Unipi technology
- Registers are 0-based. Bit numbers: 0 = LSB, 15 = MSB. 32-bit values are assumed low word first (CDAB), as on the Unipi extensions; the manual does not state the word order.
- Registers marked Reserved in the manual are left out.
- Transport is not stated in the manual; Modbus TCP on port 502 is assumed.
- All registers in this map are on Unit ID 0; the manual lists no Unit ID 1 tables for this model.
| Area | Address | Name | Type | Access | Unit | Scale | Description |
|---|---|---|---|---|---|---|---|
| HR | 3998 | bool bit 0 | W | ||||
| HR | 3998 | bool bit 1 | W | ||||
| HR | 3998 | bool bit 2 | W | ||||
| HR | 4000 | uint16 | R | % | |||
| HR | 4001 | uint16 | R | % | |||
| HR | 4200 | uint16 | R | ||||
| HR | 4201 | uint16 | R | ||||
| HR | 4202 | uint16 | R | dBm | |||
| HR | 4203 | uint16 | R | ||||
| CO | 3000 | bool | W | ||||
| CO | 3001 | bool | W | ||||
| CO | 3002 | bool | W |
No registers match
Try part of the name, an address (decimal or 0x hex) or clear the filters.
Help improve this map
- I tested it on a deviceReport whether it worked, even if you did not write the map.
- Suggest a correctionEdit the file on GitHub; it opens a pull request.
- Report a problemA wrong address, type, scale or byte order.
- Read the formatWhat each key of the file means (SPEC.md).