- Home
- BACnet points lists
- MSA FieldServer
- QuickServer M-Bus profile - EMU 3PH Power 3-85
Electricity meter (M-Bus) via QuickServer gateway · BACnet points list
MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85 BACnet points list
Updated 11 November 2026Unofficial source
The QuickServer M-Bus gateway polls the meter as an M-Bus master and serves its data as 10 read-only Analog Inputs (BACnet IP or BACnet MS/TP) plus matching Modbus input registers. The object list is the gateway's fixed EMU 3PH Power 3-85 profile from the start-up guide.
This page lists 10 BACnet objects for the MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85 — 0 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from a copy of MSA FieldServer’s documentation hosted by Chipkin Automation (MSA FieldServer distributor), not by MSA FieldServer itself, so treat it as unofficial.
- Manufacturer
- MSA FieldServer
- Model
- QuickServer M-Bus profile - EMU 3PH Power 3-85
- Equipment
- Electricity meter (M-Bus) via QuickServer gateway
- Equipment type
- Thermostats, sensors & meters
- BACnet objects
- 10 (0 writable)
- Transport
- BACnet IP, BACnet MS/TP
- Firmware
- Not stated
- Also known as
- EMU 3-phase M-Bus meter, FS-QS-1X50, QuickServer M-Bus
- Source document
- QuickServer Start-up Guide FS-QS-1011/12X0/12X1/1X50/1X51 (Appendix B, M-Bus Data Profiles) · T18600 · rev. Document Revision 2.J (systems made after July 2020) (unofficial copy, hosted by Chipkin Automation (MSA FieldServer distributor))
Reference only, provided as-is: verify against MSA FieldServer’s current documentation and the live device before use. Not official MSA FieldServer information. Terms of use.
BMS integration notes: MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85
Set the meter's M-Bus primary address and readout as its maker describes, wire it to the QuickServer's M-Bus port (R2), pick this profile, then read the Analog Inputs.
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.
| Object | Name | Why | Access |
|---|---|---|---|
| AI 2 | Energy_WH_1 | Energy register 1 | Read |
| AI 5 | Voltage_1 | Voltage 1 | Read |
| AI 8 | Current_1 | Current 1 | Read |
| AI 1 | MBUS_Meter_$node_id_Alarms | Meter alarm value | Read |
Network setup
- The meter connects to the QuickServer's M-Bus R2 port (+/-; most M-Bus devices are not polarity sensitive); on some models a jumper sets the port as M-Bus master or slave.
- Default QuickServer IP address 192.168.2.101, subnet 255.255.255.0.
Watch out for
- Units are not given; check the meter's M-Bus data records for each value's unit and scale.
MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85 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.
| Description | States | |||||
|---|---|---|---|---|---|---|
| AImin | 1 | MBUS_Meter_$node_id_Alarms | Read | |||
| AImin | 2 | Energy_WH_1 | Read | |||
| AI | 3 | Energy_WH_2 | Read | |||
| AI | 4 | Energy_WH_3 | Read | |||
| AImin | 5 | Voltage_1 | Read | |||
| AI | 6 | Voltage_2 | Read | |||
| AI | 7 | Voltage_3 | Read | |||
| AImin | 8 | Current_1 | Read | |||
| AI | 9 | Current_2 | Read | |||
| AI | 10 | Current_3 | Read |
No points match these filters.
Object ID lookup: MSA FieldServer QuickServer EMU 3PH 3-85 point IDs by name
Integration notes
- The guide prints point name, BACnet object (all Analog Inputs) and Modbus register only; no units, scaling or descriptions.
- The guide does not say what the _1/_2/_3 suffixes mean; confirm them against the meter.
- All values are floats; on the Modbus side the first register holds the least significant word.
- Access is inferred: Analog Inputs are read-only.
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 QuickServer M-Bus profile - EMU 3PH Power 3-85 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 MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85
How many BACnet points does the MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85 have?
This list has 10 BACnet objects: 10 analog inputs. The exact set on a given unit depends on its firmware, installed options and configuration.
Which MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85 BACnet points are writable?
None of the listed objects are marked writable in the source documentation. The source has no read/write column, so this is inferred from object type.
Where is the official MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85 BACnet documentation?
MSA FieldServer does not publish it on its own website. This list comes from QuickServer Start-up Guide FS-QS-1011/12X0/12X1/1X50/1X51 (Appendix B, M-Bus Data Profiles) (T18600), revision Document Revision 2.J (systems made after July 2020), a copy hosted by Chipkin Automation (MSA FieldServer distributor) at https://cdn.chipkin.com/assets/uploads/2020/Oct/FS-QS-1XXX%20-%20QuickServer%20Gateway%20-%20Manual_08-20-50-57.pdf. Ask MSA FieldServer or its representative for the current revision.
What are the minimum BACnet points to integrate the MSA FieldServer QuickServer M-Bus profile - EMU 3PH Power 3-85?
Start with AI 2 Energy_WH_1 (Energy register 1); AI 5 Voltage_1 (Voltage 1); AI 8 Current_1 (Current 1); AI 1 MBUS_Meter_$node_id_Alarms (Meter alarm value).
How do I check these points on the real QuickServer M-Bus profile - EMU 3PH Power 3-85?
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 MSA FieldServer BACnet points lists
- Room temperature and humidity sensor (M-Bus) via QuickServer gateway
MSA FieldServer QuickServer M-Bus profile - Elvaco CMa20
Elvaco CMa20 M-Bus temperature and humidity sensors read by an MSA FieldServer QuickServer (FS-QS-1X50/1X51) with its built-in Elvaco CMa20 M-Bus data profile.
Also known as: CMa20, Elvaco CMa20 M-Bus, FS-QS-1X50, QuickServer M-Bus - Heat / energy meter (M-Bus) via QuickServer gateway
MSA FieldServer QuickServer M-Bus profile - Siemens FUE950 Energy
Siemens FUE950 Energy M-Bus meters read by an MSA FieldServer QuickServer (FS-QS-1X50/1X51) with its built-in Siemens FUE950 Energy M-Bus data profile.
Also known as: FUE950, FUE950 M-Bus, FS-QS-1X50, QuickServer M-Bus
Source: QuickServer Start-up Guide FS-QS-1011/12X0/12X1/1X50/1X51 (Appendix B, M-Bus Data Profiles) · T18600 · rev. Document Revision 2.J (systems made after July 2020). Object names, instances and units are reproduced as published; descriptions are our own.