Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.
Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
| point | address (0-based) | type | scale | unit |
|---|---|---|---|---|
| status | 0 | U16 | 1 | |
| msgn | 1 | U16 | 1 | |
| gstat | 2 | U16 | 1 | |
| timer | 3 | U16 | 1 | |
| flame | 4 | U16 | 1 | |
| logstat | 5 | U16 | 1 | |
| inputs | 6 | U16 | 1 | |
| outputs | 7 | U16 | 1 | |
| sysmins | 8 | U32BE | 1 | minutes |
| bnrmins | 10 | U32BE | 1 | minutes |
| cycles | 12 | U32BE | 1 | cycles |
| lockout_count | 14 | U16 | 1 | |
| lockout_history | 15 | U16 | 1 | |
| devtyp | 21 | U16 | 1 | |
| amptyp | 22 | U16 | 1 | |
| progtyp | 23 | U16 | 1 | |
| flame_signal_average_ptfi | 24 | U16 | 1 | |
| flame_signal_average_auto | 25 | U16 | 1 |
⚠ WARNING: Selection of this control for a particular application should be made by a competent professional, licensed by a state or other government. Inappropriate application of this product could result in an unsafe condition hazardous to life and property. — Starkest reads only; we never write a control register.
| termination | The shield at the source end of the cable of the multi-drop connection can then be terminated to ground. |
| shield/ground | Proper twisted shielded pair cable must be utilized. In a multi-drop system, the shields should be tied together within a cabinet and not to any ground point. |
| wiring notes | When interfacing Fireye controls to a communication system, be it an E500, PLC or other microprocessor based device, ferrite cores should also be utilized. |
| protocol notes | It is suggested that repeated polling interval not be less than 200 mSec per request. Requesting data such as burner minutes, system minutes and burner cycles be kept at a minimum due to the amount of processing time required to gather that data. |
| model register | 21 |
| identification notes | Message 21 (DEVTYP) returns programmer device type (5=EP, 6=EPD, 7=MicroM). Message 23 (PROGTYP) returns programmer type. |
| power | 120 VAC (min. 102, max. 132) 50/60 Hz for MEC1XX, MEC3XX; 230 VAC (min. 196, max. 253) 50/60 Hz for MEC2XX, MEC4XX. Power Consumption: 12 VA (Operating) |
| environment | Operating Temperature: -40°F (-40°C) to 140°F (60°C) |
| certifications | cULus Listed, FM Approved |
| doc revision | MC-5000, MAY 9, 2008 |
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
Device not here? Upload its manual and get a checked map back. It's free.
Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.
Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.