Search Docs - Articles

What BTL listing is, how a PICS declares a device's claims, and how BTL's scenario-based testing differs from bench testing.

Reference for the NM-BBMDC-B BIBB: a device executing BDT reads/writes and FDT reads as a BACnet BBMD, and what the CAS BACnet Stack supports.

Reference for the NM-FDR-A BIBB: a device registering into a BACnet BBMD's Foreign Device Table, and what the CAS BACnet Stack supports.

Reference for the NM-RC-B BIBB: a router answering the network-layer peer messages, and what the CAS BACnet Stack supports.

Reference for the DM-DCC-B BIBB: a device executing DeviceCommunicationControl, password gating, and what the CAS BACnet Stack supports.

Reference for the DM-LM-B BIBB: a device executing AddListElement and RemoveListElement against list-typed properties, and what Chipkin supports.

Reference for the DM-RD-B BIBB: a device executing ReinitializeDevice across its restart and backup/restore states, and what Chipkin supports.

Reference for the DM-TS-B BIBB: a device accepting TimeSynchronization, the BIBB people forget on the restart-recovery path, and what Chipkin supports.

Reference for the SCHED-E-B BIBB: a device running a Schedule that writes to remote objects over the network, and what the CAS BACnet Stack supports.

Reference for the SCHED-I-B BIBB: a device running a Schedule that writes its own locally-hosted objects, and what the CAS BACnet Stack supports.

Reference for the AE-ACK-A BIBB: a workstation initiating AcknowledgeAlarm on behalf of an operator, and how it pairs with AE-ACK-B.

Reference for the AE-ACK-B BIBB: executing AcknowledgeAlarm and updating Acked_Transitions, the bookkeeping that decides if a re-fired alarm surfaces again.

The BACnet NetworkPort object (Clause 12.56) explained: per-interface property groups, the staged-changes model with ACTIVATE_CHANGES, the wildcard port, and what the CAS BACnet Stack supports.

Reference for the AE-N-A BIBB: the client side of BACnet event notification, receiving ConfirmedEventNotification and UnconfirmedEventNotification.

Reference for the AE-N-E-B BIBB: a device originating event notifications from an Event Enrollment object watching a property on another device.

Reference for the AE-N-I-B BIBB: a device originating event notifications from intrinsic reporting on its own objects, and what the CAS BACnet Stack supports.

BACnet device profiles explained: Annex L's families, the B-BC / B-AAC / B-ASC controller ladder, how profiles stack, how to pick one for your product, and what the CAS BACnet Stack provides.

The BACnet ReinitializeDevice service explained: cold start vs warm start, the backup and restore state machine, restart notifications, Last_Restart_Reason, and what the CAS BACnet Stack supports.

BACnet scheduling explained: the Schedule object's weekly and exception schedules, the Calendar object's date lists and WeekNDay entries, the midnight rule, and what the CAS BACnet Stack supports.

BACnet trend logging explained: the TrendLog and TrendLogMultiple objects, buffer and record-count semantics, reading history with ReadRange, and what the CAS BACnet Stack supports.

BACnet SC vs BACnet/IP on a real project: the questions that decide it, when BACnet/IP is still right, what BACnet SC costs you to run, and what reverses later.

The CAS BACnet Stack ships BACnet Secure Connect now: hub function, node participation, direct connect, certificate management, and the B-SCHUB profile. What 6.x adds.

BACnet Secure Connect explained: the TLS-over-WebSocket datalink, hub-and-spoke topology, the three BACnet SC BIBBs, certificates, and what the CAS BACnet Stack supports today.

What a BACnet Interoperability Building Block (BIBB) is, how BIBBs compose into device profiles, and the BACnet Secure Connect BIBB reference pages.

Protocol overview for BACnet covering history, object model, transport variants, discovery workflow, common integration targets, and diagnostics.

Index of every BACnet object type from ASHRAE 135-2024 Clause 12: analog, binary, multi-state, scheduling, trending, access control, lighting, elevators

The BACnet Access Credential object (Clause 12.35) models a credential's factors, validity, and assigned rights, with its full property tables.

The BACnet Access Door object (Clause 12.26) models a physical access-control door: its commandable door value, priority array, and full property tables.

The BACnet Access Point object (Clause 12.31) authenticates and authorizes a credential at a door or gate, with its ACCESS_EVENT reporting and properties.

The BACnet Access Rights object (Clause 12.34) holds the positive and negative rules a credential is granted, with its full property tables.

The BACnet Access User object (Clause 12.33) represents a person, group, or asset in access control, with its credential links and property tables.

The BACnet Access Zone object (Clause 12.32) is a secured area with occupancy counting and passback control, with its full property tables.

The BACnet Accumulator object (Clause 12.61) is a counting register that totals input pulses for utility metering

The BACnet Alert Enrollment object (Clause 12.52) originates alerts as an event source without affecting the monitored object

The BACnet Audit Log object (Clause 12.64) records auditable operations into a buffer read with ReadRange: required and optional properties with datatypes.

The BACnet Audit Reporter object (Clause 12.63) originates audit notifications for a device's auditable actions

The BACnet Averaging object (Clause 12.5) tracks the minimum, maximum, and average of a monitored property over a sampling window

The BACnet Binary Lighting Output object (Clause 12.55) is a commandable on/off light with a blink-warn egress model and full property tables.

The BACnet BitString Value object (Clause 12.40) exposes a named set of individually addressable bits with per-bit labels, read-only or commandable.

The BACnet Channel object (Clause 12.53) forwards one written value to a group of properties via the WriteGroup service, with its property tables.

The BACnet CharacterString Value object (Clause 12.37) exposes a named text-string value: labels, status text, and messages, read-only or commandable.

The BACnet Color Temperature object (Clause 12.66) controls white-light color temperature in Kelvin with fading commands

The BACnet Color object (Clause 12.65) controls a lighting color as CIE xy coordinates with fading commands

The BACnet Command object (Clause 12.10) runs a multi-write action list when its Present_Value is written to drive a named state, with property tables.

The BACnet Credential Data Input object (Clause 12.36) is a card, PIN, or biometric reader that captures authentication factors, with property tables.

The BACnet Date Pattern Value object (Clause 12.48) holds a date with wildcard fields that match many recurring dates, read-only or commandable.

The BACnet Date Value object (Clause 12.45) exposes a named calendar-date value like a start or expiry date, read-only or commandable.

The BACnet DateTime Pattern Value object (Clause 12.46) holds date and time fields with wildcards that match many recurring moments

The BACnet DateTime Value object (Clause 12.38) exposes a named combined date-and-time value like a timestamp, read-only or commandable.

The BACnet Device object (Clause 12.11) is the one object every BACnet device has: its identity, capabilities, and network parameters

The BACnet Elevator Group object (Clause 12.58) is a supervised group of lifts and escalators with their landing calls, with property tables.

The BACnet Escalator object (Clause 12.60) models an escalator's direction, mode, and faults, with its CHANGE_OF_STATE alarm and full property tables.

The BACnet Event Enrollment object (Clause 12.12) attaches an event or fault algorithm to any referenced property in another object.

The BACnet Global Group object (Clause 12.50) collects properties from objects across multiple devices into one readable set

The BACnet Group object (Clause 12.14) returns several objects' properties in one read: required and optional properties with datatypes.

The BACnet Integer Value object (Clause 12.43) is a signed-integer software point: counters, offsets, and calculated integers, read-only or commandable.

The BACnet Large Analog Value object (Clause 12.39) is a double-precision floating-point software point for values beyond REAL range

The BACnet Life Safety Point object (Clause 12.15) models a fire or life-safety device by mode and state, with its CHANGE_OF_LIFE_SAFETY alarm.

The BACnet Life Safety Zone object (Clause 12.16) groups life-safety points by mode and state, with its CHANGE_OF_LIFE_SAFETY alarm and properties.

The BACnet Lift object (Clause 12.59) models an elevator car's position, doors, mode, and faults, with its CHANGE_OF_STATE alarm and full property tables.

The BACnet Lighting Output object (Clause 12.54) is a commandable dimmable light with fade, ramp, and blink-warn control, plus property tables.

The BACnet Load Control object (Clause 12.28) manages sheddable load for demand response: required and optional properties with datatypes.

The BACnet Network Port object (Clause 12.56) models a device's network interface: its IP, IPv6, BBMD, and MS/TP settings

The BACnet Notification Forwarder object (Clause 12.51) re-distributes event notifications from other devices to its own recipients

The BACnet OctetString Value object (Clause 12.41) exposes a named raw byte-string value for binary data and opaque blobs, read-only or commandable.

The BACnet Positive Integer Value object (Clause 12.44) is an unsigned-integer software point: counts, indexes, and totals, read-only or commandable.

The BACnet Pulse Converter object (Clause 12.23) scales accumulated pulses into engineering units as an analog value

The BACnet Staging object (Clause 12.62) maps an analog value onto discrete stages that drive binary outputs in sequence

The BACnet Structured View object (Clause 12.29) organizes other objects into a navigable hierarchy and holds no data of its own

The BACnet Time Pattern Value object (Clause 12.47) holds a time with wildcard fields that match many recurring times, read-only or commandable.

The BACnet Time Value object (Clause 12.42) exposes a named time-of-day value like a start or setback time, read-only or commandable.

The BACnet Timer object (Clause 12.57) is a countdown timer that changes state on expiration and can drive other objects

B-AACC is the BACnet Advanced Access Control Controller profile (Annex L): what it is, where it's used, and the services it must initiate and execute.

B-AACWS is the BACnet Advanced Access Control Workstation profile (Annex L): what it is, where it's used, and the services it requires.

B-ACC is the BACnet Access Control Controller profile (Annex L): what it is, where it's used, and the services it requires.

B-ACCR is the BACnet Access Control Credential Reader profile (Annex L): a credential reader, what it is, where it's used

B-ACDC is the BACnet Access Control Door Controller profile (Annex L): a door controller, what it is, where it's used, and the services it must support.

B-ACSD is the BACnet Access Control Security Display profile (Annex L): what it is, where it's used, and the services it requires.

B-ACWS is the BACnet Access Control Workstation profile (Annex L): what it is, where it's used, and the services it requires.

B-AEC is the BACnet Advanced Elevator Controller profile (Annex L): what it is, where it's used, and the services it must initiate and execute.

B-AEWS is the BACnet Advanced Elevator Workstation profile (Annex L): what it is, where it's used, and the services it requires.

B-ALCS is the BACnet Advanced Lighting Control Station profile (Annex L): what it is, where it's used, and the services it requires.

B-ALSC is the BACnet Advanced Life Safety Controller profile (Annex L): what it is, where it's used, and the services it must initiate and execute.

B-ALSWS is the BACnet Advanced Life Safety Workstation profile (Annex L): what it is, where it's used, and the services it requires.

B-ALWS is the BACnet Advanced Lighting Workstation profile (Annex L): what it is, where it's used, and the services it requires.

B-AS is the BACnet Authorization Server profile (Annex L): the device that issues access tokens for BACnet authorization, what it is

B-AWS is the BACnet Advanced Operator Workstation profile (Annex L): what it is, where it's used, and the services it requires.

B-DAP is the BACnet Device Address Proxy profile (Annex L): a device that answers discovery on behalf of proxied devices, what it is

B-EC is the BACnet Elevator Controller profile (Annex L): what it is, where it's used, and the services an elevator controller must initiate and execute.

B-ED is the BACnet Elevator Display profile (Annex L): what it is, where it's used, and the services the display must initiate and execute.

B-EM is the BACnet Elevator Monitor profile (Annex L): a read-only elevator monitoring device, what it is, and the services it must initiate and execute.

B-EWS is the BACnet Elevator Workstation profile (Annex L): what it is, where it's used, and the services the operator interface must initiate and execute.

B-GENERAL is the BACnet General device profile (Annex L): the catch-all profile for devices that do not fit a named family

B-GW is the BACnet Gateway profile (Annex L): what a BACnet gateway is, where it's used

B-LCS is the BACnet Lighting Control Station profile (Annex L): what it is, where it's used, and the services it requires.

B-LD is the BACnet Lighting Device profile (Annex L): a lighting output device, what it is, where it's used, and the services it must support.

B-LOD is the BACnet Lighting Operator Display profile (Annex L): what it is, where it's used, and the services the display must initiate and execute.

B-LS is the BACnet Lighting Supervisor profile (Annex L): what it is, where it's used, and the WriteGroup, scheduling, and data services it must support.

B-LSAP is the BACnet Life Safety Annunciator Panel profile (Annex L): what it is, where it's used, and the services the panel must initiate and execute.

B-LSC is the BACnet Life Safety Controller profile (Annex L): what it is, where it's used, and the services it requires.

B-LSWS is the BACnet Life Safety Workstation profile (Annex L): what it is, where it's used, and the services it requires.

B-OWS is the BACnet Operator Workstation profile (Annex L): what it is, where it's used, and the services it requires.

B-RTR is the BACnet Router profile (Annex L): what a BACnet router is, where it's used, and the data-sharing and network-layer services it must support.

B-XAWS is the BACnet Cross-Domain Advanced Workstation profile (Annex L): the union of the advanced HVAC, access, lighting

AuditLogQuery gives efficient filtered access to BACnet Audit Log records (Clause 13.19): how it works, its error codes, and which profiles use it.

AuthRequest lets a client obtain an access token for protected operations on a device (Clause 17.6): how it works and its error codes.

ConfirmedCOVNotificationMultiple pushes many property changes in one acknowledged notification (Clause 13.17): how it works and its error codes.

ConfirmedPrivateTransfer invokes a vendor-defined service on a remote device with acknowledgment (Clause 16.2): how it works and its error model.

I-Am-Router-To-Network announces the networks a router can reach (Clause 6.4.2): how the announcement works and which profiles require it.

Initialize-Routing-Table reads or updates a router's routing table (Clause 6.4.7): how the request and its ack work, and which profiles require it.

Network-Number-Is announces the local network number to a segment (Clause 6.4.20): how it works and which profiles require it.

Reject-Message-To-Network tells a sender its routed message failed (Clause 6.4.4): the rejection reasons and which profiles require it.

Router-Available-To-Network re-enables traffic to networks a router had curtailed (Clause 6.4.6): how it works, and which profiles require it.

Router-Busy-To-Network tells senders to pause traffic to networks while a router is congested (Clause 6.4.5): how it works and which profiles need it.

SubscribeCOVPropertyMultiple subscribes to many properties across many objects in one request (Clause 13.16): how it works and its error codes.

UnconfirmedCOVNotificationMultiple pushes many property changes without acknowledgment (Clause 13.18): how it works and why you see no response.

UnconfirmedPrivateTransfer invokes a vendor-defined service on remote devices, no acknowledgment (Clause 16.3): how it works and why there's no response.

Who-Is-Router-To-Network asks which router reaches a given BACnet network (Clause 6.4.1): how the query works and which profiles require it.

WriteGroup pushes lighting and control values to many Channel objects at once (Clause 15.11): how the group write works and which profiles need it.

BACnet BBMD overview covering multi-subnet discovery, broadcast forwarding, BDT design, and common BACnet/IP routing mistakes.

Reference for the NM-SCCM-A BIBB: provisioning and rotating BACnet Secure Connect device certificates over standard BACnet services

Reference for the NM-SCDC-B BIBB: the optional node-to-node BACnet Secure Connect path that bypasses the hub, when to use it

Reference for the NM-SCH-B BIBB: the BACnet Secure Connect hub function, the SC BVLL message set, hub redundancy, and what the CAS BACnet Stack supports.

The BACnet Analog Input object (Clause 12.2) represents a measured value like a temperature sensor: required and optional properties with datatypes.

The BACnet Analog Output object (Clause 12.3) is a commandable analog point: how the priority array works

The BACnet Analog Value object (Clause 12.4) is an analog point with no physical I/O: setpoints and calculated values

The BACnet Binary Input object (Clause 12.6) represents a two-state input like a contact or status

The BACnet Binary Output object (Clause 12.7) is a commandable two-state output: its priority array, minimum on/off times

The BACnet Binary Value object (Clause 12.8) is a two-state software point: mode flags and enables, read-only or commandable

The BACnet Calendar object (Clause 12.9) holds dates, date ranges, and recurring days used by Schedules: properties with datatypes.

The BACnet Event Log object (Clause 12.27) records event notifications into a buffer read with ReadRange: properties with datatypes.

The BACnet File object (Clause 12.13) describes a byte- or record-accessed data file used by AtomicReadFile and AtomicWriteFile.

The BACnet Loop object (Clause 12.17) exposes a PID feedback control loop as a standardized object: required and optional properties with datatypes.

The BACnet Multi-state Input object (Clause 12.18) represents an input with several named states

The BACnet Multi-state Output object (Clause 12.19) is a commandable multi-state point: its priority array, Number_Of_States model

The BACnet Multi-state Value object (Clause 12.20) is a multi-state software point: modes and selectors, read-only or commandable

The BACnet Notification Class object (Clause 12.21) holds recipient lists, priorities, and ack requirements for event notifications.

The BACnet Schedule object (Clause 12.24) writes values to other objects on a weekly and exception schedule: properties with datatypes.

The BACnet Trend Log Multiple object (Clause 12.30) logs several properties in lockstep into one buffer read with ReadRange: properties with datatypes.

The BACnet Trend Log object (Clause 12.25) logs one property over time into a buffer read with ReadRange: required and optional properties with datatypes.

Index of the standardized BACnet device profiles from Annex L: controllers, operator interfaces, life safety, access control, lighting, elevators

B-AAC is the BACnet Advanced Application Controller profile (Annex L): what it is, where it's used, and the services it must initiate and execute.

B-ASC is the BACnet Application Specific Controller profile (Annex L): what it is, where it's used, and the services it must execute.

B-BBMD is the BACnet Broadcast Management Device profile (Annex L): what it is, where it's used, and the services a BACnet BBMD device must support.

B-BC is the BACnet Building Controller profile (Annex L): what it is, where it's used, and every service a B-BC device must initiate and execute.

B-OD is the BACnet Operator Display profile (Annex L): what it is, where it's used, and the services a B-OD operator interface must initiate and execute.

B-SA is the BACnet Smart Actuator profile (Annex L): what it is, where it's used, and the small set of services it must execute.

B-SCHUB is the BACnet Secure Connect Hub profile (Annex L): what it is, where it's used, and the services a BACnet SC hub device must support.

B-SS is the BACnet Smart Sensor profile (Annex L): the minimal read-only device profile, what it is, where it's used

BACnet Secure Connect reference covering the WebSocket and TLS transport, hub-and-spoke topology versus BBMD broadcast, node and hub roles

Index of the BACnet application-layer services from ASHRAE 135-2024: object access, alarm and event, file access, and remote device management.

AcknowledgeAlarm records that an operator saw an alarm (Clause 13.5): how it works, the error codes it returns, and which device profiles require it.

AddListElement adds entries to a BACnet list-valued property (Clause 15.1): how it works, the error codes it returns, and which profiles require it.

AtomicReadFile reads the contents of a BACnet File object (Clause 14.1): stream and record access, backup use, the error codes it returns

AtomicWriteFile writes to a BACnet File object (Clause 14.2): stream and record access, restore and firmware use, the error codes it returns

ConfirmedCOVNotification pushes a subscribed value change and expects an acknowledgment (Clause 13.6)

ConfirmedEventNotification delivers an alarm or event and expects a receipt (Clause 13.8): how it works, the error model

ConfirmedTextMessage sends a text message to one BACnet device with acknowledgment (Clause 16.5)

CreateObject makes a new object instance in a BACnet device (Clause 15.3): how it works, the error codes it returns, and which profiles require it.

DeleteObject removes an object instance from a BACnet device (Clause 15.4): how it works, the error codes it returns, and which profiles require it.

DeviceCommunicationControl silences a BACnet device for diagnostics (Clause 16.1): how it works, its password and duration, the error codes

GetAlarmSummary returns a device's active alarms (Clause 13.10): how it works, why it is deprecated, its error model, and which profiles require it.

GetEnrollmentSummary lists a device's event-initiating objects with filters (Clause 13.11): how it works, why it is deprecated, its error model

GetEventInformation returns a device's active event states with paging (Clause 13.12): how it works, the error codes it returns

I-Am is BACnet's device-announcement service (Clause 16.10): how a device advertises its identity and address, when it fires

I-Have is BACnet's object-announcement service (Clause 16.9): how a device advertises that it holds a named object, and which profiles require it.

LifeSafetyOperation carries an operator's silence or reset command to fire and life-safety devices (Clause 13.13)

ReadPropertyMultiple reads many BACnet properties in one request (Clause 15.7): how it works, the per-property errors it returns

ReadProperty is BACnet's core read service (Clause 15.5): how a read works, the error codes it returns, and which device profiles require it.

ReadRange reads a range of items from a BACnet list or log (Clause 15.8): how paging works, the position/sequence/time forms, its error codes

ReinitializeDevice cold/warm starts a BACnet device (Clause 16.4): the restart choices, backup and restore, error codes, and which profiles require it.

RemoveListElement removes entries from a BACnet list-valued property (Clause 15.2): how it works, the error codes it returns

SubscribeCOVProperty subscribes a client to change-of-value on a specific property (Clause 13.15)

SubscribeCOV signs a client up for change-of-value notifications on an object (Clause 13.14): how it works, the error codes it returns

TimeSynchronization broadcasts local time to BACnet devices (Clause 16.7): how it works, how it differs from the UTC variant

UnconfirmedCOVNotification pushes a value change with no acknowledgment (Clause 13.7): how it works, why there is no error response

UnconfirmedEventNotification announces an alarm or event with no receipt (Clause 13.9): how it works, why there is no error response

UnconfirmedTextMessage sends a text message to one or more BACnet devices without acknowledgment (Clause 16.6)

UTCTimeSynchronization broadcasts UTC to BACnet devices (Clause 16.8): how it works, why UTC over local time, and which profiles require it.

Who-Am-I lets a BACnet device ask to be assigned an identity (Clause 16.11): how zero-touch commissioning works, its failure modes

Who-Has is BACnet's object-discovery service (Clause 16.9): how it finds which device holds a named object, and which profiles require it.

Who-Is is BACnet's device-discovery service (Clause 16.10): how the broadcast works, the I-Am response, and which device profiles require it.

WritePropertyMultiple writes many BACnet properties in one request (Clause 15.10): how it works, why it is not atomic, its error codes

WriteProperty is BACnet's core write service (Clause 15.9): how a write works, priority for commandable objects, the error codes it returns

You-Are assigns a BACnet device its instance number and MAC address over the network (Clause 16.11)

Understand how QuickServer counts licensed points, what happens when the point count is exceeded, where the error appears on screen and in the diagnostic log, and how to recover.

Step-by-step checklist to verify RS-485 wiring, serial settings, and device connectivity before deploying a Modbus RTU configuration. Prevents the most common commissioning failures.

Field procedures for obtaining the 48-bit Neuron ID of a LonWorks device, covering device labels, service-pin presses, NodeUtil discovery, LonMaker and IzoT database lookup, and protocol-analyzer capture.

Reference guide to LonWorks XIF (device interface) files covering the LonMark v4.400 file format, line-by-line interpretation, generation tools, format versions, and the .xif, .xfb, and .xfo file family.

Reference page for LonWorks FT-10 free-topology twisted-pair networks covering signaling rate, segment limits, topology rules, transceiver families, termination, and common physical-layer faults.

Canonical guide to LonWorks (ISO/IEC 14908) covering LonTalk, Neuron-based devices, network variables, SNVTs, XIF files, FT-10 wiring, addressing, and gateway integration with BACnet and Modbus.

Reference page for LonWorks Standard Network Variable Types (SNVTs) covering naming, fixed-point encoding, common types, engineering-unit constraints, enumeration types, and configuration-property families.

Reference page for LonWorks XIF (external interface file) format covering header fields, network variable definitions, configuration properties, format versions, and how to extract a XIF for gateway mapping.

Canonical guide to Programmable Controller Communication Commands (PCCC) covering Allen-Bradley typed file addressing, command codes, DF1 and EtherNet/IP encapsulation, and brownfield integration scoping.

What reserved bit patterns mean in Modbus registers — sentinel values like 0x8000, 0xFFFF, and IEEE 754 NaN, signed/unsigned mismatches, word-order errors, and the FC05 coil write requirement.

Recover a QuickServer that shows a Forbidden error after being factory reset from Chipkin AE firmware back to the original MSA firmware.

Starting in 2025, QuickServer firmware moved to an encrypted .PKG format. This article explains the impact on legacy devices, transitional upgrade paths, and what to expect for post-2025 hardware.

Troubleshoot common EtherNet/IP integration failures including EDS issues, assembly mismatches, DATA_TABLE_READ / WRITE mistakes, and Allen-Bradley variant confusion.

Step-by-step instructions for installing a firmware update on a QuickServer gateway, including firmware format guidance for legacy and current devices.

Troubleshoot the getaddrinfo EAI_AGAIN error on QuickServer when DNS, default gateway, or internet reachability prevents the gateway from resolving a hostname.

Step-by-step instructions for capturing a full diagnostic log from a QuickServer gateway and sharing it with Chipkin support.

Capture an MQTT broker's topics and representative live payloads into a JSONL file that Chipkin can use to scope a QuickServer BACnet or Modbus configuration.

Reference page for DNP3 Class 0, 1, 2, and 3 behavior and how event classes shape telemetry priority and polling design.

Reference page for DNP3 integrity polling, event polling, unsolicited responses, and how event-driven telemetry behaves in practice.

Protocol overview for DNP3 covering master and outstation roles, protocol levels, addressing, transport choices, and utility telemetry diagnostics.

Reference page for DNP3 master and outstation roles, protocol level expectations, and why subset support shapes interoperability.

Reference page for serial DNP3 covering RS-232 and RS-485 transport assumptions, addressing, and telemetry commissioning dependencies.

Reference page for DNP3 over TCP covering port usage, connection roles, and Ethernet telemetry design considerations.

Protocol overview for EtherNet/IP covering CIP fundamentals, messaging variants, assembly mapping, and Allen-Bradley-centric integration risks.

Protocol overview for KNX covering group addresses, datapoint types, ETS project dependencies, media options, and supervisory integration patterns.

Reference page for KNX IP covering routed access, tunneling workflows, and supervisory integration considerations.

Reference page for KNX RF covering wireless retrofit use cases, device constraints, and integration planning considerations.

Reference page for KNX twisted-pair transport covering bus topology, power, addressing, and commissioning dependencies.

Protocol overview for M-Bus covering wired and wireless metering workflows, addressing, data extraction, and gateway integration patterns.

Modbus coil overview covering read/write bit points, common function codes, and how coils differ from other Modbus data families.

Modbus discrete input overview covering read-only bit points, status-oriented use cases, and how they differ from coils.

Modbus function code overview covering the common public read and write operations, register-type mapping, and exception behavior.

Modbus holding register overview covering 16-bit read/write values, multi-register data, and the function codes most commonly used in field integrations.

Protocol overview for Modbus covering history, register model, transport variants, addressing pitfalls, point-list intake, and diagnostics.

Modbus input register overview covering read-only 16-bit values, measurement-oriented use cases, and their relationship to holding registers.

Modbus register map overview covering vendor documentation, data types, scaling, addressing conventions, and why the map is part of the protocol workflow.

Modbus RTU overview covering RS-485 transport, serial parameters, framing, and the field conditions that cause RTU failures.

Modbus TCP overview covering MBAP header behavior, Unit ID usage, Ethernet transport, and common IP-side integration assumptions.

Modbus slave ID and unit ID overview covering RTU addressing, TCP unit handling, gateway routing, and broadcast address behavior.

Modbus word-order overview covering 16-bit word arrangement in 32-bit values and why word-order mistakes often look like bad data.

Protocol overview for SNMP covering manager and agent polling, OIDs, MIB intake requirements, and infrastructure telemetry handoff.

Reference page for the SNMP manager-agent model covering polling, request flow, and how managers interact with agents.

Reference page for SNMP MIBs and OIDs covering object identity, hierarchy, tables, and why point extraction depends on real OID inventories.

Reference page for SNMP security and notifications covering SNMPv2c, SNMPv3, traps, informs, and event-driven monitoring decisions.

Reference page for SNMP traps covering event-driven monitoring and alarm-oriented infrastructure workflows.

Reference page for SNMP v2c covering community-string access and common legacy monitoring assumptions.

Reference page for SNMP v3 covering authentication, privacy, and security-sensitive infrastructure monitoring.

Protocol overview for Veeder Root covering TLS console families, inventory and alarm data, serial intake requirements, and tank-monitoring integration workflows.

Reference glossary for common building automation and protocol-integration terms used across Chipkin documentation.

Reference guide for byte order and endianness covering big-endian vs little-endian values, multi-register data, and the relationship to word order.

Reference page for the FieldServer gateway platform covering legacy protocol coverage, Toolbox workflows, and relationship to QuickServer.

Reference guide for protocol conversion covering gateway-based translation between field protocols and supervisory systems.

Reference page for the QuickServer gateway platform covering deployment workflow, firmware model, and common support tasks.

Reference guide for RS-485 covering differential signaling, daisy-chain topology, termination, and the common protocol families that rely on it.

Reference page explaining how gateway point maps define source-to-destination translation, data typing, scaling, and read-write direction.

BACnet Change of Value overview covering subscription behavior, increment tuning, and why COV support must be verified per device.

BACnet Device Instance overview covering valid range, uniqueness requirements, and the discovery failures caused by duplicate identities.

BACnet Foreign Device Registration overview covering remote single-device access through a BBMD and when it is preferable to full BBMD deployment.

BACnet/IP overview covering UDP transport, BVLL behavior, BBMD design, discovery patterns, and common supervisory-network failure modes.

BACnet Max Masters overview covering MS/TP token search range, latency impact, and the most common configuration mistakes on RS-485 trunks.

BACnet MS/TP overview covering token passing, RS-485 design, addressing, Max Masters, and field-trunk troubleshooting patterns.

BACnet MS/TP token-passing overview covering master rotation, Poll For Master recovery, and why RS-485 quality shows up as application instability.

Protocol overview for Control4 covering XML and HTTP-facing integrations, zone constraints, read-versus-write architecture limits, and cautious smart-building gateway scoping guidance.

Protocol overview for ControlNet covering scheduled versus unscheduled traffic, media assumptions, brownfield intake risk, and cautious gateway scoping guidance.

Reference page for redundant-media ControlNet installations and their brownfield troubleshooting risk.

Reference page for scheduled traffic behavior in legacy ControlNet systems.

Reference page for unscheduled messaging behavior in legacy ControlNet systems.

Protocol overview for DF1 covering Allen-Bradley serial fundamentals, duplex behavior, command-family differences, and inquiry-stage gateway scoping.

Reference page for DNP3 source and destination addressing, endpoint identity, and what a usable addressing schedule should contain.

Reference page for DNP3 control workflow, CROB-style operations, and why control validation is separate from basic read testing.

Reference page for DNP3 object groups, variations, indexes, and why object structure drives point-list quality.

Reference page for EtherNet/IP Assembly Objects covering I/O containers, instance numbers, byte sizing, and scanner configuration risk.

Reference page for the Common Industrial Protocol foundations that matter in EtherNet/IP integrations.

Reference page for DATA_TABLE_READ and DATA_TABLE_WRITE behavior in EtherNet/IP integrations.

Reference page for EtherNet/IP Electronic Data Sheet files covering scanner auto-configuration, source locations, and revision mismatch risk.

Reference page for EtherNet/IP explicit messaging used for reads, writes, and configuration workflows.

Reference page for EtherNet/IP implicit messaging used for cyclic I/O exchange and assembly-driven data updates.

Reference page for Farenhyt event, alarm, trouble, and restore translation into supervisory point models.

Reference page for Farenhyt IFP-2100 family integrations and driver-alignment requirements.

Protocol overview for Farenhyt covering IFP-family driver selection, event translation, and fire-panel supervisory integration guidance.

Reference page for Farenhyt multi-loop panel considerations and scope risk.

Protocol overview for Franklin Fueling covering EVO tank-monitor integrations, Veeder Root compatibility assumptions, and Modbus fallback patterns.

Protocol overview for Gamewell FCI E3 covering CAMWORKS exports, RS-485 wiring, config reuse, and fire-panel gateway integration patterns.

Protocol overview for GE EGD covering exchange definition, producer-consumer mapping, and cautious supervisory integration guidance.

Protocol overview for HART covering 4-20 mA overlay communication, point-to-point versus multidrop operation, command-based device access, and process-instrument integration scope.

Protocol overview for Hochiki FireNET covering family-specific panel alignment, multi-node template workflows, and fire-panel supervisory integration guidance.

Protocol overview for Hunter ACC2 covering irrigation-controller data exposure, controller-specific point inventories, command-level intake details, and coexistence constraints.

Protocol overview for IO-Link covering master and device architecture, IODD-driven engineering, and master-focused integration workflows.

Reference page for M-Bus secondary addressing and meter discovery implications.

Reference page for wired M-Bus meter-bus deployments and integration intake.

Reference page for wireless M-Bus deployments and why they must be identified separately from wired M-Bus.

Protocol overview for McQuay covering controller-family-specific integration patterns, PCL and OPM setup issues, and legacy HVAC gateway guidance.