Bosch D6100 Receiver Account Management

09/02/2026 9:24 am EDT

OPERATIONAL HOW-TO

Bosch D6100 Receiver
Account Management

Using D6200 Programming Software to add, verify, and remove network accounts safely

Version 1.0 | Source training: August 25, 2026
Audience: Receiver Operations and Infrastructure Support

Safe operating sequence: Read the live receiver → save a backup → make one account change → send only that account → read again to verify.

Environment-specific names, addresses, and meeting participants have been removed from screenshots.

This work instruction documents the routine account-management workflow demonstrated for Bosch D6100 network receivers using the D6200 Programming Software. It covers selecting the correct receiver, reading and backing up the live account database, adding or removing one account, sending only that single change, and verifying the receiver state afterward.

CPU, line-card, network, firmware, and global configuration screens are included only as context. Those settings are normally established during receiver deployment and should not be changed during routine account work.

2. Critical operating rules

CAUTION: A saved file can belong to a different receiver or be stale. Opening it does not immediately change the receiver, but sending it can overwrite the active receiver with incorrect data. For routine work, use Read-not Open-to load the live receiver configuration.

  1. Confirm the selected receiver before reading or sending any data.

  2. Read the live account database immediately before every change.

  3. Save a fresh backup before modifying accounts, especially while learning the process.

  4. Use Send Single Account to Receiver for additions and deletions. Do not push the entire database for a routine one-account change.

  5. Do not use Resync All Accounts without explicit coordination and an approved maintenance window; it can restart supervision timers and contribute to late-to-test or communication-failure conditions.

  6. If another administrator may be working in the receiver, read again before sending and again after sending.

3. Before you begin

  1. Access to the designated receiver administration workstation and the approved D6200 operator account.

  2. A case or authorized request identifying the customer, intended receiver, panel account number, and required supervision interval.

  3. The receiver assignment: dedicated receiver, General 1, or General 2.

  4. Any required MAC address, encryption, or anti-substitution details.

  5. A clear rollback/escalation contact if the receiver state does not match the request.

Do not guess supervision settings. Use the value supplied in the request or confirm it with the appropriate technical owner. The training referenced several possible intervals but did not establish a universal value.

4. Workflow at a glance

  1. Connect to the correct receiver and verify the active receiver shown by the software.

  2. Read the live account database from that receiver.

  3. Save a timestamped backup of the newly read database.

  4. Add or mark one account for deletion.

  5. Send only the selected account change to the receiver.

  6. Read the database again and verify the final state before closing the case.

5. Connect to the correct receiver

  1. Open the D6200 Programming Software from the designated receiver administration workstation.

  2. Open Administration > Connection Settings.

  3. Select the receiver named in the request. Dedicated customers use their dedicated receiver; shared customers are assigned to the applicable general receiver.

  4. Leave the established connection details unchanged unless the task specifically authorizes a connection change.

  5. Select OK, then verify the receiver shown in the application status area matches the receiver you intended to use.

Figure 1 - Select the authorized receiver, then confirm the connection. Environment-specific values are redacted.

Stop condition: If the selected receiver, status-bar receiver, or case assignment do not agree, cancel the task and resolve the mismatch before reading or sending data.

6. Read and back up the live account database

  1. Open Network > Network Account Database and choose Read, or use the corresponding Account Database Configuration read shortcut.

  2. Wait for the receiver account list to finish loading. Larger general receivers can take longer.

  3. Review the receiver identity and total account list for reasonableness.

  4. Select Save As and save the generated receiver/date/time-stamped backup before editing.

  5. Keep the newly read database open for the change. Do not replace it with an older saved file.

Figure 2 - Account Database Configuration controls. Use Save As for a rollback point and the single-account controls for routine work.

7. Add an account

7.1 Confirm the identifiers are available

  1. Sort or search by NNC Number and confirm the proposed NNC is not already assigned.

  2. Confirm the Virtual Account matches the account/transmitter ID programmed in the panel.

  3. Use matching NNC and Virtual Account values when possible. If an account-number conflict, MAC-bound account, encryption, or anti-substitution requirement applies, stop and follow the approved exception design.

7.2 Enter the account

Select Add, then complete the Account, Settings, and Notes tabs as applicable. The table below distinguishes required and conditional fields.

Field Operational guidance
NNC Number - required Unique network account number stored in the receiver. It cannot duplicate another NNC on the same receiver.
Virtual Account - required Panel account/transmitter ID. Match the NNC when possible.
Enable Communication - required Set to Yes for an active account.
Supervision Time - required Enter the approved interval from the request or radio/service requirements. Never infer or guess it.
Virtual Receiver / Virtual Line Use the established defaults shown for the receiver unless the authorized design specifies otherwise.
Time Sync / ReSync Keep the receiver's established default unless the task explicitly requires a change.
MAC Address Conditional. Use when required for encryption or anti-substitution.
Name / contact details Optional unless provided by the customer or required by local practice.
Notes Recommended for the case number, requester, and useful implementation context.
Static Key Do not change during routine account creation.

Figure 3 - Add Account dialog. Confirm the required identifiers, enable communications, and select the approved supervision interval.

  1. Select OK. The new record should appear in the account list with a New flag.

  2. Review the row against the request before sending anything to the receiver.

Figure 4 - A newly created record remains local until it is sent; the New flag identifies the pending addition.

8. Send and verify an addition

  1. Select the newly created account row.

  2. Select Send Single Account to Receiver.

  3. Review the confirmation prompt and confirm that the selected NNC/account is the intended record.

  4. Confirm the send. Do not use the commands that send the full file or all changes for a routine addition.

  5. Read the Account Database from the receiver again.

  6. Search for the account and verify it is present, the New flag is gone, and the stored values match the request.

  7. Save the final read file and document the successful verification in the case.

Concurrent-user protection: Sending a single account limits the chance of overwriting changes made by another administrator. The final Read confirms the receiver-not merely the local file-contains the intended result.

9. Remove an account

Authorization required: Account deletion is less common and removes the selected record from the receiver. Confirm the customer/account identity and deletion authority before proceeding.

  1. Read the live Account Database immediately before the deletion.

  2. Search using the known NNC, Virtual Account, or another populated field.

  3. Select the exact account and compare it with the request.

  4. Select Delete. The row should display a Delete flag; this marks the pending local change.

  5. With that row still selected, choose Send Single Account to Receiver and confirm the deletion prompt.

  6. Read the Account Database again and verify the account no longer appears.

  7. Save the final read file and record the verification in the case.

Figure 5 - The Delete flag marks a pending removal. Send only the selected record, then read the receiver again to prove it is gone.

10. Closeout checklist

  1. Correct receiver selected and verified.

  2. Live account database read immediately before the change.

  3. Pre-change backup saved.

  4. NNC uniqueness confirmed for an addition.

  5. Virtual Account and supervision interval matched the request.

  6. Only the selected account was sent.

  7. Live database read again after the send.

  8. Final presence/absence and field values verified.

  9. Final file saved and case notes updated.

11. Troubleshooting and escalation

Condition Response
Receiver identity does not match Cancel. Reopen Connection Settings and resolve the assignment before continuing.
Account list appears stale or changed Read the live receiver again. Do not rely on the open local list.
NNC already exists Do not create a duplicate. Resolve the identifier conflict or approved exception.
Another administrator changed the receiver Read again and re-evaluate the pending change. Send only the selected account.
Account does not appear after sending Read again, confirm the receiver and selected record, then escalate rather than sending the entire database.
Resync All appears necessary Stop and coordinate with the receiver owner. Use a maintenance window and assess customer supervision impact.
CPU/network/line settings may need modification Treat as advanced receiver administration. Capture the observed state and escalate to an authorized receiver engineer.

12. Terminology and operating context

NNC Number: Receiver-held network account identifier. It must be unique on the receiver and is not programmed into the panel.

Virtual Account: Panel account/transmitter ID. The implementation generally matches it to the NNC for readability, but exceptions can exist.

General receiver: Shared receiver used by multiple customers. Automation reaches the shared receiver through the established cloud/receiver path.

Dedicated receiver: Receiver assigned to one customer. Connection direction and configuration can differ from a shared receiver.

Anti-substitution: Bosch security capability used to validate the expected source, potentially including MAC-bound behavior.

Read: Loads the configuration currently stored on the connected receiver.

Open: Loads a previously saved local configuration file; it may be stale or belong to another receiver.

Document basis

Prepared from the "Receiver Knowledge Update" training recording and transcript dated August 25, 2026. Screenshots are instructional excerpts from the recording; meeting participants and environment-specific values were cropped or redacted.

Customer Account Block Reference

CAUTION:

Account Ranges are programmed into the corresponding Cloud receiver for the General Use 6100's accounts added outside of the ranges below will not communicate into automation until the cloud receiver is updated with the extended range. Customer are not allow to submit account requests outside of their designated range.

Customer Account Block Supervision Time:
AISG 2700-2799
Atlantic 6600-6999 1hr Pri 24hr Sec
BIOLA 9000-9998 24hrs
CLEAR 4800-5000
Counterforce 2600-2699
Credit Human 5550-5999 585 sec
LJ Alarms 0001-0200
GLOBAL 4700-4799 24hrs
Paragon 5001-5100
Atlantic 2 8000-8200
Security Center 6100-6299
SIMON 4250-4259
SSA 4100-4199 (NOT ACTIVE)
TXDOT 3100-3199
6100 GENERAL 2 Account Block Supervision Time:
Washington Alarm 9400-9700
RIT 1000-1300 4 Hours
CENMON 3000-3200
RIT 2000-2400
CSCI 4000-4200
XCEL 5000-5200
Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.

Copyright © 2024-26 Bold Group All rights reserved.