Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510

Com'X510 Energy Server

Catalogue Number: EBX510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Energy Server Com'X 510
Colour: Per UOM Std.
  • 1 PCE


hide show
Range of product
Product name
Product or component type
energy server
Device short name
ComX 510
[Us] rated supply voltage
main supply: 24 V DC
Maximum power consumption in W
  • 26 W 24 V
  • 15 W via PoE
    • Communication network type
    • RS485, Modbus serial on 1 RJ45
    • RS485, Modbus serial on terminal block
    • Ethernet, PoE 15W (Power over Ethernet) on 1 RJ45
    • Ethernet, DHCP on 1 RJ45
      • Number of inputs
      • 6-6 digital
      • 2-2 analog
        • Discrete input current
          60 mA at 12 V DC
          Sensor power supply
          24-24 V DC at 50 mA
          Analogue input type
        • Pt 1000
        • Pt 100
        • 0...10 V
        • 4...20 mA
          • Number of outputs
            Communication gateway
            Ethernet TCP/IP to Modbus
            Memory capacity
          • 128 MB RAM
          • 256 MB flash
          • 4 GB SDRAM
            • Mounting mode
              Mounting support
              35 mm DIN rail
              Product certifications
            • C-Tick
            • cUL
            • UL
            • CE
              • Standards
              • EN 60950
              • EN 61010-1
              • UL 508
              • UL 60950
                • Depth
                  69 mm
                  109 mm
                  144 mm
                  Net weight
                  450 g
                  Product specific application
                  energy management systems
                  Web services
                  web server
                  Local signalling
                • LED: for power supply
                • LED: for status (GPRS)
                • LED: for communication (Modbus)
                • LED: for communication (Ethernet)
                • LED: for communication (WiFi)
                • LED: for I/O
                  • Compatibility code
                    ComX 200
                    Relative humidity
                    5-95 % at 55-55 °C without condensation
                    IP degree of protection
                  • IP20 (terminal block)
                  • IP40 (front face)
                    • Ambient air temperature for operation
                      -25-70 °C
                      Ambient air temperature for storage
                      -40-85 °C
                      Pollution degree
                      Operating altitude
                      2000 m
                      EU RoHS Directive
                      Mercury free
                      RoHS exemption information
                      China RoHS Regulation
                      The product must be disposed on European Union markets following specific waste collection and never end up in rubbish bins
                      California proposition 65
                      WARNING: This product can expose you to chemicals which are known to the State of California to cause Carcinogen and Reproductive harm.For more information go to

                      Documents & downloads

                      hide show
                      Filter items
                      • All

                      • CAD Files and Packs

                      • Product Brochures

                      • Movies

                      • Technical Data Catalogues

                      • Technical Leaflet

                      • Installation Instruction

                      • Product Environmental

                      • End of Life Manual

                      • Handout

                      • Data Bulletin

                      • Operating Manuals

                      • System User Guide

                      • Specification for Tender

                      • Specifications

                      • Application Solutions

                      • Case Studies

                      • Declaration of Conformity

                      • White Paper

                      • Certificates (MSDS)

                      • Firmware - Released

                      • Software - Updates

                      • Software - Release Notes

                      Frequently Asked Questions

                      hide show

                      ETSNZ How to Delete and import New custom devices on EBX510

                      Please see attached note on how to Remove and import custom devices on the EBX510

                      ETSNZ Configuring Com'x510 to PUblish with GPRS Modem

                      See attached document.

                      Com'X 200 / 210 / 510 Documentation (Technical Datasheet, User Guide, and Installation Guide)

                      Documentation for COM'X 200/210/510 is needed

                      Product Line
                      Com'X 200 (EBX200)
                      Com'X 210 (EGX210)
                      Com'X 510 (EBX510)


                      The documents below include Technical Datasheet, User Manual, and Installation Guide

                      Com'X 200/210/510 Installation Guide:5406AD002
                      Com'X 200/210 User Manual: DOCA0036EN
                      Com'X 510 User Manual: DOCA0098EN
                      Com'X 200/210/510 Technical Datasheet: PLSED310098EN

                      Does EBX510 come with 24V DC power supply?

                      No EBX510 does not come with 24V DC power supply.Need separate power supply 24V DC.
                      One possible power supply is ABL8RPS24030

                      regulated SMPS - 1 or 2-phase - 100..500 V - 24 V - 3 A

                      For more information on power supplies available see:

                      How can I discover ZigBee devices on the EBX510?

                      Follow this procedure to discover connected ZigBee devices:

                      1. Click the Com'X 510 in the device tree view.

                      2. Click Discover devices to open the Discovery window.

                      3. Select the communication protocol ZigBee.

                      4. Enter the Timeout time (in minutes).

                      5. Click Start to discover the devices. Discovered devices are listed in the ZigBee Discovery window. Click Stop if you want to stop the ZigBee Discovery process. Also in order to detect the ZigBee devices, you also need to activate the discovery mode on the different devices.

                      6. Close the ZigBee Discovery window. All the discovered devices appear in the device tree view.


                      Communications loss after changing Com'X security settings

                      Changing the Com'X security certificate causes communication loss

                      Product Line
                      Com'X 200, Com'X 210, Com'X 510


                      When the device security parameters have changed the Com'X must reestablish communications by reloading the web interface.

                      Allow device to reestablish communications. 

                      Note: If you are unable to find security certificate settings then you may need to perform a firmware upgrade. 

                      How do I add/create a Modbus Device Manually in EBX510?

                      Modbus devices that are not connected cannot be discovered, but they can be added manually using the following procedure:

                      1. Click the Device Settings main tab.

                      2. Select the upstream device with a Modbus serial port in the device tree view. For example, the Com'X 510 must be selected to connect a Modbus device to the Com'X 510.

                      3. Select the Modbus Serial collapsible menu.Click the header to expand the Modbus Serial collapsible menu.

                      4. Click Create a new device in the Device drop-down list.

                      5. Select a Device Type in the drop-down list. NOTE: Only the devices that can be connected to a Modbus serial port are listed.

                      6. Type the Slave ID in the Configuration collapsible menu. Refer to Common Properties on page 75 for completing the other parameters.

                      7. Click Create and the device appears in the device tree view

                      How it can be integrated Sepam Protection Relays using Sepam multi-protocol communication interfaces ACE850 ?

                      Com'X and ACE850 can communicated over Modbus TCP/IP protocol, ACE850 is not a Com'X library native device,
                      in many application where Sepam 40(fw version > 7.00), or Sepam 80(fw > 6.00) communication network
                      has been built using ACE850, it will be able to communicate with Com'X via the following configuration:

                         1. From the Ethernet Devices Menu select "Generic Modbus TCP to Serial Gateway"
                         2. Configure the Gateway with the IP Address of the ACE850
                         3. From the Modbus Serial Devices Menu select the appropriate Sepam
                         4. For the Slave ID, enter "the Unit-Id 255 or any value in the range 1-247"

                      Link150, Comx200/210, Comx510 CAD Files

                      CAD files for the gateway devices:
                      Link150, Comx200/210, Comx510

                      Product Line
                      Link150, Comx200/210, Comx510

                      Click on the links below for the Comx200/210 and Comx510 CAD files:
                      Comx510 CAD File

                      Comx200/210 CAD File

                      The Link150 CAD file is attached below

                      What is the maximum number of devices that can be added in Com'X 510/200/210?

                      User wants to know how many devices can be added in the Com'X 510/200/210.

                      Product Line
                      Com'X 510 (EBX510)
                      Com'X 210 (EBX210)
                      Com'X 510 (EBX200)

                      Adding devices via the Webpage

                      The Com'X 510/200/210 gateways support a total up to 64 devices with a maximum of 20 Modbus serial slave devices.

                      What's the Com'X510 maximum memory expansion possible?

                      User would like to know why only 3.7GB's of data is shown on the COM'X510 snapshot, as well as, is the memory expandable.

                      Product Line
                      COM'X 510

                      Energy Server, Ethernet Gateway

                      The SD Card in the COM'X 510 is actually a 4GB SD Card.  This card is used to store the historical data logged in the COM'X 510. 
                      Data is automatically overwritten after 25 months, so logging less doesn't get you more time. 
                      The amount of storage is equal to...32 devices, 30 topics each at 15 minute intervals = 25 months of data.

                      Latest firmware version for the energy server COM'X 510 (Version 5.2.0)

                      What is the latest firmware version for the Energy Server Com'X 510 ?
                      Product Line
                      COM'X 510
                      EBX 510

                      COM'X 510

                      New firmware upgrade is needed
                      As of 09/26/2018, the latest version of firmware for COM'X 510 is 5.2.0, and can be downloaded from the link below.

                      Instructions for upgrading the firmware can be found from KB FA270261

                      Com'X510(15 min data logging interval) Historically data export issue when it select every meter topics in one month time interval interval

                      The publication process limits the length of a data file published, since the limitation of the Com’X resource. So, one month data for every topic might be truncated into several small data files. To avoid publication process takes too many CPU resource, the publication process has limited time for every publication period. It means the publication process may not publish one month data at one time.
                      For example, if one month data has be truncated into 3 pieces and the publication period is one month, it means every publish period only one third of data in this month can be published. Next month another piece data will be published. It takes 3 month period to complete one month data publication, and there will be a lot of current months' data cannot be published.
                       The best way to define the publication period is based on sampling period.
                       If sampling period is one day, then publication period can be one month. If sampling period is fifteen minutes, the publication period should be everyday or less. If sampling period is less than 5 minutes, the publication period should be less than 6 hour.
                      If the customer would like to log all topics for all of the configured device, we recommend that they setup the export for once a day, at a minimum.

                      How to perform a master reset on the COM'X 200 / COM'X 210 / COM'X 510

                      A user may not know how to reset the COM'X 200, COM'X 210 or COM'X 510 to its default factory settings.

                      Product Line:
                      COM'X 200, COM'X 210
                      EBX200, COM'X 510

                      Master reset on the COM'X 200, COM'X 210 and COM'X 510

                      There may be a need to reset a COM'X to the default factory settings.

                      HAZARD OF IP ADDRESS CONFLICT
                      Disconnect the Com'X from any Ethernet networks before resetting the IP settings to factory values.
                      Failure to follow these instructions can result in impaired communications.

                      Note: When following the procedure below, all data and logs that have been stored are erased.

                      To reset the Com'X completely, follow this procedure to set all configuration settings to factory values:
                      1. Turn off the Com'X by disconnecting the control power and wait until the power LED is off.
                      2. Press simultaneously the Backup button (7) and Wi-Fi button (8) on the Com'X front face and turn on the Com'X. Hold the buttons for at least 10 seconds until the power LED flashes three times.
                      3. Release the buttons. The Com'X reboots.
                      4. Wait for the Com'X to restart completely. The power LED is:
                      • orange when the Com'X is starting.
                      • green when the Com'X has been reset to factory settings and is ready to be configured.


                      What are the Com'X 200 and EBX200 I/O capabilities?

                      What are the Com'X 200 and EBX200 I/O capabilities?

                      Product Line
                      Com'X 200, EBX200
                      Energy Servers and Ethernet Gateways

                      A user requires information about the Com'X 200 I/O capabilities.

                      Located on the device are the following digital and analog I/O ports.

                      Digital I/O:
                      input   - 6
                      output - 0

                      Analog I/O:
                      input   - 2
                      output - 0

                      Both digital and analog I/O can be powered by the Com'X 200 or by an external source.

                      Below are the I/O architecture interfaces, characteristics, and limits.

                      KYZ metering can be set up as a Digital input.
                      Reference the Com'X 200 installation guide (DOCA0035EN-01) and user guide (DOCA0036EN-01) for more details.

                      Com’X 510 enable upstream network access

                      How to enable upstream network access on Com'X 510 energy server?

                      Product Line

                      Web server 
                      Allowing downstream devices to access upstream network 

                      • In Firewall Management, you can enable upstream network access
                      • This allows downstream devices to access servers (such as DNS, SNTP, and SMTP) on the upstream network
                      • The table below describes the downstream interface (where the message originated) and the upstream interface on which the message will be forwarded, based on your network selection
                      Network Option Downstream (from) Upstream (to)
                      GPRS/3G only Ethernet Port 2 GPRS/3G
                      GPRS/3G and switched network -- --
                      Wi-Fi only Ethernet Port 2 Wi-Fi
                      Wi-Fi and switched network -- --
                      2 Switched Ports (1 IP address for both) Upstream network access not available
                      2 Separate Ports (1 IP address for each) Ethernet Port 2 Ethernet Port 1
                      • For example, with the Com’X configured to use two separate Ethernet ports, an IFE connected downstream on Com’X Ethernet Port 2 can send emails to EcoStruxure Facility Expert through Ethernet Port 1
                      • Upstream network access is disabled by default. When enabled, access adapts to the network configuration in Network Settings
                      • Go to Com'X 510 web server --->Settings-->Security-->Firewall Management-->Network Access--> Yes (to enable upstream network access)
                      • If Network Access settings are not found on Settings-->Security-->Firewall Management page, check Com'X 510 firmware version. It may need an upgrade. For example, if the FW is 2.2.6, it first needs to be upgraded to 3.6.3 and then to 5.2.0 to enable upstream network access functionality 
                      • To download latest firmware version 5.2.0, refer to FA274919
                      • To download firmware version 3.6.3, click on this link Com'X 510 v3.6.3 Firmware​
                      • For instructions on how to upgrade Com' X firmware, refer to FA270261

                      Communication Device (Gateway) Replacement List EGX series

                      User wants to replace EGX series device

                      Product Line
                      Link150 (Part # EGX150)
                      Com'X200/210, Com'X510 (Part numbers EBX200, EBX210, and EBX510)


                      The replacement for each meter is as follows
                      EGX100 ->  Link150 (Part # EGX150)
                      EGX200 ->  Link150 (Part # EGX150)
                      EGX300 -> Com'X Series
                      EGX400 -> Com'X Series

                      Please contact your local Schneider Electric sales representative to determine the most appropriate gateway for your application.
                      Sales Support:

                      Internet Explorer closes when the web page launches Java applet on ETZ510

                      Goals and Symptoms

                      Internet Explorer closes when the web page launches Java applet on ETZ510

                      Facts and Changes

                      TSXETZ510 Exec Firmware version 1.8

                      Causes and Fixes

                      The Internet Explorer window gets closed when a web page for a 'TSXETZ510' Ethernet module is
                      opened and the web page contains a Java applet.

                      This problem will occur on a TSXETZ510 module that has Exec Firmware version 1.8 and above.

                      The reason is becasue the PC does not have the 'Java Runtime Environment version 1.6.0' from 'Sun
                      Microsystems' installed or the option is not selected in the Internet Explorer 'Advanced' settings. .

                      If the 'Java Runtime Environment version 1.6.0' from 'Sun Microsystems' is not installed, download
                      it from '' and install it.

                      • Open Internet Explorer
                      • Click on 'Tools\Internet Options'

                      • Click on the 'Advanced' tab in the 'Internet Options' window.

                      • Scroll down and locate the line for Java(Sun)
                      • Click on the checkbox next to the item labeled 'Use JRE 1.6.0 for (applet ).... ' to select it.
                      • Click on the 'Apply' button in the 'Internet Options' window.
                      • Click on the 'OK' button in the 'Internet Options' window.
                      • Close Internet Explorer and restart it.


                      Legacy KB System (APS) Data: RESL184045 V1.0, Originally authored by AlCh on 05/18/2007, Last Edited by AlCh on 05/18/2007
                      Related ranges: Modicon TSX Micro ETZ - TR

                      Does the Com'X 200/210 or Com'X 510 support the Powerlogic and SY/MAX protocols?

                      A user needs to know if the Com'X 200 / Com'X 210 / Com'X 510 supports the Powerlogic and SY/MAX protocols

                      Product Line
                      Com'X 200/EBX200
                      Com'X 210/EBX210
                      Com'X 510/EBX510

                      Gateway Portocol Support

                      A user needs to convert legacy device protocols such as Powerlogic and SY/MAX from CM2000 series, CM200 series, CM100 series, etc. to Modbus TCP/IP.

                      The Com'X 200, Com'X 210 and Com'X 510 do not support the Powerlogic or SY/MAX protocols.
                      Use an EGX100 or EGX300 to convert Powerlogic or SY/MAX to Modbus TCP/IP. However, EGX100/300 have been obsoleted and the replacement is EGX150. EGX150 supports the Powerlogic or SY/MAX protocols as well.

                      Com'X 200 supported Protocols:
                      IPv6 - HTTP
                      Modbus TCP/IP

                      Com'X 510 supported Protocols:
                      Modubs TCP/IP

                      Energy Server Com'X 200 ( EBX 200 ) will not respond to ping

                      The Com'X 200 ( EBX 200 ) will not respond to pings from the Windows command prompt.

                      Product Line:
                      Com'X 200
                      EBX 200

                      Prior to firmware v2.0.5:
                      Com'X 200 does not recognize Windows pinging method, however the Com'X 200 will respond to a UDP request.

                      Firmware v2.0.5:
                      'Reply to ping' is disabled.

                      Prior to firmware v2.0.5:
                      Open the Com'X 200 login page in a browser by entering the default or assigned IP address into the address bar of a browser. Although the Com'X 200 will not respond to ping, the login page and subsequent pages are still accessible through a browser.
                      Alternatively, you may download an IP Scanner that has UDP packet capability to confirm connection.

                      Firmware v2.0.5:
                      To enable the 'Reply to ping', first open the Com'X 200 login page in a browser by entering the default or assigned IP address into the address bar of a browser and login.
                      1. Click the Settings tab
                      2. Expand the General Settings
                      3. Select Network Settings
                      4. Click Yes next to 'Reply to ping'

                      How do I bring the Com'X Analog Inputs into Power Monitoring Expert (PME)?

                      The Com'X is not a native device in PME.

                      Product Line
                      Power Monitoring Expert 7.x
                      Power Monitoring Expert 8.x
                      EBX200, Com'X200
                      EGX510, Com'X510

                      Power Monitoring Expert Modbus Device Importer

                      To bring the device into PME:
                      1. Install the Com’X via the Instruction Manual, wiring the Analog Inputs and Ethernet connection.
                      2. Connect to the Com'X via its webpage and add the Analog Input via the Com'X User Guide.
                        1. Select the Custom Library tab > + Create.
                      1. Customize the model and select Create.
                      1. Configure the properties of the model (i.e. scaling and units) and Save changes.
                      1. Add the device in Device Settings.
                        1. For the appropriate Analog Input, select 'Create a new device' for the Device dropdown menu.
                      1. Select the previously created Device Type in the Device Type dropdown menu.
                      2. Configure the device and select Create.
                      The data is now available within the Com'X webpage under the Measurements Table tab. The measurement will be associated with the Commodity specified in step 2.5.
                      1. If using a Com'X 510 with firmware v3.0.6 or Com'X 200/210 with firmware v2.2.1, Enable Modbus TCP/IP on Ethernet 1; otherwise, continue onto Step 4.
                        1. ​Select the Settings tab.
                        2. Under Security > Firewall Management, switch the Enable Modbus TCP/IP on Ethernet 1 to ON
                      1. Verify that Ethernet 1 is the Ethernet port being used to communicate to the PME server.
                      1. In PME, create a device type using the Modbus Device Importer
                        1. Open Management Console.
                        2. Select Tools > System > Modbus Device Importer.
                      1. Select Edit > Advanced Properties and rename the Device Type and check the "Make available as a direct Ethernet device in Management Console" box. Click OK.
                      2. Select Edit > New Manager
                        1. Manager Name: Analog Input
                        2. Manager Type: External Numeric Manager
                      1. Add a new Module for Analog Input 1 (**IF USING Analog Input 1)
                        1. Add a new Register
                          1. Data Type: IEEEFloat
                          2. Register Type: Holding Register
                          3. Modbus Address 410000
                          4. Request Type: R
                          5. Use the attached MDI_parameter_calc_for_ComX_AI.xlsx to calculate the appropriate Register Scale, Multiplier, and Offset value.
                      2. Add a new Module for Analog Input 2 (**IF USING Analog Input 2)
                        1. Add a new Register
                          1. Data Type: IEEEFloat
                          2. Register Type: Holding Register
                          3. Modbus Address 410002
                          4. Request Type: R
                          5. Use the attached MDI_parameter_calc_for_ComX_AI.xlsx to calculate the appropriate Register Scale, Multiplier, and Offset value.
                      3. Save the device type.
                      4. Select Tools > Validate Template and verify that there are no errors.
                      5. Configure Logging and Calculation.
                        1. Select Configure Logging and Calculation
                      1. Check "Log" to enable logging for the desired register.
                      1. Specify the desired Log Interval in seconds.
                      2. Press OK.
                      3. Save the device type.
                      4. Select Tools > Add Device Type
                      1. Open Management Console and Add the Device
                        1. Select Devices in Management Console.
                        2. Right-click and select New > Ethernet Device
                        3. Enter the desired Group and Name.
                        4. The Device Type will be the name specified in step 4.3.
                        5. Enter the IP address of the device
                        6. Click OK.

                      The referenced Com'X 200 / 210 / 510 Documentation is available here:

                      Trio Q Radios - The Channel Share + feature for Collision Avoidance

                      When using a Trio Q Series full duplex radio (eg a QB450 or QH450) as a repeater, the radio will receive the entire packet before transmitting it back out. All Ethernet packets are transmitted intact, and processed intact. This ensures highest packet integrity, and allows for routing of messages when necessary.
                      Now you’re probably going to say “Well, if that is the case, what is the advantage of a full duplex repeater, if it can’t transmit what it is receiving instantly?” (as does our older EB450 full duplex repeater, providing very low latency) The answer lies in the nature of Ethernet traffic.
                      The concern is the possible number of different applications that may be trying to access the channel, without any synchronisation between them. Even in the most basic Point to MultiPoint setup you might think all that is happening is polling of devices by the SCADA protocol, but look at the traffic with Wireshark and you may be surprised.
                      There may be one application polling devices via (eg) DNP3, Windows maintaining an ARP cache and deciding at random 15 to 45 second times to refresh the cache, and then add some SNMP diagnostics or Telnet browsing and you have a lot of different devices trying to access the channel.
                      The need for effective collision avoidance (requiring a full duplex ChannelShare+ Master) is much higher than on a serial system. The full duplex nature of a QB450 or QH450 Entry Point or Repeater allows it to both receive a message and at the same time transmit a Channel Busy flag when necessary.
                      There are several separate things to consider in the following scenarios:
                      (a)  We are talking about radio system topologies that are two frequency (simplex systems can only make use of Carrier Detect collision avoidance)
                      (b)  You can only enable “Collision Avoidance Master” in full duplex radios
                      (d)  In a PTMP system, the entry point is a collision avoidance master
                      (d)  In a PTMP via Repeater system, the repeater is a collision avoidance master
                      (e)  If you want to use ChannelShare+ collision avoidance, you MUST have a collision avoidance Master
                      (f)   If you have a two frequency system but only half duplex radios (no full duplex Entry Point or Repeater), you can only operate in Carrier Detect collision avoidance mode
                      Here are a few examples of the operation of ChannelShare+ mode, describing the activity of the Master radio and a typical Remote:
                      Scenario A:
                      (a)  CS+ Master: Has data to transmit, but Rx channel is clear (mute not broken) -> Data is transmitted but the Channel Busy flag is clear (not set)
                      (b)  Remote: Mute breaks as CS+ Master keys up. Remote initially assumes channel is busy, but once the data stream starts it sees the Channel Busy flag is clear. Remote declares channel is clear and that it is free to transmit.
                      Scenario B:
                      (a)  CS+ Master: Has data to transmit, and its Rx channel is busy (mute broken) -> Data is transmitted and the Channel Busy flag is set
                      (b)  Remote: Mute breaks as CS+ Master keys up. Remote initially assumes channel is busy and backs off. Once the data stream starts, it sees the Channel Busy flag is set. Remote declares channel is busy and continues to back off. Remote waits until Channel Busy flag is clear or its Mute re-asserts. (no signal heard)
                      Scenario C:
                      (a)  CS+ Master: Has data to transmit, and Rx channel starts off clear (Mute not broken). In middle of transmission, Mute breaks. -> Data is transmitted and Channel Busy flag is initially clear, but when Mute breaks the Channel Busy flag is set.
                      (b)  Remote: Mute breaks as CS+ Master keys up. Remote assumes channel is busy, but once data stream starts, it sees the channel busy flag is clear. Remote initially declares channel is clear and will transmit if it has data to send. When after a short time Remote detects that Channel Busy flag has now been set, it declares channel is busy and backs off.
                      The time taken for the CS+ Master to detect its mute breaking and set the Channel Busy flag is approx. 5 mS. This time is known as the collision window. During this brief time it is possible for collisions to occur.