kenoman742 wrote:Looking for opinions from those that know a lot more than me. Does this look like a viable wireless show network plan? Planning on running all multicast.
The diagram on the right is sorta how I do mine. I run Pi to wireless router, Falcon off the router via ethernet.
Yes this should work. Assuming the remote pi is generating the data for the falcon. I would use unicast from remote pi to falcon to keep the falcon data off the wifi.
Thank you. I will switch the remote pi to unicast and see how that works.
Is the Remote Pi a long distance from the Access Point? Have you tried using the Pi's built-in WiFi to connect to the AP (without having to go through the NanoStation)?
Also, if the ESPixelSticks are not all using the same Universes (probably not) then why are you Multicasting? I think I would use Unicast for all of the Universe data and only Multicast the FPP Sync packets (although with a single remote, it doesn't matter much)
Is the Remote Pi a long distance from the Access Point? Have you tried using the Pi's built-in WiFi to connect to the AP (without having to go through the NanoStation)?
Also, if the ESPixelSticks are not all using the same Universes (probably not) then why are you Multicasting? I think I would use Unicast for all of the Universe data and only Multicast the FPP Sync packets (although with a single remote, you could unicast that too)
ESPixelSticks have less lag and are more reliable using multicast compared to unicast, even though in muticast causes more network congestion. If you read anything from people using ESPixelSticks everyone will agree multicast is the preferred method. I used 30+ last year on different universes with a nano station and had no noticeable issues.
--
Shawn
sctwohig wrote:ESPixelSticks have less lag and are more reliable using multicast compared to unicast, even though in muticast causes more network congestion. If you read anything from people using ESPixelSticks everyone will agree multicast is the preferred method. I used 30+ last year on different universes with a nano station and had no noticeable issues.--
Shawn
It is unicast that slightly increases traffic on a network. However, unicast on a WIRELESS network causes the entire network to slow down significantly due to the steps needed for a wireless station to be able to send a response to the received packet (this is NOT an issue on wired networks).
The intended purpose of Multicasting is for when multiple clients need to receive the exact same data (e.g. streaming video). But that is rarely the case in the Christmas Lighting environment....UNLESS you are sending the same Universes (same channel data) to multiple controllers (possible, but rare). Multicasting *can* achieve higher performance *when* multiple clients need to receive the *same* data (sync packets for example). But when all the clients are receiving *different* data it makes more sense to Unicast that data out to the individual clients that data is intended for.
I was not aware that ESPixelsticks perform better with multicast. I'm not sure why that would be and I can't confirm or deny if that special case really exists. But generally speaking, Multicast over WiFi has more limitations and impact on overall throughput than Unicast (this is contrary to Multicast over wired networks). In fact, many modern Access Points have a feature called MC2UC which internally converts multicast on the wired connection to Unicast going out over the WiFi to reduce the performance hit with Multicast over WiFi. So its possible when you think you are multicasting it may still be unicasting behind the scenes and you aren't aware of it.
While WiFi Unicast does utilize an acking system, it is done at the lower layer-2 (its not the same as higher layer-3 TCP ack packets) and this process does not significantly slow down the layer-3 data rate. On the other hand, Multicast over WiFi is required to use the SLOWEST data rate of all receivers which can significantly slow down overall data throughput. Clients which are capable of higher data rates are all forced to use the slowest data rate for compatibility with the slowest client on the network when using Mulitcast (or broadcast). This means that all clients will be as slow as the slowest client when using Multicast, but Unicast will allow each client to communicate at the fastest speed that each one supports.
Another problem with using Multicast over WiFi is that multicast (and broadcast) packets over WiFi are buffered at the AP and only transmitted during each Beacon Interval. By default, most AP's have a Beacon Interval of 100ms which means that Multicast traffic is only sent every 100ms (by default). So if you are sending sequence data using Multicast over WiFi then it is only getting sent every 100ms and not the 50ms or 25ms that you may have set in the sequencer. For FPP sync packets this is fine because the FPP Remote will still send the local fseq data out the wired ethernet at the rate stored withing the fseq file (50ms or 25ms or whatever). But for E1.31 channel data sent over WiFi, using Multicast is going to limit the timing interval to 100ms by default.
Again, I can't comment on whether ESPixelSticks are a special case where they work better with Multicast (perhaps its the slower frame rate imposed by the WiFi Beacon interval?), but here is an abstract from the Internet Engineering Task Force (IETF) that briefly describes why Multicast over WiFi is generally discouraged unless you have a special case that needs it or where the application is not impacted by the limitations.
Multicast Wifi Problem Statement
There have been known issues with multicast, in an 802.11 environment, which have prevented the deployment of multicast in these wifi environments. IETF multicast experts have been meeting together to discuss these issues and provide IEEE updates. The mboned working group is chartered to receive regular reports on the current state of the deployment of multicast technology, create "practice and experience" documents that capture the experience of those who have deployed and are deploying various multicast technologies, and provide feedback to other relevant working groups. As such, this document will gather the problems of wifi multicast into one problem statement document so as to offer the community guidance on current limitations.
1. Introduction
Multicast over wifi has been used to low levels of success, usually to a point of being so negative that multicast over wifi is not allowed. In addition to protocol use of broadcast/multicast for control messages, more applications, such as push to talk in hospitals, video in enterprises and lectures in Universities, are streaming over wifi. And many end devices are increasingly using wifi for their connectivity. One of the primary problems multicast over wifi faces is that link local 802.11 doesn't necessarily support multicast, it supports broadcast. To make make multicast over wifi work successfully we often need to modify the multicast to instead be sent as unicast in order for it to successfully transmit with useable quality. Multicast over wifi experiences high packet error rates, no acknowledgements, and low data rate. This draft reviews these problems found with multicast over wifi. While this is not a solutions draft, common workarounds to some of the problems will be listed, along with the impact of the workarounds.
2. Multicast over WiFi Problems
802.11 is a wireless broadcast medium which works well for unicast and has become ubiquitous in its use. With multicast, however, problems arise over wifi. There are no ACKs for multicast packets, for instance, so there can be a high level of packet error rate (PER) due to lack of retransmission and because the sender never backs off. It is not uncommon for there to be a packet loss rate of 5% which is particularly troublesome for video and other environments where high data rates and high reliability are required. Multicast, over wifi, is typically sent on a low date rate which makes video negatively impacted. Wifi loses many more packets then wired due to collisions and signal loss. There are also problems because clients are unable to stay in sleep mode due to the multicast control packets continuing to unnecessarily wake up those clients which subsequently reduces energy savings. Video is becoming the dominant content for end device applications, with multicast being the most natural method for applications to transmit video. Unfortunately, multicast, even though it is a very natural choice for video, incurs a large penalty over wifi.
One big difference between multicast over wired versus multicast over wired is that wired links are a fixed transmission rate. Wifi, on the other hand, has a transmission rate which varies over time depending upon the clients proximity to the AP. Throughput of video flows, and the capacity of the broader wifi network, will change and will impact the ability for QoS solutions to effectively reserve bandwidth and provide admission control.
The main problems associated with multicast over WiFi are as follows:
- Low Reliability
- Lower Data Rate
- High interference
- High Power Consumption
These points will be elaborated separately in the following subsections.
2.1. Low Reliability
Because of the lack of acknowledgement for packets from Access Point to the receivers, it is not possible for the Access Point to know whether or not a retransmission is needed. Even in the wired Internet, this characteristic commonly causes undesirably high error rates, contributing to the relatively slow uptake of multicast applications even though the protocols have been available for decades. The situation for wireless links is much worse, and is quite sensitive to the presence of background traffic.
2.2. Low Data Rate
For wireless stations associated with an Access Points, the necessary power for good reception can vary from station to station. For unicast, the goal is to minimize power requirements while maximizing the data rate to the destination. For multicast, the goal is simply to maximize the number of receivers that will correctly receive the multicast packet. For this purpose, generally the Access Point has to use a much lower data rate at a power level high enough for even the farthest station to receive the packet. Consequently, the data rate of a video stream, for instance, would be constrained by the environmental considerations of the least reliable receiver associated with the Access Point.
2.3. High Interference
As mentioned in the previous subsection, multicast transmission to the stations associated to an Access Point typically proceeds at a much higher power level than is required for unicat to many of the receivers. High power levels directly contribute to stronger interference. The interference due to multicast may extend to effects inhibiting packet reception at more distant stations that might even be associated with other Access Points. Moreover, the use of lower data rates implies that the physical medium will be occupied for a longer time to transmit a packet than would be required at high data rates. Thus, the level of interference due to multicast will be not only higher, but longer in duration.
Depending on the choice of 802.11 technology, and the configured choice for the base data rate for multicast transmission from the Access Point, the amount of additional interference can range from a factor of ten, to a factor thousands for 802.11ac.
2.4. High Power Consumption
One of the characteristics of multicast transmission is that every station has to be configured to wake up to receive the multicast, even though the received packet may ultimately be discarded. This process has a relatively large impact on the power consumption by the multicast receiver station.
3. Common remedies to multicast over wifi problems
One common solution to the multicast over wifi problem is to convert the multicast traffic into unicast. This is often referred to as multicast to unicast (MC2UC). Converting the packets to unicast is beneficial because unicast packets are acknowledged and retransmitted as needed to prevent as much loss. The Access Points (AP) is also able to provide rate limiting as needed. The drawback with this approach is that the benefit of using multicast is defeated.
Using 802.11n helps provide a more reliable and higher level of signal-to-noise ratio in a wifi environment over which multicast (broadcast) packets can be sent. This can provide higher throughput and reliability but the broadcast limitations remain.
4. State of the Union
In discussing these issues over email and, most recently, in a side meeting at IETF 99, it is generally agreed that these problems will not be fixed anytime soon primarily because it's expensive to do so and multicast is unreliable. The problem of v6 neighbor discovery saturating the wifi link is only part of the problem. A big problem is that the 802.11 multicast channel is an afterthought and only given 100th of the bandwidth. Multicast is basically a second class citizen, to unicast, over wifi. Unicast may have allocated 10mb while Multicast will be allocated 1mb. There are many protocols using multicast and there needs to be something provided in order to make them more reliable. Wifi traffic classes may help. We need to determine what problem should be solved by the IETF and what problem should be solved by the IEEE.
I will actually be running two remotes for my show, the pi and f4v2 for the mega tree and a beaglebone black with octoscroller running a 2 x 2 p10 tune to sign. I have already tested the tune to sign and it works well on unicast. The beaglebone black is also connected through a nano station. The 8 pixel sticks also run well on multicast and that will continue to be my plan as most opinions on multiple forums claim they work best on multicast. My second pi is arriving today and I will set it up and test it as a second remote on unicast. The access station will be in the garage and all controllers in my small front yard. I live in a tract home and the entire lot is only about 60 feet wide so not any great distance. I don't use the built in wifi on the pi's because I connect that to my home network so I can access them for set up and file uploading. Eth0 is set to a separate show network. I really appreciate all the suggestions and infomation you guys have shared. I started this post because when testing the mega tree with the f4v2 connected directly to the nano station, it caused obvious lags in the lights to the music. I get the same lag if I connect the tune to sign with the beaglebone as a bridge instead of a remote. At this point I believe the only way to get it working correctly is to have the mega tree and the tune to as remotes and just have the pixel sticks getting data from the access point.
Thank you again,
Ken

