Configure IP address of XPA BRG(*Graham)
In order to configure the IP address of an XPA BRG the Network config tool must be used.
Set IP address
The user must have a computer set up on the same subnet as the XPA BRG (e.g the computer and XPA BRG have IP's that share the first three numbers, 192.168.1.2 and 192.168.1.6 share the same subnet). Use the following instructions to configure an XPA BRG's IP:
|1||Open up the Network Config tool||
|2||Click the Scan for Devices button||
|3||Locate the device that you want to configure||
|4||Select DHCP or static. If static fill in the networking details||
|5||Click the Save Configuration button||
|6||On success you will see the following dialog|
Field Bridge vs. On site Bridge
Typically, a commissioning agent will be carrying a field bridge with them. Along with their field bridge, they will likely want to carry a consumer grade router so that they can set up their own individual network even if the infrastructure on site is not completed. In this case the commissioning agent would likely want to keep their XPA BRG in DHCP mode. This allows the router to assign the IP to the XPA BRG. An on site bridge is more likely to need to be static. When infrastructure is in place, it makes a site much more stable if the devices IPs never change. Of course the user can change the IP if they need to, using the Network Config tool.
Firmware compatibility of existing XPA GWs(*Graham)
Existing XPA GWs will have to be updated to support SensorView. As of release 2.5.X the XPA GW will be renamed XPA BRG and will expose SensorView connectivity.
To test if the XPA BRG has a new enough version navigate to the XPA BRG's ip in a browser (e.g. http://192.168.1.50, this is just an example, the device ip is not guaranteed to be 192.168.1.50). The following table shows what the expected results should look like for both incompatible and compatible XPA BRGs:
How to upgrade an existing XPA BRG(*Steve - Complete)
How to determine if wireless devices are compatible with SensorView 13(*Steve - Complete)
Connect to the onsite XPA BRG once it has been updated. If there is no onsite XPA BRG, power on your field BRG. Wait a few minutes.
Open up a web browser to the IP address of the XPA BRG, load Device List page.
Check f/w versions shown on page.
How to do an Over the Air Download to update wireless devices(*Steve - Complete)
Verify that network is no larger than 300 devices. If so, escalate to Engineering or Dennis Thompson. Network will need to be broken up before continuing with OAD update
Download and install WinSCP and PuTTy
Get f/w binaries off of Box and upload to XPoint Wireless Bridge
Run OAD Master
Plan 8 minutes per device
Check progress with Device List page on BRG
How to Plan and Set Up Device Associations / RF Networks(*Steve - Complete)
BRG Virtual ports and Subports
Local channel vs. global channel implications
Considering Sequence of Operation â€“ examples of different ways to set up control channels and the implications related to local vs global channels
Radio channel requirements
1. Typical Wifi Channels 2. Commonly Preferred Zigbee channels 3. Using a Spectrum Analyzer to identify optimal RF channels v. nGWY2 device discovery
Start Sensorview commissioning tool
Configure nGWY2 association via XPoint Associations
XPoint Wireless Device association
1. Using field bridge vs onsite installed bridge; how to initialize RF settings to default or known ix. Working with barcodes x. Verifying device location.
Verifying device connectivity
Identifying installed devices not shown on the floorplan
Finding missing devices (have a barcode but doesn't discover)
Review expected timing of Network Discovery (set expectations for what's normal)
Using bridge diagnostic to check your work (routing table/network scan)
Enhanced Network Security is a new feature first available in XPoint Wireless FW release 2.5.0. This feature enables customization of the 128-bit Network Security Key.
XPoint Wireless (XPW) devices makes use of a pre-defined Network Security Key that enables XPW devices on the same RF Channel and PAN ID to form a network. Non-XPW devices cannot join the network because they do not know this pre-defined key. This provides good security since the value of the key is not discoverable by sniffing tools and is sufficiently long (128-bits) to prevent brute force attacks. However, XPW tools are preprogrammed with the Key so that they can join a network for commissioning, configuration and monitoring. These tools have historically been available only to Acuity technical personnel. As XPW becomes more widespread and configuration tools become more readily available, the need for customers to define custom network security keys has arisen.
Changing the network password
SensorView 13 provides the option to supply a custom network password which is used to generate a custom network security key. In most applications, the default key will provide sufficient security. However, in applications where additional security is desired the custom password can be used.
|1||Open the XPoint Associations tab for the XPA BRG||
|2||Load devices from tree||
|3||Change security key||
|4||Enter custom password||
|6||Confirm all devices received new password||
|7||Migrate to new password key||
nLight / XPoint wireless differences(*Refer to Alex's overview)
Bridge global vs backbone global
Default Sequence of Ops for SLC/iSLC
Out of Box
Once Migrated to Virtual Port
1. PIR sensitivity 2. Sensor enable/disable 3. Working with integrated sensor controller 4. Sensor offline timeout 5. daylighting - see https://acuitysupport.zendesk.com/hc/en-us/articles/225683068
recommended procedure per application
parking garage entryway
occupancy time outs
6. fast/slow ramp rates
use fast ramp while commissioning
change to slow ramp if needed
factory default is slow (3/23/16)
7. commission test mode 8. low end trim
Typical Application Labs
1. Occ sensing 2. Daylight continuous open loop 3. Manual control override
1. Dimming preset profiles 2. Daylight continuous open loop 3. Manual control override
1. Occ sensing 2. Daylight On/Off closed loop 3. Entryway Area 4. Manual control override