Can’t connect to Panel using Ness aComms

If you are finding the app won’t connect to your Ness D8x/D16x panel, then the following below may help..

If your Android device can’t connect to your panel then a connection issue message will appear in the app.
This is telling you that the app can’t connect using the settings you have set in the app.

A few things to check:

1. Programming locations in Panel.
Make sure the following locations are enabled in your panel otherwise the app will not be able to communicate to your D8x/D16x panel:

(You must be in installer programming mode to set these options)
P 199 E
1E ON: Send Address.
2E ON: Send Time Stamp
3E ON: Send Alarms.
4E ON: Send Warnings.
5E ON: Send Access Events.
6E ON: Zone Seal State
7E ON: Send Test ASCII String

2. IP and Port Connection Settings
Ensure you have used the correct IP (or hostname) and Port.
Before trying to get it working over the internet try and get it working on a local Wi-Fi network.

The Local IP and Port is only used while on a Wi-Fi connection.
If you have not entered in a remote IP and port during the setup then the app will automatically put in the Local IP and port into the remote IP and port section since it was left blank during the setup.

The Remote IP and port will only be used while your Android device is on a 3G/4G connection.
If you are using a Hostname rather then a IP then make sure that your Android device hasn’t auto corrected the word you where trying to type. Many devices have a spell check and will change the word as it thinks that you have spelt it wrong.

3. IP232 Module Settings
Make sure the IP232 Module is plugged into your D8x/D16x panel and ensure that a Static IP is set into this module.
If a Dynamic (or DHCP) is enabled then the IP may automatically change in a few days/weeks making it so that you can no longer connect to the panel so you need to set the IP as a static IP.

Check and make sure that the IP232 module has the baud rate set to 9600. If it’s set to any other value then the app will not work.

Ensure your IP232 module has a valid gateway set. Not having a valid gateway set may stop it from connecting to the internet for remote connection. Normally you can set this as your router, but we recommend you contact your network administrator or ISP for the correct settings.

4. Port Forwarding
If you are able to connect using your Local Wi-Fi but can’t connect using 3G/4G then the port maybe not open in your router.
The port you set in the IP232 Module must be port forwarded in the router as well.

Unfortunately we are unable to help you setup port forwarding as there are many different routers and devices and we are unable to learn each and everyone of them. However you may want to visit as it will provide you with many step-by-step guides on how to port forward otherwise contact your ISP and they should be able to guide you with the steps on how to port forward.

The IP and Port you need to port forward is the one listed in your IP232 Module. Ensure that your IP232 module has a static IP and not a DHCP IP.

5. Power Cycle
Doing a simple power cycle may fix your issue. Simply power down the IP232 module, wait for 10 seconds and power it back up.

Now you will need to wait approx. 30 seconds for it to full power up and then re-open the app and try and see if it connects.