Home AMX User Forum AMX Technical Discussion

Max No. TPs per System and Max No. TPs per WAP

Hey everyone I was wondering if any one knows if there is a maximum number of touch panels you can have on 1 system and keep them all online all the time and also what is a maximum No. of connected touch panels to a AMX NXA-WAP250G before strange things start happening.

Comments

  • Jorde_VJorde_V Posts: 393
    syslock wrote: »
    Hey everyone I was wondering if any one knows if there is a maximum number of touch panels you can have on 1 system and keep them all online all the time and also what is a maximum No. of connected touch panels to a AMX NXA-WAP250G before strange things start happening.

    That is completely dependant on what your project is like. (practically). So it depends on the network situation there.

    In theory it's 32 clients per VAP, so that's 64 clients in total. (The 250 supports 2 VAPs.)

    Touchpanels is completely dependant on the configuration, how many ports etc you use per touchpanel, how many updates need to be send, how actively the system will be used. Wireless + cabled, or just wireless etc. Max number I used on 1 system was 26, but that's R4s + Wireless Panels + Wired panels, no issues there.
  • Thanks Nerieru, the reason I asked is because I have three Boardrooms with a total of 97 touch panels 6 wired and 91 wireless, there are 3 WAPS per boardroom and 3 NI3100 controllers I have the TPs shared across the 3 systems(NI3100), but I just can't get the wireless TPs to stay online all the time. Of the 91 wireless TPs 3 are MVP8400s and the rest are MVP5200i. The MVP5200is are used at each seat in the 3 boardrooms to control that seats screen source, translation headset, and mic.

    The WAPS all have the same SSID and in each boardroom I use channels 4, 8, 13 the SSIDs are the same because the TPs are dynamically assigned to the boardrooms and then the seats from storage when needed. The building also already has a wireless infrastructure network running on channels 1, 6 and 11

    "In theory it's 32 clients per VAP"
    Thanks I didn't know that.
  • jweatherjweather Posts: 320
    You should work with the existing wireless infrastructure instead of trying to build your own. Your channels are overlapping with their channels, which is not a good result for anybody. If the building wifi isn't strong enough in those rooms, see if IT can deploy additional access points to reinforce it.
  • DHawthorneDHawthorne Posts: 4,584
    I don't know that it's possible to have a wireless panel never fall offline. Such is the nature of wireless. But three WAPs per boardroom? Are these rooms really that big? You might be over-saturating the bandwidth, especially if there are other wireless networks outside the rooms. I think you need a really good spectrum analysis of the site. If three WAPs per room are really necessary, I would put them in WDS mode rather than broadcast on 3 separate channels as well. You might simply be seeing them jumping from one WAP to another.
  • Unfortunately its a bank, and they don't want us on their network..

    I've logged the online offline status of the TPs for the day so far to text file.
  • I understand that because its wireless they might go offline for a few seconds and then go back online but how often will this happen and how long will they be offline, and how much of this is wireless network issues. Boardroom 1 is a 43 seater, boardroom 2 is a 24 seater and boardroom 3 is a 16 seater, Ive tried using less WAPs and found that more TPs were offline more of the time in boardroom 1, In boardrooms 2 & 3 it made no difference. The idea behind the multiple access points was to provide some redundancy, that's what the system designer told me.
  • jjamesjjames Posts: 2,908
    They *should* only go offline during processor reboots, panel reboots / power offs.
  • Jorde_VJorde_V Posts: 393
    syslock wrote: »
    Thanks Nerieru, the reason I asked is because I have three Boardrooms with a total of 97 touch panels 6 wired and 91 wireless, there are 3 WAPS per boardroom and 3 NI3100 controllers I have the TPs shared across the 3 systems(NI3100), but I just can't get the wireless TPs to stay online all the time. Of the 91 wireless TPs 3 are MVP8400s and the rest are MVP5200i. The MVP5200is are used at each seat in the 3 boardrooms to control that seats screen source, translation headset, and mic.

    They'll fall offline, and come back online a lot if there's a lot of interference on the network (wireless). The best way to check for interference is to use a scanner like Wi-Spy and see if you can trace it down. Changes are there are WAPs in the neighbourhood that keep changing their channel and those would then be interfering with your WAPs in turn interfering with your Wireless Panels. The dB strength from the panels isn't so high, so even little interference will kill it with certain events.

    Another point might be that your WAPs are switching channels and are going further than channel 11, in the USA the only wireless channels that you are allowed to use are channels 1-11. So AMX Panels only go that far, in most european countries it's 1-13. If the panel then can't connect because the WAP is on the wrong channel for a period of time. (if it's on 13 you might be able to connect to it over channel 11, but the connection wont be stable) your panels might fall offline and come back online.

    There might also be other 2.4Ghz equipment interfering. Devices such as Zigbee and others.
    syslock wrote: »
    The WAPS all have the same SSID and in each boardroom I use channels 4, 8, 13 the SSIDs are the same because the TPs are dynamically assigned to the boardrooms and then the seats from storage when needed. The building also already has a wireless infrastructure network running on channels 1, 6 and 11
    That means that those 2 are interfering with each other, so both should be on 1, 6, 11 if that is achievable.

    channel 1: 1 .. 3
    channel 4: 2 .. 6
    channel 6: 4 .. 8
    channel 8: 6 .. 10
    channel 11: 9 .. 13
    channel 13: 11 .. 15

    Only if your channel bandwith is set to 20Mhz btw. (1 channel = 5Mhz in that case, 4 channels are used for broadcast so that means 20Mhz)

    AMX doesn't handle channel 13, so that might explain why your pannels are going offline (they're trying to connect to your WAP using channel 11, which is the weakest point when sending out on channel 13)

    Because there is so much overlap you have a lot of interference.

    Lemme draw it out for you:


    The bandwidth you have left is everything above the red line.
    syslock wrote: »
    "In theory it's 32 clients per VAP"
    Thanks I didn't know that.

    No problem.
    syslock wrote: »
    I understand that because its wireless they might go offline for a few seconds and then go back online but how often will this happen and how long will they be offline, and how much of this is wireless network issues. Boardroom 1 is a 43 seater, boardroom 2 is a 24 seater and boardroom 3 is a 16 seater, Ive tried using less WAPs and found that more TPs were offline more of the time in boardroom 1, In boardrooms 2 & 3 it made no difference. The idea behind the multiple access points was to provide some redundancy, that's what the system designer told me.

    Most of it is network related. The idea is good, the effect is the opposite of it though.

    Edit:
    jjames wrote: »
    They *should* only go offline during processor reboots, panel reboots / power offs.

    Or when they lose signal (be it intentional or not)

    Apart from that Offline/Online events also (mostly) have an impact on your processor's load.
  • DHawthorneDHawthorne Posts: 4,584
    syslock wrote: »
    I understand that because its wireless they might go offline for a few seconds and then go back online but how often will this happen and how long will they be offline, and how much of this is wireless network issues. Boardroom 1 is a 43 seater, boardroom 2 is a 24 seater and boardroom 3 is a 16 seater, Ive tried using less WAPs and found that more TPs were offline more of the time in boardroom 1, In boardrooms 2 & 3 it made no difference. The idea behind the multiple access points was to provide some redundancy, that's what the system designer told me.

    If you want redundancy, use WDS, not multiple access points on different channels. Then they will all be on the same channel per room, and there is less opportunity for interference, and less access point hopping.
  • Jorde_VJorde_V Posts: 393
    DHawthorne wrote: »
    If you want redundancy, use WDS, not multiple access points on different channels. Then they will all be on the same channel per room, and there is less opportunity for interference, and less access point hopping.

    WDS doesn't give you redundancy WDS enables you to extend your wireless network without cables. What you're referring to is a Wireless Mesh Network, that gives you redundancy as well, because if route A fails they'll go via route B. (wireless as well)

    And in the way you're saying it the AP would need to have enough distance between them not to interfere too much and not too much distance because then the network quality would suffer, WDS is not something you should attempt in an environment where you have too little influence on things (placement etc).

    In the end you don't need this if you just set up a wired network, as that will always be more stable and faster.

    The best would be if you set it up to channels 1, 6, 11 with active roaming on the panels, where the SSID is still the same. But to do that he'll have to match them with the current system, so where there's an WAP on channel 6 he'll have to choose 1 or 11, which again is dependant on the rest of the network. But if he can he should match these that way. Without knowing the physical layout of the rooms and the where and how things are connected this will proof to be a difficult task.
  • Thanks guys for the input your help is really appreciated.
    So to sum up:
    First prize is to convince the banks IT department to allow us to use the existing wireless network.
    Second prize to setup a network using channels 1, 6 and 11 making sure not to use channels in the same area as the banks existing wireless network.
    Nerieru wrote: »
    AMX doesn't handle channel 13.
    I didn't know that either.
  • DHawthorneDHawthorne Posts: 4,584
    Nerieru wrote: »
    WDS doesn't give you redundancy WDS enables you to extend your wireless network without cables. What you're referring to is a Wireless Mesh Network, that gives you redundancy as well, because if route A fails they'll go via route B. (wireless as well)

    Yes and no. If a repeater station fails, you can still potentially pick it up from the base or another repeater, and there's your redundancy. I was thinking in terms of this specific scenario, there it seems to me there is a fair amount of overlap.
    The best would be if you set it up to channels 1, 6, 11 with active roaming on the panels, where the SSID is still the same. But to do that he'll have to match them with the current system, so where there's an WAP on channel 6 he'll have to choose 1 or 11, which again is dependant on the rest of the network. But if he can he should match these that way. Without knowing the physical layout of the rooms and the where and how things are connected this will proof to be a difficult task.

    My feeling is that this is exactly his problem. The real, if minimal, disconnect when it's roaming from one channel to another. I propose he needs to get rid of the multiple channels, period. You are right that a mesh would be better than WDS (that was just the first thing that occurred to me), but I really think he needs to eliminate the roaming. What with competing wireless in other areas, every time a panel hops from one WAP to another he is getting a noticeable delay.
  • Jorde_VJorde_V Posts: 393
    syslock wrote: »
    Thanks guys for the input your help is really appreciated.
    So to sum up:
    First prize is to convince the banks IT department to allow us to use the existing wireless network.
    Second prize to setup a network using channels 1, 6 and 11 making sure not to use channels in the same area as the banks existing wireless network.
    No first prize wouldn't be using their network because there's no way a bank is going to allow that, the security would need to be put down a few notches. Not to mention you don't know what traffic is going over their network, there might be a lot and heavily secured, so you don't want your AMX in there.

    So what you should do in this situation is prize 2 + hide your SSID so regular folks don't even see your network. Try to cover the areas well with your network, so you don't leave any gaps. Interference also comes back in to play again, so if their config in a room is:
    1 - 6 - 11
    yours should be:
    11 - 1 - 6 or
    6 - 11 - 1

    Ideal placement is nasty to work out, but often unnecessary. Just be sure you don't cause interference on other parts of the network(s).

    syslock wrote: »
    I didn't know that either.
    Just to clarify it's channel 12-13 (and technically 14) that it doesn't pick up.

    Edit:
    DHawthorne wrote: »
    Yes and no. If a repeater station fails, you can still potentially pick it up from the base or another repeater, and there's your redundancy. I was thinking in terms of this specific scenario, there it seems to me there is a fair amount of overlap.

    Depending on the size of these boardrooms, but I can't actually imagine you'd need more than 1 AP per boardroom, let alone more than 2.
    DHawthorne wrote: »
    My feeling is that this is exactly his problem. The real, if minimal, disconnect when it's roaming from one channel to another. I propose he needs to get rid of the multiple channels, period. You are right that a mesh would be better than WDS (that was just the first thing that occurred to me), but I really think he needs to eliminate the roaming. What with competing wireless in other areas, every time a panel hops from one WAP to another he is getting a noticeable delay.

    Considering the channels he's broadcasting on himself the real issue lies within that. Active roaming shouldn't cause the panel to go offline though, or rather I haven't seen that happen when I used it. Depending on the placement of the WAPs it might or might not be a good idea to put them on the same channel, apart from how the wireless panel will pick that up.
  • truetrue Posts: 307
    Nerieru wrote: »
    No first prize wouldn't be using their network because there's no way a bank is going to allow that, the security would need to be put down a few notches. Not to mention you don't know what traffic is going over their network, there might be a lot and heavily secured, so you don't want your AMX in there.
    Which is why I would hope they are capable of putting the AMX stuff on its own VLAN. If something this simple is beyond their capability and installed hardware, then I don't blame them, and their IT guys are awesome for still getting paid.
    Nerieru wrote: »
    So what you should do in this situation is prize 2 + hide your SSID so regular folks don't even see your network.
    Define 'regular?' With an AMX TP constantly talking to a master, I would get that SSID no problem. I don't even try. But I would hope the WPA(2) stops me...
    Nerieru wrote: »
    Try to cover the areas well with your network, so you don't leave any gaps. Interference also comes back in to play again, so if their config in a room is:
    1 - 6 - 11
    yours should be:
    11 - 1 - 6 or
    6 - 11 - 1

    Ideal placement is nasty to work out, but often unnecessary. Just be sure you don't cause interference on other parts of the network(s).
    Good placement isn't hard with the right tools, but sometimes is made difficult by the building :) If you can't use their WAPs, use this channel advice. If you can, with that many panels, get a spectrum analyzer to determine antenna placement, range, and noise sources.
  • Jorde_VJorde_V Posts: 393
    true wrote: »
    Which is why I would hope they are capable of putting the AMX stuff on its own VLAN. If something this simple is beyond their capability and installed hardware, then I don't blame them, and their IT guys are awesome for still getting paid.

    If possible yes, but they don't want him on their network. So I excluded that. Chances are the project manager doesn't know what you are on about and if they ask their IT they would probably ask it in a way that they'll get a 'no, insecure' answer. But if you can get them to agree to that it would/could be the best situation. Worth a shot at least.
    true wrote: »
    Define 'regular?' With an AMX TP constantly talking to a master, I would get that SSID no problem. I don't even try. But I would hope the WPA(2) stops me...

    Even without traffic you would need to be stopped by the encryption, not the hiding of the SSID or say MAC control.

    Regular folk: The none-IT people in the building & not tech-savvy people
    true wrote: »
    Good placement isn't hard with the right tools, but sometimes is made difficult by the building :) If you can't use their WAPs, use this channel advice. If you can, with that many panels, get a spectrum analyzer to determine antenna placement, range, and noise sources.

    My point exactly, and if you don't have it/can't get it or don't know how to do it. Hire a company that does. You'll get a full report and you'll be able to build your network from there.

    Chances that you'll get that through in a bank are slim though.
  • the8thstthe8thst Posts: 470
    You should also check with the IT department to make sure they don't have rogue access point detection running on their wireless system (which I would guess they will be utilizing for security purposes).

    It is not hard for wireless systems to squash, or at the very least cause major headaches, to unauthorized wireless access points within their air space.
Sign In or Register to comment.