Skip to main content

Uploading an Acquisuite A8810 or A8812 to VITALITY

Below are the network settings required to ensure that the specific Acquisuite can communicate with Vitality.

Written by Clayton Erekson
Updated over 5 months ago

Consult your IT department or network router manual for information on how to enable network communication over specific ports.

Network Settings

Uploading Channels

In order for the Acquisuite A8810 or A8812 (DAS) to push data to Vitality, data communication to Vitality’s cloud needs to be configured. It has been determined to use the Obvius “Building Manager Online” or “BMO” protocol which is set as default in the Acquisuite. This protocol is based on HTTP, and requires an outgoing TCP connection to destination port 80.

HTTP post is best and more robust than any other Push methods because:

  • XML push validation requires additional server coding.

  • HTTP post uses log file checksums between each transaction, making forensic analysis easier, as well as ensuring accuracy of the data. .

  • HTTP retains the log file format in its simplest form.

  • HTTP makes the network traffic minimal as opposed to XML. This makes transaction time to be decreased, keeping the port open for less time.

  • FTP push -- interruption (such as a reboot during an FTP push) could lose a log file.

  • If the SSL/TLS version of this protocol is being used, it will require an outgoing TCP connection to destination port 443.

To get your DAS to push data to Vitality, follow the following steps:

  1. Log into your DAS

  2. Collect the DAS Serial Number and save for later

  3. Go to Log File Data section, Upload Channel #1 (default) or the other channels you prefer.

  4. Change the protocol to “Obvius Building Manager Online (default)”

  5. Change the Upload URL to “https://upload.vitality.io/acq/https/”

  6. Click Apply.

  7. Run Test as requested by the Acquisuite.

  8. Contact your Vitality Representative

  9. Give the Representative the saved MAC address

  10. Wait for their verification that the DAS is communicating and uploading to Vitality.

Time Server Sync

  • NTP protocol - Inbound and outbound communication UDP traffic over port 123 to time.buildingmanageronline.com

  • RDATE protocol - Inbound and outbound communication over port 37 to time.buildingmanageronline.com

Automatic Firmware Updates (optional)

If Obvius_SSLUpload is installed, the AcquiSuite will check for firmware updates over HTTPS, and your firewall should allow TCP port 443.

Remote Access (optional)

The "Remote Access" feature is based on the mature SSHv2 protocol. This feature should only be enabled at the direction of Tech Support. It is enabled or disabled via the AcquiSuite's LCD menu and/or "Networking >> Setup" page. Even if "Remote Access" is enabled, the "admin" password is still required to login to the AcquiSuite.

Troubleshooting Inbound Communications

Vitality requests that enabling inbound communication from Vitality’s office allows for easier remote troubleshooting and support. Vitality requires this communication to be as follows:

  • Option 1(preferred): Inbound access over port 80 from Vitality’s office (142.254.102.34).

  • Option 2: Virtual Private Network (VPN) connection access over port 80 from Vitality’s office.

  • Option 3: Remote Access Enabled from the Acquisuite.

  • Option 4: Webex or GoTo meeting session, in conjunction with a local machine connected to the internal network hosting the Acquisuite.

Did this answer your question?