Easy BACnet
  1. Home
  2. BACnet points lists
  3. AERCO
  4. AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35)

Boiler / water heater cascade controller gateway · BACnet points list

AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) BACnet points list

Updated 6 November 2026

Short answer

AERCO's ProtoNode maps the AM Series managing unit to 95 objects. Objects 1-48 are the unit's own state, status, error and warning codes, setpoints, operation and mode settings, temperatures, firing rates, pump states, counters and lockout/blocking history; 49-76 report state, status, error and firing rate of up to 7 dependent units; 77-94 are the cascade controller's state, setpoints, outdoor reset settings, header temperature and firing rate; MV 95 is the Control Register that unlocks writes.

This page lists 95 BACnet objects for the AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) — 16 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from AERCO’s own free documentation, linked below.

Manufacturer
AERCO
Model
AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35)
Equipment
Boiler / water heater cascade controller gateway
Equipment type
Boilers & water heaters
BACnet objects
95 (16 writable)
Transport
BACnet IP, BACnet MS/TP
Firmware
Not stated
Also known as
AM Series, AM Manager, AM Mngr, AERCO AM, ProtoNode FPC-N34, FPC-N35
Source document
AERCO ProtoNode FPC-N34 & FPC-N35 User Manual, Appendix C-1 AM Mngr Modbus RTU Mappings to BACnet · OMM-0107_0B (GF-150) · rev. 2017-03-07
Download CSV 95 rows Download EDE B.I.G.-EU JSON Manufacturer PDF ↗ Compare with your scan Download Easy BACnet Mobile App Google Play

Reference only, provided as-is: verify against AERCO’s current documentation and the live device before use. Not official AERCO information. Terms of use.

BMS integration notes: AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35)

Integration in brief

For each write, first set MV 95 Control Register bit 0, then write Boiler Operation, the CH or DHW setpoint or the controller setpoints. Read State, Status, supply/return/header temperatures, firing rates, the error and warning codes and the state of each dependent unit. Do not use the setpoints for continuous temperature control.

Minimum points to map

The short list most integrators start with — enough to run the unit from a BMS. Map more as the job needs.

ObjectNameWhyAccess
MV 95Control RegisterWrite 1 (bit 0) before any write; bit 14 resetsWrite
AV 9Boiler OperationBoiler operation command (0..x per AERCO)Write
AV 81Controller CH SPCascade CH setpoint (preset, not dynamic)Write
AI 3StateManaging boiler state; see Appendix IRead
AI 4StatusManaging boiler status; see Appendix IRead
AI 89Header TempCascade header temperatureRead
AI 91Cascade Firing RateCascade firing rateRead
AI 49Dependent_1 StateDependent 1 state (repeat for 2-7)Read
AI 5Error CodeManaging boiler error codeRead
AI 79Controller Error CodeController (cascade) error codeRead

Enable & remote start

Writing is a two-step process: write 1 to MV 95 Control Register (bit 0 = write enable), then write the target AV (e.g. AV 9 Boiler Operation, AV 7/8 boiler CH/DHW setpoints, AV 81/82 controller setpoints). Bit 14 of the Control Register resets the controller after a lockout.

Heartbeat & communication loss

The Control Register bits reset when the AM unit sees no Modbus traffic for more than 4 seconds, so set bit 0 again right before each write.

Network setup

Watch out for

AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) BACnet objects

Type: AI, AO, AV, BI, BO, BV, MI/MO/MV (multi-state) · Access: Read read-only, Write writable, Command writable with a priority array.

Note: the source document has no read/write column, so access here is inferred from the object type (inputs read-only, values writable). Confirm on the live controller before writing.

95 of 95 shown
Type
Multi-state
Access
Show
AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) BACnet Points List
DescriptionStates
AV1Modbus UnitsModbus register 40101Write
AI2Device TypeModbus register 40102Read
AImin3StateModbus register 40103Read
AImin4StatusModbus register 40104Read
AImin5Error CodeModbus register 40105Read
AI6Warning CodeModbus register 40106Read
AV7Boiler CH SPModbus register 40107Write
AV8Boiler DHW SPModbus register 40108Write
AVmin9Boiler OperationModbus register 40109Write
AV10DHW TypeModbus register 40110Write
AV11CH ModeModbus register 40111Write
AV12DHW ModeModbus register 40112Write
AI13Supply TempModbus register 40113Read
AI14Return TempModbus register 40114Read
AI15DHW TempModbus register 40115Read
AI16Flue Gas TempModbus register 40116Read
AI17Heat Exchanger TempModbus register 40117Read
AI18Firing RateModbus register 40118Read
AI19Min Firing RateModbus register 40119Read
AI20Flame CurrentModbus register 40120Read
AI21Water PressureModbus register 40121Read
AI22Analog inModbus register 40122Read
AI23Analog outModbus register 40123Read
AI24InformationModbus register 40124Read
AI25CH pumpModbus register 40125Read
AI26DHW pumpModbus register 40126Read
AI27Ignition Count OKModbus register 40127Read
AI28Ignition Count FailedModbus register 40128Read
AI29Flame Count FailedModbus register 40129Read
AI30Burner High Hours / CH HoursModbus register 40130Read
AI31Burner Med Hours / DHW HoursModbus register 40131Read
AI32Burner Low HoursModbus register 40132Read
AI331st Lockout in HistoryModbus register 40133Read
AI34Time after 1st LockoutModbus register 40134Read
AI352nd LockoutModbus register 40135Read
AI36Time after 2nd LockoutModbus register 40136Read
AI373rd LockoutModbus register 40137Read
AI38Time after 3rd LockoutModbus register 40138Read
AI394th LockoutModbus register 40139Read
AI40Time after 4th LockoutModbus register 40140Read
AI411st Blocking Error in HistoryModbus register 40143Read
AI42Time after 1st Blocking ErrorModbus register 40144Read
AI432nd Blocking ErrorModbus register 40145Read
AI44Time after 2nd Blocking ErrorModbus register 40146Read
AI453rd Blocking ErrorModbus register 40147Read
AI46Time after 3rd Blocking ErrorModbus register 40148Read
AI474th Blocking ErrorModbus register 40149Read
AI48Time after 4th Blocking ErrorModbus register 40150Read
AImin49Dependent_1 StateModbus register 40151Read
AI50Dependent_1 StatusModbus register 40152Read
AI51Dependent_1 Error NumberModbus register 40153Read
AI52Dependent_1 Firing RateModbus register 40154Read
AI53Dependent_2 StateModbus register 40156Read
AI54Dependent_2 StatusModbus register 40157Read
AI55Dependent_2 Error NumberModbus register 40158Read
AI56Dependent_2 Firing RateModbus register 40159Read
AI57Dependent_3 StateModbus register 40161Read
AI58Dependent_3 SatusModbus register 40162Read
AI59Dependent_3 Error NumberModbus register 40163Read
AI60Dependent_3 Firing RateModbus register 40164Read
AI61Dependent_4 StateModbus register 40166Read
AI62Dependent_4 StatusModbus register 40167Read
AI63Dependent_4 Error NumberModbus register 40168Read
AI64Dependent_4 Firing RateModbus register 40169Read
AI65Dependent_5 StateModbus register 40171Read
AI66Dependent_5 StatusModbus register 40172Read
AI67Dependent_5 Error NumberModbus register 40173Read
AI68Dependent_5 Firing RateModbus register 40174Read
AI69Dependent_6 StateModbus register 40176Read
AI70Dependent_6 StatusModbus register 40177Read
AI71Dependent_6 Error NumberModbus register 40178Read
AI72Dependent_6 Firing RateModbus register 40179Read
AI73Dependent_7 StateModbus register 40181Read
AI74Dependent_7 StatusModbus register 40182Read
AI75Dependent_7 Error NumberModbus register 40183Read
AI76Dependent_7 Firing RateModbus register 40184Read
AI77Controller StateModbus register 40201Read
AI78Controller StatusModbus register 40202Read
AImin79Controller Error CodeModbus register 40203Read
AI80Controller Warning CodeModbus register 40204Read
AVmin81Controller CH SPModbus register 40205Write
AV82Controller DHW SPModbus register 40206Write
AV83High Outdoor Air TempModbus register 40207Write
AV84Minimum Outdoor Air SPModbus register 40208Write
AV85Low Outdoor Air TempModbus register 40209Write
AV86Maximum Outdoor Air SPModbus register 40210Write
AV87Outdoor Air Shutdown TempModbus register 40211Write
AV88Night SetbackModbus register 40212Write
AImin89Header TempModbus register 40213Read
AI90Outside TempModbus register 40214Read
AImin91Cascade Firing RateModbus register 40215Read
AI92Min Firing RateModbus register 40216Read
AI93System PumpModbus register 40217Read
AI94Amount of Dep DetectedModbus register 40218Read
MVmin95Control RegisterBit 0 write enable, bit 14 reset; register 40100Write
Object ID lookup: AERCO AM Series Managing boiler / water heater point IDs by name

Integration notes

Check it against the live device. A points list tells you what the controller can expose; the unit in front of you may differ by firmware or installed options. This list is provided as-is for reference only and may contain mistakes — confirming it before you write, map or commission anything is up to you (terms). Easy BACnet scans a network for BACnet IP devices from an Android phone, reads every object on the AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) and exports what it actually has to Excel — free. New to BACnet? Start with what a BACnet points list is and what the object types mean.

Questions about the AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35)

How many BACnet points does the AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) have?

This list has 95 BACnet objects: 79 analog inputs, 15 analog values, 1 multi-state value. The exact set on a given unit depends on its firmware, installed options and configuration.

Which AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) BACnet points are writable?

16 of the 95 objects accept a write. Points marked Command have a priority array: a write holds until it is released, so release it back to automatic when you are done. The source has no read/write column, so this is inferred from object type.

Where is the official AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) BACnet documentation?

The source is AERCO ProtoNode FPC-N34 & FPC-N35 User Manual, Appendix C-1 AM Mngr Modbus RTU Mappings to BACnet (OMM-0107_0B (GF-150)), revision 2017-03-07, published free by AERCO at https://www.watts.com/dfsmedia/0533dbba17714b1ab581ab07a4cbb521/58270-source/OMM-0107_0B_GF-150_ProtoNode%20FPC%20N34-N35%20User%20Manual_03-07-17.pdf.

What are the minimum BACnet points to integrate the AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35)?

Start with MV 95 Control Register (Write 1 (bit 0) before any write; bit 14 resets); AV 9 Boiler Operation (Boiler operation command (0..x per AERCO)); AV 81 Controller CH SP (Cascade CH setpoint (preset, not dynamic)); AI 3 State (Managing boiler state; see Appendix I); AI 4 Status (Managing boiler status; see Appendix I); AI 89 Header Temp (Cascade header temperature); AI 91 Cascade Firing Rate (Cascade firing rate); AI 49 Dependent_1 State (Dependent 1 state (repeat for 2-7)); AI 5 Error Code (Managing boiler error code); AI 79 Controller Error Code (Controller (cascade) error code).

How do I enable BMS control of the AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35)?

Writing is a two-step process: write 1 to MV 95 Control Register (bit 0 = write enable), then write the target AV (e.g. AV 9 Boiler Operation, AV 7/8 boiler CH/DHW setpoints, AV 81/82 controller setpoints). Bit 14 of the Control Register resets the controller after a lockout.

Does the AERCO AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35) need a BACnet heartbeat or have a communication timeout?

The Control Register bits reset when the AM unit sees no Modbus traffic for more than 4 seconds, so set bit 0 again right before each write.

How do I check these points on the real AM Series Managing boiler / water heater (ProtoNode FPC-N34/N35)?

Scan the network with a BACnet IP browser such as Easy BACnet, open the device and compare its object list with this table. Anything missing is usually an option that isn't installed or a point that is disabled in the controller's configuration.

More AERCO BACnet points lists

Source: AERCO ProtoNode FPC-N34 & FPC-N35 User Manual, Appendix C-1 AM Mngr Modbus RTU Mappings to BACnet · OMM-0107_0B (GF-150) · rev. 2017-03-07. Object names, instances and units are reproduced as published; descriptions are our own.