TPcontrol connection issue
andrewsmc
Posts: 7
Im having a problem with a nx3200 running the latest firmware, When a iPad connects it comes online then almost straight away goes offline. In the diagnostic window i get a load of messages one saying something along the lines of "could not open outside port" and the other says "Ethernet port might not be available" any idears what could cause this and a fix. Netlinxs can connect fine.
I have tested it with simple code just one button event that sends a beep and same problem.
I have tested it with simple code just one button event that sends a beep and same problem.
0
Comments
Paul
At sites where it is seen often, we generally schedule a 3AM reboot once a week, and never see the problem again.
We are also doing what we can in our code to never open an IP connection that isn't actually in use or doesn't need reopening.
This does NOT address Andrew's issue... which appears to be ALL THE TIME.
For that, I would suggest substitution of an AMX panel for the iPad and seeing if it changes the results.
What is your security configuration on the NX-3200 in particular with respect to device connections to the master? I ran into a problem where the User ID used for TPControl authentication to the master did not have sufficient permissions in order to perform the functions required by TPControl. Initially, I used the same User ID for Modero touchpanels but that User ID did not have sufficient permission. I narrowed down the permission set required by then changing TPControl devices to use a User ID with *all* permissions and this worked. I then experimented until I found the minimum set of permissions required for TPControl. This may not be your problem but your symptoms and what you are seeing in Diagnostics are very similar to what I saw when I ran into the permission problem testing TPControl with my NX processors. Note also that in the TPControl setup for a device where you specify the User ID/password, there is a checkbox for ICSP Encryption. This box must be checked if authentication is required since TPControl interprets this checkbox as an authentication/encryption flag. If you do not use encryption but you use authentication, this box must be checked. Initially I did not select the checkbox although I specified a User ID/password since I did not require encryption but without the checkbox selected, TPControl would not authenticate the device User ID to the NX master.