Unofficial Mackie User Forums > DL1608/DL806/DL32R/ProDX Mixers
WiFi the weak link in the chain
WK154:
It seems that some mixer manufacturers recently are bound and determined to include a critical link of equipment control to outdated and poor performing internal units. This holds true at least for both the Music Tribe and now Mackie products. Both the XR/MR series and more recently the DL16/32S series suffer from this problem. Prior units such as the DL1608/806 and the DL32R from Mackie and the X32 Series from Behringer had no embedded WiFi units and as such left this choice to the user. They would have been better off leaving this aspect to companies whose business depends on reliable equipment by simply providing information on tested units in conjunction with their mixers for users to buy. I don’t mean company names as some provided but product models. Forums and their participants filled that need by trial and error, how sad, but fortunate for the users.
I have repeatedly suggested that they substitute a more current and just possibly less expensive (due to higher volume production) 10/100/1000 Mbps Ethernet units into their mixers instead of the 10/100 Mbps units they currently have. This was 5 years ago when these designs were started. This now limits the speed of recent external WiFi routers with a max of over 1000 Mbps with these mixers by a factor of 10. Even wired units are now limited by this. The price you pay for backward compatibility with older, slower equipment running at 10 Mbps. This is why WiFi speed tests come up with significantly lower AVERAGE thru put. Beacon Frames are sent at 1Mbps and use a significant portion of the available bandwidth as are other packets to comply with backward compatibility.
For those of you still determined to deal with the 2.4 Ghz band here are a few tips.
There are only three channels in the US without interference, 1,6,11. These should be used and often mistakenly other channels are used with the misconception that no-one is using them, surprise. There are 1,11 that have guard bands on either side (no one should be transmitting here) . Six unfortunately has no protection from either side. Old auto sensing units will pick these channels (2-5 and 7-10) and shoot themselves in the foot. I ran a scan on channel 2 only to find channel 1 frames showing up. Channel 3 showed none. So what you are now faced with is adjacent channels messages for which you have no ability to sync with disrupting the channel. A serious overlap. Not good and it goes both ways! If your traffic is on the same channel there is a mechanism to share bandwidth. That is not the case between 1 & 2 or any other adjacent channels. I choose 1 or 11 if possible. Hiding the SSID is also a fruitless exercise.
A tool for dealing with WiFi issues that I would recommend is
http://nutsaboutnets.com/wifimetrix-product-info/
I am always eager to learn new concepts and factual experiences so please post but don’t give me the “I never had this problem” or “mine doesn’t do that” scenario it’s getting old.
Cheers
Wynnd:
The way I read the firmware update on the DL16S is that it has to be through the internal WiFi. I'm hoping that is wrong because switching back and forth would be a pain.
WK154:
--- Quote from: Wynnd on February 01, 2019, 12:40:59 AM ---The way I read the firmware update on the DL16S is that it has to be through the internal WiFi. I'm hoping that is wrong because switching back and forth would be a pain.
--- End quote ---
Wynnd come on. In the DL16S lifetime a few disconnects of the network cable shouln't be a issue. I do wonder why it needs to be done with the internal WiFi.
Wynnd:
I plan to try it through the external WiFi first. It seems to be more than disconnecting the cable. One needs to change the mode then connect or disconnect the wire. My first attempt to connect externally was a failure. I think I have it down now. Still wouldn't want to get stuck doing that before a gig. My plan is to do it at home first and test it a few days first.
WK154:
Reading the manual I interpret using the AP mode as a contingency plan should the update fail using whatever connection method you were using before (ie. Static IP, Dynamic). The process has always been to connect the iPad first to the mixer (in Setup) and then run the MF App. At which time MF will check versions and either continue or request a firmware update or go offline. I don't see AP mode as a requirement.
Navigation
[0] Message Index
[#] Next page
Go to full version