Retour à Solutions

Intégration protocole

Intégration PMS hôtel et contrôle de chambre — interfaces Modbus, RS485, BACnet et BMS pour projets d'intégrateurs.

  • 3 layersIntegration paths
    Modbus · DI/DO · REST
  • LocalRCU scene keep-alive
    offline without cloud
  • BOM tablesRegister / terminal defs
    delivered at project kickoff
  • IntegratorPMS/BMS deployment
    Point Pur Intelligent not SaaS vendor

* Example mapping—not final register addresses; project Modbus table and DI/DO diagram after contract. Webhook / REST require project enablement.

RCU protocol mapping

Protocol mapping table

Core tender and integration documentation—how platform events land on RCU hardware;specific addresses per project BOM appendix.

Platform eventIntegration methodRCU / registerDirectionNotes
Check-inModbus RTU/TCP0x0100room-state wordWTriggers Welcome · seecard power
Check-outModbus0x0100WAccess revoke · vacant cutoff
Room VC / OCC / OOOModbus / API0x0101R/WAlign with PMS enum
DND / MURDry contact + ModbusDI-03 /0x0200RSeedoor sign solution
Engineering / housekeeping cardModbus0x0102WTimed access · lock linkage

Hardware layer · three node types

RCU host

RCU host: local scene engine, offline keep-alive, Modbus slave/gateway; per room or riser aggregation.

Edge gateway

Protocol conversion, multi-RCU aggregation, RS485 isolation; TCP/RTU dual mode; firewall policy by integrator.

Delivery boundary · Point Pur Intelligent vs integrator

CapabilityPoint Pur Intelligent deliversIntegrator / client
RCU / modules / panels✓ hardware + wiring diagramsInstallation
Modbus register table✓ project documentationMap to PMS/BMS
Local scenes / card power logic✓ RCU configurationPolicy confirmation
PMS / GRMS software✓ third party or custom
Room-state dashboard / NOC✓ integrator platform
Remote ops consoleOptional capability✓ seecloud protocol guide

Guestroom capabilities · public schedules

Layered protocol topology

Layered architecture

PMS/BMS → integrator middleware → RCU/gateway → modules/panels/sensors. Bidirectional commands and status; scenes execute locally on RCU.

Engineering docs →
Integrator platform optional

Typical integration sequence

① single RCU scene acceptance → ② Modbus read/write → ③ PMS room mapping → ④ alarm Webhook → ⑤ offline regression.

Protocol inquiry →

Hardware topology reference

Topologie intégration protocole RCU
PMS/BMS (integrator) → gateway/Modbus → RCU → modules/sensors; local scenes without WAN. Cite this diagram +API docs.

Documentation et enablement

Modbus register table

After contract export Excel/PDF per model—coils and holding registers.

DI/DO terminal diagram

Same volume as per-room wiring—SOS/contact/card power terminals matched.

REST / Webhook

Project API key; heartbeat, room state, alarm push format on developer site.

Integration support

Integrator supplies PMS simulator or test environment; Point Pur Intelligent aligns registers.

Modèles recommandés