Schneider SXWASPSBX10002 BMS Network Controller

EcoStruxure Building (SpaceLogic AS-P-NLS) Building Automation Server (BMS Network Controller) with Secure Boot. Designed for HVAC, lighting, chilled water & heat source control, alarm management, trend logging and protocol gateway applications.

✅ Model Code Definition

AS-P: SpaceLogic Automation Server Premium (high-end automation server)

NLS: N = No LON bus; L = Zigbee wireless support; S = Secure Boot firmware verification

Comparison: AS-P-NL (SXWASPXXX10002) without Secure Boot; AS-P-NLS equipped with anti-tampering firmware authentication.

📌 Hardware Ports

2 × RJ45 10/100 Mbps Ethernet (LAN1/LAN2, dual-port network isolation supported)

2 × RS485 field buses (M-Bus, Modbus RTU compatible)

1 × I/O Bus for SpaceLogic I/O expansion modules

1 × USB Device (program download & commissioning)

1 × USB Host (USB storage, Zigbee wireless adapter)

📋 Core Technical Specifications

Power supply: 24 VDC

Max power consumption: 10 W

Memory: 512 MB RAM / 4 GB Flash

Enclosure rating: IP20, DIN rail mounting

Dimensions: 90(W) × 114(H) × 64(D) mm

Net weight: 0.321 kg

Operating temperature: 0 ~ +50 ℃; Storage temperature: -20 ~ +70 ℃

Humidity: ≤95% RH, non-condensing

🧩 Protocols & Core Functions

BACnet IP, BACnet/SC (Secure Connect), Modbus TCP/RTU

Zigbee wireless device integration

Control logic execution, trend logging, alarm management, user access control

Standalone operation or zone controller under upper-level servers; acts as multi-protocol gateway

Secure Boot: prevents firmware tampering, ideal for high-security projects (hospitals, data centers)

⚠️ Product Lifecycle (Critical Information)

End of Order (EOO): 31 Dec 2026

End of Service (EOS): 31 Dec 2029

Recommended Replacement Model: SXWASP3XX10001 (AS-P-3 V3 New Generation)

Upgrade highlights for AS-P-3: Gigabit Ethernet port, 3 RS485 ports, dual USB Host ports, higher performance, fully compatible with EcoStruxure toolchain.

📎 Matching Accessories

TB-ASP-W1: Terminal base

PS-24V: 24 VDC power supply

Zigbee USB adapter, SXW series I/O expansion modules

📝 Quick Selection Comparison Table

Migration Guidelines: AS-P-NLS (SXWASPSBX10002) → AS-P-3 (SXWASP3XX10001)

Core Tool: Device Administrator – Convert backup set server type (do NOT restore backup directly). Minimum EBO version requirement: EBO 7.0 or later. Older EBO versions cannot recognize AS-P-3.

Preconditions: Offline full backup, field trial first, scheduled downtime, rollback plan prepared.

1. Program Migration (EBO Project, Control Logic, Scripts, Licenses)
2. Backup & Conversion Workflow (Most Critical Step)
3. Perform a full online backup of the legacy AS-P-NLS (including control programs, trends, alarms, permissions, gateway settings, TGML graphics). Never restore this backup directly onto AS-P-3.
4. Open the backup set in Device Administrator, run the Convert backup set server type function to change the target device type from AS-P to AS-P-3. Only converted backups can be downloaded to the new controller.
5. Most control logic, FBD, ST programs, schedules, alarm strategies and trend configurations remain fully compatible after conversion, no program rewriting required.
6. Always open the converted project in WorkStation and run a full compile check to eliminate errors and warnings.
7. Key Compatibility Checks

✅ Standard HVAC, BACnet and Modbus function blocks are fully compatible.

⚠️ Custom third-party drivers, user-defined C-scripts and special driver packages must be validated for AS-P-3 compatibility; older drivers may not work.

Zigbee Compatibility: The original Zigbee USB adapter works on AS-P-3, but the USB port path changes (legacy: 1 USB Host; new: 2 USB Host ports). Update the USB device path inside the project.

Secure Boot: Certificates and BACnet/SC credentials are retained after conversion; re-export and validate certificates after migration.

❌ Incompatibility Risks:

1. Legacy AS-P exclusive system variables and status objects
2. Hardcoded USB/COM port numbers in TGML graphics
3. TLS version mismatch: AS-P-NLS uses TLS 1.0 while AS-P-3 defaults to TLS 1.3. Email alerts and web access will fail due to handshake errors; adjust mail server TLS settings accordingly.

✅ License Note: The original AS-P software license cannot be migrated directly. Apply for license re-binding with the new AS-P-3 serial number in advance via Schneider license transfer process.

3. Post-Migration Testing Items
4. Full project compilation, resolve all errors & warnings
5. Offline simulation of control sequences, PID loops and interlocks
6. Verify alarm forwarding, trend recording and event logging
7. Test TGML graphic access and point read/write permissions
8. I/O Bus & I/O Mapping (Top Risk Area – Hardware Topology Changed)

Legacy AS-P uses TB-ASP-W1 terminal base with different I/O Bus addressing and power budget. AS-P-3 is an integrated unit without a separate base.

1. I/O Bus Address Rule Change (Most Common Failure)

Legacy AS-P: Server occupies I/O Bus address 1

AS-P-3: Server is fixed at I/O Bus address 2. I/O modules start from address 3, maximum 32 nodes (max 31 I/O devices).

Direct migration will cause I/O address offset, module offline and wrong point readings.

Two solutions:

1. Rearrange the physical I/O Bus topology, reassign addresses following AS-P-3 rules, then cross-check I/O mapping table in the project (Recommended).
2. Modify each I/O module’s bus address inside the project to match physical wiring.

Wiring rule: Install AS-P-3 on the far left of the DIN rail; I/O modules extend rightwards. Position 1 is reserved and unavailable.

2. I/O Bus Power Budget

Legacy AS-P base has limited power output; AS-P-3 built-in I/O Bus power: Max 20 W. Add an external 30 W I/O bus power supply if the total power consumption exceeds the limit, otherwise modules will drop offline randomly.

Calculate total module power consumption before migration.

3. I/O Mapping Validation

DI/DO/AI/AO channel definitions remain unchanged; only the I/O Bus address is updated.

Verify every item after download: module number, bus address, channel number, forced values, channel inversion and filter parameters.

SXW series I/O modules are fully interchangeable between legacy AS-P and AS-P-3; no hardware replacement needed.

III. Network Configuration (Ethernet Ports, RS485, BACnet, Gateways)

1. Ethernet Port Comparison

Legacy AS-P-NLS: 2 × 10/100 Mbps LAN (LAN1/LAN2)

AS-P-3: Port1 (10/100/1000 Gigabit), Port2 & Port3 (10/100 Mbps). 3 ports total, supports RSTP and isolated private subnets.

Major Pitfall: Port numbering and subnet roles have changed.

1. IP Planning: Keep the same Device Name and BACnet Device ID to avoid reconfiguration on upper BMS and third-party integration systems.
2. Port Role Reassignment:

Port1 = Main WAN (BMS backbone network)

Port2 / Port3 = WAN or Private Network (configurable)

All static routes, BACnet IP interfaces and gateway bindings previously assigned to LAN1/LAN2 must be re-bound to the new AS-P-3 port numbers, otherwise BACnet IP communication and cross-subnet routing will break.

2. BACnet Settings

BACnet IP and BACnet/SC protocols are compatible. Certificates are preserved after backup conversion, but TLS 1.3 is enabled on AS-P-3; BACnet/SC clients must support TLS 1.3.

Re-scan BACnet routers, BBMD and external device subscriptions after migration.

3. RS485 Serial Ports (COM Ports)

Legacy AS-P: COM A, COM B (2 RS485 ports)

AS-P-3: COM A, COM B, COM C (3 RS485 ports)

Modbus RTU / MS/TP programs referencing COM A/B do not require editing; only re-terminate field wiring to the new terminal block.

Bus biasing and termination resistors: AS-P-3 has different built-in biasing characteristics. Retest bus waveform and adjust termination resistors on long-distance MS/TP buses to eliminate intermittent communication loss.

4. Additional Network Services

Recheck NTP, DNS, static routes, VPN and SNMP settings; re-bind all network objects to the correct physical ports.

1. Hardware, Wiring & Installation Differences (Field Implementation)
2. Power Supply: Legacy AS-P requires separate PS-24V power module; AS-P-3 has integrated power supply, directly powered by 24 VAC / 24~30 VDC. The external PS-24V can be removed from the cabinet.
3. Mechanical Size: Legacy AS-P + base + power supply; AS-P-3 integrated body matches the overall size of legacy AS-P plus PS-24V. DIN rail mounting position is interchangeable, but terminal layout differs – do not reuse existing pre-wired terminal plugs; re-crimp all field wires.
4. USB Interfaces: Legacy: 1 Mini-B debug + 1 USB-A Host; New: 1 USB-C debug + 2 USB-A Host. After plugging the Zigbee adapter into the new USB Host, update the USB instance path inside the project.
5. Heat Dissipation: AS-P-3 has higher power consumption. Install horizontally on DIN rail with sufficient top & bottom ventilation; avoid dense stacking.
6. Step-by-Step Migration Procedure (Minimize Downtime Risk)
7. Before shutdown: Create full project backup, export I/O mapping table, network parameters, BACnet device list, Modbus point list and Zigbee device inventory; keep hard copies.
8. Upgrade EBO WorkStation to V7.0+, and install the matching Device Administrator version.
9. Convert the backup to AS-P-3 format, compile the project and complete offline simulation testing.
10. Replace the controller hardware inside the cabinet, rewire I/O Bus, 24V power, RS485 buses, Ethernet and Zigbee adapter.
11. Flash the latest firmware to AS-P-3, import the converted backup and activate the software license.
12. Power up step by step: First I/O Bus, then RS485 field buses, finally the backbone Ethernet network.
13. Full point verification: I/O channels, field bus communication, BACnet, Modbus, alarms, trends, graphics and Zigbee sub-devices.
14. 24-hour continuous trial run. Keep the original AS-P-NLS as rollback spare hardware; do not remove it immediately.
15. Common Post-Migration Troubleshooting
16. I/O modules offline: Wrong I/O Bus address (server address changed from 1 to 2), incorrect physical topology, or total bus power exceeds 20 W limit.
17. Intermittent Modbus/MS/TP communication: Improper bus biasing or termination resistors, or COM port binding mismatch.
18. Upper BMS cannot read BACnet points: WAN/Private subnet misconfiguration, BBMD error or duplicate BACnet Device ID.
19. Zigbee devices offline: USB Host instance path not updated in the project.
20. Email notification failure: TLS version incompatibility (mail server does not support TLS 1.3).
21. Backup restore error: Direct restore without running the Convert backup set server type tool.

Full Model List of the Series

1st Generation AS-P (Discontinued, with TB-ASP-W1 Base)

Standard HVAC Models

UL864 Smoke Control (SMK) Fire Models

Terminal Bases (Mandatory Accessories)

1. TB-ASP-W1: SXWTBASW110002 (Standard projects)
2. TB-ASP-W1-BAA: SXWTBASW110A02 (BAA-compliant projects)

2nd Generation AS-P-3 V3 (New Replacement, Integrated Unit, No Base Required)

All models include Secure Boot; EBO V7.0+ required.

Key Difference: AS-P-3 has one extra RS485 port; AS-P-L-3 keeps LON bus with one fewer RS485 port.

Model Coding Breakdown (SXWASPSBX10002)

1. SXWASP = SpaceLogic AS-P Automation Server
2. 6th character: S = Secure Boot enabled; X = No Secure Boot
3. 7th character: B = No LON bus; L = LON bus enabled
4. 8th character: X = No Zigbee; L = Zigbee enabled
5. Suffix 10001/10002 = Version & compliance variant; S = SMK smoke control firmware

End-of-Life Replacement Mapping Table

1. SXWASPSBX10002 (AS-P-NLS) → SXWASP3XX10001 (AS-P-3)
2. SXWASPXXX10002 (AS-P-NL) → SXWASP3XX10001
3. SXWASPSBX10001 (AS-P-S) → SXWASPL3X10001 (AS-P-L-3, LON retained)
4. SXWASPXXX10001 (AS-P) → SXWASPL3X10001

Compatible I/O Modules (SXW Series, Interchangeable Between Old & New Servers)

UI-8/AO-V-4, UI-16, DI-16, DO-FC-8, AO-8, RTD-DI-16, etc. No hardware replacement needed; only update I/O Bus address settings.