Home AMX User Forum AMXForums Archive Threads AMX Hardware

cannot access the NI-3000

from netlinx studio, I can listen and find the NI-3000, but I connot connect to it.
from program port everything seems normal.
from the NXA-WAP200G, I see 2 connection, NI-3000 and my PC, but not the 8400 panel

I removed all files from 8400 panel to return it to the original state, I put the NI-3000 in PRD mode in hope that I would be able to access it to no avail.

config
NI-3000 10.10.10.4/24 dynamic
8400 10.10.10.2/24 dynamic
WAP 10.10.10.240 static
PC 10.10.10.101 dynamic

I do not see any blinking status to show network activity when in the MVP8400 config, but if I reset the MVP8400, it does get an address.

To me the NI-3000 is OK, problem seem to be the 8400

Comments

  • Re:

    I had that a time ago.
    First check if you're networkswitch is ok.
    You can also try to force the network speed of the ni-3000 to 10Mb/s halfduplex
    instead of auto as default.
    It seems to be that some network switches not working correct with amx. The problem is that they nagotiate about the network speed for ever if both are set tot auto.
    It worked for me but it took me about 3 hours to find out this issue.

    Good Luck
  • informel wrote:
    from netlinx studio, I can listen and find the NI-3000, but I connot connect to it.
    from program port everything seems normal.
    from the NXA-WAP200G, I see 2 connection, NI-3000 and my PC, but not the 8400 panel

    I removed all files from 8400 panel to return it to the original state, I put the NI-3000 in PRD mode in hope that I would be able to access it to no avail.

    config
    NI-3000 10.10.10.4/24 dynamic
    8400 10.10.10.2/24 dynamic
    WAP 10.10.10.240 static
    PC 10.10.10.101 dynamic

    I do not see any blinking status to show network activity when in the MVP8400 config, but if I reset the MVP8400, it does get an address.

    To me the NI-3000 is OK, problem seem to be the 8400

    First of all:
    What do you mean with the "/24" and "dynamic" in your config list?

    This would be the steps for checking the setup of the MVP

    -> in protected setup / Wireless settings
    Do you get a MAC address in IP settings?
    If not, maybe the WLAn card in the panel is not connected correctly.

    Do you get any RF Link Info? Check SSID Channel number (try channel 11) and default settings (no encryption, SSID is AMX)

    If wireless settings are ok and working, you should get the MAC address of the WAP, and the panle's MAC should be listed in the WAP.

    If you have this things above, check network settings (gateway address, subnet mask) set in the MVP. Can you ping the panel?

    If this also works, the network setting in general should be ok.
    Next and last would be to check the System Settings of the MVP. I would prefer Mode "URL", and in this mode the master IP/URL must fit to your master's IP address.
  • cannot access NI-3000

    Thanks for your help
    problem was with a cheap 24 ports switch connected to my Cisco router.
    It is strange that I could ping everything, I can listen in Nextlinks studio, but would not be able to connect.

    info requested
    /24 is for the network mask instead of writing 255.255.255.0 (/24 means that there are twenty four "1" in the mask), it is faster to write it this way.
    dynamic means it received and addrees from my router (DHCP)
  • viningvining Posts: 4,368
    /24

    Subnet Tables:
    Class A Host/Subnet Table 
    Class A
    Number of
    Bits Borrowed            Subnet         Effective     Number of      Number of Subnet
    from Host Portion        Mask           Subnets       Hosts/Subnet   Mask Bits
    -------               ---------------  	---------     -------------  -------------
      1                    255.128.0.0            2       8388606           /9
      2                    255.192.0.0            4       4194302           /10
      3                    255.224.0.0            8       2097150           /11
      4                    255.240.0.0           16       1048574           /12
      5                    255.248.0.0           32        524286           /13
      6                    255.252.0.0           64        262142           /14
      7                    255.254.0.0          128        131070           /15
      8                    255.255.0.0          256         65534           /16
      9                    255.255.128.0        512         32766           /17
      10                   255.255.192.0       1024         16382           /18
      11                   255.255.224.0       2048          8190           /19
      12                   255.255.240.0       4096          4094           /20
      13                   255.255.248.0       8192          2046           /21
      14                   255.255.252.0      16384          1022           /22
      15                   255.255.254.0      32768           510           /23
      16                   255.255.255.0      65536           254           /24
      17                   255.255.255.128   131072           126           /25
      18                   255.255.255.192   262144            62           /26
      19                   255.255.255.224   524288            30           /27
      20                   255.255.255.240  1048576            14           /28
      21                   255.255.255.248  2097152             6           /29
      22                   255.255.255.252  4194304             2           /30
      23                   255.255.255.254  8388608             2*          /31Class B Host/Subnet Table 
    Class B	     Subnet               Effective       Effective    Number of Subnet
     Bits        Mask                 Subnets         Hosts        Mask Bits
    -------  ---------------          ---------       ---------    -------------
      1      255.255.128.0                2             32766        /17
      2      255.255.192.0                4             16382        /18
      3      255.255.224.0                8              8190        /19
      4      255.255.240.0               16              4094        /20
      5      255.255.248.0               32              2046        /21
      6      255.255.252.0               64              1022        /22
      7      255.255.254.0              128               510        /23
      8      255.255.255.0              256               254        /24
      9      255.255.255.128            512               126        /25
      10     255.255.255.192           1024                62        /26
      11     255.255.255.224           2048                30        /27
      12     255.255.255.240           4096                14        /28
      13     255.255.255.248      	    8192                 6        /29
      14     255.255.255.252    	     16384                 2        /30
      15     255.255.255.254          32768                 2*       /31Class C Host/Subnet Table 
    Class C      Subnet       Effective  Effective  Number of Subnet
     Bits        Mask         Subnets     Hosts     Mask Bits
    -------  ---------------  ---------  ---------  --------------
      1      255.255.255.128      2        126        /25
      2      255.255.255.192      4         62        /26
      3      255.255.255.224      8         30        /27
      4      255.255.255.240     16         14        /28
      5      255.255.255.248     32          6        /29
      6      255.255.255.252     64          2        /30
      7      255.255.255.254    128          2*       /31
    
  • informel wrote:
    info requested
    /24 is for the network mask instead of writing 255.255.255.0 (/24 means that there are twenty four "1" in the mask), it is faster to write it this way.
    dynamic means it received and addrees from my router (DHCP)

    Never have seen this notation, so... :rolleyes:
  • /XX notation

    Hi Marc
    Cisco use it a lot. It is faster to write (I'm lazy)
  • yuriyuri Posts: 861
    its not only cisco, its a standard notation used in the networking business :)
  • cannot access NI-3000 AGAIN

    This ting is driving me crazy!
    I could not access it the next day

    I notice that the indicator would stay red on the MVP for communication.
    So I changed system setup (URL instead of listen), reboot panel and got the indicator turned green.

    To communicate from my PC, I have to turn the firewall off in trendmicro PCCillin.
    I went in the firewall exeption and allow all TCP/UDP, all port, IN/OUT for my LAN (10.10.10.XXX) without result, but that is not a concern for me right now.

    What bugs me is that when I first installed it, it worked right out of the box, i.e. MVP in listen mode.
  • informel wrote:
    This ting is driving me crazy!
    I could not access it the next day

    I notice that the indicator would stay red on the MVP for communication.
    So I changed system setup (URL instead of listen), reboot panel and got the indicator turned green.

    To communicate from my PC, I have to turn the firewall off in trendmicro PCCillin.
    I went in the firewall exeption and allow all TCP/UDP, all port, IN/OUT for my LAN (10.10.10.XXX) without result, but that is not a concern for me right now.

    What bugs me is that when I first installed it, it worked right out of the box, i.e. MVP in listen mode.

    One more idea would be to turn off the UDP broadcast the master sends.
    In terminal/telnet on the master (only required for URL mode AUTO)
    Welcome to NetLinx v3.21.343 Copyright AMX Corp. 1999-2006
    >set udp bc rate
    
      Current broadcast message rate is 5 seconds between messages.
      Enter broadcast message rate in seconds between messages
     (off=0 ; default=5) (valid values 0-300): 0
      Setting broadcast message rate to 0 seconds between messages
      New broadcast message rate set.
    
    >
    
    Some Switches detect this permanent broadcast message as flooding and disable the switcher's port after some time.
    If broadcast is off, you MUST work in URL mode (personally I always use URL mode)
  • DHawthorneDHawthorne Posts: 4,584
    I would recommend a static IP on the master and using URL mode as well. It's by far the most reliable for a persistent connection, and will allow the AMX equipment to remain connected to each other even if there is disruption with the DHCP server. My experience has been this is usually the problem with these kinds of mysterious disconnects - the DHCP server somehow has lost the devices, even though they are still online.

    You can't rule out other aspects of the network infrastructure either. I was just at a job where the NetLinx was functioning perfectly, but the touch panels couldn't connect to it. The panels appeared on the network, but the NetLinx did not. There was a router on the job, and a 16 port switch at the router location, and resetting both of them did nothing. Then I remembered that we had added an Escient Fireball to the equipment rack, but there were not enough connections for it's network, and we installed a small switch there to "split" the network for the Fireball and the NetLinx. Resetting that switch restored my connection. Cascaded switches are often the cause of this kind of problem, and I am continuously browbeating sales and installation teams to avoid it whenever possible, and especially if one or more of those switches have to be at a non-central location.

    A bad wire or crimp can be the culprit too. Some operations are not as fussy as others. A weak signal or a noisy one might be able to "connect" to the network, but not be able to transfer meaningful data. I had another job where a Wi-Fi connection between buildings was replaced with an underground run. The total distance was about 400', so I knew I had to boost it, but even though I could get a link light at my nearest junction, I couldn't get a usable signal. It turned out there was a length of CAT3 between the router and the underground feed. When I replaced that with CAT5, all was well. It was only about 40' of CAT3, but it degraded the signal enough to prevent a solid connection, even though wire testers and even NIC link lights showed it to be good.
  • JustinCJustinC Posts: 74
    Dave brings up a good point about noisy connections, I also have noticed that the NIC on the AMX devices are a little more picky than pc NIC. I have been able to use a cable for my laptop just fine but then put the master on the same wire and it not work, replace both ends and it works fine.

    The other thing you may try is to make sure that there is not another WAP anywhere close to your current one. I have seen this same kind of scenario whenever a customer put a CISCO WAP in close proximity to my router, I had to step off the beacon interval in the router and then all my problems disappeared.
  • Static or DHCP that is the question
    DHawthorne wrote:
    I would recommend a static IP on the master and using URL mode as well. It's by far the most reliable for a persistent connection, and will allow the AMX equipment to remain connected to each other even if there is disruption with the DHCP server. My experience has been this is usually the problem with these kinds of mysterious disconnects - the DHCP server somehow has lost the devices, even though they are still online.

    Hi Dave
    I am from PC/network field and kind of new in this field, I take care of a site that has 1500+ PC and never see behavier like that. PC are DHCP, printers and servers are static.

    Since the NI3000 and MVP panel are the equivalent of server/peripheral, it make sence to make those address static,

    thanks for the advise
    Brgds Yves
  • DarksideDarkside Posts: 345
    Is it all new kit?

    Please list firmware revs for mvp wap and ni.

    There could be some clues here.

    There were significant issues with connection in some of the early f/w revs.

    Also, check the data rate in the mvp and advise how many decimal places are shown in the info window. This will determine if you have a really old NIC or not.
  • DHawthorneDHawthorne Posts: 4,584
    informel wrote:
    Hi Dave
    I am from PC/network field and kind of new in this field, I take care of a site that has 1500+ PC and never see behavier like that. PC are DHCP, printers and servers are static.

    Since the NI3000 and MVP panel are the equivalent of server/peripheral, it make sence to make those address static,

    thanks for the advise
    Brgds Yves

    I've seen a lot of it. Perhaps it's peculiar to the AMX NICs. I have many times had AMX devices drop off the network even though they could still talk to each other (because of a static IP). Resetting the switch brings them back. Perhaps my diagnosis that it's a lost connection to the DHCP is not correct, but it sure seems like something of that order.
Sign In or Register to comment.