Trinity Xpert Modbus register map
- Unofficial
- 50 registers
- Revision 2
Unofficial: Copied from an unofficial source and not tested. Read it as a draft and check a value on the real device before you rely on the rest. Check the map against the manufacturer's documentation before you write to a live device. Tested it? Report a test.
Communication
- Protocol
- Modbus TCP and RTUdefault
- Unit ID
- 1default
- TCP port
- 502default
- Serial
- 9600 8E1 · 9600 baud, 8 data bits, even parity, 1 stop bit defaults
- Byte / word order
- ABCD · bytes big-endian, words high first
- Addresses
- 0-based
Connection values are defaults: the device may be configured differently.
Map
- Registers
- 50 holding registers
- Revision
- 2
- Added
- ()
- File
- maps/trinity/xpert.mbmap.json · 6 KB · history
- SHA-256
- 09ac943d4a558cafc95291b81c1adcf0215c9921fd2e42b594c19a6f4dc6ecb9
- Manufacturer
- trinityenergy.co.in
Sources and notes
Source: Modbus Database (Jibril Sharafi, MIT licence), table trinity/xpert; https://www.aggsoft.com/serial-data-logger/tutorials/modbus-data-logging/trinity-xpert.htm. Not verified against the manufacturer's documentation
- Trinity Xpert.
- Converted automatically from the Modbus Database (MIT licence, Jibril Sharafi).
- Not verified against the manufacturer's documentation. The byte order is a guess: the source does not give one.
- Corrections are welcome (CONTRIBUTING.md). Change x_status once this table has been checked against the manual.
| Area | Address | Name | Type | Access | Unit | Scale | Description |
|---|---|---|---|---|---|---|---|
| HR | 199 | uint32 ABCD | R | ||||
| HR | 203 | uint32 ABCD | R | ||||
| HR | 213 | uint32 ABCD | R | ||||
| HR | 215 | uint32 ABCD | R | ||||
| HR | 219 | uint32 ABCD | R | ||||
| HR | 221 | uint32 ABCD | R | ||||
| HR | 229 | uint32 ABCD | R | ||||
| HR | 231 | uint32 ABCD | R | ||||
| HR | 239 | uint32 ABCD | R | ||||
| HR | 241 | uint32 ABCD | R | ||||
| HR | 243 | uint32 ABCD | R | ||||
| HR | 267 | uint32 ABCD | R | ||||
| HR | 269 | uint32 ABCD | R | ||||
| HR | 271 | uint32 ABCD | R | ||||
| HR | 273 | uint32 ABCD | R | ||||
| HR | 275 | uint32 ABCD | R | ||||
| HR | 277 | uint32 ABCD | R | ||||
| HR | 281 | uint32 ABCD | R | ||||
| HR | 283 | uint32 ABCD | R | ||||
| HR | 285 | uint32 ABCD | R | ||||
| HR | 287 | uint32 ABCD | R | ||||
| HR | 289 | uint32 ABCD | R | ||||
| HR | 291 | uint32 ABCD | R | ||||
| HR | 293 | uint32 ABCD | R | ||||
| HR | 295 | uint32 ABCD | R | ||||
| HR | 297 | uint32 ABCD | R | ||||
| HR | 299 | uint32 ABCD | R | ||||
| HR | 301 | uint32 ABCD | R | ||||
| HR | 303 | uint32 ABCD | R | ||||
| HR | 305 | uint32 ABCD | R | ||||
| HR | 307 | uint32 ABCD | R | ||||
| HR | 309 | uint32 ABCD | R | ||||
| HR | 311 | uint32 ABCD | R | ||||
| HR | 313 | uint32 ABCD | R | ||||
| HR | 315 | uint32 ABCD | R | ||||
| HR | 349 | uint32 ABCD | R | ||||
| HR | 351 | uint32 ABCD | R | ||||
| HR | 353 | uint32 ABCD | R | ||||
| HR | 355 | uint32 ABCD | R | ||||
| HR | 357 | uint32 ABCD | R | ||||
| HR | 359 | uint32 ABCD | R | ||||
| HR | 361 | uint32 ABCD | R | ||||
| HR | 363 | uint32 ABCD | R | ||||
| HR | 365 | uint32 ABCD | R | ||||
| HR | 367 | uint32 ABCD | R | ||||
| HR | 369 | uint32 ABCD | R | ||||
| HR | 371 | uint32 ABCD | R | ||||
| HR | 373 | uint32 ABCD | R | ||||
| HR | 375 | uint32 ABCD | R | ||||
| HR | 377 | uint32 ABCD | R |
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).