Home AMX User Forum AMX Control Products

MVP-8400 Online, Offline, Online, Offline....

Greetings,

Since installing the latest firmware, my MVP-8400 constantly goes on and offline every thirty seconds or so.

It is currently connected to an open WAP with no encryption. The connection is URL with the IP address of the master entered in.

Any ideas?

Thank you.

Comments

  • DarksideDarkside Posts: 345
    Which NIC has the panel got?

    54G?
  • TurnipTruckTurnipTruck Posts: 1,485
    It is the older generation one. The new firmware will not allow anything except WEP on the existing card.
  • DarksideDarkside Posts: 345
    We saw some hopping on and off the network issues like this recently after upgrading the 'old NIC' to the 54G (to improve range/connectivity only).

    Netstumbler showed several devices on our channel, so I shifted the router channel and the disconnection behavior has indeed gone.

    Surprised me a bit that this was the problem, but, happily, it's now gone!

    I've not seen this rapidity of disconnection using the old NIC before.

    What firmware in the master are you running?
  • TurnipTruckTurnipTruck Posts: 1,485
    The master is an NXC-ME/260 with 2.31.37 (latest available)
  • IP Conflict

    Do you show Link Quality and Link Status when the panel drops offline? If so, pull the batteries and try to ping the IP address... if you have a reply, you have another device at the same IP. Also, as Stephen said above, make sure it is not environmental by taking the same Wireless Router/AP to a completely different location (or at least the panel) and see if you can connect at that different location.
  • TurnipTruckTurnipTruck Posts: 1,485
    Yes, the wireless connection and quality is excellent as the panel is only 15 feet or so from the AP. I will check for an IP conflict although all of the devices are hard-set IP addresses and the DHCP range is way up high above.

    Good advice nonetheless, I'll check it out.
  • DarksideDarkside Posts: 345
    TT,

    Check you network setup in the master. Make sure the gateway is correctly entered - even if you don't have one.

    I recently had to debug a job where the n/w was flaky - studio wouldn't stay connected, the panel wouldn't stay connected properly etc. Debug revealed that the gateway address field was incorrectly set and was indeed the root of the problem.

    In this job there is no network gateway, but, this address must still be set on the same subnet as the master. It gets very upset if it's not. You will see from the attached image, line 82 shows a UDP error 65 - this is directly related to this issue.

    Hope this helps
Sign In or Register to comment.