When I start the NCD Base application to configure 2 new modules a fault window pops up with the message
“An attempts was made to access a socket in a way forbidden by its access permissions.”
If I click on OK the app closes. If I ignore the message, I can connect to the devices.
The 2 devices do not seem to be paired?
They have static addresses on the same network.
PS C:\Users\Michael> ping 10.223.1.110
Pinging 10.223.1.110 with 32 bytes of data:
Reply from 10.223.1.110: bytes=32 time<1ms TTL=128
Reply from 10.223.1.110: bytes=32 time<1ms TTL=128
Reply from 10.223.1.110: bytes=32 time<1ms TTL=128
Reply from 10.223.1.110: bytes=32 time<1ms TTL=128
Ping statistics for 10.223.1.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS C:\Users\Michael> ping 10.223.1.111
Pinging 10.223.1.111 with 32 bytes of data:
Reply from 10.223.1.111: bytes=32 time<1ms TTL=128
Reply from 10.223.1.111: bytes=32 time<1ms TTL=128
Reply from 10.223.1.111: bytes=32 time<1ms TTL=128
Reply from 10.223.1.111: bytes=32 time<1ms TTL=128
Ping statistics for 10.223.1.111:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS C:\Users\Michael>
I tried the MXNET / MCNET Device Pairing Utility - no devices show up…
Both on same network and reachable
PS C:\Users\Michael> ping 10.223.1.110
Pinging 10.223.1.110 with 32 bytes of data:
Reply from 10.223.1.110: bytes=32 time<1ms TTL=128
Reply from 10.223.1.110: bytes=32 time<1ms TTL=128
Reply from 10.223.1.110: bytes=32 time<1ms TTL=128
Reply from 10.223.1.110: bytes=32 time<1ms TTL=128
Ping statistics for 10.223.1.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS C:\Users\Michael> ping 10.223.1.111
Pinging 10.223.1.111 with 32 bytes of data:
Reply from 10.223.1.111: bytes=32 time<1ms TTL=128
Reply from 10.223.1.111: bytes=32 time<1ms TTL=128
Reply from 10.223.1.111: bytes=32 time<1ms TTL=128
Reply from 10.223.1.111: bytes=32 time<1ms TTL=128
Ping statistics for 10.223.1.111:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS C:\Users\Michael>
Hi,
I would recommend following the instructions in this guide:
If you have any questions on this please let us know.
Thank you,
Travis Elliott
Working - just ther baud rate that was wrong. I had not touched it from the default.
What about the message that comes up when NCD Base is started?
“An attempt to access a socket in a way forbidden by its access permissions” ?
If I ignore it - App seems to work, if I click on OK the app closes.
We can check into that. I would say it has to do with establishing a raw TCP socket over port 2101. My guess is user permissions on the PC you are using blocks this type of communication. I would assume this is a PC configured by a Corporate IT department. If you run NCD Base Station as an administrator you more than likely would not see the problem.
I have an additional question. I gor the plastic cases from Relay Pros - are there exposed points so that externally visible LEDs (connection, relay state) could be connected?
I.E. - to verify that the devices are connected, and the status of the relays.
These are simple, generic, electronics enclosures the boards are profiled to fit inside. All holes must be drilled manually.
Thank you,
Travis Elliott
