Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

[Imported] ChannelShare+ Collision Avoidance in Q Series

Remote Operations Forum

Support forum for Schneider Electric SCADA systems, radios and RTUs. From commissioning integration devices and software, to enhancing existing installations or troubleshooting.​

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Remote Operations
  • Remote Operations Forum
  • [Imported] ChannelShare+ Collision Avoidance in Q Series
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
Joel_Weder
Captain Joel_Weder Captain
76
BevanWeiss
Spock BevanWeiss
20
sbeadle
Kirk sbeadle Kirk
17
MartinChartrand
Captain MartinChartrand Captain
15
View All
Related Products
product field
Schneider Electric
Trio Licensed Radios

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Remote Operations Forum
sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2019-10-25 03:24 PM

0 Likes
0
686
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2019-10-25 03:24 PM

[Imported] ChannelShare+ Collision Avoidance in Q Series

>>Message imported from previous forum - Category:Trio Data Radios<<
User: joelw, originally posted: 2018-10-17 22:35:37 Id:120
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.

---------------

**_jweder:_**

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:**
- We are talking about radio system topologies that are two frequency (simplex systems can only make use of Carrier Detect collision avoidance)
- You can only enable "Collision Avoidance Master" in full duplex radios
- In a PTMP system, the entry point is a collision avoidance master
- In a PTMP via Repeater system, the repeater is a collision avoidance master
- If you want to use ChannelShare+ collision avoidance, you MUST have a collision avoidance Master
- 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.

Labels
  • Labels:
  • Radio
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic
Replies 0
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of